Be sure to keep up! We're moving fast!

Now that we've got people running track meets and giving us some bug reports we're finally getting things clean. We're very close to calling this RaceTab 4 and pushing to everyone. Even now though, I really encourage everyone to run this version. It's more stable already than 3.053 and it helps us find any remaining issues and gets you used to this latest and greatest, which we think is going to really change how meets are run.


Views: 400

Comment by Rodney Cain on March 10, 2013 at 12:17pm

used in a race yesterday with no major issues. Would like to figure out how to get racetab to pull the time in hundredths  from flash timing. I had to manually enter in do to rounding up to the nearest tenth caused a tie in a sprint race. Also on live results relay teams show up as undefined. MUCH better than 3.053.

Our meet set up was three computers linked via Wireless N router, wireless printer,. and Flash Timing System..

Comment by John B Caulfield on March 10, 2013 at 5:10pm

In the results listed above there are events that have times to the thousandth, and times shown to the hundredth, which were the ones hand entered?   Flash times should only be considered accurate to the hundredth if the camera is set for 100 frames a second . The thousandth digit should be rounded up if non zero. Just like other photo timing cameras. 

Comment by Rodney Cain on March 10, 2013 at 5:32pm

The event I am referring to would be the HS Girls Premier 100 Meter Dash. On the review computer the flash timing says the time was 13.419 when imported to racetab it changed to 13.42 and another girl ran 14.42 in another hat creating a tie.

Comment by John B Caulfield on March 10, 2013 at 7:48pm

In the two time you quoted one shows one to hundredths and the other thousandths,so can not be compared, even if the one heat had 13.419 and the other heat had 13.420 with a video system the two are still tied.

The high end flash FT 120 can not tell the difference of less than .00833 between heats (1 /120 of a second) so a difference of less than that between heats should still be reported as a tie and remain a tie.  Just as if  when you look at the pictures from a single race and the frame before, the frame on and the frame after  two runners cross the finish line have the runners change place the runners should be given a tie with a video timing system even if one runner seemed to be ahead in the single frame where they were on the finish line.  If you have a chance look at a I.A.A.F. (or one of the U.S.governing bodies) rule book from before 2006 when video was still allowed internationally on how to read and report times from a video timing system.

Comment by Rodney Cain on March 11, 2013 at 8:41am

Thanks. Will do...

Comment by T Penman on March 11, 2013 at 2:13pm

Thanks for the Javelin update for Washington state. If it's that easy to make changes, then: we also have the girls 4x200m relay (no boys) and we do not have the 4x800 (for either boys or girls).

Comment by David Meuleman on March 11, 2013 at 4:54pm

In distance races, let's say there are twelve competitors on a six lane track.  I want to assign them randomly, two per lane (what I would call a one-lane alley).

In the seeding window, I choose 6 lanes, select "Use alleys" and set the lane assignment to random, Racetab fills the first six slots (1A-6A).  It shows the next six slots (1B-6B) as empty.  There are no more names under "Unassigned."  Interestingly, if I change lane assignment to one of the waterfall options, it correctly assigns starting positions all twelve runners.

Also, if I try to Auto-Pilot the seeding with "Use Alleys," it appears to ignore that and does something very strange where it does not assign any athletes to any lanes.

Comment by Jason Byrne on March 12, 2013 at 4:02am

Next update will remove 4x8 from Washington and add girls 4x2

Comment by Jason Byrne on March 12, 2013 at 4:02am

David, I will look into it for you... but not tonight :) 

Comment by Chad Mitchell on March 12, 2013 at 10:28am

When not using fully automatic timing, the option always defaults back to "yes" in the meet setup.  It doesn't matter how many times I click "no".  I don't know that it makes a practical difference, but the issue is there.


You need to be a member of RaceTab to add comments!

Join RaceTab

Facebook Page

© 2020   Created by Jason Byrne.   Powered by

Badges  |  Report an Issue  |  Terms of Service