This *sounds like* a calibration string problem. The reason I say that
is I suspect that the recording never found an autostop point, and that
is often a symptom of a bad calibration string. If that's the case, the
data is, unfortunately, junk. To check that just send me a copy of your
calibration string; bad ones are easily identifiable.
If that's not it, then we can probably parse the data manually, but not
by reading it into GEEZ. GEEZ has a 6 minute limit for a single run (3
minutes at 20Hz), or 3600 samples. If your run exceeds this there
*could* be some errors that come up. But if you load the GCD file into
a text type word processor, you'll be able to scan down the file quickly
and cut out the individual runs. Where you see the same numbers with
little or no change the car is sitting still. When you are on course,
there's huge jumps all over the place. This isn't fun, but it will
work.
But let's start with the bad calibration string theory. Send me a copy
of your cal string and I'll know for sure.
--Byron
Wally Strzelec wrote:
>
> Had something pretty weird happen yesterday. Yesterday when I tried to
> record my runs, instead of creating four files, it created 1 large file. I
> set the geez up in autostart and just left it on for the whole run group.
> My first thought was that I would be able to just cut each of the runs out
> of the large file. When I try to read the file in, I get the errors;
> "Floating Point division by zero", "Invalid floating point operation" and
> "Range check error".
>
> Any ideas on what I messed up to just get one file?
>
> Is there anyway to cat the runs out?
>
> -Wally
|