HHSOJ-Essential Doc
  • Welcome
  • Structure
    • Github Structure
    • OJ Structure
  • Building
    • Judger Building
      • Installing Lo-runner
      • Core.py return code list
    • Server Manager Building
    • Frontend Building
  • Language Setup
    • Sample C++ Language Template
    • Sample Python3 Language Template
  • Problem Setup
    • Problemset Setup
    • Problem structure:Full
    • The problem.json file
    • The statement & testcases
    • Writing checkers
    • Dealing with scoring
    • Judging Inside
  • Supplying feature
    • User
    • Standings
  • What's New
  • Credits
    • Donate
    • HHS Blog
    • Github
    • Maven Rewrite Github
    • Live Demo
    • HHSOJ Web Edition
  • License
    • Apache 2.0
    • GPL 3.0
Powered by GitBook
On this page
  • Step 1 - Receiving Submission
  • Step 2 - Downloading Data
  • Step 3 - Compiling Code
  • Step 4 - Run Subtask
  • Step 5 - Finish

Was this helpful?

  1. Problem Setup

Judging Inside

Briefly about how we judge

PreviousDealing with scoringNextSupplying feature

Last updated 5 years ago

Was this helpful?

In this section, we will talk about the judging process.

Step 1 - Receiving Submission

The Judger receives the submission from the Manager and fills the judger attribute of the submission.

Step 2 - Downloading Data

If the Judger is missing problem data(i.e: problem version not right, problem folder empty) , it will download data from manager.

Step 3 - Compiling Code

The code gets compiled

Step 4 - Run Subtask

The subtasks get run one by one according to the

In each subtask, the testcases are run one by one according to their ID. Once the program gets a non-accepted verdict(i.e:anything except Accepted and Point) and the is false, the subtask is skipped.

Step 5 - Finish

The judger returns the submission when it is finished.

order
toEnd attribute