Planned RC10 functionality, not an available release. Full development roadmap · Download this plan as Markdown.

GRIME3 RC10 — Operational Measurement, History, and Playback

Plan approved October 18, 2026. RC10 is planned work; RC9 remains the current published release.

RC10 will let a hydrologist configure a deterministic processing station, process incoming images continuously, retain durable measurement history, recover after interruption, review stage in a hydrograph, export selected results, and replay images with overlays. Linux and native Windows acceptance, plus the established Conda and Docker paths, are required before delivery.

This public plan is derived from the detailed RC10 working plan at source commit 2c3d72a60cc91e6652ddfa33aa314f98b766fea0. The development roadmap defines the complete RC10–RC13 sequence toward v1.0.0.

Functional scope

1. Preserve the RC9 scientific and desktop baseline

Retain calibration, octagon detection/refinement, deterministic waterline and stage measurement, configuration compatibility checks, image-quality and linefind-quality reporting, overlays, single-image and folder/tree processing, browser/CLI access, catalog/Data Roots/assignments, portable configurations, native file browsing and its fallback, and launcher lifecycle behavior.

Any scientific-output changes require an explained reason and regression evidence. Existing historical guides, fixtures, user images/configurations, and other protected files remain protected.

2. Durable measurement database

The database is authoritative for production measurement history and hydrographs. PNG metadata is a portable provenance copy.

Records must preserve, as applicable:

Requirements:

Implementation preference: a local embedded database, likely SQLite, if inspection confirms it fits. The engine is a kickoff design choice, not a new requirement for an external database server.

3. Portable output metadata

Write important measurement/provenance information into generated PNG outputs:

Preserve original input files. Define how existing non-PNG overlays/results are handled without changing their meaning. Large diagnostics can remain in JSON/database records; the portable metadata contract must be documented.

4. Unattended ingestion and processing

A genuine scientific rejection is a completed measurement outcome, distinct from a transient file-read or processing failure.

5. Basic station setup and operation

A simple browser setup workflow should collect:

Validate locations, permissions, configuration compatibility, and obviously conflicting directory choices. Show status, recent progress, counts, and actionable failures in user terms.

Provide a supported and documented automatic-start mechanism on Linux and Windows, reusing operating-system facilities where practical. Document how to stop or disable it. Exact mechanisms are selected during inspection; RC10 does not require a general-purpose service-management framework.

Normal setup should not require users to initialize database tables or edit Python code.

6. Hydrograph review

RC10 displays raw deterministic history. SDF and Bayesian estimates enter in later candidates.

7. Export and bounded API

This is a measurement-history interface. It is not an expansion into a general hydrologic analysis platform or a new public hosting/authentication product.

8. Demonstration and playback

Screen playback uses individual still images. Video export, animation encoding, FFmpeg, and OpenCV videoio are outside RC10.

Work order and resumable batches

Batch Work Exit evidence
A Baseline inspection, scope reconciliation and design decisions Verified baseline and explicit requirement/test matrix
B Database schema, result identity, durable writes, PNG metadata, result/overlay association Consistent history and artifacts; documented reprocessing/recovery semantics
C Unattended worker, backlog/new-image handling, readiness checks, duplicate prevention, recovery, logs Fault/interruption tests and a working Linux ingestion workflow
D Hydrograph, details/image linkage, range controls, CSV and read API Browser behavior and agreement between chart, database, and exports
E Demo/playback and basic station setup/automatic operation Complete interactive and unattended Linux user journeys
F Linux standalone/Conda/Docker packaging, documentation, extended operation Linux acceptance report and accepted source checkpoint
G Native Windows completion and packaged acceptance Windows workflow evidence and cross-platform scientific comparison
H RC10 release preparation, approved publication, website synchronization, cleanup Coordinated downloads/docs, source provenance, committed/pushed changes

An early, small native Windows check should follow the first working database/worker checkpoint. It checks imports, storage locations, background execution and a basic frozen launch, and should not become a full parallel Windows implementation effort.

Each batch must be rerunnable or resumable, record its checkpoint, and stop on an unexpected starting state. Combine independent checks, avoid redundant complete-suite runs, and rebuild only affected distributions. Full required checks still run at release gates.

Platform policy and packaging

Complete substantive Linux work first. Then complete Windows acceptance before RC10 publication. Keep one shared scientific implementation and one accepted source identity across distributions.

Deliver:

Do not silently add claims for ARM64, RPi, macOS, new package registries, or operating-system versions not validated. Preserve any existing documented best-effort support without making it a new RC10 acceptance platform.

Preserve RC9's FFmpeg/videoio removal and dependency/license constraints. RC10 introduces no ML runtime. Training/inference packaging is RC12 work.

Acceptance criteria

The release is complete only when applicable checks pass in actual supported packages, not only the source environment.

Scientific and workflow regression

Storage and recovery

Browser review and playback

Operational acceptance

Distribution and release acceptance

Documentation and user deliverables

Scope boundaries

RC11 owns annotation UI and dataset preparation. RC12 owns SDF model development, scientific evaluation, execution modes, and optional ML deployments. RC13 owns Bayesian temporal analysis and final production integration.

RC10 does not include:

These boundaries do not delete future roadmap items.