Dashboards#
A directory of QuantEcon’s live status dashboards — what each one tracks, where it lives, and how it stays fresh.
QuantEcon programs report status through small, self-updating dashboards: a collector computes facts from live GitHub state on a schedule, commits or regenerates a JSON data store, and a static site on GitHub Pages renders it. No credentials beyond GITHUB_TOKEN; every number is reproducible from public state.
Live dashboards#
Dashboard |
Tracks |
Refresh |
Source repo |
|---|---|---|---|
Coverage, per-lecture freshness, automation wiring, and review state for every language edition, grouped by English source series. Three pages: overview, rollout lifecycle, per-lecture sync detail. |
Nightly collector (03:17 UTC) |
||
Dataset hosting patterns across the Python-family lecture repos, and the migration of static data into the canonical data repository — per-dataset lifecycle with the PRs that moved it. |
On push, weekly, and manual dispatch; strict build fails on inconsistency |
||
What projects the organisation has across every programme and how each is going — a reviewed registry of declared facts (stage, priority, owner) graded against what the collector observes on each project’s tracker issue, with a pipeline board and a priority/health triage matrix. |
Twice daily (01:30 and 06:30 UTC), and on any merge that touches the registry |
status-projects (private) |
The Execution Statistics page on this site complements these: it reports live build/execution health for each published lecture website.
Repos without a live site yet#
status-lectures — build/environment-configuration reporting for the lecture series (in-repo JSON store; Pages site not yet deployed).
QuantEcon/dashboard(private) — reserved for hosting dashboards that are too heavy for a static page: advanced analytics and Grafana-style boards over live data, atdashboards.quantecon.org. Nothing is built yet. Its original brief — a curated hub that links out rather than hosting — was retired on 2026-09-08, because this page already does the linking; the intent recorded on QuantEcon/dashboard#1 (private) is that it eventually becomes one home for every QuantEcon dashboard, public and private, with what a visitor sees decided by who they are.
Conventions#
status-*pattern: data lives with its collection pipeline; each dashboard repo is self-contained (site + versioned data contract) so it can relocate cheaply if the org’s reporting strategy changes (meta#332, meta#321).Freshness badges: pages state when their data was collected, so a stale dashboard announces itself instead of quietly misleading. The thresholds follow the collection cadence rather than a single org-wide rule — green within 7 days, orange past one week, red past two weeks for a nightly collector; the portfolio dashboard collects twice daily and so turns orange after 1 day and red after 3 days, because at 7 and 14 days its badge would stay green through six consecutive failed collections.
History: collectors append dated snapshots (
data/history/), so trend views come free once history accumulates.
When you add a dashboard, list it here.