View Issue Details

IDProjectCategoryView StatusLast Update
0004015Slicer4Module DICOMpublic2015-08-03 14:05
Reportertjdett Assigned Topieper  
Status acknowledgedResolutionopen 
Product VersionSlicer 4.4.0 
Target VersionFixed in Version 
Summary0004015: DICOM browser fails to launch if $HOME/Documents does not exist

On first run, after clicking "Load DICOM Data", a window pops up reading:

DICOM Database will be stored in


Use the Local Database button in the DICOM Browser to pick a different location.

After clicking OK, the following error is output to the console:

PythonQt: QObject::connect() signal 'valueChanged(double)' does not exist on QWidget
Traceback (most recent call last):
  File "/opt/slicer/lib/Slicer-4.4/qt-scripted-modules/", line 254, in setup
  File "/opt/slicer/lib/Slicer-4.4/qt-scripted-modules/", line 411, in promptForDatabaseDirectory
OSError: [Errno 2] No such file or directory: '/home/researcher/Documents/SlicerDICOMDatabase'
Traceback (most recent call last):
  File "/opt/slicer/lib/Slicer-4.4/qt-scripted-modules/", line 191, in enter
AttributeError: DICOMWidget instance has no attribute 'detailsPopup'

Because the parent directory ($HOME/Documents) does not exist, os.mkdir(databaseDirectory) will fail, as it is not recursive. os.makedirs(databaseDirectory) may be a better choice.

Additional Information

In trunk this code is located in Modules/Scripted/DICOMLib/ rather than Modules/Scripted/DICOM/

TagsNo tags attached.


related to 0004022 resolvedpieper Default DICOM database directory might not be writable 




2015-08-03 14:05

administrator   ~0013209

I guess this makes sense - another option might be to use the home directory itself or maybe prompt the user to select something.

Since we are using the Qt call to get the location it's odd to me that it doesn't exist:

But I guess we need to handle that case explicitly.

Issue History

Date Modified Username Field Change
2015-07-08 17:02 tjdett New Issue
2015-07-08 17:02 tjdett Status new => assigned
2015-07-08 17:02 tjdett Assigned To => pieper
2015-07-17 05:27 pieper Relationship added related to 0004022
2015-08-03 14:05 pieper Note Added: 0013209
2015-08-03 14:05 pieper Status assigned => acknowledged