What the class got wrong, and who is still stuck.
Alps finds the wrong answers and errors many students share on an assignment, and the few students who need you.
See what to revisit and why, and assign a follow-up to just the students who need it.
From 30 students to the error they share
Find the shared error, the students stuck on it and the run where it broke. Then see what to revisit.
A scripted walkthrough with a sample class of 30. Every count on screen is computed from the sample answers.
The mistakes many students share
The Common mistakes tab lists the wrong answers and Code errors from the whole assignment, most common first.
![The Common mistakes tab for a Loops Practice assignment and a class of 30: wrong answers many students shared, such as 11 students picking [1, 2, 3, 4, 5] for list(range(1, 5)), tagged More than the right answer, and 7 with the right order but wrong indentation on a Parsons activity; then errors that keep coming back, NameError for 10 students and IndexError for 6, each in plain words, with a dot under each activity where it happened.](/s/img/features/class-insights/ci-mistakes-m.svg)
Code
Errors that keep coming back, in plain words: NameError reads “Uses a name the computer was never told about”. The test most students still fail is marked Hardest.
Multiple choice
What students picked first, and who picked each option. A wrong answer picked first more often than the right one is tagged More than the right answer.
Parsons
Where first arrangements went wrong, line by line: blocks out of order, or the right order with the wrong indentation, and which distractors students used.
Fill in the blank
What students typed in each blank. A near miss the key marked wrong, like range(1,6) for range(1, 6), is a sign your key may be too strict.
A mistake is listed only when at least 3 students made it. Snap! and AlpsBlocks projects show how far each student got, and which requirements they missed.
The few who need you, and where in the code
Click a count or a part of a bar, and Alps lists just those students.
- ✓ On Submissions, Not yet correct lists everyone with something not right yet
- ✓ On a Code activity, the hardest test, and each error with how many are still stuck on it
- ✓ Groups by code history sorts the class by what is holding each student up, such as lost working progress or the same tests still failing
-
1
Open the Code activity
Its Class Analysis groups the class by how their runs went.
-
2
Click Stuck on the same failure
Students who each hit the same error 3 or more runs in a row, a mark for each run, and a next step such as “Review the error together”.
-
3
Click a run
Work history opens at that run: what it printed, and what changed in the code since the run before.
Alps shows what the code did. It doesn’t guess at the bug.
Spot who may be clicking through
Rapid retries marks students who got a multiple-choice or true/false question right only after retries, each within 3 seconds of the one before. It’s a hint, not a verdict, so the next step is to ask one to explain their answer.
Low first-try success flags a question few students got right the first time, even when most got there in the end.
Correct after retries, rapid retries · 4 students
Ask one to explain their answer Show all
Know what to revisit, then act on it
Turn on Revisit first, and the activities worth a second look move to the top, each with its reason.
Option c was the most common first pick (10 of 27), ahead of the right answer (4).
15% got it right first time (4 of 27); the median question in this coursework: 50%.
4 students keep failing Test 3.
Every flag says why
A flag needs enough students to mean something. Open the activity, and each reason is a card that shows just the students it is about.
Follow up with just those students
A group’s next step, like “Review the error together”, or Offer a Challenge to students whose first run passed, starts a new assignment with those students already picked.
Plain counts, and you make the call
Alps reports what students did. It doesn’t label a student.
- ✓ Results, not grades: nothing here changes a score
- ✓ Class views show answers, counts and names. Code appears only when you open a student’s work, and that is logged
- ✓ Only the section’s teachers, school admins and Alps staff can see it, not students or teaching assistants
- ✓ It updates on its own, normally within about 20 minutes, and shows the time its numbers stand at
Find it on an assignment’s Activities and Common mistakes tabs, or click an activity for its Class Analysis. In the textbook, an assignment’s card has a Class analysis button.
Class Insights looks at one assignment at a time. For every assignment, or the class right now, see below.
Reteach the mistake that matters
The shared mistake, the students stuck on it, and what to revisit, on every assignment.