Hi David,
1) Don’t worry about it, if it starts you do not need to do anything. This
is an issue with NSIS and a long PATH variable. I have opened a ticket for it
and will look into getting rid of the warning:
https://phabricator.mitk.org/T22509
2) Some other users have encountered slow dicom loading before
(https://sourceforge.net/p/mitk/mailman/message/35612118/) however, we could
never reproduce it on our end and it seems hardware dependent
3) We have not heard about slow segmentation UI before. Considering you
are using a relatively powerful PC, is it possible that MITK is running in a
sandbox or otherwise impacted by antivirus software or similar? Did you use
older version of the Workbench before without those issues? How big is your
dataset?
Best,
Caspar
Von: David Channnin [mailto:[email protected]]
Gesendet: Donnerstag, 9. Februar 2017 19:06
An: [email protected]
Betreff: [mitk-users] Newbie help
Hello!
I just downloaded MITK Workbench 2016.11 on a Windows 10 PC (Intel Core
[email protected]<mailto:[email protected]> GHz, 32 GB RAM) and I have two issues:
1) During install, the wizard gave an error about not being able to configure
the system path because (apparently) my system path is too long. I want to fix
this but I do not know what the MITK path value(s) should be. Any ideas?
2) The system is unusably slow...6 minutes to import a single DICOM series from
disk (images load instantly in another DICOM tool). Segmentation tools UI do
not respond in real time. Any suggestions?
Thank you,
Dave
David S. Channin MD
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
