खोज के नतीजे

A code template is the starter code a participant finds already in the editor when they open the problem in one particular language — usually the input reading and the output printing, so they can get on with the algorithm. One template per runtime; a problem can have as many as you want to write.

A problem with a hundred generated tests does not need a hundred trips through the new-test dialog. The test script is one program, stored with the problem, that declares all of them: it calls once per test, and running it creates those tests, updates the ones that changed and removes the ones it no longer declares.

A test is an input and an answer. When someone submits a solution, the system runs their program once per test, feeds it the input, captures what the program printed, and asks the checker whether that output is right for this input. Passing a test awards the test's score.

A testset is a group of tests that share limits, a scoring rule and a feedback rule. Testsets are how a problem is broken into subtasks: a first testset for the small cases, a second for the full constraints, each worth its own points and each judged on its own terms.

A problem's type decides what a submission is and how it is graded: a whole program, a single function, answer files, a set of questions, or an answer built inside a page you upload. You choose it when you create the problem: New problem opens a list of types, and the problem is created with the one you pick.

A validator is a program that reads a test's input and asserts that it satisfies the problem's constraints — that really is within the bounds the statement promises, that the graph really is connected, that the file has as many lines as its first number claims. It grades nothing and never sees a participant's output. Its job is to keep malformed tests out of the problem.

A widget problem is solved inside a small web page you write, instead of by writing a program. The participant reads the statement, then clicks, drags or draws in the page below it, and submits what they built there. This is the shape of a Bebras task: the question is a picture you interact with, and the answer is a state — which cells are marked, which path was drawn, how the boxes were ordered.

This tutorial builds a complete widget problem, from an empty folder to a problem participants can solve on Eolymp. The task is small, but it goes through every step you will take with your own problems.

Questions is the jury inbox: the clarification requests participants raise during contests, from every contest in the space, in one queue. You answer them here, one thread at a time.

Settings configures the space itself — its name and address, who may administer it, what the subscription pays for, and the registries other sections draw on. It is not where you change your own name, language or timezone; those are in your account menu at the bottom of the sidebar, described in Find your way around the console.

151-160 of 216