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

Home » Public Forums » archive » error reading a large number of binary files
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: error reading a large number of binary files [message #53732 is a reply to message #53600] Mon, 23 April 2007 07:59 Go to previous messageGo to previous message
Mark Branson is currently offline  Mark Branson
Messages: 9
Registered: May 2006
Junior Member
On Apr 23, 8:24 am, Paul van Delst <Paul.vanDe...@noaa.gov> wrote:
> Are the original files little or big endian?
>
> On what machine did you create the "new" files? A little or big endian machine? (Your mac
> is big endian, right?)
>
> On what machines did you test the fortran program? All your NAG and xlf compilers on you mac?
>
> What happens when you use the /SWAP_ENDIAN keyword in your OPENR?
>
> What does the binary keyword do?> openr, lun, infiles[i], /get_lun, /binary, /f77_unformatted
>
> I can't find a reference to it in the docs.
>
> cheers,
>
> paulv
>
> --
> Paul van Delst Ride lots.
> CIMSS @ NOAA/NCEP/EMC Eddy Merckx

Hi Paul. I'm 99% sure this is not a big-endian/little-endian or
f77_unformatted issue. I deal with grib files and their conversion
quite often in my work, and my experience is that if you don't have
the switches for them set up correctly, then IDL (or fortran) will
either fail reading the (first) file or you'll get garbage for input.
In this case, I know I can read any of the input files okay because I
can print out a sample from within the program and they are correct
(and I ran the wgrib program on my G5, which for the record is big-
endian). Why it will suddenly fail x number of files into the read
process is where I'm stuck, and it seems to occur at a random spot
with repeated trials.

Before I submitted this post, I searched this newsgroup for related
discussion on this subject, and someone mentioned that the use of the /
binary keyword might be helpful, but like you I don't see it
documented in current IDL help for OPENR. Since I've been clutching
at straws I decided to insert it, and while it did not produce an
error message, it also didn't fix the problem.

Oh, and yes -- I'm running IDL as well as the fortran read program on
my Mac G5. I have the NAGWare, Absoft and XLF compilers available. I
believe the Absoft compiler also produces the same error, but I should
double-check that.

Cheers,
Mark
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Antes de FAC Club
Next Topic: MPFIT Limits

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

Current Time: Sat Oct 11 05:37:12 PDT 2025

Total time taken to generate the page: 0.32399 seconds