| Re: reading in binary data [message #17269 is a reply to message #17158] |
Thu, 16 September 1999 00:00  |
Lazzar
Messages: 9
Registered: February 1999
|
Junior Member |
|
|
David Fanning wrote:
> This surprises me. There is obviously some overhead in
> creating an IDL save file, but this seems a bit excessive.
> Usually in these situations I always blame the programmer.
> I'm wrong about 0.05 percent of the time. :-)
>
> And, anyway, why are you so enamored with IDL SAVE files?
> I use them occasionally, of course, but I'm scratching my
> head to think of the need for them here. What exactly are
> you trying to do?
>
> Cheers,
>
> David
>
It's not so much that I'm enamored with IDL SAVE files, but I'm looking for
speed when opening a file. It takes IDL around 2-3 minutes to open the raw
binary file and put the data into the appropriate arrays, but only 30 sec. or
so for it to open the IDL SAVE file. I've been in contact with RSI tech
support and they've indicated that a new 5.3 feature of having a binary file
template might be able to help me with this problem. I'm dealing with
hydroacoustic data (like a fish finder) that has a vertical resolution of 53
samples per meter of water and it collects upwards of 5 soundings of data per
second. The files can get very big very quickly and speed is very important
when process this data. Right now I have a program that reads in the data and
converts it from an binary file to an IDL SAVE file so that future processing
is faster. IDL is the perfect language to do my data processing in, as I can
deal with my data as an image and do whole array processing in one step, but
it isn't the best at reading in the data. Also as a non programmer I've been
able to learn enough IDL to get by, but seem to be pushing my limits (not
necessary a bad thing).
Brian
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
