# Data policy (repo convention): Dropbox-backed site/observation data is
# gitignored in the working tree and must NEVER enter a container image.
# The patterns below are defense in depth: even a misconfigured COPY cannot
# ship site rasters, forcing files, caches, or state.
Input_rasters/
Input_subset/
ERA-5/
fixtures/
cache/
site-cache/
state/
ownmet_Forcing_data.txt
# Backstops must be doubly-anchored to match at ANY depth (a bare "*.tif"
# is root-anchored under dockerignore semantics, so a stray raster in a
# nested directory would slip through).
**/*.tif
**/*.tiff
**/*.nc
**/*.sqlite3
**/*.sqlite3-*

# Repository/infrastructure noise.
.git/
.gitignore
.github/
.claude/
.omc/
.venv/
venv/
.coverage
.pytest_cache/
.mypy_cache/
.ruff_cache/
**/__pycache__/
*.pyc
.DS_Store
*.egg-info/
paper/
.claude-worktrees/
docker-compose.override.yml