Hi Semia,

The subject height should be in m, not in cm. Your subject's height is 168.
We will make sure it is not possible to do that on our end moving forward.

Best,
Antoine

Hi Lisa, I sent back the trials with errors for reprocessing. Please take a look in a couple hours and let us know whether things are better. Some machines may have failed us. Side note, you might want to ask your participant to briefly punch the air (fail-safe synchronization mode); I see that came...

Hi, if you run the analysis locally https://github.com/stanfordnmbl/opencap ... nalysis.py then you can use the class to access the gait events https://github.com/stanfordnmbl/opencap ... sis.py#L81. Best, Antoine

When you download data, you should have two videos per camera per trial (eg, /Videos/Cam0/InputMedia/<trial_name>; the one with _sync is after we correct for the delay. It should thus be synchronized with the corresponding ones from other cameras(eg, Cam1 and Cam2). And the synced videos correspond ...

There is an example here https://github.com/stanfordnmbl/opencap ... nalysis.py with some plots at the end. This might be useful. Antoine

Hi Aaron,

Syncing is done on a per-trial basis, so there should not be any "drifting" there. If the vibrations are really big and the cameras are moving then I would recommend re-calibrating now and then. I don't see any other reasons.

Best,
Antoine

For dynamics, you should run dynamic simulations: https://github.com/stanfordnmbl/opencap ... imulations We have examples here https://github.com/stanfordnmbl/opencap ... e#examples

Antoine

Thanks for reporting this issue. Could you point to the session for which this is happening?

I think you forgot the screenshot

Did you install visual studio? https://github.com/stanfordnmbl/opencap ... imulations