Each team member should choose one and only one at-home (or what you consider home for this contest) computer for problem set development and submission. Contestants can use native software development tools, and/or the virtual appliance. The computer hosting the virtual appliance is considered the same workstation as the appliance.
Each team will be assigned a common DOMJudge username and password. Each member of the team will use a web browser to connect to the DOMJudge contest environment.
Each team member will be assigned a unique Zoom username for
Please download and read the Team Manual for information on how to use the DOMJudge interface.
If you have any questions about the Contest Environment, send them to <email@example.com> .
For more information regarding UNIX or the editors that will be available, see our Guide to UNIX and Editors.
Problem subissions will be compiled and executed in the following environment.
The judges accept problem submissions only in the following programming languages.
|Java||openjdk 11.0.10 with the standard OpenJDK library|
|Python||Python 3, version 3.9.1, standard release, no external libraries|
The execution time limits set for each problem will NOT be scaled based on the language. It is the contestants' responsibility to select the appropriate tool (language and algorithm) to produce correct output within the allotted time limits.
Programs will be compiled and linked using the Standard C++ Library included by default with g++.
Regional judges will accept solutions coded in Python 3.
After you have submitted a source file for judging, your submission will be run with one or several sets of input data and the results reviewed. It is the judges' intent never to reveal directly or indirectly the specific input data the judges use to test contestant programs. The judges will respond to your submission with one of the following messages. If a submission contains more than one type of error, the response will still contain only one message. The judges will report only the first error seen, which may not necessarily be the error that occurs first or most frequently in the output.
You have solved the problem.
The judges were unable to compile or link your program. Check whether
No expression or line number information will be returned to contestants.
Your program crashed during execution or an assertion failed. In the former case, the judges' response will also include a description of the signal received by the program, e.g., "Segmentation Fault." If an assertion failed, the message will state, "Assertion Failed." In neither case will expression, file, or line number information be returned to contestants.
Your program ran for more than the allotted CPU seconds.
Your program did not produce the expected results.
Although we do use robo-judge where possible, we verify every response before returning it to the team to ensure accurate, quality responses. The effect of this is that, depending on solution traffic and other factors, it may take longer to respond.