View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002406Slicer4Module DICOMpublic2012-08-16 14:582012-08-22 05:49
Reporterfedorov Assigned Topieper  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.2.0 
Summary0002406: DICOM module not usable first time Slicer is run on fresh Slicer install
Description

When I start Slicer from binary package for the first time with
~/.config directory erased, I am not able to pop up the DICOM browser
window. Python console shows this error:

Traceback (most recent call last):
File "/Applications/Slicer.app/Contents/lib/Slicer-4.1/qt-scripted-modules/DICOM.py",
line 191, in setup
self.setDatabasePrecacheTags()
File "/Applications/Slicer.app/Contents/lib/Slicer-4.1/qt-scripted-modules/DICOM.py",
line 285, in setDatabasePrecacheTags
tagsToPrecache = list(slicer.dicomDatabase.tagsToPrecache)
AttributeError: 'NoneType' object has no attribute 'tagsToPrecache'
Traceback (most recent call last):
File "/Applications/Slicer.app/Contents/lib/Slicer-4.1/qt-scripted-modules/DICOM.py",
line 125, in enter
self.detailsPopup.open()
AttributeError: DICOMWidget instance has no attribute 'detailsPopup'

If I quit and start again, I am being prompted to initialize the
database directory and DICOM browser shows up.

Tested on Mac, not sure what is the behavior on other platforms.

TagsNo tags attached.

Relationships

related to 0001969 closedpieper can't import dicom images 

Activities

Lchauvin

Lchauvin

2012-08-20 11:57

developer   ~0005629

I had this issue after updating with Github source code (commit 5d50eb24df0933d9c310a923fef0bf94c1a843ce) and building Slicer (Slicer-build).

This issue disappeared when I fully recompiled Slicer (Slicer4-Superbuild).

I hope this could help to solve this issue.
fedorov

fedorov

2012-08-20 11:59

developer   ~0005630

I have this issue with Slicer installed from nightly binary build both on Linux and Mac, so it's unrelated to build process.
Lchauvin

Lchauvin

2012-08-20 12:07

developer   ~0005631

Could it be how the binary has been generated ? Without updating full Slicer (only building Slicer-build) ?
pieper

pieper

2012-08-22 04:36

administrator   ~0005676

Fixed in revision 20810

Issue History

Date Modified Username Field Change
2012-08-16 14:58 fedorov New Issue
2012-08-16 14:58 fedorov Status new => assigned
2012-08-16 14:58 fedorov Assigned To => pieper
2012-08-20 09:54 pieper Target Version => Slicer 4.2.0 - Feature freeze Sept 1st 2012
2012-08-20 11:57 Lchauvin Note Added: 0005629
2012-08-20 11:59 fedorov Note Added: 0005630
2012-08-20 12:07 Lchauvin Note Added: 0005631
2012-08-22 04:36 pieper Note Added: 0005676
2012-08-22 04:36 pieper Status assigned => resolved
2012-08-22 04:36 pieper Resolution open => fixed
2012-08-22 04:57 pieper Relationship added related to 0001969
2012-08-22 05:49 fedorov Status resolved => closed
2012-08-22 05:49 fedorov Fixed in Version => Slicer 4.2.0 - Feature freeze Sept 1st 2012