Compile & run
Builds each submission with your gcc flags and runs your test cases.
It runs your tests on every submission and flags banned functions, copied code, and AI-generated work, so you grade with the evidence in front of you.
Wednesday 14 October
You have 2 labs to grade. Next is S5 · Class 1 A, due Tue 27 Oct.
This week it's S5 for Class 1 and Class 2, due Tue 27 Oct.
Students pass 52% of graded labs.
Class 1Class 2Recent runs
autOScan turns a zip of C submissions into a graded run, building, testing, and flagging each one against your lab policy, so you grade with the evidence in front of you.
Builds each submission with your gcc flags and runs your test cases.
Flags disallowed calls like system or exit in every lab.
Surfaces suspiciously similar submissions across the cohort.
Scores AI-style evidence in each submission, traced to lines.
Runs any submission in a sandboxed shell, with Valgrind one click away.
Define the compiler flags, files, and tests for every lab.
From upload to grades
Five checks run on every submission and flow into one grid: compile, tests, banned calls, similarity, AI. You review the flags, set the grades, and export the feedback.
Upload a zip of C submissions and the engine compiles, runs test cases, flags banned functions, and checks similarity and AI-likelihood, across every cohort, with every grade left in your hands.
checks on every submission: compile, tests, banned calls, similarity, AI
zip per lab, the whole cohort graded as one batch
point AI score, every point traced to lines in the code
grades written by the engine. You set every one.
Everything you need to know about grading labs with autOScan. Can't find an answer? Take a look at how it works.
C labs compiled with gcc. Compiler flags, files and test cases are configurable per lab, and banned functions for the whole course.
Sign in and grade your next lab in minutes.