PyRaspLeaderboards and ties
Every day has its own leaderboard. It ranks only the makers who solved the objective, by score, lowest first.
Reading the table
| Column | Meaning |
|---|---|
| # | rank for the day |
| Maker | the public display name, or a generated handle |
| Score | the final score in seconds |
| Time | the seconds used, shown as a duration |
| Cost | the accepted build's bill |
| Wrong | rejected, build-error and over-budget submissions before acceptance |
The header reminds you of the rule: Score = seconds used + cost penalty + 300 s per wrong submission. Lower wins. The full arithmetic is on how scoring works.
Ties
Equal scores break by finish time: the maker whose accepted submission reached the server first ranks ahead. Both the table order and the ranks follow that rule — score first, finish second.
Your row
Sign in and your own row is highlighted in the table. Once your submission is accepted, the Today page and the Results tab show your rank, score, time, cost and wrong count. If you have not solved, you have no row: the leaderboard lists solvers only.
Past days and the archive
Every day's leaderboard is kept. Open a past day's from the practice archive and it gains a View build link on each row: once a day ends, that day's accepted solutions become public, and View build opens the maker's two files in your sandbox. More on that in past solutions.
The objective itself also moves to the archive. Past objectives are untimed and unranked practice: no clock, no Submit, no penalties, and you can run the tests as often as you like. The contest-day leaderboard still reflects what happened while the day was live. See the daily contest for the reveal and start rules.
Going deeper
- Rank is defined by the same ordering as the table: the number of solved attempts with a lower score, or the same score and an earlier finish, plus one.
- The schedule runs through the full list of objectives and then repeats it. The archive lists each objective once, at its most recent day, but every day's leaderboard and solutions stay available by date.
- A day's solutions are only reachable after the day is over; before that, the server refuses to serve them and the View build links are not shown.