RaceVIEW Description

Overview

RaceVIEW's Derby Method

	Two-Tier Derby using Divisions
	Elimination Phase
	Finals Phase
	Results Storage
	Derby Finals

Sample Screen Shots

	Lane Assignments
	Race Display
	Leader Board
	Championship Display

Systems Requirements

Ordering Information

Overview (next)

RaceVIEW is an application for managing and displaying the results of Pinewood Derbies, Rain Gutter Regattas, KubKar Rallies, and similar events run by numerous youth organizations such as BSA Cub Scouts, AWANA, Christian Service Bridge (CSB), Royal Rangers, and YMCA.

RaceVIEW allows for both manual and automatic finish results. The manual mode allows finish orders to be typed in for those groups who do not have a compatible finish line timer equipped with a computer interface. In the automatic mode, RaceVIEW supports all commercially available timers with a computer interface.

	RaceVIEW manages and displays Derby results on all tracks with three (3) to eight lanes (8).
	RaceVIEW supports ANY group, such as Cub Scouts, Royal Rangers, AWANA, and YMCA.
	RaceVIEW uses a hybrid method involving an Elimination Phase where cars are randomly assigned in successive rounds to determine a set of finalists and a Finals Phase where the finalists race each other with each car racing once per lane. See below for more details about RaceVIEW's method.
	RaceVIEW does NOT work on two (2) lane tracks.
	RaceVIEW does NOT conduct single or double elimination races, although by choosing the right threshold value you can get close to these formats.

RaceVIEW's Derby Method (next) (top)

Two-Tiered Derby (next)

RaceVIEW implements a Two-Tiered Derby Format; one or more Divisions whose finalists advance to a Derby Finals. In the individual Divisions and the Derby Finals, a Point Elimination Derby format, devised by members of the Pack 34 (Mystic, CT) Race Committee is used. This format consists of two phases; an Elimination Phase and a Finals Phase.

RaceVIEW allows for running your Derby in two tiers, the Division Level and the Derby Finals. Finalists from the Division level may be automatically registered for the optional Derby Finals. RaceVIEW lets the committee decide which Divisions and how many Finalists from those divisions will advance to the Derby Finals. Of course, you can also elect to run your entire Derby as a single Division. (This is only recommended for group sizes of less than eight times the number of lanes.)

Elimination Phase (prev) (next)

During the Elimination Phase, cars are randomly assigned to races. The cars accumulate points for each race equal to their finish order (one through the number of lanes). All cars race once per round. They continue to race in subsequent rounds until they exceed the elimination threshold. Filler cars are used to round out those "odd" car heats to maximize the fairness of the points accumulated in each round.

RaceVIEW allows the committee to adjust the elimination threshold to tradeoff between maximizing the number of races for each car and minimizing the total time to run a Derby. Using the typical threshold value of nine, each car will race at least three times (on a four lane track). Rounds are run until the number of remaining cars is less than or equal to the number of lanes. At this point, the cars with the lowest point totals become the finalists. A single sudden death run-off race may be required to break a tie, which is handled automatically by RaceVIEW.

Finals Phase (prev) (next)

The Finals Phase consists of a single round of races among the finalists. In this round, the finalists compete directly against each other for the title of champion. Each car races once in each lane. This ensures that no car receives the real or perceived advantage of racing in the “fast lane”. The car with the lowest point total for these final races is declared the Champion for that division!

Results Storage (prev) (next)

RaceVIEW stores the results of each race in a tab-delimited ASCII file (it's stored in YourDerby/Results-text/YourDerby.rs1), which you can open in a program such as Microsoft Excel. If you are using a serial timer, then the elapsed times for each car is stored, along with lane assignments and finish orders. This file also includes detailed time stamping, which can be used to help plan next year's Derby. A separate file contains the names of the Finalists, in finish order (the *.ch1 file). Finally, a log file (*.lg1) which contains useful summary start and stop times for each round and division is kept to help you plan next year's Derby. Detailed timing on each race can be found in the *.rs1 file.

Derby Finals (prev) (top)

RaceVIEW provides for a Derby Finals. The committee can choose to allow one to four of the finalists from selected Divisions to compete in this finals. RaceVIEW will automatically add their names to the Finals registration. If there are more racers than lanes, the Derby Finals will be run in the same manner as any other Division; that is, with Elimination and Finals Phases. If the number of finalists is equal to or less than the number of lanes, then RaceVIEW will simply run a Finals Phase.

See the Sample Derby Summary page for examples showing how many races were run, elapsed time and other statistics.

System Requirements (prev) (top)

The minimum hardware and operating system requirements for RaceVIEW are:

Operating Systems :	Windows95/98/NT 4.0 and Windows XP
CPU :	Pentium or equivalent
RAM :	16 Mb minimum, 32 Mb recommended
Hard Disk :	16 Mbytes
Monitor :	640x480 minimum, 256 Colors

"Satisfaction Guaranteed"
Return for Refund within 30 days if not fully satisfied
"RaceVIEW Refund Policy