Week 460 dated course items
Contact hours: kickoff; modelling theory 2; python 2
Course items
- Mon 9 Nov 2026 Kickoff (week 46) Session
Suggested Kickoff; form group, choose project
Course items, suggested work and tasks per calendar week. Course items come from kb/events.json; suggested work from kb/plan.json; tasks from the task split in kb/group-plan.md (c), placed in the week of their "Needed by" date. Collision weeks (51, 3, 4 and 5) are marked. The bar counts dated course deadlines, exams and resits in the week.
Contact hours: kickoff; modelling theory 2; python 2
Suggested Kickoff; form group, choose project
Contact hours: coaching 2; modelling 4; python 2+2; PoA 2; practicals 2
No dated course item.
Suggested PoA workshop; start PoA; send the long-lead order form by 2026-11-20 Fri
Contact hours: coaching 2; modelling 4; control theory 2; python Assign 1; PoA 2; practicals 2 (assessed)
Suggested PoA drafting; practicals start
Contact hours: coaching 2; modelling 4; control theory 2; python 2+2; practicals 4 (assessed)
Suggested Protects the PoA review on 1–2 Dec
Contact hours: mentor meeting; coaching 2; modelling 4; control theory 2; python 2; PoA submit (grid); practicals 2 (assessed)
No dated course item.
Suggested Freeze mechanical design before the break
Contact hours: coaching 2; MODELLING EXAM; control theory 2; practicals 2 (assessed)
Suggested Exam + resit collision; do not plan build work this week. Practicals must be "finished before 2027" and weeks 52–53 are holiday, so 2026-12-18 Fri is the last lesson day: pass all open post-assessments by then (the grid also has an assessed practical in week 3; see schedule.md note 7)
Contact hours: HOLIDAY — Christmas break
Suggested Holiday
Contact hours: HOLIDAY — Christmas break
Suggested Holiday
Contact hours: feedback; coaching 2; labsupport 4; modelling questions; control theory 2; python Assign 2; simulation 2+2
Suggested Simulation teaching starts; build resumes
Contact hours: coaching 2; labsupport 4; control theory 2; simulation 2+2; test protocol 2; intermediate delivery
Suggested Build must be finished; simulation notebook also due 18 Jan
Contact hours: coaching 2; modelling resit; control theory 2; simulation present; practicals 2; test protocol delivery
Suggested Three collisions: resit + simulation + test plan
Contact hours: coaching 2; labsupport 4+4+4 (one grid cell across weeks 4–5, see note 5); CONTROL EXAM; python resit; practicals resit
Suggested Exam week: avoid new build scope
Contact hours: coaching 2; labsupport (shared cell with week 4, see note 5); simulation resit; test protocol resit; final delivery
Suggested Heaviest week: final delivery Monday, reflection Friday
Contact hours: feedback; labsupport 4; control theory questions; deliveries resit
Suggested Feedback week; only resit work
Contact hours: control theory resit
Suggested Last chance; resit + reflection same day
Segway consequences that affect planning (course facts from project.md unless marked Suggested):
The owner prefers general time slots to a per-person task plan. The course gives contact hours per week ("course planning image"), not weekdays; fit the blocks around the real timetable.
| Block | When | Who | Use |
|---|---|---|---|
| Weekly group meeting, 1 h | Right after the weekly 2 h coaching session (every week 47-5) | A-D | Status, next week's goals, decisions; A keeps the action list |
| Build / lab block, 3-4 h | One fixed half-day per week from week 50; in weeks 1-5 use the labsupport hours (4 h in weeks 1 and 2; 12 h across weeks 4-5) | A-D, or at least 2 | Mechanics, motor amplifier, PID PCB, tuning |
| Writing block, 2 h | Weeks 47-49 (PoA), week 2-3 (test protocol), week 5 (final documentation) | 2 members | Documents due that week |
| Simulation block, 2 h | Weeks 1-2, next to the 2+2 h simulation lessons | 2 members | Segway model, linearisation, controller, notebook |
Weeks with less group time: 51 (modelling exam), 52-53 (holiday), 4 (control exam). Do the main mechanical work in weeks 49-50 and 1-2.
Owner is intentionally blank. Suggested task breakdown; add or merge rows to fit the group.
| Task | Skill area | Needed by | Depends on |
|---|---|---|---|
| PoA: assignment description + literature review | Documentation / research | 2026-12-01 | Project choice |
| PoA: planning, roles, risks, budget | Project management | 2026-12-01 | PoA scope |
| PoA: final check + submission | Documentation | 2026-12-04 23:59 | All PoA sections |
| Mechanical design and CAD | Mechanical / hardware | 2026-12-11 | PoA, project choice |
| Mechanical build and assembly | Mechanical / workshop | 2027-01-11 | Mechanical design |
| Actuator, sensor and motor amplifier | Hardware / electronics | 2027-01-11 | Mechanical design |
| Order long-lead parts (motor, gearbox, sensor) via order form | Procurement | 2026-11-20 | Motor/gearbox choice, €75 budget |
| Order remaining parts via order form | Procurement | 2026-12-11 | Frozen mechanical design, rest of €75 budget |
| PID PCB assembly (kit from Practical 1) | Hardware / electronics | Before analogue-PID practical | Practical 1 |
| Simulation: non-linear time-domain model | Modelling / Python | 2027-01-08 | DE model of the setup |
| Simulation: linearisation + s-domain model | Modelling / control | 2027-01-13 | Non-linear model |
| Simulation: controller design + closed loop | Control systems | 2027-01-15 | s-domain model |
| Simulation: notebook QA + presentation | Documentation / presenting | 2027-01-18 12:00 | All simulation parts |
| Controller tuning and video | Control systems / practical | 2027-01-22 | Intermediate build, PID PCB |
| Test plan + test protocols | Testing / documentation | 2027-01-20 | Requirements, build |
| Test-plan session presentation | Presenting | Week 3 session | Test plan |
| Python data acquisition for the display | Programming | 2027-01-25 | Python assignment 2 |
| Semi-real-time plot + automatic performance metric | Programming / control | 2027-01-27 | Data acquisition, tuning |
| Final report / documentation | Documentation | 2027-01-29 | All technical work |
| Final demonstration and rubric check | Presenting / all | 2027-02-01 09:00 | Complete working system |
| Individual reflection | Reflective writing | 2027-02-05 17:00 | Final coaching session date |
Suggested. "Latest sensible start" means the last week in which starting still leaves time for one review cycle; "internal review" is 2–3 days before the deadline so fixes are possible.
| Milestone | Suggested date | Notes |
|---|---|---|
| Start; choose project, draft scope and literature review | 2026-11-16 Mon (week 47) | PoA workshop and 2 h PoA are scheduled in week 47 |
| Draft planning, roles, risks, communication plan | 2026-11-23 Mon (week 48) | Use the template headings |
| Internal review (2–3 days before) | 2026-12-01 Tue – 2026-12-02 Wed | Check against rubric: assignment description and planning |
| Submit | 2026-12-04 Fri 23:59 | One group member submits |
| Milestone | Suggested date | Notes |
|---|---|---|
| Mechanical design frozen | 2026-12-11 Fri (week 50) | Before the Christmas break |
| Build mechanical system | 2026-12-14 – 2027-01-08 | Weeks 51 and 1; hardware support in weeks 1–2 |
| Working mechanical system + internal check | 2027-01-11 Mon (week 2) | Electrical parts not required for this delivery |
| Internal review (2–3 days before) | 2027-01-12 Tue – 2027-01-13 Wed | Check "well designed, finished, all present, feedback ready" |
| Session | Week 2 (2027-01-11 – 2027-01-15) | Timeslot follows on Brightspace |
| Milestone | Suggested date | Notes |
|---|---|---|
| Non-linear model + time-domain code complete | 2027-01-08 Fri (week 1) | Only NumPy/Matplotlib allowed |
| s-domain model + controller + closed loop | 2027-01-12 Tue | Control-library part |
| Internal review | 2027-01-14 Thu | One day before the intermediate deadline (2027-01-15), so the two do not collide |
| Submit notebook | 2027-01-18 Mon before 09:00 | Brightspace closes at 12:00, but the simulation page says 09:00 (schedule.md note 3): the earlier time is safe. Finish the notebook by Friday 2027-01-15: the modelling resit is on the same Monday. Presentation follows in week 3 |
| Milestone | Suggested date | Notes |
|---|---|---|
| Requirements and test questions agreed | 2027-01-11 Mon (week 2) | Derived from the customer requirements |
| Draft test plan + protocols | 2027-01-18 Mon (week 3) | Template-based |
| Internal review (2–3 days before) | 2027-01-19 Tue – 2027-01-20 Wed | Check reproducibility and data analysis |
| Submit + session | 2027-01-22 Fri 23:59; session week 3 | Pass needs submission, presence and participation |
| Milestone | Suggested date | Notes |
|---|---|---|
| Controller tuning complete, closed loop stable | 2027-01-22 Fri | Builds on intermediate + simulation |
| User interface and semi-real-time display working | 2027-01-25 Mon | Depends on Python assignment 2 |
| Final documentation draft | 2027-01-27 Wed | One person will submit for the group |
| Internal review (2–3 days before) | 2027-01-28 Thu – 2027-01-29 Fri | Check rubric and demo script |
| Submit documentation + demonstration | 2027-02-01 Mon 09:00; demo week 5 | Complete group expected |
| Milestone | Suggested date | Notes |
|---|---|---|
| Draft half-page reflection | 2027-01-29 Fri | Individual. The real deadline is 24 h before the final coaching session in week 5; if that session is on Monday or Tuesday, the reflection is due on 2027-01-31 or 2027-02-01 |
| Internal review with a peer | 2027-01-30 Sat – 2027-01-31 Sun | Check rubric |
| Submit 24 h before final coaching session | Coaching day minus 24 h; 2027-02-05 Fri 17:00 at the latest | Brightspace calendar stresses "24 hours BEFORE your coaching session". Ask the coach for the week-5 slot in week 3 |
Course facts — the overview diagram gives these arrows:
PoA ──► build setup ──► build & tune controller ──► closed loop system ──► complete system ──► evaluate system
PoA ──► test protocol ──────────────────────────────────────────────────────────────────────► evaluate system
closed-loop simulation ──► build & tune controller
python assignment 2 ──► create user interface ──► complete system
Source: "course planning image"; the same dependency wording is in _src/text/01 Course information - Cursusinformatie/02 att - kickoff control systems 2026 - 2027.pptx.md.
Mapping to dated group deliverables:
| Chain node | Deliverable | Date | Source |
|---|---|---|---|
| PoA | Plan of approach | 2026-12-04 Fri 23:59 | _src/deadlines.md |
| build setup | Intermediate delivery | 2027-01-15 Fri 23:59 | _src/deadlines.md |
| closed-loop simulation | Simulation | 2027-01-18 Mon 12:00 | _src/deadlines.md |
| test protocol | Testplan | 2027-01-22 Fri 23:59 | _src/deadlines.md |
| complete/evaluate system | Final delivery | 2027-02-01 Mon 09:00 | _src/deadlines.md |
| individual evaluation | Reflection | 2027-02-05 Fri 17:00 | _src/deadlines.md |