StageRace 2003 - Road Cycling Administration Help
border

Export Competitors for Omega Scan'O'Vision

Competitors can be exported from StageRace so they can be used in Omega® Scan'O'Vision.

Note that you can also import Scan'O'Vision files for ranking a stage.

Introduction

Omega® Electronics is part of the world famous watch manufacturer and is among other things specialized in the development of top-end equipment for sports timing.

One of Omega® Electronics' products is the Scan'O'Vision finish camera.

The StageRace program has been made capable to generate files for Scan'O'Vision.

Exporting

Under the name Data Handling, the Scan'O'Vision software works with a number of text files, which consist of competitors information and classifications. Data Handling files can typically be found in the \osvcolor\dh folder.

StageRace can generate all Data Handling files for an event.

In order to have StageRace generate such output files, the Export competitors for Omega Scan'O'Vision option in the Tools menu has to be chosen.

To configure the Data Handling in Scan'O'Vision, please refer to the appropriate documentation.

File Set-up

The following files will be generated:

  • LstCat.txt: list of categories
  • LstConc.txt: list of competitors
  • LstLong.txt: list of race lengths
  • LstNat.txt: list of nations or teams
  • LstRace.txt: list of events
  • LstStart.txt: list of starters
  • LstStyle.txt: list of race types
  • LstTitPr.txt: list of race names for printing

These files contain the entire event; ergo all stages. Furthermore there are five additional events foreseen, including all competitors, to be used for testing.

In the conversion from StageRace to Scan'O'Vision, the following translations apply:

 

In Scan'O'Vision

In StageRace

Nation

Team

Event

Full stage or day

Round

Half stage

Heat

No equivalent

All files together

Event

 

StageRace provides in the generated files a number of heats for every half stage, in case the photo finish operator needs to recover a finish.

 

Go top

Converted from CHM to HTML with chm2web Standard 2.8 (unicode)