Each part has a job. Each connection describes exactly what passes through it. Select a step to look inside.
Local summary module available
Analyze
Local Python modules use explicit input/output contracts. Browser OpenSim uses its pinned runtime; specialized GPU jobs require their own reviewed runtime profiles.
Input
Validated joint-angle samples in seconds and degrees
Output
Metric set, chart points and provenance
Runs on
Local Python now; managed CPU/GPU runtimes planned
A worked example of this stage.
The trace is the kind of input this stage accepts: validated joint-angle samples in seconds and degrees. Lowest, peak and range are the metric set a summary module returns for it. Scrub the trace to see each sample on the figure.
The series is synthetic. The figure is a planar illustration, not a recording.
The foundation is shared. Data access stays scoped.
Study access, synthetic sessions and private video capture work locally. A managed verifier is deployed; biomechanics inference and 3D replay remain on the roadmap.
At-home live rehabilitation and asynchronous analysis have different timing requirements. The planned system supports both without promising instant cloud inference. OpenCap-style multiview processing and OpenSim use specialized runtime adapters.