# GRIME3 0.1.0 RC8.4 Field Evaluation Workflow

This workflow describes deterministic GRIME3 field-data evaluation using
the browser interface or command line.

## Before processing

Confirm that:

1. the correct RC8.4 package or environment is being used;
2. the intended Site Configuration is available;
3. the Site Configuration corresponds to the camera/site geometry;
4. the image data are available without modifying the source images;
5. the chosen output directory is writable.

## Reusing one Site Configuration

The same canonical Site Configuration can be used for multiple folder
runs when those images belong to the same calibrated site configuration.

The command line always names the Site Configuration explicitly so each
run remains reproducible.

## Browser workflow

1. Start GRIME3.
2. Load the Site Configuration.
3. Load or select the image data.
4. inspect the calibration and search-region overlays;
5. process representative images first;
6. inspect deterministic measurement diagnostics;
7. run the intended folder workflow;
8. preserve the JSON and CSV outputs with the source dataset.

## Command-line folder workflow

Example:

```text
GRIME3.exe measure folder ^
  --images "C:\Data\Images" ^
  --site-config "C:\Data\Site\site_config.json" ^
  --output-dir "C:\Data\Results"
```

For a folder containing multiple child image folders:

```text
GRIME3.exe measure folders ^
  --images-root "C:\Data\Campaign" ^
  --site-config "C:\Data\Site\site_config.json" ^
  --output-dir "C:\Data\Results"
```

Use `GRIME3.exe measure --help` and the packaged `CLI_REFERENCE.md` for
the complete command-line contract.

## Result interpretation

`water_level_final` is the official deterministic RC8.4 water-level result.

Exhaustive diagnostic information is retained in JSON. The measurement
CSV is intended for convenient scientific tabulation and downstream
analysis.

Rejected or failed measurements should be retained rather than silently
removed. Their diagnostic status is part of the evaluation record.

## Provenance

Keep the following with evaluation results:

- `BUILD_INFO.json`;
- the Site Configuration used for processing;
- the output `run_manifest.json`;
- exhaustive JSON measurement outputs;
- measurement CSV files;
- the source image dataset or a stable reference to it.

This allows later results to be traced to an exact GRIME3 build and
configuration.

## RC8.4 octagon acceptance check

Before saving or using a Site Configuration:

1. inspect all eight displayed octagon vertices at high zoom;
2. verify that every vertex follows the intended physical octagon
   boundary;
3. verify the top, bottom, left, and right facets as well as all four
   diagonal facets;
4. reject the calibration if the overlay forms a smaller regular
   octagon inside the physical target or otherwise misses its boundary;
5. do not treat an HTTP 200 response by itself as geometric acceptance.

If detection reports no accepted candidate, adjust the search ROI,
image quality, or target visibility. Do not reuse geometry from an
earlier failed attempt.