How rogerlew/wepppy works
WEPPpy is the modeling and orchestration core behind WEPPcloud, supporting watershed erosion simulations and wildfire-response analysis. The main workflow starts with a user submitting a run, proceeds through queued preparation of watershed, climate, soils, and land-use inputs, then runs WEPP and exposes results for querying and export. NoDb controllers manage run state; Redis supports coordination and caching. The README documents additional telemetry and extension capabilities. Some subsystem links rely on that documentation because their implementation was not sampled.
Main entry points: rq_worker.py RQ workers · base.py NoDb controllers · landuse_routes.py Run API · wepp_rq_pipeline.py RQ workflow
Components 19
Run entry
- Run API
wepppy/microservices/rq_engine/landuse_routes.py - RQ workflow
wepppy/rq/wepp_rq_pipeline.py - RQ workers
wepppy/rq/rq_worker.py
Simulation workflow
- Watershed prep
wepppy/nodb/core/watershed.py - Climate inputs
wepppy/nodb/core/climate.py - Soils inputs
wepppy/nodb/core/soils.py - Land-use inputs
wepppy/nodb/core/landuse.py - WEPP simulation
wepppy/nodb/core/wepp.py - Scenario runs
wepppy/nodb/mods/omni/omni_run_orchestration_service.py
Run state
- NoDb controllers
wepppy/nodb/base.py - Redis coordination
wepppy/config/redis_settings.py - Run files
Results and extensions
- Model extensions
wepppy/nodb/mods/disturbed/disturbed.py - Query engine
wepppy/query_engine/app/server.py - Result exports
wepppy/export/export.py
Platform services
- Live telemetry
services/status2/internal/server/server.go - Climate services
wepppy/climates/metquery_client.py
Other components
- WEPPcloud user
- External data sources
Connections 20
- WEPPcloud user → Run API: submits run
- Run API → RQ workflow: enqueues work
wepppy/microservices/rq_engine/landuse_routes.py - RQ workflow → RQ workers: queues jobs
- RQ workers → Watershed prep: prepares watershed
- RQ workers → Climate inputs: prepares climate
- RQ workers → Soils inputs: prepares soils
- RQ workers → Land-use inputs: prepares land use
- RQ workers → WEPP simulation: runs simulation
- RQ workers → NoDb controllers: uses run state
- NoDb controllers → Run files: persists state
- NoDb controllers → Redis coordination: caches and locks
wepppy/nodb/base.py - RQ workers → Scenario runs: runs scenarios
- Scenario runs → WEPP simulation: runs watershed
wepppy/nodb/mods/omni/omni_run_orchestration_service.py - RQ workers → Model extensions: uses extensions
- WEPPcloud user → Query engine: requests results
- Query engine → Run files: queries run data
- RQ workers → Result exports: exports results
- RQ workers → Live telemetry: publishes status
- Climate services → External data sources: requests climate data
wepppy/climates/metquery_client.py - RQ workers → Climate services: acquires climate