Hi Arpit,
Do you have a screenshot of how this looks? This seems like a simple
solution for the simple case where you are just dealing with a line.
Although it seems like you'd also want to set the "Pointset.2D.distance to
plane" property to something large so that the entire line is always
projected onto the plane, no? For the case where you want a surface (e.g.
an instrument CAD model) projected onto the plane, a more complete solution
is required.
Taylor
On Wed, Jan 28, 2015 at 8:41 AM, Arpit Paliwal <arpit.pali...@gmail.com>
wrote:
> Dear Alfred & Taylor,
>
> Thanks for your replies.
>
> I am a beginner to MITK so am still learning various concepts. I tried few
> patchy solutions in last few days & one of the solution somehow just
> worked.
>
> I used Pointset contours. All the projections in orthogonal planes were
> coming properly (currently I am only working with Orthogonal planes)
>
> Following is the code.
>
> mitk::PointSet::Pointer m_pointer_line = mitk::PointSet::New();
> mitk::PointSet::PointType start,end;
>
> start[0] = 0.0;
> start[1] = 0.0;
> start[2] = 0.0;
>
> end[0] = 50;
> end[1] = 0;
> end[2] = 0;
>
> m_pointer_line->InsertPoint(0,start);
> m_pointer_line->InsertPoint(1,end);
>
> mitk::DataNode::Pointer lineNode = mitk::DataNode::New();
> lineNode->SetData(m_pointer_line);
> lineNode->SetName("Pointer");
> lineNode->SetBoolProperty("show points", false);
> lineNode->SetBoolProperty("show contour", true);
> lineNode->SetBoolProperty("updateDataOnRender", false);
> lineNode->SetFloatProperty("contoursize", 1.0);
> lineNode->SetIntProperty("line width", 3);
> lineNode->SetProperty("contourcolor",
> mitk::ColorProperty::New(1.0,0.0,0.0));
>
> m_standalone_datastorage->Add(lineNode);
> // m_visualizer is
> mitk::NavigationDataObjectVisualizationFilter::Pointer
> // m_pointer_pos_relative_img is navigation data
> m_visualizer->SetInput(0, m_pointer_pos_relative_img);
> m_visualizer->SetRepresentationObject(0, m_pointer_line);
>
> Please let me know if this acceptable way to do it.
>
> Best Regards,
> Arpit
>
> On Wed, Jan 28, 2015 at 3:16 AM, Taylor Braun-Jones <
> tay...@braun-jones.org> wrote:
>
>> There are two ways to always visualize the tool in the slicing plane:
>>
>> (1) Use an orthogonal plane and project the tool onto that plane. This is
>> what Alfred describes. I have a custom mapper that does this, but I'd need
>> to get permission to share it.
>>
>> (2) Use an oblique plane that is tilted to be inline the tools axis. Some
>> products call these oblique planes "Axial Oblique" and "Sagittal Oblique".
>> Other products use terms like "Inline Axial" and "Inline Sagittal". Arpit,
>> if I understand you correctly, I think this is what you are looking for.
>>
>> Bug 15777[1] is meant to implement (2) and has been waiting on me to
>> update my pull request - which I have finally done just now. Arpit, maybe
>> this will get integrated and added as a feature in MITK Workbench so that
>> you can test it out and see if it does what you're looking for.
>>
>> Regards,
>> Taylor
>>
>> [1] http://bugs.mitk.org/show_bug.cgi?id=15777
>>
>> On Tue, Jan 27, 2015 at 9:28 AM, Alfred Franz <a.fr...@dkfz-heidelberg.de
>> > wrote:
>>
>>> Dear Arpit,
>>>
>>> for this purpose you would need to project the tool onto the 2D image
>>> plane. This could be done by a (new) image filter. To my knowledge,
>>> unfortunately, there is no such image filter in MITK at the moment. But
>>> such a feature would be very nice for the IGT module we thought about it a
>>> number of times too. A good starting point to implement such a filter might
>>> be the mitk::NeedleProjectionFilter from the ultrasound module. It only
>>> projects a point at the moment (see the screenshot attached to this mail),
>>> but maybe it can be extended to your needs. If you have time to do so, we
>>> would appreciate contributing this to MITK.
>>>
>>> Regards,
>>>
>>> Alfred
>>>
>>>
>>>
>>> Am 20.01.2015 05:10, schrieb Arpit Paliwal:
>>>
>>> Thanks Ingmar for your quick reply.
>>>
>>> I would like to visualize the axis of the tool. This will help in
>>> displaying direction of the tool in surgery while following a defined
>>> trajectory.
>>> I have attached an example with the mail. Yellow line shows the
>>> trajectory & green line shows the location of tool.
>>>
>>> Best Regards,
>>> Arpit
>>>
>>>
>>> On Tue, Jan 20, 2015 at 4:18 AM, Ingmar Wegner <iweg...@gmx.de> wrote:
>>>
>>>> Hi Arpit,
>>>> that looks like a regular setup of 2D and 3D widgets to me. What do you
>>>> want to visualize?
>>>>
>>>> The widgets are setup by default to show 3 x 2D (sliced) and 1 x 3D
>>>> widgets. So in the 2D views the tool is sliced as well.
>>>>
>>>> You can easily change the rendering mode of a widget from 2D to 3D. But
>>>> then you end up with a scene similar to your lower right widget (yellow
>>>> boarder).
>>>> So what do you want to show?
>>>>
>>>> Regards,
>>>> Ingmar
>>>>
>>>>
>>>>
>>>>
>>>> Arpit Paliwal <arpit.pali...@gmail.com>schrieb:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I am facing problem with the visualization of navigation tool.
>>>>>
>>>>> I am using NavigationDataObjectVisualizationFilter to connect STL
>>>>> data with pointer tool navigation data.
>>>>>
>>>>> I am getting pointer tip visible in all the views but not the
>>>>> compete tool. It seems like the portion of pointer in the slice is only
>>>>> visible. If I align the pointer parallel to any of Axial/ Sagittal/
>>>>> Coronal
>>>>> plane then I see the almost all portion of the pointer. Even if I hide
>>>>> the
>>>>> image I still get the same visualization of the pointer in all the views.
>>>>>
>>>>> How can I visualize the complete geometry of the tool instead of
>>>>> sliced portion? I have attached file for your reference.
>>>>> [image: Inline image 2]
>>>>>
>>>>>
>>>>> Best Regards,
>>>>> Arpit
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>>>> Higher
>>>>> redundancy.Lower latency.Increased capacity.Completely compliant.
>>>>> http://p.sf.net/sfu/gigenet_______________________________________________
>>>>> mitk-users mailing list mitk-users@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/mitk-users
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming. The Go Parallel Website,
>>> sponsored by Intel and developed in partnership with Slashdot Media, is
>>> your
>>> hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials and more. Take
>>> a
>>> look and join the conversation now. http://goparallel.sourceforge.net/
>>> _______________________________________________
>>> mitk-users mailing list
>>> mitk-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/mitk-users
>>>
>>>
>>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users
