Simulation Time Cycle Diagrams#
Scope#
These diagrams document the canonical time cycle driven by
[simulation.time] inside the simulation orchestration layer.
They focus on:
normalization and validation of the simulation window,
canonical stress-period grid construction,
strict orchestration-level enforcement for flow-process time grids,
typed validation of
[recharge_chronicle]payloads before runtime use,propagation toward forcing preparation and flow solvers,
generator-based forcing built at fine resolution then aggregated to stress periods,
runtime coordination between canonical
time_gridand solvertgrid.
The forcing path now separates three responsibilities:
hydromodpy.physics.hydrology.synthetic.forcinggenerates conceptual hydrological signals such asseasonal_step.hydromodpy.physics.forcing.forcing_bridgeconverts loaded data to homogeneous or heterogeneous solver-ready forcing payloads.hydromodpy.physics.forcing.time_alignmentaligns series on simulation stress-period boundaries.hydromodpy.simulation.forcingremains the stable re-export surface used by orchestration code.
Code map#
hydromodpy/simulation/settings.py: typed simulation settings and canonical time-window validation.hydromodpy/process/hydrology/synthetic/forcing.py: generator-side synthetic forcing helpers.hydromodpy/process/forcing/forcing_bridge.py: generic forcing conversion and unit handling.hydromodpy/process/forcing/time_alignment.py: stress-period aggregation.hydromodpy/process/flow/time_forcing.py: flow-side forcing preparation before adapter dispatch.
Recommended reading path#
hydromodpy/simulation/settings.pyhydromodpy/process/hydrology/synthetic/forcing.pyhydromodpy/process/forcing/forcing_bridge.pyhydromodpy/process/forcing/time_alignment.pyhydromodpy/process/flow/time_forcing.py
Class Diagram#
Structure Diagram#
Activity Diagram#