Search results
A problem prepared in Polygon is imported into your space from its package link. Most of the work happens on the Polygon side: the package has to exist, and the user has to be allowed to download it.
A problem in one of your other spaces can be copied into this one. Spaces are otherwise separate, and this is the way a problem crosses between them — the copy becomes an ordinary problem of the receiving space, editable and independent of the original.
An interactor is a program that talks to the participant's solution while it runs. Rather than handing the solution a static input file, the interactor starts on every test just before the solution does, with the two processes' standard input and output wired to each other: whatever the solution prints, the interactor reads, and whatever the interactor prints goes to the solution's input.
Every problem has an issue tracker of its own: bad tests, statements that contradict themselves, a checker that rejects a correct answer. Issues are filed on the problem's Issues tab, by console users and by members or testers of the space, and they change nothing about the problem — they are a to-do list attached to it.
Publishing puts a problem in your space's public catalog, where participants can find it and solve it. Until then it exists only in the console: problems you create and problems you import both start unpublished.
A quiz is a problem answered on the page rather than with a program. The participant reads the statement, answers a set of questions — picking options or typing a short answer — and submits. The submission is graded straight away, with no tests, no checker and nothing compiled.
A reference solution is a program kept with the problem that declares what should happen when it is judged: this one must be accepted everywhere, that one must time out, this other one must give a wrong answer. Running them is how you find out whether the problem's tests and limits do what you think they do — whether the intended solution fits inside the time limit, and whether the naive one really doesn't.
The statement is what a participant reads: the task, its constraints, the input and output formats, and worked examples. A problem can have a statement in as many languages as you like — one per language — and participants get the one matching their language.
A stress test hunts for the test you didn't think of. It runs one of your generators over and over with random arguments, and on every input it produces it compares your solutions against a reference one. The moment a solution does something its declared type does not allow, the run stops and hands you the exact generator command that produced the input.
The Studio is a full-screen editor for a problem's programs and tests. Instead of opening the checker, a generator and a solution one page at a time, you open them side by side as tabs, change one, run another against a test, and see the result without leaving the screen.