खोज के नतीजे

Testsets are groups of test cases that help organize the problem's testing into sub-tasks, each with its own scoring rules and constraints. For instance, you might create a basic testset to check simple functionality and another more advanced testset for edge cases or larger inputs. Each testset can have unique time, CPU, and memory limits, tailored to the task.

Spaces are shared accounts where users can publish problems, contest and manage members. You can organize spaces around competitions, problem archives, classes where you teach, etc.

Quota of resources is a limit on the amount of resources (competitions, participants, tasks, etc.) in space. When the quota is reached, you will not be able to create additional resources of the appropriate type.

You can try our system, free of charge, for 30 days. During this period, you will be able to try all features of the platform and evaluate if it fits your needs. Please, keep in mind that some conditions apply,

The console is where you run your space: you create problems there, set up contests and courses, manage the people who take part, and publish the pages your participants read. Everything you do in the console shows up on your space's own website, which is what participants see.

The activity log is a feed of what people have been doing in your space — problems solved, contests joined and finished, comments posted, achievements earned, members arriving. It's on the dashboard as Recent Activity, and See all opens the full list at , newest first.

Automation makes your space react to events on its own. You write rules, and each rule runs whenever something happens — a submission is judged, a contest is finalized, a new member joins — or on a schedule, every hour or every day. Instead of watching for those moments and acting by hand, you describe once what should happen.

Every run of a rule is recorded in the Logs tab, with every message and every operation its actions produced. A rule whose conditions did not match is the exception: it did not run, so it leaves no log entry and its Executions count does not move. That single fact separates most of the cases below.

A script is one of the two kinds of action an automation rule can take. When the rule fires, the script runs once, with the data of the event that triggered it, and calls platform functions directly. Scripts suit fixed, predictable steps — award an achievement, move a member into a group, set a medal — that should run the same way every time.

71-80 of 216