Dicominfo tag is being read as uint16 instead of float double

Hello,

I am trying to read a private dicom tag using the dicominfo commat.

Following the instructions in MathWorks site:

(a) Genrated a unique dicom dictionary, where I added this tag <using the format: [Tag] [Name] FL (float double) 4>

(b) set the code to use this dictionary when reading the dicominfo <using the dicomdict('set',....) command>

Now, When I am running the code I see that the dicominfo is using the new dictionary (Tag name is according to the dictionary setup), yet the tag value is still being imported as unit16 and not float double.

Any ideas that can help to solve this one?

[ErLan]

... small correction, for float double I used the FD code not the FL VR type.

[Rik]

Could you post an example that we can run to reproduce the problem?

[Star Strider]

ErLan’s Answer moved here — (Posted: 20 Sep 2019 at ~12:30)

Can try to :)

The DICOM tag ID is {0x01f5,0x1012}

File 'dicom-dict-MyDict.txt' was created and placed in the iptformats folder, the file contains a line referring to this private tag, saying:

(01f5,1012) FD XYZPoints 4

DICOM dictionary setting was done using the following command:

dicomdict('set','C:\Program Files\MATLAB\R2017a\toolbox\images\iptformats\dicom-dict-MyDict.txt')

When applying the DICOMinfo command:

metadata = dicominfo([directory_name, '\',DICOM_FILE_NAME])

and looking at metadata.XYZPoints, I get a uint16 column vector (see below):

~~~~~ copied from MATLAB ~~~~~

> metadata.XYZPoints,

ans =

2016×1 uint16 column vector

41664

16742

6784

16456

39360

16665

8832

16727

14592

49191

17952

...

~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~

Thanks,

[Star Strider]

Rik Commented —

It also is not what I meant. What would help is a piece of code that does not require any other settings and reproduces the issue. In this case that would include the dict file and an example dicom file.

Feel free to delete this answer and repost it as a comment.

[ErLan]

Thanks Rik,

... I have some challanges to share datafile (senstive record); are their possible actions\indicators that I can hunt down (via. your guidence) and will allow us a 'remote' debugging?

[Rik]

I would expect this issue to appear irrespective of the actual content of the dicom file. As long you have a similar data type you can even randomly generate a dicom file. That is actually even the preferred method. In that case you will only need to attach the dictionary and write some code that generates the dicom file and returns this result when loading it again.

Feel free to use included example files to generate an image (like S=load('mri');IM=squeeze(S.D);).