खोज के नतीजे
Problems are added to a contest from the space's problem library, on the contest's Problems tab. A contest problem is a separate thing that references a library problem: statements, tests, limits, checkers and code templates all stay on the library problem, and the contest keeps only its position, its attempt limit and its scoring switch.
There are two ways into a contest: an organizer adds someone, or the person joins by themselves because the contest's visibility lets them. Most contests use both — the roster is seeded with the people who must be there, and everyone else registers.
Finalizing declares a contest's results final. It fixes the standings, freezes the medals each participant holds, issues certificates where certification is configured, and sends the result notification where that was enabled. From then on the console stops offering any edit that would move an official participant's result.
The Scoreboard tab is the ranked table of a contest's participants: one row per participant, one column per problem, a total, and a rank. It is built from the submissions recorded in the contest, in the shape the contest format dictates, and clicking a row opens that participant's page.
A contest scoreboard covers one contest. For a standing that spans several (a season table, a multi-day olympiad, a league) you create a scoreboard: it adds several contests together into one standing, keyed by space member, so the same person appearing in five contests is one row rather than five.
A series is a named grouping for contests — a recurring olympiad, a weekly training round, a school league. It is one of the classification facts a contest carries, and it is the one that makes a set of contests findable as a set: the contest list filters and sorts by it, and the public contest page shows it.
When a participant may work, and for how long, comes from three places: the contest's schedule, its duration in virtual mode, and the extra time granted to one participant. The schedule is on Settings → General; extra time is on the participant's own page.
A violation is a record that a participant may have broken the rules of a contest — a solution copied from someone else, code the participant did not write, or a way of working through the round that does not look like solving problems unaided. Every contest has a Violations tab holding them.
Copilot is an assistant that works inside the console with you. It answers questions about Eolymp, looks things up in your space, and — once you allow it — makes changes: creating a contest, adding participants, replying to a question, writing a problem's statement or its tests.
A course is a syllabus with a gradebook. It holds material a member works through at their own pace — explanations to read and problems to solve — and every task they solve feeds a grade. Where a contest is a timed event that ends in a scoreboard, a course stays open as long as you leave it open, and what it produces is a grade per student.