ntnsndr/protocol-bicorder
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Flatten data/readings/ → data/

Browse Source 
Remove the intermediate readings/ subdirectory level — dataset naming
(synthetic_YYYYMMDD, manual_YYYYMMDD) already encodes what the data is.
Update all path references across scripts and docs accordingly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Nathan Schneider
2026-03-20 17:46:23 -06:00
parent 1a80219a25
commit 60e83783ec
533 changed files with 97 additions and 97 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
analysis/INTEGRATION_GUIDE.md
View File

@@ -12,7 +12,7 @@ This guide explains how to integrate the cluster classification system into the
**Version-based compatibility**: The model includes a `bicorder_version` field. The classifier checks that versions match. When bicorder.json structure changes:
1. Increment the version number in bicorder.json
2. Retrain the model with `python3 scripts/export_model_for_js.py data/readings/synthetic_20251116/readings.csv`
2. Retrain the model with `python3 scripts/export_model_for_js.py data/synthetic_20251116/readings.csv`
3. The new model will have the updated version
This ensures the web app and model stay in sync without complex backward compatibility.
@@ -25,7 +25,7 @@ This ensures the web app and model stay in sync without complex backward compati
The model is the only artifact produced by this analysis directory that the app consumes. Regenerate it after re-running analysis on the synthetic dataset:
```bash
python3 scripts/export_model_for_js.py data/readings/synthetic_20251116/readings.csv
python3 scripts/export_model_for_js.py data/synthetic_20251116/readings.csv
```
## Quick Start