CAPCON Checks Help

Direct-threshold CAP control over the per-field statistical time series, with threshold-validation tooling (ยง4).
โ† All apps

CAPCON Checks

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.

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.

Threshold Assessment

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: Direct-threshold assessment per field over the selected period's statistics.

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.

SQL / Bash Scripts

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: Incorporate existing SQL/bash scripts against the results database or sqlite3.

Before you start

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

The period's record of the algorithm. Every algorithm that works on a crop list (all but Mowing and COETUS) runs on the lists PROJECTS โ†’ Periods recorded for it in the selected period โ€” set them for the project in PROJECTS โ†’ Algorithms, then record a version in Periods. The form shows the version and its lists under the algorithm's name and starts from them; a run may untick crops but not add any, and its INI names the version ([record]). Without a record the run is refused and the form says where to make one.

Who can run what

Every algorithm except the COETUS WCS layers writes into the client database, so only the project's Client's Manager or an Administrator can run them (the client.push permission). An Operator can open and fill in the forms, and can also run the COETUS WCS layers.

Package number (ppz_pak_id)

In the CAPCON algorithms (Crop recognition, Mowing, Arable land and GAN, Fallow, DGP/GPลฝ) the package number is set automatically: the last package NMA accepted (max(ppz_pak_id) from pvsad.pvsad_poz) + 1. For example, if the last one is 400, this run writes 401. To see the number before running, press Get from NMA and it is entered into the field. The number can be raised but not lowered. If the field is left empty, the number read at the run is used. At the run the number is read from NMA again, and a number lower than the automatic one is refused.

For the query, a VPN tunnel is started on the x51 server and stopped right after it, so that it is not left running. The tunnel is left up only when a Database โ†’ Master table job is running at that moment. If NMA cannot be reached, the run stops before computing anything: a guessed number would be assigned by NMA to another package's data. VPN control must be set up on the x51 server (Database โ†’ Master table).

In the stubble delivery (ALNSIS 2) the package number is entered as before.

How to use it

Next to every algorithm parameter there is a ?. Pressing it opens an explanation under the parameter: what the value means, how to choose it and what changes when it is raised or lowered. Pressing it again closes the explanation.

  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.

Threshold 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 proposed threshold values across large declaration sets.

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 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: Export period results as CSV 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.