CAPCON Results Help

Validation of the results produced by Checks and Models (ยง6).
โ† All apps

CAPCON Results

Validation of the results produced by Checks and Models (ยง6).

Validation of the results produced by Checks and Models (ยง6). Scope is deliberately not settled yet; the app exists so the menu slot, the URL, the entitlement key and the period scoping are fixed now rather than retrofitted.

What it does

Everything here is scoped to one period

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.

Panels

Use the menu on the left; each panel has its own help topic.

Review Results

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.

What this panel is for

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: Review the result sets Checks and Models wrote into the selected period.

Before you start

TODO โ€” what must already be true. This app needs a year, project and sampling period selected in the top bar.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

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.

When it goes wrong

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.

Validation

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.

What this panel is for

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 results against declared crops and previous periods (to be defined).

Before you start

TODO โ€” what must already be true. This app needs a year, project and sampling period selected in the top bar.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

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.

When it goes wrong

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.

Export Package

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.

What this panel is for

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 a validated result package into the period's results folder.

Before you start

TODO โ€” what must already be true. This app needs a year, project and sampling period selected in the top bar.

How to use it

  1. TODO โ€” the first thing the operator does.
  2. TODO โ€” the second.
  3. TODO โ€” how they know it worked.

What it writes

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.

When it goes wrong

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.