pf_app
Paul Trowbridge
2689e95b2c
pf_bucket mirrored pf_segment for scale/recode/clone rows, so adjustments showed as '(adjustment)' -- a banner of their own, sitting outside the forecast they are adjustments to. Grouping by pf_bucket therefore split the forecast in two. An adjustment is always part of the forecast: exclude_iters keeps operations off the reference segments, so there is no adjustment that is not. It falls back to 'Forecast' now, and still yields to an explicit bucket on its own log entry. pf_segment keeps '(adjustment)', which is right there -- it answers which segment a row came from, and an adjustment came from none. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||