Commit History
3 days ago
-
[NOTICKET] feat(query): PA over several periods from summed hours
Rifqi Hafizuddin +1: Claude Opus 5.5The planner averaged monthly `pa` values (12 of 12 PA aggregations in the local ema_demo runs). The company standard and EMA's model compute PA over several periods as 100 * (sum INPR hours - sum breakdown) / sum INPR hours, which changes the lowest unit and the PA bands on the monthly table. - IR: optional `AggSelect.computed` (ratio of signed sums, scale 1|100), only on `avg`; SQL and pandas compile it as a double-precision ratio over rows where every term is set. Validator checks ids and numeric types. - Definition is data: a `compute` block on the approved PA formula knowledge entry, bound per turn to every table holding the named columns (`Column.measure_method`, Python-only). - Plan validator, last and fail-open: `avg(pa)` gets the computed spec; Check 8o rejects analyze_trend/analyze_aggregate averaging raw rows of a ratio measure. "rata-rata sederhana"/"simple average" keeps the plain average (Constraints.plain_average). - Scope line names the method ("metode: PA…307bac0
-
/fix traceability (#15)
- [KM-691] Traceability: add resolved data_used layer for the FE (a646735e33f6ac725d0756a88956b0aec15fe495) - check: don't leak user-scope catalog when analysis catalog missing (c0ba82938383169b41059c4125765db5275885e7) Co-authored-by: Sofhia Az-Zahra <sofhiaazzhr@users.noreply.huggingface.co>32abc41
