Run It Code It
 | This page is incomplete. |
| Run It Code It | |
|---|---|
| Type | Inquiry |
| Category | Lab |
| Description | Teams will run a given compiled program and recreate it |
| Event Information | |
| Participants | 2 |
| Approx. Time | 50 minutes |
| First Appearance | 2022 |
| Official Resources | |
| Division B Website | www |
| Division C Website | www |
Run It Code It is a trial event being run for Division B in the 2022 season in Southern California.
Event Parameters
Teams may not bring any materials or resources. Event Supervisors will provide one internet-connected computer per team and the compiled program to be recreated. Event Supervisors are encouraged to provide access to the compiled program only available through a web terminal. Participants will be allowed to access the internet and may use any code publicly available online. Accepted programming languages in which participants can program will be announced by the Event Supervisor no later than two month before the tournament. Event Supervisors are highly encouraged to use the latest version of C++, Java, and Python 3.
The Competition
The Event Supervisor will provide access to the compiled program at the beginning of the 50 minute period. The compiled program will have multiple functionalities and will accept input and display the corresponding output. Teams must not have access to the source code of the compiled program. Participants will have the 50 minutes to run the compiled program any number of times and use an online IDE (such as replit.com) to write a single program in one file to recreate the compiled program. At the end of the 50 minute period, teams will submit their program as source code (.cpp, .java, .py, etc.). All input and output to the program must be through the standard streams (stdin and stdout, respectively).
Scoring
All teams must be scored using an identical scoring rubric, containing the following weighted sections:
- Functionality (90%): Each functionality of the program will have a predetermined point value, which will be the same for all teams but will not be announced to participants at any point.
- Documentation and Style (5%): The program should include documentation for all major functions, variables, and non-trivial algorithms and have a consistent style with proper formatting, indentation, and other white space to aid readability.
- Modularity (5%): The program should use good modular design, separating the functionality of the program into coherent and reusable functions, classes, or objects.