View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004372Slicer4Module DICOMpublic2017-05-11 15:192017-07-25 00:55
Reporterkirimliezgi Assigned Topieper  
PriorityhighSeveritycrashReproducibilityN/A
Status closedResolutionfixed 
Product VersionSlicer 4.6.1 
Target VersionFixed in VersionSlicer 4.7.0 
Summary0004372: Issues with loading DCE DICOM MRI files
Description

I have a T1 axial contrasted MRI image datasets. I` d like to load it into Slicer 4.6.2 but it gives the error you can see in the log file below. I used the DICOM module, also DATA load options to load the images. Also I have some DCE MRI images But the software crashes whenever I try to load those DCE folders, which contain 1400 DICOM files in each.

TagsNo tags attached.

Activities

kirimliezgi

kirimliezgi

2017-05-11 15:19

reporter  

DEBUG_log.docx (180,483 bytes)
pieper

pieper

2017-05-11 16:36

administrator   ~0014479

Hi -

Please try the latest nightly and follow the suggestions on the FAQ:

https://www.slicer.org/wiki/Documentation/Nightly/FAQ/DICOM

If that doesn't work, please start a discussion at http://discourse.slicer.org. Chances are that there is a plugin or something to work with your data.

-Steve
kirimliezgi

kirimliezgi

2017-05-15 14:35

reporter   ~0014484

Hi,

I tried your suggestion but it did not work. Before starting a discussion I want to be sure that my data can be viewed in Slicer. I saw that saying If you share the data (e.g., upload it to Dropbox and add the link to the error report) then Slicer developers can reproduce and fix the problem faster. So I`d like to share my data here in this link : https://mdacc.box.com/s/avfmvczlbc6oksevtsxg3obbzo5lg3fd

Could you check it?

Thanks,
Ezgi
pieper

pieper

2017-05-18 21:30

administrator   ~0014487

Hi -

Box says the data has been deleted or isn't available to me.

Is this the same issue you are working on with Andrey?

https://discourse.slicer.org/t/error-with-dce-mri-loading-in-dicom-browser/327/17

If so, can you post a link to this bug report in the discourse topic and then if Andrey (or someone) figures out the fix we can close this bug report.

Thanks,
Steve
lassoan

lassoan

2017-07-25 00:55

developer   ~0014959

No response from the reporter, assuming it was the same issue that was discussed and fixed.

Issue History

Date Modified Username Field Change
2017-05-11 15:19 kirimliezgi New Issue
2017-05-11 15:19 kirimliezgi Status new => assigned
2017-05-11 15:19 kirimliezgi Assigned To => pieper
2017-05-11 15:19 kirimliezgi File Added: DEBUG_log.docx
2017-05-11 16:36 pieper Note Added: 0014479
2017-05-11 16:36 pieper Status assigned => feedback
2017-05-15 14:35 kirimliezgi Note Added: 0014484
2017-05-15 14:35 kirimliezgi Status feedback => assigned
2017-05-18 21:30 pieper Note Added: 0014487
2017-07-25 00:55 lassoan Status assigned => closed
2017-07-25 00:55 lassoan Resolution open => fixed
2017-07-25 00:55 lassoan Fixed in Version => Slicer 4.7.0
2017-07-25 00:55 lassoan Note Added: 0014959