You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can’t convert my DICOM files in Bq/mL into SUV.
I think the problem comes from the metadata of my data which do not contain the tag (0018,1072) RadiopharmaceuticalStartTime, as the error message of the “SUV Factor Calculator” module tells me:
itk::ExceptionObject (0000005A9AB9D0D0)
Location: “unknown”
File: D:\D\S\S-0-E-b\PETDICOMExtension\SUVFactorCalculatorCLI\itkDCMTKFileReader.cxx
Line: 89
Description: ITK ERROR: Can’t find tag 18 1072
However, in the documentation of this module, they mention that the tag (0018,1078) RadiopharmaceuticalStartDateTime can be interchangeable with the tag (0018,1072) RadiopharmaceuticalStartTime, and my metadata contains this tag.
How can I overcome this error message?
Thank you very much for your attention !
The text was updated successfully, but these errors were encountered:
created a tag with pydicom >>ds.add_new('0x00181072', 'TM', '105650.000') didn't work even though tag (0018,1072) shown up in the metadata
The solution is to create the tag under the (0054,0016) RadiopharmaceuticalInformationSequence
Hello,
I can’t convert my DICOM files in Bq/mL into SUV.
I think the problem comes from the metadata of my data which do not contain the tag (0018,1072) RadiopharmaceuticalStartTime, as the error message of the “SUV Factor Calculator” module tells me:
itk::ExceptionObject (0000005A9AB9D0D0)
Location: “unknown”
File: D:\D\S\S-0-E-b\PETDICOMExtension\SUVFactorCalculatorCLI\itkDCMTKFileReader.cxx
Line: 89
Description: ITK ERROR: Can’t find tag 18 1072
However, in the documentation of this module, they mention that the tag (0018,1078) RadiopharmaceuticalStartDateTime can be interchangeable with the tag (0018,1072) RadiopharmaceuticalStartTime, and my metadata contains this tag.
How can I overcome this error message?
Thank you very much for your attention !
The text was updated successfully, but these errors were encountered: