View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003801Slicer4Module DICOMpublic2014-08-14 08:562014-08-19 04:20
Reporterpolony Assigned Topieper  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Product VersionSlicer 4.3.1-2 
Target VersionFixed in VersionSlicer 4.4.0 
Summary0003801: Slicer does not recognise DICOM orientation in new update
Description

I have been using Slicer 4.2.1 for some time. It reads in the tag Pixel Spacing (0028,0030) in order to reconstruct the slice data in a ultrasound volume. I had to uninstall 4.3.1 and revert to 4.2.1 because of this problem

TagsNo tags attached.

Activities

pieper

pieper

2014-08-14 16:24

administrator   ~0012373

Can you try the nightly build of slicer to see if the issue is fixed? There was an issue with specific US dataset that was fixed at the ITK level and that may have been after the release.

If that doesn't fix it, by any chance to do you have an anonymized file that can be used to replicate the issue? We do a lot of DICOM reading and the spacing is fine in general.
polony

polony

2014-08-19 02:50

reporter   ~0012397

I installed the nightly build version which has resolved problem I was having.

The programme (4.2.1) would also occasionally crash when loading the datasets I was working with. Nightly build version 4.3.1 seems resilient to crashing
pieper

pieper

2014-08-19 04:20

administrator   ~0012398

Excellent - thanks for reporting and following up.

Issue History

Date Modified Username Field Change
2014-08-14 08:56 polony New Issue
2014-08-14 08:56 polony Status new => assigned
2014-08-14 08:56 polony Assigned To => pieper
2014-08-14 16:24 pieper Note Added: 0012373
2014-08-19 02:50 polony Note Added: 0012397
2014-08-19 04:20 pieper Note Added: 0012398
2014-08-19 04:20 pieper Status assigned => closed
2014-08-19 04:20 pieper Resolution open => fixed
2014-08-19 04:20 pieper Fixed in Version => Slicer 4.4.0