Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dicom Slice order #560

Closed
frickt opened this issue Aug 29, 2018 · 5 comments
Closed

Dicom Slice order #560

frickt opened this issue Aug 29, 2018 · 5 comments
Labels
question Further information is requested
Milestone

Comments

@frickt
Copy link
Contributor

frickt commented Aug 29, 2018

I've a problem with the slice ordering of a series. not sure if 0020,1041 SliceLocation should be taken into account.

@frickt
Copy link
Contributor Author

frickt commented Aug 29, 2018

example.zip

@ivmartel ivmartel added the question Further information is requested label Sep 3, 2018
@ivmartel ivmartel added this to the 0.25.0 milestone Sep 3, 2018
@ivmartel
Copy link
Owner

ivmartel commented Sep 5, 2018

What is the problem with your data: are there misplaced slices or would you have it completely reversed?

@frickt
Copy link
Contributor Author

frickt commented Sep 5, 2018

the order is reversed. InstanceNumber is 1,2,3,4... where the calculated order through ImagePositionPatient goes the other way around. Other viewers like Synedra or Radiant works as expected first Image is InstanceNumber=1. Is the ImagePositionPatient wrong for this series or the calculation we do with it?

@ivmartel
Copy link
Owner

ivmartel commented Sep 5, 2018

The code uses the ImagePositionPatient to determine the order of the slices according the their physical position in space. It uses the ImageOrientationPatient to guess the order.

There seem to be two viewing conventions: radiological and neurological. They order slices differently, now I am not sure if this is file based or a user preference...

Related to #317, #261.

@frickt
Copy link
Contributor Author

frickt commented Sep 5, 2018

okay, thank you.
Seems to be an issue with the metatdata that the direction does not correspond between InstanceNumber and ImagePositionPatient. I'm not sure, if preferring the SliceLocation over ImagePatientPosition would lead into other problems...

@frickt frickt closed this as completed Sep 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants