Skip to content

LM Dashboard

LM Dashboard is a live "who needs help" board for a room full of students coding in the VEX block environment. It mirrors what they're doing from the Reflecks production backend onto your own machine, works out each student's coding strategy with a Hidden Markov Model, splits their session into episodes, raises intervention flags when someone is wheel-spinning, idle, or rewriting everything, and lays it all out on one screen.

%%{init: {"flowchart": {"nodeSpacing": 90, "rankSpacing": 110}, "themeVariables": {"fontSize": "22px"}}}%%
flowchart LR
    students["Students coding<br/>in VEX"] --> prod[("Reflecks<br/>production server")]
    prod -. "polls, read-only" .-> daemon["Local daemon<br/>mirror and analyze"]
    daemon --> sqlite[("Local SQLite<br/>mirror")]
    sqlite --> api["Read API"]
    api --> dash["Researcher<br/>dashboard"]

How It Works, In One Paragraph

Students code in VEX, and their logs land in the Reflecks production server. A local daemon asks that server's REST API for new events (keeping a cursor and backing off when things go quiet), drops the raw logs into a local SQLite file, and keeps each tracked student's derived state, strategy, episodes, and flags, up to date in a materialized table. A small read API serves that table to a React dashboard. Only the daemon writes; the dashboard recomputes nothing, it just reads what's already there. And nothing ever flows back to production. It's a read-only mirror, full stop.

What You Get

For each student you track, the daemon takes a raw stream of VEX events and turns it into three things you can actually act on:

flowchart LR
    ev["One student's<br/>VEX event stream"] --> d{{"Local daemon<br/>read-only mirror"}}
    d --> strat["Strategy (HMM)<br/>Iterator · Explorer · Stuck"]
    d --> epi["Episodes<br/>code · run · reset + pauses"]
    d --> flags["Intervention flags<br/>wheel-spin · idle · big rewrite"]

The whole thing runs on one laptop with a single SQLite file, and production is never touched.

Where To Go Next

  • Quickstart

    Install it, add your credentials, and get all three processes running.

  • Architecture

    The CQRS plus materialized-view design and the polled micro-batch model.

  • Using The Dashboard

    Student cards, the who-needs-help column, drill-down, and reset.

  • API Reference

    Every endpoint the read API exposes.