|
Claudio Pedrazzi wrote:
Hi Stuart and Werner
that's cool!
I never used READBIN, I didn't even know its existence. Thanks a lot!
So for the data quantity, I have chosen the smallest file that I have !!!
It should actually contain 2,973,921 time points!
So Stuart is right about the round three millions. I have other files containing 18 millions points.
For information, the values are rms of vibration speed in one direction, registered by an instrument during a long measurement campaign.
To develop a parser appears to me pretty difficult, but I have to say, in principle what I would like to have is very simple:
-two columns, one with a time stamp, the other with the measured value.
- so that I can try to make plots, interpolations, correlations, and so on.
Thanks a lot again and have a nice day
Claudio
|
If this file is representative of the data you're looking at, then writing a parser should be fairly straightforward - it's what I had to do to convert the initial parts to the nested array shown in my previous message.
READBIN should allow you to read in segments of data rather than reading in the whole thing (READBIN("file", "type", [[endian], [cols], [skip], [maxrows]]). Use [skip] to get to where the segment starts and [maxrows] to determine the size of the segment (eg, READBIN("file", "byte", 0, 1, 2000, 1000) to get a block of 1000 bytes starting at the 2000th byte) - I've used this before to read chunks of large files and, if you find the starting point for the CS raw data, you might even be able to set type as "float" to simplify the process).
Stuart