Fix DAILY_BATTERY_STATE night end and rise, document phase C contract
The night end and rise were anchored on the first daily maximum, which can be the 00:00 tail of the previous evening: 2026-05-05 was read NO_CHARGE despite a +0.079 V rise, 2026-09-30 showed a wrong night end, and 2026-09-26 stayed unknown from 04:00 to 11:00 when evaluated mid-day. The rise now starts from an earlier minimum and the knee is tested on the daily minimum (min_v). VERMONT: 139 / 31 / 14 / 0. Docs: sheet 02 page order, battery_state.py in the CLAUDE.md map, phase C exception to "anomaly = None means UNKNOWN". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
eacc0ecd4a
commit
5e039ef3bb
5 files changed
+27
-18
No files matched your search
@@ -14,7 +14,7 @@ paths:
|
||||
- **Contrat commun** :
|
||||
- `run(series) -> {analysis, rule, points: [{t, value, anomaly, facts}]}` ;
|
||||
- calcul **causal** : le point t n'utilise que les données ≤ t ;
|
||||
- `anomaly = None` signifie UNKNOWN ;
|
||||
- `anomaly = None` signifie UNKNOWN (exception : analyse 03 en phase C, où `None` = pas de verdict ; l'UNKNOWN est dans `facts.state`) ;
|
||||
- une analyse seule conclut au plus `consistent with`.
|
||||
- **Code de calcul** : bibliothèque standard uniquement, car il doit tourner sur la station. Plotly ne sert qu'aux graphiques, sur le poste de dev (`.venv`).
|
||||
- **Constantes** : chacune a sa source, en commentaire dans le code et dans le tableau de la fiche. Aucun seuil sans source.
|
||||
|
||||
Reference in new issue
Block a user