SeiictyUsui / pydicom

Automatically exported from code.google.com/p/pydicom
0 stars 0 forks source link

possibly different repr representation for tag, sequence #106

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

details below

What is the expected output? What do you see instead?

<Sequence, Length X>

or <Sequence, Length X, offset_hdr/data>

but, i agree this should be thought through before making a change.

What version of the product are you using?

current dev

***NOTE***: any text or attached files posted with the issue can be viewed
by anyone. You are solely responsible to ensure that they contain no
confidential information of any kind.

Please provide any additional information below.

when i print a tag, that is a sequence, it says:

<Sequence, length 1, at 109AA8FC8>

when i rerun it, it gives me a different hex number which leads me to believe 
this is a memory address. should it be a memory address, or should it give a 
byte offset into the dicom header/data or simply say <Sequence, length x>?

i'm generating the headers automatically and git is picking up this difference 
between header output each time.

-(0008, 1110) Referenced Study Sequence           SQ: <Sequence, length 1, at 
109AA8FC8>
-(0008, 1111) Referenced Performed Procedure Step SQ: <Sequence, length 1, at 
109AB5AF8>
-(0008, 1140) Referenced Image Sequence           SQ: <Sequence, length 2, at 
109AB5BA8>
+(0008, 1110) Referenced Study Sequence           SQ: <Sequence, length 1, at 
109AB5FC8>
+(0008, 1111) Referenced Performed Procedure Step SQ: <Sequence, length 1, at 
109AB5E68>
+(0008, 1140) Referenced Image Sequence           SQ: <Sequence, length 2, at 
109AB5EC0>

Original issue reported on code.google.com by satrajit...@gmail.com on 16 Oct 2011 at 2:23