This document gives a functional / technical description of the Ariadne
(canoe/kayak) competition administration software.
Ariadne pre-competition |
|
Slalom |
Mara thon |
WW race |
Regatta |
Web entries |
|
Initialization of the system at start
up, refreshing links to attached databases |
X |
X |
X |
X |
X |
|
Loading the main menu |
X |
X |
X |
X |
X |
|
Displaying copyright and license information |
X |
X |
X |
X |
- |
|
Subform Remarks, which is linked in more
forms |
X |
X |
X |
X |
X |
|
Subform Addresses, which is linked in
more forms |
X |
X |
X |
X |
|
|
Competition statistics |
X |
X |
X |
X |
|
|
Maintenance of persons data |
X |
X |
X |
X |
|
|
Displays archived results of competitions,
normalized against a ranking scale |
X |
X |
X |
X |
|
|
Displays and resolves multiple records
for persons |
X |
X |
X |
X |
|
|
Sets the age class according to the year
of birth |
X |
X |
X |
X |
|
|
Maintenance of club data |
X |
X |
X |
X |
|
|
Maintaining categories |
X |
X |
X |
X |
X |
|
Report of available categories |
X |
X |
X |
X |
|
|
Competition organizing club data |
X |
X |
X |
X |
|
|
Competition settings |
X |
X |
X |
X |
|
|
Set and refresh the links to the current competition and the archive database modules |
X |
X |
X |
X |
X |
|
Initialization (removal) of run results and entries |
X |
X |
X |
X |
|
|
setting of the COM-port for the startpost device |
X |
X |
X |
X |
|
|
AWE Ariadne Web Entries table initializations |
|
|
|
|
X |
|
Setting available and missing start numbers |
X |
X |
X |
X |
|
|
Mailinglist and address labels for inviting
clubs for the new competition |
X |
X |
X |
X |
|
Ariadne Competition planning |
|
|
|
|
|
|
|
Entry input on a per person basis |
X |
X |
X |
X |
|
|
Entry input on a per club basis |
X |
X |
X |
X |
|
|
Overview of clubs which submitted
entries, plus their contact persons |
X |
X |
X |
X |
|
|
List of entries per club and know
officials |
X |
X |
X |
X |
|
|
Report of entries per category |
X |
X |
X |
X |
|
|
Select / add person to be a participant
in an entry |
X |
X |
X |
X |
|
|
Entry input form |
X |
X |
X |
X |
|
|
Entry input on a per root race |
X |
X |
X |
X |
|
|
List with entries alphabetical on person |
- |
X |
- |
|
|
|
Export an xml file with competition data, program blocks and races |
X |
X |
X |
X |
|
|
Setup and maintenance of races |
X |
X |
X |
|
|
|
A check form that shows categories with entries, which categories have not been assigned to a race |
X |
X |
X |
X |
|
|
A form to split or merge race |
X |
X |
X |
|
|
|
Initialization of ranking per competing
unit on basis of archived rankings |
X |
X |
X |
|
|
A220-Allocating Series |
Allocating competing units to series per race |
|
|
|
X |
|
|
Dividing competition into program blocks |
X |
X |
X |
X |
|
|
Set of consistency checks on entries, categories, classes, races |
X |
X |
X |
X |
|
A240-Program block - races |
Races per program block |
- |
- |
- |
X |
|
|
Lists participants which have entries
for more races in the same program block |
X |
- |
- |
- |
|
|
A start list of competing units, sorted
to race and ranking |
X |
X |
X |
- |
|
|
Definition of gates in the slalom course
and assigning them to gate sections |
X |
- |
- |
- |
|
|
Definition of gate sections, and assigning
the section judge |
X |
- |
- |
- |
|
|
Report supporting the assignment of gate
judge tasks to clubs |
X |
- |
- |
- |
|
|
Mailing of entry confirmations |
X |
X |
X |
X |
|
|
Entry confirmations per club |
X |
X |
X |
X |
|
|
Producing address label for entry confirmations
per paper mail |
X |
X |
X |
X |
|
|
Produces emails with entry confirmations |
X |
X |
X |
X |
|
|
Checklist for the sending of entry confirmations |
X |
X |
X |
X |
|
|
Automatically assigning start numbers |
X |
X |
X |
X |
|
|
Startlist for the competition program |
X |
X |
X |
X |
|
Ariadne Competition operations |
|
|
|
|
|
|
|
Scheduling of races into time tables |
X |
X |
X |
X |
|
|
List with distribution of start numbers
to clubs |
X |
X |
X |
X |
|
|
List with allocation of start numbers
to participants/ clubs |
X |
X |
X |
X |
|
A343-Entries to participant |
List of entries alphabetically ordered to participants name |
- |
X |
- |
- |
|
A344-Buoy-rounding-checklist |
List with participants per distance |
- |
X |
- |
- |
|
|
Prints entries on labels. Used to stick
on the start number signs |
- |
X |
- |
- |
|
|
Control form for the production of entry
fee invoices |
X |
X |
X |
X |
|
|
Invoices per club for the entry
fees |
X |
X |
X |
X |
|
|
Checklist for the generated invoices |
X |
X |
X |
X |
|
|
Setting of the entry fees per race |
X |
X |
X |
X |
|
|
List of entry fee per entry |
- |
X |
- |
- |
|
|
Labels for the distribution of startbib packages |
X |
- |
- |
- |
|
|
Present results for promoting CU's to a x-finals |
X |
X |
X |
X |
|
|
A method of composing teams on basis of individual resuls |
- |
- |
X |
- |
|
A420-Start schedule |
Start Schedule of group starts |
- |
X |
- |
X |
|
|
Startlist with late entries and cancellations |
X |
X |
X |
X |
|
|
Displaying and editing of competing unit
data (=entry data) |
X |
X |
X |
X |
|
|
Set abnormal runstatuses: DNF, DSQ, or
set these back to normal. |
X |
X |
X |
X |
|
|
Gives sorted list of improvements runtimes
current competition vs archived competitions |
- |
X |
- |
- |
|
A443-NES-Racepoints |
Reports race points calculation for NES Challenge |
X |
- |
- |
- |
|
|
Viking specific calculation of team results |
- |
- |
X |
- |
|
|
Produces a mail list to send results to
participants |
- |
X |
- |
- |
|
|
Swaps runs between two competing units |
X |
X |
X |
X |
|
|
Swaps bib numbers between two competing units |
X |
X |
X |
X |
|
Ariadne Race Processing |
A400-Race scheduling, A500 results collection, A600 results publishing |
|
|
|
|
|
|
Triggers the run event processing |
X |
- |
X |
X |
|
|
Record starts (Marathon and Regatta) and assign the start to races |
- |
X |
- |
X |
|
|
Shows the events for a start |
- |
X |
- |
X |
|
|
Processing start- and finish events slalom |
X |
- |
- |
- |
|
|
Processing start- and finish events from backup timing slalom |
X |
- |
- |
- |
|
|
Records finishes for Marathon, by PC, by Timy or by Hand |
- |
X |
X |
X |
|
A553-Timing events assignment |
Form view which timing events are assigned to which start number |
X |
X |
X |
X |
|
A555-Timing events swap |
Swap the timing events assignment of two competing units |
X |
X |
X |
X |
|
|
Processes Timy timing messages over serial port |
X |
X |
X |
X |
|
A570-Running time from start |
Displays running times from start (marathon) |
- |
X |
- |
- |
|
|
X |
- |
- |
- |
|
A585-Penalty points processing |
Processes the penalty points from gate judgements to the Ariadne database |
x |
- |
- |
- |
|
A588-Penalty points check |
Screen to check the penalty points against the judge scoring papers |
X |
- |
- |
- |
|
Ariadne Results publishing |
A400-Race scheduling, A500 results collection, A600 results publishing |
|
|
|
|
|
|
Shows running time during run and run results at finish |
X |
- |
- |
- |
|
|
Presentation of last 20 results on publication screen |
X |
X |
X |
X |
|
|
Race results printout |
X |
X |
X |
X |
|
A652-Holland Cup export |
Results export for Holland Cup ranking |
X |
- |
- |
- |
|
Ariadne System |
|
|
|
|
|
|
|
Function to retrieve messages from a table |
X |
X |
X |
X |
|
|
Transaction routing function to route
transaction between forms and or reports. |
X |
X |
X |
X |
|
|
Maintenance screen for the menu tables |
X |
X |
X |
X |
X |
|
Module to translate the GUI to another
language |
X |
X |
X |
X |
|
|
module to open a html help page of a specified
page id |
X |
X |
X |
X |
|
Ariadne Archive |
|
|
|
|
|
|
|
Archiving of persons, clubs, categories,
results |
X |
X |
X |
X |
|
|
Determines the start interval per category
on basis of the actual starts of the current competition |
X |
- |
- |
- |
|
|
|
|
|
|
|
|
All objects in then design are prefixed with a letter and a three digit
number:
For practical reasons, and where possible, there is some correspondence
between numbers. Q200-Persons is a query on table T200-Person, for the
form F200-Persons. This correspondence is however not strict.
Apart from the numbers used in database obects, the functions are numbered
(with prefix 'A'). In general the function numbers have an order as they
appear in the menu. Also this numbering is not strict. And there is no
correspondence between the function numbers and the object numbers.
1. To make a distinction between form field which are editable and which
are not, non-editable field appear with a grey back ground, where editable
fields have a white background.
2. Non-editable fields which have a related button with which you can
jump to a form on which these fields can be edited, also have a white
background.