GRIME3 0.1.0 RC9 Field Evaluation Workflow
This workflow describes deterministic GRIME3 field-data evaluation using the browser interface or command line.
Before processing
Confirm that:
- the correct RC9 package or environment is being used;
- the intended Site Configuration is available;
- the Site Configuration corresponds to the camera/site geometry;
- the image data are available without modifying the source images;
- 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
- Start GRIME3.
- Load the Site Configuration.
- Load or select the image data.
- inspect the calibration and search-region overlays;
- process representative images first;
- inspect deterministic measurement diagnostics;
- run the intended folder workflow;
- preserve the JSON and CSV outputs with the source dataset.
Command-line folder workflow
Example:
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:
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 RC9
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.
RC9 octagon acceptance check
Before saving or using a Site Configuration:
- inspect all eight displayed octagon vertices at high zoom;
- verify that every vertex follows the intended physical octagon boundary;
- verify the top, bottom, left, and right facets as well as all four diagonal facets;
- reject the calibration if the overlay forms a smaller regular octagon inside the physical target or otherwise misses its boundary;
- 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.
RC9 compatibility and quality
New Site Configurations record native image width, height,
channel/color organization, dtype and bit depth. Incompatible images are
rejected before scientific processing. The current pipeline supports
8-bit inputs; do not use silent down-conversion to make an incompatible
image pass. Older configurations retain explicit dimension-only
compatibility until verified migration. See
image_compatibility.md.
Image and linefind quality are separate documented heuristic scores
from 0.0 to 1.0. Inspect status, reason codes and diagnostics in
exhaustive JSON; quality does not change scientific acceptance. Either
score can be selected for CSV output within the existing 20-column
limit. See measurement_quality.md.
The minimum octagon width and height are configurable positive finite source-image pixel counts; the default is 100.0. Force-small detection does not override that setting. Demo playback and hydrograph controls are RC10 work.