All authors
Claude Skills by lzwei196
github.com/lzwei196354 skills5 installs1,081 views
- DocsRun ParFlow, monitor convergence via kinsol.log, and validate output files.Votes: 0GitHub stars: 231
- DocsExtract hydrological variables from ParFlow PFB output and convert to standard formats.Votes: 0GitHub stars: 231
- PorePy| Field | Value | |------------------|--------------------------------------------------------------| | **Model** | PorePy v1.12.0 | | **Domain** | Fractured porous media simulation (subsurface flow, poromechanics) | | **Language** | Python 3.10+ | | **Build** | pip install (setuptools) ...Votes: 0GitHub stars: 231
- PyAEZ**Package**: hydrocraft-pyaez-crop v1.0.0 **Stats**: 6 pipeline stages | current tool, stage-doc and triplet counts: the KI map at the top of this fileVotes: 0GitHub stars: 231
- PyDeltaRCM**Package**: `pyDeltaRCM-ki` v1.0.0 **Model**: pyDeltaRCM v2.2.0 — Reduced-Complexity Delta Model **Domain**: Geomorphology / Delta Evolution / Sediment Transport **Authors**: Andrew J. Moodie, Jayaram Hariharan, Eric Barefoot, Paola Passalacqua **Paper**: Moodie et al. (2021), JOSS, 6(64), 3398 **Last updated**: 2026-03-26 **Stats**: current tool, stage-doc and triplet counts: the KI map at the top of this file **Validation status**: `tested` (default delta, 5 timesteps) ---Votes: 0GitHub stars: 231
- PyMT```yaml package: name: pymt-ki version: 1.0.0 target_model: PyMT (Python Modeling Toolkit) model_version: 1.3.3.dev0 domain: earth-surface-dynamics / model-coupling-framework language: python authors: [CSDMS team, mcflugen@gmail.com] license: MIT validation_status: tested ``` ---Votes: 0GitHub stars: 231
- PySWMM> PySWMM — Python Wrapper for EPA SWMM5 Stormwater Management Model > Domain: Urban hydrology / stormwater management > Engine: EPA SWMM 5.1.14–5.2.4 via swmm-toolkit > Language: Python 3.10–3.12 ---Votes: 0GitHub stars: 231
- Pywr**Package**: `pywr-knowledge-infrastructure` v1.0.0 **Model**: Pywr 1.30.0 (Python Water Resources Framework) **Domain**: Reservoir operations, water resources management, flood control, water supply **Role in HydroCraft**: Fills the reservoir operations gap — couples with VIC (inflow), CaMa-Flood (regulated routing), DSSAT (irrigation demand), DLBreach (dam-break trigger) ---Votes: 0GitHub stars: 231
- QUINCY> **Version**: QUINCY standalone qs-2026.04-public (real engine `qs.bin`) > **Domain**: terrestrial biogeochemistry (coupled C-N-P, water and energy) > **Last updated**: 2026-10-07 > **Validation status**: real engine (tier `tested`); built-in self-tests reproduced byte for byte > (no official site example is public) ---Votes: 0GitHub stars: 231
- RAPID**Package**: hydrocraft-rapid-routing **Version**: 1.0.0 **Model**: RAPID (Routing Application for Parallel computatIon of Discharge) **Domain**: River network routing **Language**: Fortran 90 + PETSc **Counts**: tools, stage docs and triplets — see the KI map at the top of this file ---Votes: 0GitHub stars: 231
- Ki**Package**: hydrocraft-rapid-routing **Version**: 1.0.0 **Model**: RAPID (Routing Application for Parallel computatIon of Discharge) **Domain**: River network routing **Language**: Fortran 90 + PETSc **Tools**: 5 | **Skill Documents**: 6 | **Diagnostic Triplets**: 20 ---Votes: 0GitHub stars: 231
- RHESSys**Package:** `rhessys-ki` v1.0.0 **Model:** RHESSys (Regional Hydro-Ecologic Simulation System) v7.4 / 5.14.3 **Domain:** Hydrology, Ecohydrology, Biogeochemistry **Language:** C (501 source files) **Build:** GNU Make **Last Updated:** 2026-03-25 | Metric | Value | |--------|-------| | Tools | see the KI map at the top of this file | | Skill Documents | see `docs/` | | Diagnostic Triplets | see the KI map at the top of this file | | Validation Status | HJ Andrews Watershed 8 | ---Votes: 0GitHub stars: 231
- ROMS**Target Model:** ROMS v4.1 (Regional Ocean Modeling System) **Domain:** Ocean hydrodynamics, coastal/estuarine modeling **Developers:** Rutgers University — H. Arango, A. Shchepetkin, J. Warner **License:** MIT/X style **Repository:** https://github.com/myroms/roms ---Votes: 0GitHub stars: 231
- RZWQM2python tools/s7_scenario_assembly/initialize_scenario.py \ /path/to/new_project bengbu_wheat <new_site_name> \ <start_date> <end_date> python tools/s8_execution/run_rzwqm2.py <scenario_dir> <binary_path> ``` **For mass/batch runs**, use `tools/s10_mass_generation/mass_project_generator.py` which automates this entire copy-then-update pipeline for a CSV of sites. ``` KISSPATH_HOME/RZWQM2/RZWQM2/linux/main_ryzen_patched ``` The binary is also copied into each scenario directory by the temp...Votes: 0GitHub stars: 231
- DocsRetrieve crop management parameters from five global geospatial datasets and write them into RZWQM2's `RZWQM.dat` management sections. This closes the gap where management events (planting dates, fertilizer amounts, harvest dates, irrigation mode) were previously inherited verbatim from template scenarios, enabling truly data-driven mass project generation.Votes: 0GitHub stars: 231
- Docs**Stage:** s1_site_config **Pipeline Order:** 1 **Depends On:** None **Tool:** `write_site_properties` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s2_met_prep **Pipeline Order:** 2 **Depends On:** None (independent of site config, but needed before breakpoint generation) **Tools:** `generate_met_file`, `met_quality_check` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s3_brk_generation **Pipeline Order:** 3 **Depends On:** s2_met_prep (requires a completed .met file with daily precipitation data) **Tool:** `create_breakpoint_file` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s4_soil_setup **Pipeline Order:** 4 **Depends On:** s1_site_config **Tools:** `soil_texture_classification`, `pedotransfer_hydraulic`, `write_soil_properties` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s5_node_discretization **Pipeline Order:** 5 **Depends On:** s4_soil_setup (requires horizon depths to be set in RZWQM.dat) **Tool:** `generate_nodes` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s6_initial_conditions **Pipeline Order:** 6 **Depends On:** s4_soil_setup (horizon count and depths must match RZWQM.dat) **Tool:** `write_initial_conditions` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s7_scenario_assembly **Pipeline Order:** 7 **Depends On:** s2_met_prep, s3_brk_generation, s4_soil_setup, s5_node_discretization, s6_initial_conditions **Tools:** `initialize_scenario`, `update_ipnames_paths`, `update_rzx_paths` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s8_execution **Pipeline Order:** 8 **Depends On:** s7_scenario_assembly (complete, validated scenario directory) **Tool:** `run_rzwqm2` ---Votes: 0GitHub stars: 231
- Docs**Stage:** s9_result_parsing **Pipeline Order:** 9 **Depends On:** s8_execution (model must have completed successfully, producing output files) **Tools:** `parse_ana_output`, `parse_layer_output` ---Votes: 0GitHub stars: 231
- Raven**Package**: `hydrocraft-raven` v1.0.0 **Model**: Raven v4.1 (University of Waterloo, Prof. James Craig) **Created by**: Jianyun Zhang Research Group, Hohai University **Last updated**: 2026-03-21 **Stats**: 9 error log entries | current tool, stage-doc and triplet counts: the KI map at the top of this file **Validation Status**: `production_validated` ---Votes: 0GitHub stars: 231
- DocsCompare Raven output with VIC output for the same basin, and optionally couple Raven with CaMa-Flood for routing. The primary use case is quantifying **structural uncertainty** by comparing independent model results.Votes: 0GitHub stars: 231
- DocsChoose the right Raven emulation template for a basin. Wrong choice produces plausible but suboptimal results (e.g., no snow process in a snow basin). This stage determines the entire model structure.Votes: 0GitHub stars: 231
- DocsGenerate the Raven .rvh file defining subbasins and HRUs (Hydrologic Response Units). The .rvh file is the spatial foundation — it defines where and how water moves through the basin.Votes: 0GitHub stars: 231
- DocsBuild the Raven `.rvt` forcing file straight from a forcing source (CMFD, MSWX or NASA POWER) with correct units. **This is the single most critical stage in the entire Raven pipeline.** Raven explicitly states: "Raven ignores units and will not do units conversion." Every unit error produces a silent failure — the model runs fine with completely wrong results.Votes: 0GitHub stars: 231
- DocsRun multiple Raven model structures on the same basin with identical forcing and compare results. This quantifies **structural uncertainty** — how much hydrological predictions depend on model choice. This is Raven's unique capability within HydroCraft.Votes: 0GitHub stars: 231
- DocsOptimize model parameters using DDS (Dynamically Dimensioned Search) to match observed discharge. Calibrate ONLY the best-performing template from the ensemble comparison.Votes: 0GitHub stars: 231
- Ribasim**Package**: `hydrocraft-ribasim` v1.0.0 **Model**: Ribasim 2026.1.0-rc2 (Deltares) **Domain**: Water resources / regional surface water management **Created by**: HydroCraft Auto-Dissect **Last updated**: 2026-03-26 **Stats**: current tool, stage-doc and triplet counts: the KI map at the top of this file **Validation status**: `prototype` ---Votes: 0GitHub stars: 231
- SFINCS**Package**: `hydrocraft-sfincs` v1.0.0 **Model**: SFINCS v2.x (Deltares) **Created by**: Jianyun Zhang Research Group, Hohai University **Last updated**: 2026-03-22 **Stats**: 12 error log entries | current tool, stage-doc and triplet counts: the KI map at the top of this file **Validation**: Step 3 — real-basin flood test; results: see the run records. ---Votes: 0GitHub stars: 231
- DocsDefine the SFINCS computational grid from a basin shapefile or bounding box. This stage determines the spatial extent, resolution, and coordinate reference system for the entire simulation. All subsequent stages depend on the grid definition.Votes: 0GitHub stars: 231
- DocsBuild SFINCS topography (sfincs.dep), active cell mask (sfincs.msk), and index (sfincs.ind) files from a DEM. The quality of flood simulation depends critically on DEM accuracy and vertical datum consistency.Votes: 0GitHub stars: 231
- DocsGenerate spatially varying Manning's n roughness coefficient from land use/land cover data. Manning's n controls flow velocity and is the primary calibration parameter for SFINCS.Votes: 0GitHub stars: 231
- DocsPrepare all forcing inputs for SFINCS: precipitation (rainfall), river discharge boundaries (from CaMa-Flood), and optionally tidal/surge boundaries for coastal domains. This is the most error-prone stage due to **unit conversions**.Votes: 0GitHub stars: 231
- DocsAdd thin dams (levees, embankments), weirs, and drainage structures to the SFINCS model. This stage is OPTIONAL — only needed for domains with significant hydraulic infrastructure that affects flood routing.Votes: 0GitHub stars: 231
- DocsGenerate the main SFINCS configuration file (sfincs.inp) with all simulation parameters. The most critical parameter is the computational timestep `dt`, which must satisfy the CFL stability condition.Votes: 0GitHub stars: 231
- DocsExecute the SFINCS binary with preflight validation, log monitoring, and output verification. SFINCS is a Fortran binary that reads from the current working directory.Votes: 0GitHub stars: 231
- DocsExtract flood results from SFINCS NetCDF output, compute flood statistics, generate GeoTIFF rasters and publication-quality flood maps.Votes: 0GitHub stars: 231
- SHAWpython {KI}/s2_weather_prep/tools/convert_forcing_to_shaw.py --source nasa_power \ --lat 45.3 --lon -75.0 --start_year 2015 --end_year 2019 --mode daily --output site.wea python {KI}/s2_weather_prep/tools/convert_forcing_to_shaw.py --source cmfd \ --forcing_dir KISSPATH_DATA/forcing/Data_forcing_03hr_010deg \ --lat 32.43 --lon 115.6 --start_year 2010 --end_year 2010 --mode daily --output site.wea ``` | `--source` | Read by | Notes | |---|---|---| | `nasa_power` | shared loader (network, one r...Votes: 0GitHub stars: 231
- SNOWPACK- **Package version**: 1.0.0 - **Model**: SNOWPACK 3.7.1 - **Domain**: Cryosphere (snow/land-surface) - **Created**: 2026-03-26 - **Updated**: 2026-04-30 - **Counts**: tools, stage docs and triplets — see the KI map at the top of this file - **Validation status**: production_validated ---Votes: 0GitHub stars: 231
- SUMMA**SUMMA** (Structure for Unifying Multiple Modeling Alternatives) is a flexible multi-physics hydrologic modeling framework developed by NCAR (Clark et al., 2015a,b). Unlike traditional hydrologic models that hardcode one set of process representations, SUMMA lets you **choose** which physics to use for each process via "model decisions" -- then systematically compare alternatives. This knowledge infrastructure enables autonomous AI operation of SUMMA. **Model**: SUMMA (CH-Earth/summa), Fortr...Votes: 0GitHub stars: 231
- Docs> **Stage ID**: s1_domain_setup > **Pipeline order**: 1 of 7 > **Depends on**: noneVotes: 0GitHub stars: 231
- Docs> **Stage ID**: s2_forcing_prep > **Pipeline order**: 2 of 7 > **Depends on**: s1_domain_setupVotes: 0GitHub stars: 231
- Docs> **Stage ID**: s3_decisions > **Pipeline order**: 3 of 7 > **Depends on**: none (can run in parallel with Stage 1)Votes: 0GitHub stars: 231
- Docs> **Stage ID**: s4_parameters > **Pipeline order**: 4 of 7 > **Depends on**: s1_domain_setup, s3_decisionsVotes: 0GitHub stars: 231
- Docs> **Stage ID**: s5_initial_conditions > **Pipeline order**: 5 of 7 > **Depends on**: s1_domain_setup, s4_parametersVotes: 0GitHub stars: 231
- Docs> **Stage ID**: s6_execution > **Pipeline order**: 6 of 7 > **Depends on**: s1_domain_setup, s2_forcing_prep, s3_decisions, s4_parameters, s5_initial_conditionsVotes: 0GitHub stars: 231