Open GoogleCodeExporter opened 9 years ago
This might be the same issue referred to here:
https://code.google.com/p/pydicom/source/browse/source/dicom/examples/write_new.
py#64
Original comment by agrothberg
on 10 Nov 2014 at 6:01
As a rule, pydicom does not "connect" different data elements (or in this case,
flags for transfer syntax to data elements). It is up to the user to set all
appropriate dicom data elements. This might change in some future version, but
DICOM is so complex in its requirements it would be very difficult to fulfill
them (or warn) on behalf of the user for most situations. The write_new
program you linked does provide an example of how to set the elements.
As for pynetdicom, I'm not sure I understand the issue there ... you can set
ds.file_meta.TransferSyntaxUID in memory before calling pynetdicom code.
Original comment by darcymason@gmail.com
on 11 Nov 2014 at 8:48
The issue is that If i set:
ds.is_little_endian = True
ds.is_implicit_VR = True
and then try to read:
ds.file_meta.TransferSyntaxUID
I get an error.
If instead, i set:
ds.is_little_endian = True
ds.is_implicit_VR = True
save the file as XXXX.dcm. Then load XXXX.dcm and then read:
ds.file_meta.TransferSyntaxUID
I can properly read that value. In other words, round-tripping the DICOM to
disk changes ds.file_meta.TransferSyntaxUID
Original comment by agrothberg
on 11 Nov 2014 at 8:50
Original issue reported on code.google.com by
agrothberg
on 10 Nov 2014 at 5:58