Issue with unexpected changes in "save to" import converter files

  • I have an issue with images saved using a "save to" import converter.

    I have DICOM image analysis written in python. If I run it on the DICOM image saved by conquest to its default storage location (MAGDevice0), it runs fine. If I try to run it on the .dcm file saved using an import converter, it fails.

    Looking at the DICOM tags of the two files, it appears the one saved by the import converter has had the private tags re-written, so I'm wondering if this is what causes my software to fail, possibly there are other changes I'm not aware of.


    Is it possible to stop the import converter file being changed, so that it is identical to the file saved in conquests database (and the original file!)?


    Many thanks for any help and the extremely useful software!


    The relevant lines for the import converters are:

    Code
    #Create a folder with SOP instance UID
    ImportConverter1 = mkdir E:\auto_QC\%o\
    #Save file to created folder with file base name
    ImportConverter2 = save to E:\auto_QC\%o\%b.dcm

    Some of the private tags from the file saved to MAGDevice0:

    Tags from the same image, but saved using "save to" import converter

  • Thank you, dicom.ini is as follows:

    Basically it seems to be rewriting the private tags, changing the value representation and storing the values as binary?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!