I'm happy to see that the TORCS page view statistics on sourceforge has turned 1,000,000
Have Fun !
Purpose of this document: - Collect ideas. - Base for discussion. TODO: - Structure, formulations. - Joining the championship during the season? - Filling gaps with stock drivers? - ? - web-application. TORCS Endurance World Championship (Draft) ----------------------------------------- Goals: - Build up a TORCS AI racing community, enjoy the people. - Explore various ideas. - Fun. Overview: Welcome to the "TORCS Endurance World championship". The championship consists of races over ~500km on various suitable road tracks. The robots are rewarded with points for their rank in the races. Based on these results the standings of the driver and team championship are computed. To run the races TORCS-1.2.2 is used. There will be approximately one race every 3-4 Weeks. To avoid cheating every competitor is invited to run the races on his own system and submit the result to a web-application (name?). To get as much results as possible the submission is rewarded with points for the team championship. Parallel to the official championship there will be open preparation races to give you the opportunity to stabilize your code. Before all this actually can happen I need to develop/set up a web-application. To test it there will be a test-championship with 3 races to fix the rules, process and the application. "Gentlemen, start your processors." Process for the Championship (supported by web-application, TODO): ------------------------------------------------------------------ Phases overview: - Register as 'spectator' (web-application). - Move your account into a 'racer' account (web-application) . - Create your Team(s) (web-application). - Sign up the team for the championship (web-application). - Championship starts, ~every 3-4 weeks one race, a schedule will be prepared (TODO) - Tracks: ERoad, CG-Track-2, CG-Track-3, Spring, Wheel-1, Alpine-1, E-Track-1, E-Track-2, E-Track-3, E-Track-4, E-Track-6. - Race: Robot submission phase 1 week, race execution and result submission 1 week, 1-2 weeks break (-->open testing races). - Recommended: attend unofficial "test races" to discover/fix/avoid problems. Process for one Race (supported by web-application, TODO): ---------------------------------------------------------- Phases overview: - Robot submission. - Installation. - Running the race. - Submit the results. - The standings are computed. Detailed: - Submission: The team owners can upload their updated tar.bz2 of the robots during one Week. - Race preparation: The team owners willing to run the race download all robots and install them on their system and run an endurance race according to the official start list. - The team owners submit the result xml file, the submission is rewarded with 2 points for the team championship. If it owns more than one team, the team with the least points get the reward. (1 Week) - For every driver the median of the ranks of the submitted results is taken for the points, e. g. driver "d1" became 18,7,7,7,6 then the median is the 7 in the middle. If the number of submitted results is even then the median is the arithmetic mean of the two elements in the middle. Driver Point System: Rank : 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 Points : 18 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 - Why not FIA? --> Brain dead. It destroys gathered information below the 8th rank, but it is certainly better to become 11th than 17th, no? So we reward any place but the last. - No points for qualifying because the reward is the position in the starting grid. - Winning is good, so you get an extra point. Team Point System: - Sum of drivers points. - Additional 2 points per result submission to motivate for submission (max. 1 submission per race). Why the median: - With the median floor(n/2) of n (n odd) submissions can be cheated and the result is still reasonable. - The median is a measured result, not a "virtual" computed value. - Outliers (? measurements with outstanding error) do not harm like in the mean (e.g. arithmetic mean). Why distributed: - Avoid cheating. - Different binaries can end up in different results (no joke). - I want attend and you do not trust me:-) Inofficial Races: - To avoid compilation, runtime, etc. problems there is before (1-2 Weeks) the official race an inoffical open test race. Rules ----- The Rules over the Rules: - If problems with the rules are discovered they can become adjusted during the championship. - The updated rules are just applied to the upcoming races, the former results are not affected. - Changes are discussed via a forum or mailing list (TODO). - Rule changes are accepted or rejected via voting (poll), where every team owner has exactly one vote, independent how many teams it owns. - A rule change must get more than the half of all votes to become accepted. Technical Rules: TORCS: TORCS installation: - Vanilla TORCS-1.2.2 on Linux. - simuv2 is used. - If problems are discovered fixes might be applied during the championship. - The environment should be set up according to the robot tutorial ($TORCS_BASE, $MAKE_DEFAULT). TORCS runtime problems: - If TORCS is not able to run a race because of a TORCS bug the race is repeated after the last race of the championship but with the currently submitted robots. - Definition of "not able to run a race": More than the half of the competitors willing to run the race were no able to do so. This could be abused, better ideas? - If the problem becomes not fixed till the end of the championship the race is canceled. Robots/Robot Module: - The robot module name must consist of lowercase letters, followed by _2004 (^[a-z]+_2004$), e. g. "damned_2004" (-->portability). - The robots names are free but must not match one of the stock robots of TORCS 1.2.2 (-->parallel installation). - The robots module must be licensed under the GPL and must not contain any precompiled object files (-->system intrusion, cheating, copyright problems). - The robots code must not be obfuscated. - The robots must compile on g++ > 3.0 (namespace prefix,
Content received from: torcs, http://torcs.org