[mitk-users] TextOverlay3D updates one frame later

2019-06-17 Thread Daniel Maleike
Hi everybody, I have a question regarding mitk::TextAnnotation3D. As far as I can see, this replaces mitk::TextOverlay3D from the 2016.11 release. I am just modifying a custom mapper to use TextAnnotation3D instead of TextOverlay3D. I took orientation from documentation and

[mitk-users] Segmentation of a specific ROI

2019-06-17 Thread B J
Dear All, I am a new MITK user. I have loaded DICOM CT images into MITK tool. I want to define a volume that will occupied by ROI in which I will make an organ segmentation. However, I can find any way to do that. Can you give me any suggestion. Thanks, Regards. Jaafar.

Re: [mitk-users] Help building mitk superbuild 64 bit in wimdows

2019-06-17 Thread Pruthvesh Pipaliya
Hello, Thankyou for your reply. I tried multiple times before with CMake 3.15 and I am quite sure about my selection of x64. As you mentioned you also didn't tested CMake 3.15, I uninstalled it and installed CMake 3.13.5. After this I again generated project and now its compiling. I am newbie

Re: [mitk-users] Segmentation of a specific ROI

2019-06-17 Thread Dinkelacker, Stefan
Hi Jaafar, welcome to the MITK community. To crop an image you could use the Image Cropper plugin for example. It is the kind of box-shaped icon in the General toolbar. You also have the option to roughly pre-segment your structure of interest and right-click on your segmentation in the Data

Re: [mitk-users] Help building mitk superbuild 64 bit in wimdows

2019-06-17 Thread Pierre-Yves Menguy
Hello, New versions of CMake (I have 3.14.4) doesn't make the distinction between 32 and 64 bits in the list, probably to avoid clutter (32, 64, arm 32, arm 64 for each generator). It is now an option in the second dropdown "Optional platform for generator". Regards, Pierre-Yves Le lun. 17 juin

Re: [mitk-users] org.mitk.gui.qt.python plugin fails to run on Windows

2019-06-17 Thread Alex Lisovich
Dear All, Sorry for a long post, but here it goes: For the last few days I was trying to compile/run the org.mitk.gui.qt.python Python pligin. Basically, it compiles just fine, but when trying to load (both in Release and Debug mode) it generates (and displays instead of Python console) the

[mitk-users] Help building mitk superbuild 64 bit in wimdows

2019-06-17 Thread Pruthvesh Pipaliya
Hello All, I am trying to build mitk on windows platform in 64 bit. I am getting below error for all project, please help me out. *Error : *fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64' My current configuration of platform is as follows, 1) On what

Re: [mitk-users] Help building mitk superbuild 64 bit in wimdows

2019-06-17 Thread Dinkelacker, Stefan
Hi, please make sure you chose the right CMake generator which is something like “Visual Studio 15 2017 *Win64*” or in case of Visual Studio 2019 64 bit should be automatically set for you. We also recommend to use the release version of the code (tag v2018.04.2) instead of the latest master

Re: [mitk-users] Unable to open DICOM file - Help required

2019-06-17 Thread Stein, Tobias
Hi Selva, this is a legitimate question. In fact you should either open just one of the DICOM files and all others in the folder will be recognized or use the DICOM Browser Plugin within the Icon-Bar on the top. With this browser you can go with the „Import“-Tab and choose „Scan directory“

Re: [mitk-users] Not all plugins

2019-06-17 Thread Dinkelacker, Stefan
Hi Nil, switching them on in CMake and regenerating should be enough. If they do not appear in VS, please try a clean rebuild. It never happened to me and it could be related to some customizations maybe. It is also worth mentioning the CMake/BuildConfigurations directory. Just have a look at

Re: [mitk-users] Unable to open DICOM file - Help required

2019-06-17 Thread Dinkelacker, Stefan
Hi Selva, DICOM images typically are 3d or 4d volumes stored as separate slices in a directory. As it is not always easy to see which files/slices belong together our DICOM readers use a quite sophisticated heuristic to rebuild a correct volume out of these slice files. Therefore it scans all