fix: carry institutional→formal rename through analysis rename maps
Nathan renamed the Design gradient 'institutional' → 'formal' (v1.4.0). The analysis scripts carry historical rename maps that route old data (elite/institutional) into the current bicorder.json gradient names, and those maps still stopped at 'institutional' — so old readings would have silently misaligned against the v1.4.0 structure. - bicorder_classifier.py / export_model_for_js.py: add institutional_vs_vernacular → formal_vs_vernacular, keep elite→formal - json_to_csv.py TERM_RENAMES: same two-step route - convert_csv_to_json.py GRADIENT_MAPPINGS: elite_vs_vernacular now maps to 'formal' - bicorder_classifier.py demo ratings: use the current dimension name - analysis/README.md: example run name 1.3.0 → 1.4.0
This commit is contained in:
1 parent
6ae77a4f9b
commit
161ba3b136
5 files changed
+12
-9
No files matched your search
+2
-2
@@ -18,11 +18,11 @@ Runs:
|
||||
|
||||
### Adding a new run (e.g. re-running on edited gradients)
|
||||
|
||||
1. Make a new run directory keyed by bicorder version, e.g. `data/synthetic_1.3.0/`.
|
||||
1. Make a new run directory keyed by bicorder version, e.g. `data/synthetic_1.4.0/`.
|
||||
2. Point `bicorder_batch.py` at the shared input and the new output:
|
||||
```bash
|
||||
python3 scripts/bicorder_batch.py data/protocols_edited.csv \
|
||||
-o data/synthetic_1.3.0/readings.csv \
|
||||
-o data/synthetic_1.4.0/readings.csv \
|
||||
-b bicorder.json \
|
||||
-m <model> -a "<analyst>" -s "<standpoint>"
|
||||
```
|
||||
|
||||
Reference in new issue
Block a user