Telemetry, Evidence & Operations
Replay and Mission Debrief
Use the replay tool to re-examine a completed run and build an evidence-based mission debrief.
- Time estimate
- 25–30 min
- Complexity
- developing
- Maturity
- pilot ready
- Simulator readiness
- implemented
- Software available now
- Available now as replay/evidence workflow — `replay_and_mission_debrief`; compare runs and capture chart evidence.
Student path
- Choose a replay preset (nominal hold or wheel speed warning).
- Slowly drag the time cursor and watch the telemetry values change.
- Find one event and read its evidence quote (channel + value + timestamp).
- Write a one-sentence debrief: "At t=X s, [channel] showed [value], which means…"
- Copy your evidence before moving to Session 4.
Learning outcomes
Student can replay a run, identify key events in the telemetry, and write a short mission debrief statement.
- Identify at least two events in a replay trace.
- Write a mission debrief statement connecting evidence to outcome.
- Explain why replay is valuable for improving future missions.
Concept primer
Use the replay tool to re-examine a completed run and build an evidence-based mission debrief.
Run replay_and_mission_debrief experiment; use run summary and chart evidence.
Complete a debrief template: event, time, telemetry value, interpretation.
Interactive lab
Teaching-grade software activity slot — not a flight simulator or certified propagator.
Replay timeline lab
Scrub through a mission run
Choose a replay preset and drag the time cursor. The telemetry values update and the active event card highlights. Use the evidence quote to practice citing timestamps in a debrief statement.
Spacecraft acquires target and holds. Battery recovers after eclipse exit.
Attitude error
45.0 deg
Wheel speed
0 rpm
Battery voltage
7.8 V
Timeline events
The active event (at or before your cursor) is highlighted. Click the cursor to advance.
Operator uplinked a 45° attitude hold command.
t=0 s: target_angle set to 45.0 deg; controller enabled.
Error converged below 2°. Controller in hold mode.
Solar panels illuminate. Battery begins charging.
Ground station link established. Telemetry downlink begins.
Nominal mission segment complete.
Teaching note
Replay is the primary method for post-mission review. Engineers cite channel + value + timestamp to make evidence-backed claims. A claim without a citation (e.g., "attitude was fine") is not accepted in engineering debrief culture.
Teaching-grade model — not a real replay system, not a ground-station debrief tool.
Self-check · Local only
3 questions — 0/3 answered correctly
Local-only. No submission, no grade. Answers revealed here only.
What is the main value of replaying a completed mission run?
What should a mission debrief statement always include?
In a replay, battery voltage rises from 7.8 V to 8.1 V at t = 55 s. What does this suggest?
Evidence · Local only
Capture your evidence
Local-only — no submission, no upload. Copy the text below or screenshot this panel to share manually.
Evidence prompts
- Which replay preset did you examine?
- Name one event on the timeline and describe what the telemetry showed before and after.
- Write a one-sentence debrief quoting a channel, value, and timestamp.
Captured values
- Run preset
- See your selection above
- Event identified
- Record one event label and its timestamp
- Evidence quote
- channel + value + timestamp
- Debrief sentence
- Write your one-sentence debrief here (manual)
Track 6 — Telemetry / Evidence Activity: telemetry_replay_debrief Captured: 2026-05-16T07:38:33.421Z --- Run preset: See your selection above Event identified: Record one event label and its timestamp Evidence quote: channel + value + timestamp Debrief sentence: Write your one-sentence debrief here (manual) --- Teaching-grade evidence. Local-only — no account, no submission, no official grade.
Evidence capture
Expected outputs learners should be able to show after the lab (Phase 9 evidence engine preview available).
- Replay artifact reference (run id or screenshot)
- Three-sentence debrief citing at least two chart moments
Reflection
Replay a run; identify settle time, overshoot, and any anomalies; write a three-sentence debrief.
Responses are not persisted in this preview unless a specific activity component adds storage later.
Assessment / quick check
What is one claim you would not make without replay evidence, and what chart proves it?
Teacher notes
Require evidence quotes: timestamp + channel + value trend.
Teacher use
Require evidence quotes in every debrief statement. Prompt: "What claim would you NOT make without seeing the replay? What chart moment proves it?" Connect the eclipse-exit battery recovery event to Track 3 (day/night energy balance) and the contact-window event to Track 4 (contact windows + RSSI).
Next activity
Suggested progression from the mission learning path. Links avoid missing activity routes.