I want my results in a spreadsheet
Recordings, results and raw samples from Movetrics Cloud in Excel, refreshed with one click. Excel in 5 minutes
Movetrics for developers
Force plate data in Excel, Python, MATLAB, OpenSim, LabRecorder or your own code, with the same names, units and time base everywhere.
Which path is mine?
Section titled “Which path is mine?”I analyse in Python or MATLAB
I record EMG, EEG or video too
Lab Streaming Layer for LabRecorder, sync pulses for sample-level alignment. Record with EMG and cameras
I run OpenSim or Pose2Sim
C3D and OpenSim external loads with the centre of pressure where it belongs. OpenSim and Pose2Sim
I want to ask an AI about my athletes
Connect Claude or ChatGPT to your workspace, read only. Ask Claude or ChatGPT
I build software
The byte-level protocol, test vectors and a simulator that speaks it. Reference
I want an AI assistant to build it
Paste one prompt into Claude Code, Cursor, ChatGPT or Copilot; the repository tells it everything else. Build with an AI assistant
One vocabulary
Section titled “One vocabulary”Wherever the data comes from, it has the same shape: t in seconds from the FDT’s own clock, fx fy fz in newtons, mx my mz in newton-metres, cop_x cop_y in metres from the plate centre, a list of events (sync edges, notes) and a list of gaps that is never hidden. Names, units and axes.
Why you can trust it
Section titled “Why you can trust it”The Python, TypeScript and MATLAB clients pass the same shared test data, each the parts it uses. The centre of pressure agrees with Studio’s own figures within 0.28 mm rms on real recordings, and C3D files land within 0.3 mm in the reader OpenSim uses (measured). The clients cannot send firmware, calibration or reset commands. Every page says what was measured, what was simulated and what has not been run yet; this version has not yet run against a real FDT. Why you can trust it.
Free and open under Apache 2.0, at github.com/movetrics/sdk.