V3d Com Xcom Bos Mos

If anthropometrics are not provided, you must request them. This project requires anthropometrics to generate BoS landmarks and XCoM.

Outputs

Typical outputs per trial:

• *_COM.csv (COM position)
• *_XCOM.csv (XCoM position)
• *_BOS_vertices.csv (BoS hull vertices per frame)
• *_MOS.csv (signed MoS time series)
• Optional: *_COM_validation.txt (correlation vs V3D COM export)

Visual3D-equivalent method (conceptual)

Mirror the canonical V3D tutorial logic:

1. COM and COM velocity from a kinematic model (or a validated proxy)
2. XCoM computed from COM and COM velocity using Hof’s inverted-pendulum scaling
3. BoS derived from foot landmarks (measured or virtual) to form a polygon (single/double support)
4. MoS as the shortest distance from XCoM to the BoS boundary (signed)

See references:

• references/v3d-logic-summary.md
• references/anthropometrics.md

Scripted pipeline (recommended)

Quick start (batch-only via main.py)

conda run -n module python main.py \
  --c3d_dir /path/to/c3d_folder \
  --event_xlsm /path/to/perturb_inform.xlsm \
  --out_csv output/all_trials_timeseries.csv \
  --overwrite

MOS-focused batch export (direct batch script)

conda run -n module python scripts/run_batch_all_timeseries_csv.py \
  --c3d_dir /path/to/c3d_folder \
  --event_xlsm /path/to/perturb_inform.xlsm \
  --out_csv output/all_trials_timeseries.csv \
  --analysis_mode prestep \
  --overwrite

Implementation notes

• The pipeline assumes C3D marker trajectories are already labeled/filtered.
• No force plate is required; if force channels exist, they are ignored.
• Coordinate axes can vary; the script allows configuring the vertical axis and ground plane.