Hi,

thanks for the explanation. If I understand you right, the MITK can 
display a multimodality image (e.g. PET/CT) with one color-mapped image 
(e.g. PET) over a black-white background image (e.g. CT) in slice 
windows. Is it possible only in a "developer mode" or there exists more 
user-friendly way for doing that?

Best,
Urban

On 14.1.2014 13:45, Sascha Zelzer wrote:
> Hi,
>
> On 01/12/2014 10:58 PM, Urban Simoncic wrote:
>> Hi,
>>
>> first I would like to thanks Caspar and Sascha for the response. Of
>> course I do not expect to get unbiased opinion here, but I know the
>> "conflict of interests", so your thoughts are still valuable for me.
>>
>> I have done some comparisons of MITK and Slicer, but I am not
>> experienced user of any, so my conclusions might be affected by the
>> insufficient knowledge of these tools. In MITK I like the way how data
>> is displayed in Data Manager and in different view windows that are
>> cnnected. However, it seems that MITK is more suited for working on
>> single image at time, while the slicer is better suited to work with
>> different (possibly multimodality) images concurrently.
> The MITK Workbench (and Slicer as well, AFAIK) do not restrict the 
> user in the amount of loaded/displayed data sets. At the MITK toolkit 
> or application framework level, developers also have a much higher 
> degree of freedom for combining and displaying images (concurrently) 
> in different render windows.
>
>>
>> To confirm/reject my findings, I would like to know:
>> - Is MITK Workbench able to concurrently display different images (e.g.
>> multiple non-registered images of the same patient, acquired at
>> different time point) in different slice windows?
> The MITK Workbench internally uses a single "data storage" which 
> contains the scene for the default render windows. Each render window 
> (e.g. each of the four render windows in the "default render window 
> editor" - the main control displaying the data) uses this data storage 
> and by default display the complete scene. In the MITK Workbench under 
> the "Preferences" dialog, there is an option to enable a "developer 
> mode" for "Properties". With this mode enabled, The "Properties" view 
> in the MITK Workbench allows you to override specific properties (like 
> "visible") for specific render windows. Admittedly, this not an 
> end-user feature and a little cumbersome to work with.
>
> For special applications, developers usually create their own render 
> window editor and control visibility or similar properties in their 
> plug-ins.
>
>> - Is MITK Workbench able to display multimodality images (e.g.
>> color-mapped PET over black-white CT) in slice windows?
> Yes, this one of the main requirements of the toolkit / Workbench.
>
>> - If not, at what coding level this could be implemented; just at the
>> "MITK toolkit" or also at the "application platform" level?
> Actually both. For maximum re-usability of existing code, people often 
> create plug-ins for the MITK Workbench.
>
> Best,
> Sascha
>
>> Best Regards,
>> Urban
>>
>> On 10.1.2014 16:09, Sascha Zelzer wrote:
>>> Hi Urban,
>>>
>>> welcome to MITK!
>>>
>>> Disclaimer: I am one of the main MITK developers and know a few things
>>> about the Slicer architecture as well. I didn't use the Slicer
>>> end-user application extensively, though. We keep a friendly and
>>> collaborative atmosphere and meet regularly on various events. I try
>>> my best to be objective in the following statements.
>>>
>>> Both Slicer and MITK have a long history in the medical imaging
>>> community and are well known international toolkits / applications
>>> with a large user base.
>>>
>>> MITK positions itself as a multi-layered software platform (written in
>>> C++) with a focus on modularity and extensibility.
>>>
>>> It can be used as a traditional toolkit (aka using C++ shared
>>> libraries) which basically extends ITK and VTK. Many projects use MITK
>>> as a toolkit and build complete custom applications on top of it.
>>> Second, it provides an *application platform* on top of the toolkit
>>> for creating your own modular application. This is mostly used in
>>> mid-sized to large groups which need to deploy a modular application
>>> with custom plug-ins but which re-uses a configurable set of existing
>>> MITK functionality. Third, MITK provides an end-user application,
>>> called the MITK Workbench which is based on the application platform
>>> and aims to be an extensible and easy to use imaging platform,
>>> providing the most commonly needed functionality. Many groups also
>>> take the MITK Workbench and just add their own plug-ins to extend its
>>> functionality.
>>>
>>> The architecture of 3DSlicer is highly modular as well. As an
>>> out-of-the-box end-user application, Slicer contains many specialized
>>> imaging algorithms, allowing a wide range of research on existing
>>> imaging data without having to program your own plug-in. It can also
>>> be extended with different kind of "plug-ins". Some type of plug-ins
>>> can even be shared between an MITK application and 3DSlicer (so called
>>> CLI modules). In the end-user application, Slicer definitely contains
>>> more algorithms contributed by a multitude of plug-ins, whereas the
>>> MITK Workbench focuses on the basics and end-user usability. If you
>>> are into Python programming, Slicer also offers quite a few
>>> possibilities to either create Python plug-ins as CLIs or script
>>> Slicer functionality via Python. MITK provides some experimental
>>> Python scripting support for the Core library, but it is not as
>>> exhaustive as the Slice Python support.
>>>
>>> If you are into building your own (C++) applications instead of using
>>> the provided end-user applications, MITK offers a lot of possibilities
>>> and flexibility. While you could probably use Slicer in that context
>>> as well, I am not aware of any projects using Slicer except for
>>> plug-in development for the existing 3DSlicer application (please tell
>>> me if you know any!). Further, MITK at its Core (toolkit level)
>>> depends only on VTK and ITK and has no GUI or Qt dependency. Slicer
>>> depends on Qt throughout its code-base.
>>>
>>> Regarding the documentation, Caspar already provided some useful
>>> links. We try to provide extensive documentation for the API as well
>>> as user documentation. However, documentation is never finished and
>>> there is always room for improvements.
>>>
>>> No matter what you decide to use, we are always interested in the
>>> outcome of such evaluations and what your decision process looked like!
>>>
>>> Best,
>>> Sascha
>>>
>>>
>>> On 01/08/2014 12:57 PM, Urban Simoncic wrote:
>>>> Dear MITK users,
>>>>
>>>> I am looking for the software platform that I can use for the
>>>> development of tool for medical image processing and visualization. 
>>>> MITK
>>>> appears to be one good candidate. Another candidate is Slicer, which
>>>> appears to be very similar tool as the MITK.
>>>>
>>>> I would appreciate if anyone could explain me the differences between
>>>> these two tools. I am interested especially in the modularity of the
>>>> software and in the quality of the documentation, but any other 
>>>> thoughts
>>>> are welcome.
>>>>
>>>> Thanks,
>>>> Urban
>>>>
>>>> ------------------------------------------------------------------------------
>>>>  
>>>>
>>>>
>>>> Rapidly troubleshoot problems before they affect your business. 
>>>> Most IT
>>>> organizations don't have a clear picture of how application 
>>>> performance
>>>> affects their revenue. With AppDynamics, you get 100% visibility into
>>>> your
>>>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
>>>> AppDynamics Pro!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>>>>  
>>>>
>>>>
>>>> _______________________________________________
>>>> mitk-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/mitk-users
>>>
>
>


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to