Repository modules

This section groups the main repository components into their functional roles inside the pipeline.

Overview

The project is organized into four main layers:

1. Shared infrastructure - msTools

2. Bottom-up semantic construction - msCodeID - find_mscodeids

3. Movement and gait detection - msGait - find_gait

4. Validation and supporting utilities - tests and auxiliary scripts outside the main package structure

Pipeline view

Repository module relationships

Module groups

Shared infrastructure

• msTools package

Bottom-up semantic construction

• msCodeID package
• find_mscodeids

Movement and gait detection

• msGait package
• find_gait

How the pieces fit together

msTools

Provides configuration loading, UTC normalization, internationalization, shared models, and PostgreSQL/InfluxDB access.

msCodeID

Implements the bottom-up construction of semantic activity windows from raw wearable references.

find_mscodeids

Runs the first executable pipeline stage and stores activity_leg and activity_all.

msGait

Implements inertial movement detection, bilateral gait derivation, and GPS enrichment.

find_gait

Runs the second executable pipeline stage and stores effective_movement and effective_gait.

tests

Contains empirical validation utilities based on manually labeled ground-truth windows.

Notes

The repository is intentionally structured so that semantic construction and gait detection are separated into two stages:

• a first stage that builds semantic candidate windows from raw wearable data

• a second stage that performs inertial analysis and gait validation on those previously built windows