Hi Niels,
I can't remember what the original problem was. Were the dicom fields missing or were they just wrong? We can handle wrong ones, but missing ones cause our 3rd party dicom reader to fail, which we can't really do anything about.
doug
Niels Bergsland wrote:
Hi again, From the last time that I asked about this, the project was temporarily put on hold, but now it has started up again...
When looking back at the responses from last time, I realized that I am not sure if I made it clear what I was proposing as a solution to the missing fields 0020,0032 (ImagePositionPatient) and 0020,0037 (ImageOrientationPatient). My original question was as follows:
Is it possible to 'fake' the 20,37 field by inserting the values: 1\0\0\0\1\0 since we know they are acquired in the axial plane? We also know which way the slices are supposed to be sorted, is it possible to insert values into 20,32 in order to have freesurfer able to 'know' the proper sorting order?
To which you said that you didn't have something to allow us to specify the fields ourselves. I realized that you thought I was asking if Freesurfer has the capability. What I actually meant though is if I can manually insert the values using, for example, dcmodify (part of the DCMTK) and then process the scans with Freesurfer. Hopefully this is a bit more clear! Thanks again, Niels Bergsland