cs-127 — The Data Clinic
| Field | Value |
|---|---|
| id | cs-127 |
| difficulty | Intermediate |
| topics | integration, cleaning, statistics |
| lecture | lecture-32 |
| estimated time | 5-minute attempt + 10-minute discussion |
| prerequisites | loops, lists, and tracing from lectures 1-6 |
| objective | choose the technique, trace it faithfully, and defend the boundary behaviour |
| solution | held by the instructor; discussed after the attempt |
Problem
A messy departmental dataset end-to-end: profile, clean, summarise honestly, and answer three posed questions with stated limitations.
Your deliverable is the stated assumptions, the rule list, the decision for the worked instance, and one contested case. If the problem is ambiguous anywhere, state the assumption you are making and carry on — a stated assumption is part of a good answer.
Examples
- Input: rows with missing hours, duplicate ids, one 25-hour day, mixed am/pm
- Output: profile -> clean (typed policies per defect) -> honest summary (median, with N after cleaning) -> 3 answers with limitations
Solve for the worked instance first. Then ask what would change if one number, name, or condition were replaced by something stranger.
What to notice
- Full pipeline, small data: profile first (counts per defect), THEN policies, then the summary states its N.
- Writing the rules IS the solution; code is transcription.
- Every assumption is a place where two good answers can differ.
Discussion starter
After the solution is revealed, the class spends five minutes on this prompt: "Propose one extra rule that would change the verdict — is it an improvement?"
Constraints and assumptions
- Difficulty: Intermediate (loops and lists assumed).
- Topics: integration, cleaning, statistics.
- Classroom-scale inputs unless the problem says otherwise.
- Time-box: about five minutes for the plan and trace; finishing the details is a bonus, defending the method is the target.
- Optional stretch (not required): describe an alternative approach and say when it beats the obvious one.
Hints and extension
- First nudge: identify the pattern the worked instance uses before computing anything.
- If stuck after three minutes, write the input/output line you expect and trace the smallest example by hand.
- After the reveal, attempt the extension below before the next lecture.
- Extension challenge: Write the one-page post-mortem: what the plan missed and what transfers.