Hi All,
Some additional thoughts on this issue:
1. Regarding when to test:
I agree absolutely that the best moment to test the start lanes is the day before the race during practice sessions.
Sue brought up an excellent concern about changed water levels on race day. IF the river water level changes ON RACE DAY enough to impact the course, then unfortunately I see no other fair solution than to retest because at this point the testing that was done previously has been negated (although the reality is that a race day retest will probably be very difficult if not impossible). One possible answer would be to require the event host to test the course at various levels as a contingency for this problem (when holding events on rivers where an overnight change of the level is a real possibility). Then, with the course already certifiably/reliably tested, the lanes can be adjusted and the race run without race day retesting. Not the best answer however, because there is no guarantee that the race day level will be one of the levels that was pretested - but we can hope...
2. Regarding which teams should do the test:
I don't think that it is terribly important that it is the best teams or even comparable teams that are doing the testing, as long as they are reasonably consistent in their speed and track the fast course in each lane. (This should be the case with most every team in a World Champs.)
The best (and most dependable) test is to have as many teams as possible test the course and aggregate the results of each lane. Putting two teams against one another in a H2H format makes the testing more efficient, (because we can test more teams quickly) and it is more fun - but it is not strictly necessary that they are evenly matched - remember, in this case it is the lanes we are testing, not the teams. The most important thing is that each team
must test both start lanes for the comparison, and enough teams must participate in the testing to reliably average the results. In the example I created below, the teams are not equal, but the aggregated results provide the lane data needed. Once again, remember that it is the starting lanes we are timing (the section of the course between the start platform and the top of the first rapid), not the entire course.
Example of equal lanes
First run:
Team 1 - Lane A - 45.25 seconds
Team 2 - Lane A - 38.73 seconds
Team 3 - Lane A - 40.21 seconds
Team 4 - Lane A - 50.72 seconds
Second run:
Team 1 - Lane B - 44.97 seconds
Team 2 - Lane B - 39.18 seconds
Team 3 - Lane B - 40.19 seconds
Team 4 - Lane b - 51.01 seconds
aggregate results: Lane A - 174.91, Lane B - 175.35
average times. Lane A - 43.72, Lane B - 43.83
conclusion: Average time in each lane is relatively equal so it can be assumed that both lanes are relatively equal.
Example of unequal lanes
First run:
Team 1 - Lane A - 45.25 seconds
Team 2 - Lane A - 38.73 seconds
Team 3 - Lane A - 40.21 seconds
Team 4 - Lane A - 50.72 seconds
Second run:
Team 1 - Lane B - 50.01 seconds
Team 2 - Lane B - 42.01 seconds
Team 3 - Lane B - 45.10 seconds
Team 4 - Lane B - 54.17 seconds
aggregate results: Lane A - 177.92, Lane B - 191.29
average times: Lane A - 44.48, Lane B - 47.82
conclusion: Averaged time shows that Lane B is 3.34 seconds faster than Lane A. Clearly these lanes are not equal.
Obviously, the more teams that participate in the test, the more reliable will be the results. With enough teams participating (10+), then the slowest and fastest times can be tossed out to further eliminate any inconsistencies. If a lane inequity is discovered, then it is a simple matter to handicap the teams in the faster lane with an adjustment equal to the time difference.
Hope this makes sense... and sorry for the long post.