RACE TP Interface
If you got new pilot entries during the day, first enter them as pilots in RACE
before creating the task. In case you have to add pilots after a task got
created in RACE, use MS Access and add the pilot to the tblTaskResult.
Create a TASK first in RACE before creating a task in TP. To provide the correct
Task ID.
In RACE do not provide any radius info. RACE has a bug and can not calculate the
distances correct. Besides getting the value correct into RACE.
If Launch or a Turnpoint is SS, define it once with a default 0 radius and mark
it as SS.
Turnpoints from TP to RACE
In the csv file make sure each turnpoint has a unique ID and a unique
Description. RACE does not like 2 turnpoints and both are called Intersection.
Then use the RACE / xxx.csv>RACE to transfer the turnpoint info into
RACE.
Choose the correct Region and then hit the transfer button.
RACE Bulk Data Interface
To match the pilot number used by TP with the database identifier
of each pilot used by RACE one has to create a cross reference file called
pilnrid.csv.
If the RACE database is not located on the same computer as TP
then use the XML>Pilot_ID option to create the pilnrid.csv file is by
-
Load all pilots into RACE
-
xml export a task
-
Use in TP the RACE XML>PID menu function
-
select the xml file just created from RACE
-
press the click button in the window
-
a pilnrid.csv file gets created in the compdir
If the RACE database is located on the same computer as TP, ( the better
option ) then
-
Make sure in SETTINGS that TP knows about the correct RACE database that
is used
-
Use in TP the RACE DB>Pilot_ID menu option
-
the pilnrid.csv file gets created in the comp directory
Alternatively, if MS Access is available, export as CSV the PilNumber and
PilPk columns of the tblPilot table.
You need a PILNRID.csv file before you start scoring any tracks for
RACE!
The PILNRID.csv file has to be in the competition directory.
And copy the PILNRID.csv file to all the other PC's that
are used for scoring tracks.
How to make a bulk xml file with a days task results for RACE
Create and define the days task in RACE.
XML export the task.
Check with notepad or a browser what taskid and task name RACE
is using.
Make sure that the same TASK ID and task name is
used in the Settings for the days task.
Save the Settings, close TP, start TP, load the Task, check that the
Taskid and task name now match that of RACE
Then use in TP the menu RACE/RESET to create the header entry in the
RACE.xml file.
To test , in TP, select PilotData and Analyze some pilots.
Each Track Analysis adds a record to the RACE.xml file
Once finished, use in TP the menu RACE/BULK to create a TASKxSyyy.xml
file
Within RACE read the TASKxSyyy.xml file into RACE
BULK add an end of xml statement to the current bulk file.
To create a new bulk file use the RESET menu option.
RACE Export XML file for Task Definition
Instead of defining a task within TP, one can also read in an export
xml file from RACE.
-
Define the pilots and task in RACE
-
Export in RACE the task as an xml file into the RACE/DATA directory
-
In TP use Task Create and click on the GET DATA FROM RACE button
-
Select the xml export file created by RACE from the RACE/DATA directory
-
A new window appears, click on the .. Click to use ...
-
The task definition gets loaded into the Task Create window
-
Close the ..PARSE RACE XML window
-
to get the times visible, click again on the Get Data button, and cancel
and close the Parse Window
-
Now also the time and date info has been refreshed
( Grateful if someone can point out to me how to get the values refreshed
immediately)
Then one can Preview, and Save the task
But there is some info missing.
TP works on the basis that a SS can be anywhere and have a big
circle.
While RACE only works on turnpoints that have to be reached.
So, add any extra info which was not available from RACE.
Possible problems
With the Direct RACE Interface
One can also use a direct database interface from TP to RACE.
I prefer the XML route.
The direct interface can have potential problems , like
-
if multiple copies of TP try to access the one database table, one can
get a locked table?
-
if, for whatever reason, one gets the task_id wrong, one can overwrite
a previous day and not score the current day
-
if there is a latecomer pilot, who has not been registered in RACE yet,
he does not get scored. One has to redo him later again.
-
If you loose a RACE task day, you have to manual rerun the direct interface
for all pilots. While with bulk, just suck in the xml again.
Possible XML problems
-
check the task id in the xml file to make sure it really is for the
correct task in RACE
-
hang on to old xml files, in case you loose a day in RACE you can
rebuild it from there
-
a latecomer pilot should not make it into an xml file. If he is there anyway,
with an unknown id for RACE, the bulk import will fall over.
Recommendation
Use the xml file approach, easier to restore/recover if you loose
some scores in RACE
GAP 2002 support
If you plan to use GAP 2002, download and score all the pilots. Bulk
XML them across to RACE. Then run the RACE/ GAP>RACE to feed the Lc factor to
RACE
Back to Index for TP Code