Challenge Overview
Introduction
Welcome to our second Rapid Development Match Practice Challenge!!
Each match has three (3) problems: easy, medium, and hard. Points will be allotted to each problem depending on difficulty.
Learn More Competition FAQs and Rules
Interested in writing problems for RDMs? Read More
Match Schedule and Phases
Registration Phase: Jan 13, 2021 - Ongoing
Submission Phase: Jan 13, 2021 - Ongoing
Final Testing Phase: Testing as soon as you submitted.
Leaderboard
Individual problem scores will be available on the respective problem scorecards. Here is the consolidated Match Leaderboard
Prizes
Match Prizes
No prize is available for the practice challenge.
Scoring
The submissions in an RDM are reviewed by an automated review scorer as soon as you submit your submission. The point value of submission is going to be a product of your submissions Test Case Accuracy and a Decaying Time Component.
The Test Case Accuracy is nothing but the ratio of Test Cases your submission passes to the Total Test Cases used for that problem.
The Decaying Time Component is dependent upon the problem’s level of difficulty and the time it took to submit a submission. The Topcoder server will calculate the time spent on a problem by counting the time between the match’s start time and when a submission is submitted on that particular problem. Keep in mind that these times are captured when a problem request or problem submission actually gets to our server, so network latency may play a minor role in the competition process.
Total points awarded =
TotalPassingTestCases is the total number of test cases your submission successfully passes
TotalTestCases is the total number of test cases set for the problem
PassedTime is the time elapsed between match start time and submission time in minutes.
TotalTime is the total time allocated for coding all problems in minutes, and
MaxPoints is the maximum points available for that problem.
For example:
A coder spends 22.7 minutes working on the medium problem before submitting and his submission passes 6/7 test cases defined in the problem statement. Given the fact that the total match is one hour, and the maximum point value for the medium problem is 500, the coder’s awarded points for the submission will be:
(6/7)(500(.3 + .7*602/(10*22.72+60^2)))
or
251.95 points (point calculations are rounded to two decimal places)
Judging Criteria
Each problem will have a set of requirements to achieve and instructions around what is expected from you. Sometimes the technology and/or language and/or platform to use will also be specified. The requirements will be simple and straightforward to understand. Also all for all the problems you would be provided with a sample submission to start with.If your submission achieves the requirements you are able to get the score you received based on the scoring formula mentioned above and in detail here.
After the submission phase, a final review would be done to check any cases of Code Obfuscation and Collaborating/Cheating, and incase found your submission will be rejected and your score would be updated to zero for that particular problem.
Minimal code quality is expected for the reviewer to review the submission and go through your code.
- Obvious and deliberate Code Obfuscation will be rejected.
- Collaborating/Cheating in any way with anyone else (member or not) during a rated event is considered cheating.
- An excessive amount of unused content should be avoided.
- Code readability is expected with necessary comments, indentation, and somewhat refactored code (as much as possible).
Problems
Easy: https://www.topcoder.com/challenges/30162204Medium: https://www.topcoder.com/challenges/30162208
Hard: https://www.topcoder.com/challenges/30162209