[Insight-users] DicomImageReadChangeHeaderWrite---0002|0003

[Todd Jensen]

I have found the easiest solution is to just let GDCM generate the SOP instance UIDs for both elements.  That results in the same UID for both as the current implementation does not allow you to override both.

Every image should have a different UID, so it is not a good idea to hard-code the sop string in gdcmFileHelper. It is best just to leave the GDCM code as is and remove setting the SOP instance UID in your application. Why do you need this exact UID?

Todd




________________________________
From: x0_y0_0 <x0_y0_0 at 126.com>
To: Todd Jensen <todd.jensen at ieee.org>; itk <insight-users at itk.org>
Sent: Monday, May 11, 2009 8:46:12 AM
Subject: Re:Re: [Insight-users] DicomImageReadChangeHeaderWrite---0002|0003


Thank you very much,Todd Jensen. I overwrite gdcmFileHelper.cxx as followed:
                 std::string sop = "1.2.86.755.4.2.4.24.1.3.201";
                 CopyMandatoryEntry(0x0002,0x0003,sop);
and then rebuilt ITK(InsightToolkit-3.8.0),but  the SOP Instance UID become wrong:
     (0002|0003) Media Storage SOP Instance UID = 1.2.826.0.1.3680043.2.1125.1.78291920758156013450636231478551699
I don't know what's wrong with it?
 
regards,
                                                                                mexiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20090511/5d1a0d00/attachment.htm>