← GCSE Computer Science

Session 117

2026-10-19 · 2026-W43 ✓ reviewed

What happened

Ran 13:02-14:13 on Mon 19 Oct (block 7), logged next morning once the tracker was switched on; planned from chat notes, not the tracker, so why-hex was asked cold against session 114's 'not within the week' line. Cold, one per message: overflow sentence 2/2 unaided (16 Oct was 1/2); FOR i <- 1 TO 4 -> 4 passes and range(1, 5) written unasked; why-hex 1/2 cold (consequences only), 2/2 inside a sentence frame. Trace: first reply copied the algorithm out as Python; after rows 1-2 were set out she completed the x*2 while-loop table alone, all right (output 4). Handwritten 'count numbers until 0' built line by line with each step asked for: while x > 0 first, failed on 5,-3,2,0, fixed to != 0; 4/4 on logic, colon missing on while. Traced her own program on 7,3,0 alone: right. Running total: 'i don't know', then count = count + x after one hint; trace of that version not run. About 14 items, 0 blank.

Planned next

FIRST: trace her running-total program (count = count + x) on 7, 3, 0 on paper, expecting 10, headings x | total | OUTPUT. Before it, 5 min cold, one per message: 2-mark why-hex with 'fact, then so-what' under it (19 Oct 1/2 cold, 2/2 in a frame); FOR i <- 1 TO 5 passes then last i. Then the handwritten while loop from a ONE-LINE brief, no line-by-line scaffold and no 'inside the loop' hints, photo time agreed, due by 29 Oct. Overflow sentence done (2/2 cold 19 Oct): do not re-ask this week.

Unfinished unfinished

Trace of the running-total version (7,3,0 -> 10) not run. Handwritten while loop from a one-line brief with no scaffold still owed (due by 29 Oct); 19 Oct's was guided line by line.

Unfinished: Trace of the running-total version (7,3,0 -> 10) not run. Handwritten while loop from a one-line brief with no scaffold still owed (due by 29 Oct); 19 Oct's was guided line by line. (P05, P04, A07)

Resolved

What this session changed

TopicNameChangeEvidence recorded
D05Developing → Developing19 Oct cold, first item, typed: extra digit is lost and the stored answer is too small. Name, mechanism and effect in one unaided sentence, 2/2 (16 Oct 1/2). With the 16 Oct handwritten sum, proposed secure for adjudication.
A04Developing → Developing19 Oct cold: FOR i <- 1 TO 4 -> 4 passes, then range(1, 5) written unasked; read as 3 passes on 16 Oct. 1/1 unaided.
D01Developing → Developing19 Oct cold, 2-mark why-hex: 'less chance of mistakes and easier to type' 1/2, no fewer-digits fact; 2/2 inside a sentence frame. 2/2 cold on 16 Oct did not hold three days later. Stays developing.
A07Gap → Gap19 Oct: first reply to a headings-only trace was the algorithm copied out. After rows 1-2 were set out she completed the x*2 table alone, all right (output 4), and later traced her own program on 7,3,0 unaided, right. Stays gap, proposed developing for adjudication.
P05Developing → Developing19 Oct handwritten, built line by line: while x > 0 first, failed on 5,-3,2,0, fixed to != 0; counter and update lines inside, print outside, 4/4 on logic, colon missing on while. Not independent: each line was asked for. Stays developing.
P04Developing → Developing19 Oct: count = count + 1 inside the loop unprompted; with one hint wrote count = count + x for a running total. Trace of the total version not run.