DRACO7RT · archive, events and notebooks · 29 October 2026
Where the telemetry and the flight events go, how to watch them, how to search them, and how an engineer asks the archive a question in Python
Both ground stations receive the same packets. This deck shows the four ways to look at the events (dock, catalog, each station's own pages, the mute buttons), the notebook environment with the draco package, and the station-neutral archive underneath: raw packet recordings and Parquet exports that outlive every stack start.
Slides 2 and 3: the questions and the map. Slides 4 to 9: events (the dock and its controls, the catalog, muting at the source and where the buttons are, the stations' own pages). Slides 10 to 15: notebooks (environment, opening and running one, the worked example, the package, finding when a value went high, what a notebook cannot do). Slides 16 and 17: the archive and the rules.
Why
The fixed pages answer the first column. The second and third change every time, which is why the engineers get a Python interpreter with the archive behind it instead of one more search form.
DRACO7RT archive guide · 2 / 17
Map
COSMOS’s QuestDB already holds every telemetry item, every flight event and every COSMOS command in SQL, so it is the common store; the Parquet export copies it out before each clear-on-start (dashed amber). The raw recording is what either station could be replayed from.
DRACO7RT archive guide · 3 / 17
Events
Yamcs folds DEBUG into INFO; the dock takes the true type from the catalog, so the DEBUG chip hides the SCH “slot did not increment” lines (159 of 500 rows at the time of the test).
DRACO7RT archive guide · 4 / 17 · every control, left to right: next slide · web/viewer/events.js
Events · using the dock
| Control (exact label) | What happens when you use it |
|---|---|
| ▾ Events (far left) | Closes the list to one bar showing the last event; the button then reads ▴ Events and reopens it |
| Expand / Compact | Taller list with the Apps row and a status line; or drag the thin top edge of the dock to any height |
| Last-event line | Time, app, type and message of the newest event; red for ERROR and CRITICAL |
| Source Yamcs / COSMOS | Yamcs (default): archive, newest 500 at open, then every 2 s. COSMOS: live stream, needs a COSMOS session (else “no COSMOS session token: open a COSMOS page first”) |
| DEBUG INFO ERROR CRITICAL | Severity chips: click one to hide or show that type |
| filter text, app or id | Keeps only lines whose app, id or message contains the text |
| Pause / Resume | Stops the list moving; nothing is lost, polling carries on from where it stopped |
| Clear | Empties the list on this screen; the archives are untouched |
| Full page | Source Yamcs: Viewer › Yamcs › Events. Source COSMOS: Viewer › Tools › Data Viewer, then File › Open Configuration › cfe_events |
| Catalog (far right) | Viewer › Mission › Event catalog (slide 6) |
| Apps row (expanded) | One chip per app with its count, chattiest first: click to hide (struck through); unmute all shows them again. Ground side only |
| An event line | Hover: time, catalog name and type, message format, file:line. Click: the app’s screen opens above |
DRACO7RT archive guide · 5 / 17 · settings are kept in this browser; the list holds the last 2,000 events · web/viewer/index.html, events.js
Events
tools/ground/evscat.py reads the flight source: every event-id define and every CFE_EVS_SendEvent call in the 17 apps and 5 cFE modules on the vehicle, with comments stripped and string literals joined. It records id, name, type, message format and file:line per app, plus the viewer page for that app.
Run it after any change that adds or changes an event; --check reports drift.
| Measured 29 Oct 2026 | Value |
|---|---|
| Apps catalogued | 22 |
| Events | 1,344 |
| Ids that could not be resolved | 0 |
| evscat.py --check, 10 Nov | current, 1,344 in 22 |
| Defined but never sent (kept, marked) | message reads “defined, never sent” |
| Run-time ids (EventID variables, FM offsets) | not catalogued, shown as “not in the catalog” |
The SCH entries, for example: 16 “Slot did not increment” (DEBUG), 17 “Slots skipped” (ERROR), 18 “Multiple slots processed” (INFO), all from sch_app.c.
DRACO7RT archive guide · 6 / 17 · https://draco.efsi.com/viewer/catalog.html · web/viewer/events_catalog.json
Events
Over 26 hours the vehicle sent 300 to 470 events an hour; 80 to 85 % were SCH “Slots skipped” and “Multiple slots processed”, one of each about every 24 s.
SCH registers them as send-once filters, but the stock SCH code calls CFE_EVS_ResetAllFilters() after every housekeeping packet, so the filter re-arms each cycle. A ground-added filter would be reset the same way; disabling the event type per app sticks.
Those events are real one-second guest stalls with 42 running, not noise. The cause was not chased.
COSMOS: Viewer › Mission › Events, box “Mute at the source”. Yamcs: left sidebar › Stacks › DRACO › 9-evs-mute.ycs. Click by click: next slide.
| Test, SCH events per minute | Before | Muted | After unmute |
|---|---|---|---|
| COSMOS screen buttons, clicked in a browser | 11 | 0 | 6 in 45 s |
| Yamcs commanding, link on for the test only | 10 | 0 | 8 in 50 s |
| Plain command API | 12 | 0 | 6 in 90 s |
EVS reported every command valid, zero errors. The Yamcs link was disabled again afterwards.
CFE_EVS DIS_APP_EVENT_TYPE with APP_NAME SCH_APP, BITMASK 7 CFE_EVS ENA_APP_EVENT_TYPE with APP_NAME SCH_APP, BITMASK 15 # bits: 1 DEBUG, 2 INFO, 4 ERROR, 8 CRITICAL (DEBUG is on in this build)
DRACO7RT archive guide · 7 / 17 · cosmos FOGI/EVENTS screen, run/yamcs/operator/stacks/9-evs-mute.ycs
Events · muting, click by click
A mute holds until the next vehicle boot and hides real errors too: unmute after the demo. Ground-side hiding (the dock’s chips) changes nothing on the vehicle.
DRACO7RT archive guide · 8 / 17 · cosmos FOGI/EVENTS screen, run/yamcs/operator/stacks/9-evs-mute.ycs
Events
DRACO7RT archive guide · 9 / 17
Notebooks
Engineers. Two people editing the same notebook at once overwrite each other (no collaboration extension); copy a notebook before changing someone else’s.
cd /home/efsi/draco7_0/run/jupyter && ./up.sh # start / restart docker logs draco-lab # Jupyter's log
DRACO7RT archive guide · 10 / 17 · run/jupyter/README.md
Notebooks · first use
DRACO7RT archive guide · 11 / 17 · JupyterLab 4.4.5 · run/jupyter/compose.yml, run/jupyter/README.md
Notebooks
from draco import archive as a
ev = a.events(app="IMU", text="STALE", last="24h") # 127 matching events
e = ev.iloc[-1] # 19:10:02 IMU 6 ERROR "sample stream STALE, 0.5 s"
df = a.around(e, "IMU HK_TLM_PKT",
["STATE", "SAMPLE_AGE_S", "RATE_HZ", "FAULT_FLAGS", "STALE_COUNT"],
before="2m", after="30s") # 142 samples
a.show(df, mark=e) # one axis per item, the event marked
a.events(start=e.time - a.minutes(2), stop=e.time + a.seconds(30)) # every app in that window
acs = a.around(e, "ACS HK_TLM_PKT", ["MODE", "RATE_SOURCE", "RATE_MAG", "FUEL_KG"])
a.show(acs, mark=e)Items come back COSMOS-converted where a conversion exists (states as names, not numbers).
DRACO7RT archive guide · 12 / 17 · run/jupyter/notebooks/01-find-an-event-and-look-back.ipynb
Notebooks
| Call | Returns | Source |
|---|---|---|
| events(app, text, event_id, start, stop, last) | flight events: time, app, id, type, message | QuestDB |
| events_yamcs(text, source, severity, ...) | the same from the Yamcs archive (plus Yamcs’s own events) | Yamcs REST |
| around(when, packet, items, before, after) | telemetry around a moment (a Timestamp or an event row) | QuestDB |
| tlm(packet, items, start, stop, last) · latest(packet, items) | samples of one packet, converted values | QuestDB |
| crossings(packet, item, above, below, equals, ...) | episodes: start, end, duration, samples, peak | QuestDB |
| limit_changes(packet, item, ...) | when the COSMOS limit state changed (GREEN, YELLOW, RED) | QuestDB |
| alarms(start, stop, last) | Yamcs parameter alarms: time, parameter, severity, value | Yamcs REST |
| commands(target, ...) · commands_yamcs(...) | what each station sent, with arguments | QuestDB / Yamcs |
| parquet(packet, items, ...) · history(...) | the Parquet archive; history = Parquet + live, de-duplicated | files |
| raw.index(last) · raw.records(...) · raw.stats(...) | the tee’s raw packets: time, stream id, sequence, length | files |
| sql(query) | anything read-only, as a DataFrame | QuestDB |
| show(df, mark) | one axis per numeric item, vertical marks | matplotlib |
Tables are "DEFAULT__TLM__<TARGET>__<PACKET>" and "DEFAULT__CMD__..."; the time column is PACKET_TIMESECONDS. The package also runs on a laptop with pandas, requests and matplotlib, pointed at the site with a token or a signed-in browser’s cookie.
DRACO7RT archive guide · 13 / 17 · tools/archive/draco/
Notebooks
a.crossings("IMU HK_TLM_PKT", "SAMPLE_AGE_S", above=0.5, last="6h")
# start end duration samples peak
# 0 2026-10-29 18:21:43.98 2026-10-29 18:21:43.98 0 days 1 0.6077
# 1 2026-10-29 19:01:16.13 2026-10-29 19:01:16.13 0 days 1 0.5977
# ... (5 episodes)
a.limit_changes("IMU HK_TLM_PKT", "STATE", last="6h") # 19 changes, e.g. YELLOW -> GREEN
a.alarms(last="1d") # 180 Yamcs alarms that dayEvery result row carries a time, so it goes straight into around() and show().
DRACO7RT archive guide · 14 / 17
Notebooks
| Request with the service token | Result |
|---|---|
| POST /api/draco/sql, a SELECT | 200, rows |
| POST /api/draco/sql, TRUNCATE TABLE | 400, refused by the gate |
| POST /api/draco/sql, “select 1; drop table x” | 400, one statement only |
| POST /api/draco/action/clear_data | 403, “service token: read-only routes only” |
| GET /yamcs/api/archive/draco/events | 200 |
| POST /yamcs/api/links/draco/tc-out:enable | 302 to sign-in; the link stayed DISABLED |
| GET /api/draco/cosmos/token (since 10 Nov) | 403; before 10 Nov it returned a COSMOS token |
Kernels run in the container, not in a browser, so they hold no session cookie. The token is a bearer created by the control service at start, stored outside git, copied into the container’s environment by up.sh, and recognised only for reads.
DRACO7RT archive guide · 15 / 17 · web/control/README.md “Service token”
Archive
| First export, 29 Oct 2026 | Value |
|---|---|
| Rows | 4,962,296 |
| Files (table × day) | 59 |
| Size on disk | 544 MB |
| Time | 940 s |
| Tables with rows (of 324 in QuestDB) | 27 |
Neither product can read the other’s archive, and both are kept as delivered. The common layer is the data: identical packets into both, the raw recording as truth, QuestDB as the SQL store, Parquet as the long-term copy. The search tool sits on that layer and links back into both UIs.
DRACO7RT archive guide · 16 / 17 · run/downlink-tee/tee.py, tools/archive/export_parquet.py, run/clear-data.sh, run/disk-cleanup.sh
Rules
DRACO7RT archive guide · 17 / 17