Here is the purpose of this tool:
Because a good director of flights is not necessarily a computer guru, he can renounce to organize a competition when the difficulties to manage the participants and scores emerge.
That is why this tool was created.
Anyone can create and organize a competition on Condor Club easily in minutes and then focus on creating interesting tasks. The whole administrative part is managed by Condor Club. The organizers just have to run one or more servers to host tasks (except of course for offline competitions).
After each flight, participants send their flight track(files. FTR) to the site for analysis and then are scored according to parameters defined by the organizer.
You know how to create interesting tasks? You can host a race in good conditions? This tool is for you!
Thus, each of us can create his competition (provided, however, to be serious when creating tasks and during the organization).
When creating a competition, you can:
- Define whether the competition is in individual or with teams (see below)
- Define whether the competition is off-line (the flight plan is sent to participants) or uses one or more servers
- Choose the method of global ranking
- Define the number of tries by race
- Define the policy to apply in case of crash / landing out/ missing FTR (0 points, suspension for n days, ignore)
- Define whether server(s) is (are) protected with a password
- Determine the number of timeslots (Max 24) per day of competition and the maximum number of pilots per slot
- Add organizers to share management
- Definie one or more hosts for each slot
- Fix the cost of registration (free / pay / free scoring but paying) and your Paypal account
- Define the maximum period to send the FTR
- Add a link to website / forum
- Add a logo
Once created, you can add tasks that are either training day, or day of competition at your convenience.
Note that minimum 2 tasks are needed to enable competition and make it visible.
Each task can be a speed race or Assigned Area Task (AAT). You can set the date of each race (time will be the same as that defined when creating competition).
To group comments, you can define for each task address of the forum where a topic is open on this day of competition.
Note you can add tasks at any time, but preferably at least 24 hours before the race.
24 hours before the start of the race, an email containing instructions for server parameters (including the password) and FPL is sent to all hosts. Passwords are generated automatically by Condor Club, for each task and each slot.
2 hours before the start of the race (or slot), a briefing is sent to the participants with a link to the detailed task.
At the end of the day of competition, an email is sent to participants and organizers to announce the availability of results, which were hidden until then.
The organizer has access to an overview of the participants and can manually manage the status of the pilot (suspension, banishment, payment of registration, ...), remove a result, send an email to a pilot or to a team or to all participants.
The tool can also be coupled with DSHelper. Thus, each server sends its results after every race so you can perform cross-checks (for example, verify that a pilot has not made more attempts than authorized or has not cheated by comparing the results of the server and those contained in FTR).
This package makes it virtually impossible to cheat during online competitions.
Another advantage is that all the sceneries can be used for the competition; flight records are not converted to be sent to Seeyou but managed natively, so there is no problem of calibration.
A word about teams:
The management of teams in Condor is very limited (only choice of color). That's why I created this independent and simple solution, which does not require any particular action in Condor. The organizers set the maximum number of team and the minimum / maximum members.
Concerning the score, the choice is offered between the average of N first pilots, the average of all pilots or retain score from nth pilot.
The creator of a team can restrict registration by a password, choose the skin of the glider team and add a link to a website and / or forum.
The "team flying" on several slots is possible. On receipt of a FTR, Condor club knows in which team is the pilot and grants points accordingly.
To do list:
- unsubscribe a participant
- The scoring of a team in which there is no quorum
- Sending a file via FTP to hosts to configure and start the server automatically
- The ability to manage automatically competitions'payment
I just have a look on my code I written for Condor Club, I impress myself:)
- 3 MB of source (about 65000 lines), equivalent to a 1500 pages pocket book!
- The size of text for each language corresponds to a book of 100 pages!
That is, who will be the first to launch a competition?