MotionCommons documentation
Developer preview
Capture movement. Build an analysis. Make the result useful.
01 / Start here
A local result in a few commands.
Start with synthetic data and a working example. Add a study workspace when you need one.
Follow the quickstart ↗A shared foundation for movement
MotionCommons brings study workspaces, patient sessions, movement recordings, versioned analysis modules and dashboards into one project. Researchers extend the science through Python; staff use scoped application workflows to organize and explore results.
The current release is a developer preview. Local synthetic analysis, recorded OptiGait review, scoped workspaces and dashboard authoring are implemented. General cloud execution, biomechanical inference and clinical deployment remain outstanding.
Choose your starting point
From recording to result
- Create an authorized study workspace and patient session.
- Capture or import original recordings. Preserve their identity, units and provenance.
- Run trusted local Python modules or finite JSON workflows, or use the supported fixed inspection worker. Managed native/cloud graph dispatch is still planned.
- Explore accepted outputs in a dashboard. Share presentation definitions separately from patient access.
Understand the status labels
| Label | Meaning |
|---|---|
| Developer preview | Implemented features with stated local and synthetic validation limits. |
| Local execution | Runs trusted code on your machine; not a security sandbox or managed compute service. |
| Deployment planning | Target architecture and operator requirements; not a turnkey production installer. |