comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Bug in 5.3 read_binary template ?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Bug in 5.3 read_binary template ? [message #26006] Wed, 01 August 2001 15:00
ignore_this_adress is currently offline  ignore_this_adress
Messages: 3
Registered: June 2001
Junior Member
Dear reader,

I came across something, that appears as a bug to me :
When reading in some material of our GE MR scanner, I need to have some
information about the imaging parameters that are set in the proprietary
file format. Using the (very useful) read_binary template I have defined
16- and 32bit ints, longs and floats, big endian. When running the
read_binary function with the template, I receive well defined ints, but
not longs and floats. Running the same program on an IRIX workstation
(IDL 5.4), the results are fine.

The resulting values should be the following
Property Value Offset
Sizeof() IDL 5.3
Exam number for this image: 1246 0x890 2
1246
Series Number for this image: 12 0x892
2 12
Image Number: 284 0x894
2 284
Slice Thickness (mm): 8.00 0x8a4
4 2.33e-041
Image matrix size - X: 512 0x8a8
2 512
Image matrix size - Y: 512 0x8aa
2 512
Display field of view - X (mm): 340.00 0x8ac 4
2.42e-041
Display field of view - Y (if different): 272.00 0x8b0 4
2.42e-041
Image dimension - X: 256.00 0x8b4
4 2.41e-041
Image dimension - Y: 192.00 0x8b8
4 2.41e-041
etc...

To me it seems that IDL does not do the endian swapping on the float
data type... Please share your thoughts :-)

M. Vogel
[Message index]
 
Read Message
Previous Topic: Re: IDL crashing badly on my solaris 8 system
Next Topic: Re: Editor feature?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 18:44:33 PDT 2025

Total time taken to generate the page: 0.00395 seconds