01 / ATTEMPT
Work through the code
Read a precise task, submit your own attempt and inspect its observed result.
A RESEARCH PROJECT IN COMPUTING EDUCATION
A closer look at how learners revise code, explain their reasoning and decide what to try next.
Independent records · Saved progress · English materials
01 / ATTEMPT
Read a precise task, submit your own attempt and inspect its observed result.
02 / REVISE
A neutral reminder starts one timed revision opportunity. Your work is saved separately.
03 / EXPLAIN
Complete focused questions with separate fields for the answer and your explanation.
TWO TASK FAMILIES
Short Python functions with explicit input domains and more than one possible correct solution.
Research in progress. Invitations specify whether a record belongs to a rehearsal or a released study batch. No automated teaching-need judgment is assigned.
METHOD & CAPABILITIES
Invitation-based access keeps each person's tasks and responses separate. Re-enter your invitation to continue on another device.
The server starts the 90-second window when your visible browser acknowledges the reminder. Refreshing does not restart it. An unconfirmed submission can be safely retried.
Diagnostic questions follow the revision. A separate verification stage follows the locked online stage. No answer key is displayed during either stage.
Researchers can export event records and a separate coding packet. Reference judgments remain empty until an independent review is completed.
DEVELOPMENT NOTES
The overview and workspace now share a single entry point. This candidate adds versioned study information, participation decisions, background questions, ordered tasks and separate prediction and outcome exports.
Filtered accumulation and first-match tasks have computationally checked author materials. Independent curriculum review and form-equivalence assessment remain pending.
Server acceptance and the final study protocol are separate release requirements. Predictions are prepared offline after collection. Formal batches can only be issued after the researcher records the required release evidence.
PYTHON PRACTICE / WORKSPACE
Use the code supplied by your researcher. Keep it private; it provides access to your saved workspace.
Complete the tasks in the assigned order. Your existing attempt resumes automatically. Use your own reasoning; do not use AI assistance, websites or help from others.
The revision outcome is now saved. Describe what you changed and why, or state that you are unsure.