Direct-threshold CAP control over the per-field statistical time series, with threshold-validation tooling (§4).
Direct-threshold CAP control over the per-field statistical time series, with threshold-validation tooling (§4). Every run is scoped to the year · project · period selected in the top bar.
This app opens on a year · project · period selector in the top bar. A run reads only the statistical tables inside the selected period, and writes only into that period's results/ folder. That is not a convenience: a number computed from a silently mixed set of periods looks defensible and cannot be reproduced.
If the panels look empty, check the selector before checking the data.
Use the menu on the left; each panel has its own help topic.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Direct-threshold assessment per field over the selected period's statistics.
TODO — what must already be true. This app needs a year, project and sampling period selected in the top bar.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Incorporate existing SQL/bash scripts against the results database or sqlite3.
TODO — what must already be true. This app needs a year, project and sampling period selected in the top bar.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Validate proposed threshold values across large declaration sets.
TODO — what must already be true. This app needs a year, project and sampling period selected in the top bar.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.
Status: not written yet. This topic is a stub created with the project template. The panel's owner (see
.github/CODEOWNERS) fills it in as the panel is built. Delete this quote block when you do.
TODO — one or two sentences: what question does this panel answer, and at what point in the CAP-control workflow does an operator open it?
The manifest describes it as: Export period results as CSV into the period's results folder.
TODO — what must already be true. This app needs a year, project and sampling period selected in the top bar.
TODO — name the outputs exactly: which table, which CSV, which folder under the project tree. An operator reading this later needs to find the artefact without reading the code.
TODO — the failure you actually hit while building this, and the check that distinguishes it from the next-most-likely cause. This section is the reason the help system exists; a list of buttons is not.