For a participant
Signing in, getting into an activity, sending a solution, and reading what came back.
You are here to take part in a contest or a course, not to run one. These pages cover exactly the screens you can open.
In a hurry
| You want to | Read |
|---|---|
| get in at all | Signing in |
| open an activity from inside your course | Arriving from your course |
| find your contest or course, or join one | Activities |
| read the regulations, where the organiser published any | Rules |
| know why a round shows nothing | Rounds, weeks and classes |
| read a problem, or find out why Submit is greyed out | Problems |
| send a solution | Sending a solution |
| find out what happened to one | What happened to my submission |
| get your code back, or fix and resend it | Your source code |
| see where you stand | Ranking |
| ask the organisers something | Questions and announcements |
The shape of it
An activity is one contest or one course. Inside it are series — a contest calls a series a round, a course calls it a week or a class. Each series holds problems. You send a submission to a problem, a Runner evaluates it, and a result comes back.
Everything you do happens inside one activity. The navigation on the left changes when you enter one, and what it offers depends on what the organiser switched on.
Two things worth knowing before a contest starts
Problems open at a moment, not when you refresh. The screen updates itself when a round opens, is paused, or ends. You do not have to reload.
Three kinds of problem ask for three different things. One takes a program, one takes a program and sends it to an external archive, and one takes answer files and no program at all. Which one you are looking at decides what the submit form shows you. See Sending a solution.