PyRaspPast solutions
After a contest day ends, its accepted builds become public. They are the best answer to "how would someone else have solved that?" — and they are open to run and to fork.
Opening a winning build
Every past day keeps its leaderboard; open it from the practice archive. Once the day is over, each row gains a View build link. It opens the winning maker's build in the sandbox, with the date in the title ("winning build from ...").
The server only serves solutions after their day has ended, so a live contest cannot be spoiled this way. See leaderboards and ties for the leaderboard itself.
Reading the two files
The build opens with both files loaded:
- circuit.py — the board: what they bought and how they wired it. This is where the cost comes from.
- main.py — the program that ran on the Pi.
Switch between the two with the file tabs above the editor. The bill is visible in the workspace's cost readout, and you can press Run to see it work.
Forking with Open in sandbox
The solution is a copy. Edit anything, rename, wire extra parts, break it and fix it — the original maker's accepted build and leaderboard entry do not change. Everything you do stays in your sandbox, stored in your browser. Community posts carry the same idea: the Open in sandbox button on a post forks that post's files into your sandbox.
Practice mode vs the ranked attempt
| Ranked attempt (contest) | Practice (archive) | |
|---|---|---|
| Clock | server deadline, 1–3 hours | none |
| Submit | yes; verdicts and penalties count | no Submit button |
| Ranking | listed on the day's leaderboard | not ranked |
| Tests | Run tests, free | Run tests as often as you like |
Practice objectives open with the label "practice · not ranked". A forked solution or community post opens in the sandbox instead, where there is no clock, no Submit and no checks to run — just the board, the two editors and the console. Use practice to try the winning idea your own way, then bring it back on a contest day.
Going deeper
- The files you open are exactly what the server recorded at the moment of acceptance, not a later edit — the attempt's circuit and program are frozen when it is accepted.
- Objectives repeat after the full list has run, and the archive lists each once at its most recent day; every day's leaderboard and solutions stay available by date.
- For drag-and-drop editing, instruments and live data, the sandbox's Lab mode link opens the full simulator — see Lab mode.