Opened 2 years ago
Closed 2 years ago
#8989 closed defect (fixed)
TCIA 1.3.6.1.4.1.9328.50.17.177679383028944381508162168149189677080 appears to be a time series
Reported by: | Zach Pearson | Owned by: | Zach Pearson |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | DICOM | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | ChimeraX |
Description
This series displays like it's a 3D dataset, but all the slices in the dataset look like they're at the same depth, except the heart is moving around. It looks like a time series of a heartbeat to me. Opening this ticket so I can remember to double check that.
Change History (4)
comment:1 by , 2 years ago
comment:2 by , 2 years ago
I modified SeriesFile to return either TriggerTime or ContentTime for its trigger_time attribute (which should be renamed to 'time' soon). The series is correctly shown as a time series but its slices are out of order. We're trying to sort them by ImagePositionPatient, the highest priority attribute. They all have the attribute, but it's all the same.
comment:3 by , 2 years ago
Added checks to make sure not all Z values are the same when sorting by position. We now fall back to other checks if all positions are the same. In this case, AcquisitionNumber ( a low priority sort ) lined up with ContentTime, so no further changes were needed.
This dataset lacks TriggerTime, TemporalPositionIdentifier, and NumberOfTemporalPositions. The only way to know it's a time series is to observe every slice is in the same location, then we can order them by InstanceNumber.