Domain
A domain is an isolated space, typically one per institution. It holds its own problems, assignments, contests, trainings, discussions, members, and roles.
Whether a domain is public or private is controlled by its roles and their permissions.
The default domain is system. Visiting MyCode without a domain path opens it, and the logo always links back to it.
Data in one domain is not visible from another unless an administrator explicitly shares it.
Compilers' Version and Parameters
MyCode judges submissions in an isolated sandbox. The compiler versions and compile options for each language are listed on the status page.
Limitations
Time usage is measured as the CPU time of your process. The limit is the one set for each test case of the problem.
Memory usage is measured as the peak memory of your process. The default limit is 256 MiB unless the problem states otherwise.
IO
Unless the problem states otherwise, read from standard input and write to standard output.
Judge Status
- Waiting Queued: waiting for a judge worker to pick it up.
- Fetched In progress: a judge worker has taken the submission and is preparing.
- Compiling In progress: compiling.
- Judging In progress: compiled successfully, running test cases.
- Accepted Passed: output is correct.
- Wrong Answer Failed: output differs from the expected answer (trailing spaces and trailing blank lines are ignored).
- Time Limit Exceeded Failed: the program ran longer than the time limit.
- Memory Limit Exceeded Failed: the program used more memory than the limit.
- Output Limit Exceeded Failed: the program produced too much output.
- Runtime Error Failed: the program crashed (for example out-of-bounds access, division by zero, stack overflow, invalid pointer) or exited with a non-zero code.
- Compile Error Failed: compilation failed.
- System Error Error: an internal judging error. Please report it to your administrator.
- Canceled Other: judging was canceled.
- Unknown Error Other: unknown error.
- Ignored Other: ignored.
A record marked as cancelled was manually voided by an administrator, for example because it broke academic-integrity rules.
Compile Error
Common causes:
- 1. The wrong language was selected when submitting.
- 2. In Java, the public class is not named
Main.- 3. C/C++ specific issues (see below).
- 4. Ordinary syntax or type errors.
Notes for C/C++:
- 1. Use
long longinstead of__int64with GNU C++.- 2.
main()must returnint, notvoid.- 3. A loop variable declared as
for (int i = 0; ...)is not visible after the loop.- 4.
itoais not a standard C/C++ function.- 5. Use
%f, not%lf, to print adoublewithprintfin strict C89.
Training
Trainings are curated learning paths of problems. Open "Training" in the navigation bar to start one.
Contest
Submission and ranking rules depend on the contest format.
In IOI, ICPC, Ledo and IOI (Strict) formats you may submit a problem many times and see results immediately.
In IOI, ICPC and Ledo formats the scoreboard is visible during the contest.
In OI format only your last submission for each problem counts, so avoid compile errors.
OI ranking: higher total score ranks first; equal totals share the same rank.
In ICPC format each rejected submission adds a 20-minute penalty to that problem.
ICPC ranking: more solved problems ranks first; ties are broken by lower total time including penalties.
In Ledo format repeated submissions reduce your score; the scoreboard shows your best score.
In Ledo format the score for a problem is $s \times \max(0.95^{n}, 0.7)$, where $s$ is the submission's score and $n$ the number of earlier attempts.
Ledo ranking: by the adjusted total score, highest first.
In IOI(Strict) format a problem's score is the sum, over subtasks, of your best score for each subtask across all submissions.
Time and memory limits are given in each problem; see Limitations for defaults.
Accepted Ratio
The accepted ratio is the share of submissions to a problem that were accepted. It is only a rough guide to difficulty.
RP Algorithm
Rating points (RP) are earned by solving problems and taking part in contests and other activities.
Difficulty Algorithm
Problem difficulty in MyCode is calculated from the number of submissions, the acceptance rate, and the time and result of each submission.
Keep in mind:
- 0. A higher number means a harder problem.
- 1. Difficulty for new problems is unreliable until they have many submissions.
- 2. Earlier submissions influence the difficulty more than later ones.
- 3. The value is computed automatically and may be inaccurate.
Dataset Format
Test data is uploaded as files on the problem's Files page, with an optional config.yaml describing subtasks, scores, limits, and checkers. See the Faculty Manual for the full format.
Forgot Password and/or Username
If you cannot log in, first check that you are using the right username. It may differ from the one you intended if that name was already taken.
If you have forgotten your username or password, or think your account is compromised, Reset Password or Find Username right away.
Markdown
Text areas in MyCode use CommonMark with these extensions:
- Math formulas in KaTeX syntax.
- Mention a user with
@[](/user/uid). - Highlight text with
==text==. - Set an embedded image's size with
. - Embed a video file with
@[video](https://.../a.mp4). - Embed a YouTube video with
@[youtube](VIDEO_ID). - Embed a PDF with
@[pdf](https://.../a.pdf). - In problems, contests, assignments, and trainings, link an attachment with
file://filename(recommended). - A safe subset of HTML tags.