GRIME3 0.1.0 RC9 — Conda Quick Start

After RC9 publication, GRIME3 is distributed through the versioned CoffeeSig static Conda channel at:

https://coffeesig.com/gaugecam/conda/rc9

The versioned path keeps release-candidate software isolated from other GRIME3 Conda publication paths.

The GRIME3 package is noarch: python; Conda resolves platform-specific runtime dependencies.

Create a dedicated environment from the CoffeeSig RC9 channel:

conda create -n grime3-rc9 --override-channels -c https://coffeesig.com/gaugecam/conda/rc9 -c conda-forge python=3.11 grime3=0.1.0=py_11

If grime3-rc9 already exists as a development environment, leave it intact and choose a different environment name in the creation/activation commands. Do not install build tools in an end-user measurement environment.

Activate it:

conda activate grime3-rc9

Verify it:

grime3 --version
grime3 --help
grime3 measure --help
grime3 web --help

The CoffeeSig RC9 channel supplies the noarch GRIME3 package and its platform-specific grime3-opencv companion for Linux x86_64 and Windows x64. Normal runtime dependencies are resolved from conda-forge. The companion constrains the RC9 runtime to Python 3.11 and supplies the prepared headless, FFmpeg-free OpenCV distribution; a stock OpenCV package is not a substitute.

Windows runtime compatibility

The Windows companion pins the tested conda-forge runtime: Python 3.11.9 (h631f459_0_cpython), OpenSSL 3.6.4 (hf411b9b_0), libffi 3.7.0 (h3d046cb_1) and NumPy 2.4.6 (py311h65cb7f3_0). Conda selects these through the companion dependency; the installation command remains the same. A Python 3.11.17 build failed to load a Windows DLL on the validation Dell. That failure was resolved using the tested runtime without changing Windows security settings. Other Python builds have not been accepted for Windows RC9. Linux retains the Python 3.11 range and its separately validated environment.

Direct artifact installation

The exact .conda artifact is also distributed with RC9 for archival, reproducibility, and controlled package validation.

For normal installation, install GRIME3 by package name from the RC9 Conda channel as shown above. This allows Conda to resolve all required runtime dependencies and create the platform-specific command launcher.

Installing the .conda file directly by filesystem path is not the recommended end-user installation method. In validation on Windows, an explicit artifact-path installation did not populate the required runtime dependencies in an otherwise bare environment.

On Windows, installation by package name creates these native entry points:

Scripts\grime3.exe
Scripts\grime3-script.py

and the grime3 command is directly available after environment activation.

Runtime dependency policy

RC9 Conda uses:

python >=3.11,<3.12
grime3-opencv 5.0.0.93 py311_ffmpeg_free_1

along with NumPy, Pillow, FastAPI, Pydantic, Uvicorn, and Click.

Qt, PyTorch, torchvision, torchaudio, and SAM2 are not required by the RC9 Conda runtime.

Conda uses the same prepared FFmpeg-free OpenCV wheel as the corresponding standalone distribution, supplied by a platform-specific companion package. The publication channel must include that companion before RC9 installation.

Start the browser

grime3 web --open-browser

The normal local address is:

http://127.0.0.1:8000/

Measure one image

grime3 measure image \
  --image "/data/images/image001.jpg" \
  --site-config "/data/site/site_config.json" \
  --output-dir "/data/results"

Measure one folder

grime3 measure folder \
  --images "/data/images" \
  --site-config "/data/site/site_config.json" \
  --output-dir "/data/results"

Measure a folder of folders

grime3 measure folders \
  --images-root "/data/campaign" \
  --site-config "/data/site/site_config.json" \
  --output-dir "/data/results"

The browser and CLI use the same canonical Site Configuration and scientific measurement implementation.

Verify headless OpenCV

python - <<'PY'
import cv2

print(cv2.__version__)

for line in cv2.getBuildInformation().splitlines():
    if line.strip().startswith("GUI:"):
        print(line.strip())
PY

The GUI line should report NONE.

Updating

For RC9, install newer RC9 builds from the same versioned channel when provided.

A later production package can use a stable CoffeeSig Conda channel path without requiring users to select an RC-specific path.

Remove GRIME3

conda activate grime3-rc9
conda remove grime3

Remove the complete environment

conda deactivate
conda env remove -n grime3-rc9

Troubleshooting

grime3: command not found

conda env list
conda activate grime3-rc9
grime3 --version

GRIME3 cannot be found by Conda

For RC9, make sure the versioned release-candidate channel is present:

https://coffeesig.com/gaugecam/conda/rc9

The RC9 package is intentionally isolated from other Conda publication paths.

Unexpected GUI OpenCV

The official recipe requires:

grime3-opencv 5.0.0.93 py311_ffmpeg_free_1

Browser does not open automatically

Leave grime3 web running and open:

http://127.0.0.1:8000/

manually.

Data moved to another computer

Use the current filesystem paths for images, Site Configuration, and output. Persistent Site and Configuration identities do not depend on the path where the JSON file happens to be stored.

Provenance

Preserve the Site Configuration, JSON, CSV, run manifest, and build identity with scientific results.

Native browsing and provenance

Start with grime3 web --host 127.0.0.1 --open-browser and use the printed URL. Linux uses the desktop's portal and system GIO/GLib when available; Windows uses its shell dialogs. Docker, remote, headless and unavailable providers retain the GRIME3 browser. See native_browsing.md.

The published package must identify the RC9 commit, clean state and Conda distribution. Pre-tag validation packages are not published channel releases.