I am currently trying to import a DICOM file into the program through “Import DICOM files from directory”. Once I have located the file and clicked “Import” the above image appears. This is my first time using the software. Any help is appreciated.
Can you check the folder chosen as location for your DICOM database is writeable?
Can you import some public DICOM dataset that is known to work? (for example, you can try importing the files from this directory and see if you still have the crash)
Can you try applying DICOMPatcher to your DICOM dataset before trying to import it?
Thank you for your reply and suggestion. I downloaded the Preview Release and dragged the folder in, but nothing appears. It also says no valid DICOM database found in folder.
I think this will come up more and more as that message is really quite obscure. I still propose to disable out the import tab until database initialized (or auto create the database first time DICOM module is run).
You can find messages about why file s are not imported in the application log (menu: Help / Report a bug). Could you upload it somewhere and post the link here?
I’ve implemented automatic creation now: if no valid database is available when user drag-and-drops a folder or clicks the import button then a new database is created with default settings. If it fails (e.g., because Slicer cannot find a writeable folder) then an error message is displayed and the user is instructed to resolve the error using options shown in DICOM browser. This will be available in Slicer Preview Releases from tomorrow.
Thank you for your replies and suggestions. I do have another one:
So I downloaded 3D Slicer onto two other workstations to see if it was going to be a recurring problem. When I drag-and-drop the files in, the images load fine (the DICOM browser window displays the correct BodyPartExamined - which for me is Abd; unlike previously where it would say HeadNeck for the same data set). Are there any suggestions as to why this is and how it can be fixed? (I can post this separately if need be)
From this much information we cannot even guess what behavior you see on your computers and why.
If you find that on any computer the latest Slicer Preview Release does not load any DICOM data correctly then send us anonymized/animal/phantom sample data (preferred) or at least send the application log of DICOM import and loading (menu: Help / Report a bug).
It seems that the database could not be created at the default location, because it was a virtual/network drive. Change the database location to a local folder that your user has write access to. It can even be a folder used for temporary files.
If you download today’s Slicer Preview Release then you should get an informative error popup about what is wrong and what you should do to fix it.