How hydrotian/cama-flood_v4 works
Main System Components
a. Preprocessing (Map/Input Preparation)
• /src/src_param
• /src/src_region
• /src/src_dam
• etc/downscale_flddph, etc/levee_test, etc/n-year_flood_depth, etc/storage_to_floodstage, etc/runoff_preset, etc/sealev_boundary, etc/sediment
• Scripts & Python helpers under etc/* (e.g., .sh, .py)
b. Build & Execution Orchestration
• adm/ (compiler‐specific include files)
• src/ & util/ (Fortran codebase + Makefiles)
• gosh/ (job‐submission & run workflows for various HPC configs)
c. Model Core
• src/ (MAIN_cmf.F90, modules controlling boundary, physics, output, MPI, time, tracer, etc.)
• src/ICI (ice module)
• src/sediment (sediment module)
• util/igetday.F90 (utility)
d. Postprocessing & Analysis
• etc/validation (validation scripts, Python)
• etc/result_mapping (plotting)
• etc/… (various analysis workflows)
e. External Dependencies & Environment
• HPC Scheduler (SLURM/PBS/MPI)
• netCDF, MPI libraries
• External input data (maps, gauges, boundary data—not in repo, downloaded separately)
• GitHub (repository, version control)
Architectural Patterns & Design Principles
• Modular Fortran design (separate modules for I/O, physics, tracers, time, etc.)
• Configuration‐driven builds via adm/ include files for cross‐platform HPC builds
• Pipeline/workflow pattern: preprocess ➔ build & run ➔ postprocess
• Separation of concerns: core compute engine vs. data preparation vs. visualization
• Extensibility: new schemes toggled by runtime switches, sample workflows under etc/