Adding sectors programmatically - issues?
Posted: Mon Jun 18, 2007 2:30 am
I was autocrossing this weekend and put my DL1 through its virgin runs in my car and in a friend's. I'm doing analysis now, and I can't seem to get run times to make sense relative to the official times at the event.
I can get a pretty accurate "start of run" marker by looking at the longitudinal acceleration of the cars. Actually I'm creating a "staging" marker where the car is at rest before the start line, and then programmatically adding the "start of run" marker 2 meters after that. But when I try to add a "end of run" marker programmatically by doing it xx.xxx seconds after the "start of run" marker (where xx.xxx is the official time for the run), the times are off fairly significantly (~1 second), and not in any identifiable pattern. For example, I have two runs for my friend in his car, but the software is showing a difference of 0.27 seconds between those two runs, where his official times were about 0.7 seconds apart.
A question that may lead me to an answer: when a marker is added programmatically based on time (from a previous marker), on what run is that based?
I can get a pretty accurate "start of run" marker by looking at the longitudinal acceleration of the cars. Actually I'm creating a "staging" marker where the car is at rest before the start line, and then programmatically adding the "start of run" marker 2 meters after that. But when I try to add a "end of run" marker programmatically by doing it xx.xxx seconds after the "start of run" marker (where xx.xxx is the official time for the run), the times are off fairly significantly (~1 second), and not in any identifiable pattern. For example, I have two runs for my friend in his car, but the software is showing a difference of 0.27 seconds between those two runs, where his official times were about 0.7 seconds apart.
A question that may lead me to an answer: when a marker is added programmatically based on time (from a previous marker), on what run is that based?