Hi manager, the Dicom images downloaded from the pacs always shows the “pixel larger than the output tpye” and with the information “could not load xxx as Scalar volume”.The dicom reader was setted to be GDCM approach.I have already checked the document which told me to go to the module “cast scalar volume” and choose the float, it also doesn’t work. Is there any way to raise the pixel output in the slicer? Thx!
If you can share example data (not patient data) that replicates the issue someone can probably look. But my guess is that this is some kind of non-standard dicom data so you may not have much luck.
Thank you for your reply 
but what weird is, another set of the Images can be imported and 3d slicer worked well , which also comes from the same PACS system. 
. The engineer in our hospital said that the images are 100% in the form of dicom， truely confused now
Probably it’s not dependent on the PACS itself but the modality that created the data. If you can’t share a de-identified example it’s hard for us to say. There are lots of lower-level dicom tools you could use to investigate. Try using a the File Editor feature at this site to figure out what’s going on All CIODs – DICOM Standard Browser
What software created the image?
What is the voxel type of the image? Double floating point?
Does the image load correctly if you use DCMTK approach?
I am sorry sir, this is my first time trying to get help in the community, i don’t know how to share a dicom file directly in the reply form. May I email you for a check ? Thank you very much.
You can upload the files anywhere (dropbox, onedrive, google drive, etc.) and post the link here.
Hello sir, here is the OneDrive link ,Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. . Thank you for your information
The data set is invalid. See the output of David Clunie’s dciodvfy tool:
(0x0040,0x1008) LO Confidentiality Code - Warning - Explicit value representation doesn't match data dictionary; Explicit <ST> Dictionary <LO>
(0x07a3,0x10ca) ? - Warning - Unrecognized tag - assuming explicit value representation OK
Warning - Value dubious for this VR - (0x0010,0x0010) PN Patient's Name PN [1] = <Anonymous> - Retired Person Name form
MRImage
Error - Empty attribute (no value) Type 1 Required Element=<ReferencedSOPClassUID> Module=<SOPInstanceReferenceMacro>
Error - Empty attribute (no value) Type 1 Required Element=<ReferencedSOPInstanceUID> Module=<SOPInstanceReferenceMacro>
Error - Empty attribute (no value) Type 1C Conditional Element=<CodeValue> Module=<BasicCodeSequenceMacro>
Error - Empty attribute (no value) Type 1C Conditional Element=<CodingSchemeDesignator> Module=<BasicCodeSequenceMacro>
Error - Empty attribute (no value) Type 1 Required Element=<CodeMeaning> Module=<BasicCodeSequenceMacro>
Error - Attribute present when condition unsatisfied (which may not be present otherwise) Type 2C Conditional Element=<Laterality> Module=<GeneralSeries>
Warning - is only permitted to be empty when actually unknown; should be absent (not empty) if an unpaired body part, and have a value if a paired body part - attribute <Laterality>
Error - Empty attribute (no value) Type 1C Conditional Element=<CodeValue> Module=<BasicCodeSequenceMacro>
Error - Empty attribute (no value) Type 1C Conditional Element=<CodingSchemeDesignator> Module=<BasicCodeSequenceMacro>
Error - Empty attribute (no value) Type 1 Required Element=<CodeMeaning> Module=<BasicCodeSequenceMacro>
Warning - Unrecognized defined term <M> for value 3 of attribute <Image Type>
Warning - Non-identity Modality LUT Module (RescaleSlope and RescaleIntercept) not expected to be present in standard MR IOD - may cause windowing problems - attribute <RescaleIntercept> = <32768>
Warning - Non-identity Modality LUT Module (RescaleSlope and RescaleIntercept) not expected to be present in standard MR IOD - may cause windowing problems - attribute <RescaleSlope> = <1>
Warning - Attribute is not present in standard DICOM IOD - (0x0008,0x0061) CS Modalities in Study
Warning - Attribute is not present in standard DICOM IOD - (0x0008,0x9208) CS Complex Image Component
Warning - Attribute is not present in standard DICOM IOD - (0x0018,0x1061) LO Trigger Source or Type
Warning - Attribute is not present in standard DICOM IOD - (0x0018,0x9073) FD Acquisition Duration
Warning - Attribute is not present in standard DICOM IOD - (0x0020,0x1208) IS Number of Study Related Instances
Warning - Attribute is not present in standard DICOM IOD - (0x0028,0x1052) DS Rescale Intercept
Warning - Attribute is not present in standard DICOM IOD - (0x0028,0x1053) DS Rescale Slope
Warning - Attribute is not present in standard DICOM IOD - (0x0032,0x1032) PN Requesting Physician
Warning - Attribute is not present in standard DICOM IOD - (0x0032,0x1060) LO Requested Procedure Description
Warning - Attribute is not present in standard DICOM IOD - (0x0040,0x1008) LO Confidentiality Code
Warning - Attribute is not present in standard DICOM IOD - (0x0054,0x0081) US Number of Slices
Warning - Dicom dataset contains attributes not present in standard DICOM IOD - this is a Standard Extended SOP Class
The invalid tag value that causes the load failure is <RescaleIntercept> = <32768>. Probably ITK complains because if this rescaling was applied then values stored in the image may not fit in the 16-bit voxel type.
If this value is not introduced by post-processing/anonymization then report the error to the manufacturer.
In the meantime, you can patch the files using DCMTK’s dcmodify tool by running it on each file like this:
dcmodify.exe -i RescaleIntercept=0 I1000000
1 Like
thank you for your help manager , I successfully open the file, love u. I will go try to tell the engineer to fix the trouble