A simpler flow through the Modeling App, built around what a user needs to do rather than one form per chap-core table.
What it is
A proposal to replace the Modeling App's chain of one form per chap-core table with two jobs: one setup screen (what
to predict, which covariates from which source, which modeling packages to try), an automatic job that configures,
tunes and backtests every model, and a review screen where someone promotes the best model to a prediction setup.
Status, decisions and open questions live in the main epic, CLIM-1752.
Where we are
As of November 2026 this is a proposal, not a decision. The deck under Material shows the flow and mockups and was
made for a meeting on 12 November 2026. The next step is a spike meeting to agree the flow and file the tasks.
How to contribute
- Feedback on the flow: comment on CLIM-1752. Questions about the
boundary with OCS, CAPS or chap-core go to CLIM-1619.
- User stories for setting up and judging evaluations: the user-stories repo, linked above.
- Code: chap-frontend, linked above.
Presentations · Proposal
Feedback on the Modeling App and four threads to address it: a simpler user flow, building blocks, user stories and a CLI path. Ideas for feedback.
For Implementers and HISP groups, Partners and funders, Data scientists and modellers
Introductory · 20 min · Presented live or self-paced from a link · Synthetic data
New Modeling App user flow
modeling appuser flowbuilding blocksuser storiescliproposal
Chap learning material