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

dcm2mnc not using private Philips dicom tags for scaling #89

Open
jpcoutu opened this issue Jun 12, 2019 · 1 comment
Open

dcm2mnc not using private Philips dicom tags for scaling #89

jpcoutu opened this issue Jun 12, 2019 · 1 comment

Comments

@jpcoutu
Copy link

jpcoutu commented Jun 12, 2019

It seems that dcm2mnc does not make use of the private Philips dicom tags (2005,100D) (SI) and (2005,100E) (SS) for scaling the stored pixel data. Currently it seems to only use the public scaling tags (0028,1052) (RI) and (0028,1053) (RS), to output the 'display value' (DV) scaled from the stored pixel value (PV):

DV = PV ⋅ RS + RI

As described in this paper, for Philips, to obtain the true floating-point value, one needs to do instead:

FP = DV / (RS ⋅ SS) = (PV +RI / RS) / SS = (PV − SI) / SS

This is what is currently done in dcm2niix here. Chris Rorden also added an option to output the DV instead of FP, but expresses his dislike about this option here.

I noticed that dcm2mnc currently will use the (2005,140a) as an alternative rescale slope when (0028,1053) (RS) is 1; I am not sure where this fits in. Note that using the FP only matters in quantitative applications.

@jpcoutu
Copy link
Author

jpcoutu commented Jun 14, 2021

By the way, this is fixed by: #113

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant