Topcoder Open: Difference between revisions

Revision as of 21:39, 10 July 2018

Revision as of 18:36, 25 July 2018

Line 17:

Competition tracks included in Topcoder Open tournament changed through its history. Many of them resemble the types of challenges offered to [[Topcoder#Topcoder Community|Topcoder Community]] through the year, but there is no 1:1 match. Here is the alphabetical list of all competition tracks ever present at TCO:

=== Algorithm CompeitionCompetition (SRM) ===

'''Timeline:''' ''2001 - nowadays''

Line 26:

The only track that was present at all main TCOs events, and at the most of other Topcoder events. Follows the format of regular 1.5 hours Single Round Matches:<ref>{{Cite web|url=https://help.topcoder.com/hc/en-us/articles/115006162527-SRM-Overview|title=SRM Overview|last=Sial|first=Rashid|date=April 25, 2017|website=Topcoder Help Center|archive-url=|archive-date=|dead-url=|access-date=April 23, 2018}}</ref>

* ''The Coding Phase –'' 75 mins'':'' All competitors are presented with the same three algorithmic problems of different complexity, each problem has its own maximal number of points. Problem descriptions are initially invisible. Competitors have 75 minutes to solve these problems. Competitor can open any problem description in any order; once he opened a problem, the number of points he can get for the correct solution of that problem starts decreasing over time. When competitor submits problem solution (a code that successfully compiles), he is awarded with the current amount of points he can get for that problem. He can re-submit a solution, getting the further descreasedecrease amount of points, minus extra penalty for the resubmission. During the phase competitors can see the current points awarded to each participant, but they don't know whether solutions of those participants are correct or wrong, thus whether these scores will hold after ''The System Testing Phase'', or will be reset.

* ''The Challenge Phase'' – 15 mins: Each competitor can see all submission done by other competitors. He can (optionally) challenge any of them, submitting test cases that will cause other competitor's submission produce a wrong result. Submission of correct challenge test case gives sumittersubmitter 50 points award, submission of an incorrect test case (i.e. the challenged solution can solve it successfully) will lead to 25 points penalty for the test case submitter.

* ''The System Testing Phase'' – In the last phase system tests are automatically executed for all submissions from all competitors. If a submission fails testing, the scores awarded for that submission during ''The Coding Phase'' are reset to zero. The final scores after the system testing determine the winner.