// sign in with your college Google account
Grader sign-in
Students collect the
code check.py asks for when you hand your work in.
Students: do not sign in on a lab PC.
Open this on your phone instead.
Lab computers are shared. If you sign in on one, your Google account stays open for whoever sits down next — and they can collect a code as you, without needing your password.
Loading sign-in…
Where you stand
Your predicted grade so far, on the class curve: open your standing.
Your week
Your submissions
This is an instructor token. It can read every student's submissions, marks and stored output in the courses it covers. Keep it off shared machines, and out of slides and screen shares.
You only need one for a shell. To watch a lab, the dashboard signs you in by itself; if you mint one here first, the button takes it along.
You do not have a code yet.
You already have one, issued .
It cannot be shown again. The grader stores only a fingerprint, never the thing itself — so if you have lost it, the only thing anyone can do is give you a new one, and your old one stops working straight away.
Keep this now.
What to do with it
- Open
check.pyin Thonny, from the folder your work is in. Your lab folder came with one; if it has none, or yours says it is out of date, download it above and put it in that folder. Onecheck.pyworks for every lab and assignment this term. - Press F5.
- When it asks for your code, type it in exactly as it is shown above: eight capitals, no dash, no spaces.
- Paste it where your shell can reach it, on a machine you own.
- Use it as
Authorization: Bearer <token>, or letmanage.shon the server use its own. - Keep it out of slides, screen shares and shared machines.
- The dashboard button above opens the board with this token, and this browser remembers it there until it expires or you sign out.
You type it in every time you run
check.py. It is never saved on that computer, so you
leave nothing behind for the next person.