Skip to content

Redo infiltration#330

Draft
Leynse wants to merge 24 commits into
mainfrom
redo_infiltration
Draft

Redo infiltration#330
Leynse wants to merge 24 commits into
mainfrom
redo_infiltration

Conversation

@Leynse

@Leynse Leynse commented May 6, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

Leynse and others added 24 commits February 4, 2026 13:28
…ric function

- Apply first to netcdf storage volume
- Work in progress still
…(can always add a snapwave one) and with real*4 (can always make a double version as well)

- In sfincs_domain.f90, 'call read_netcdf_storage_volume' is now replaced by 'call read_netcdf_quadtree_to_sfincs'
- Succesfully tested for testbed run 'storage_volume_qt_sbg_thd2'
- Tested by supplying dummy stoarge volume nc file for manning, now nicely stops
- If netinfiltrationfile exists, then netinftype should be used
- Do precheck of netinfiltrationfile before reading in all data
- Current implementation will check and retrieve multiple variables from the same file (e.g. cnb) individually
- Added some documentation what part of the code is reading/allocating/generic needed conversions
- Kept naming in netcdf files for now consistent with the equivalent netcdf files
…pe (orignal vs netcdf) vs grid type (regular vs quadtree)

- Idea for now is if quadtree model, only netcdf input is support, and for regular model only the original binary files
* - Added version for reading in netcdf quadtree manningfile
- For now: input argument is still manningfile, internally checked whether it is a netcdf file or binary
- For now: expected variable in the netcdf file is 'manning'
- For now: tested only with dummy of stoarge nc file
- Full testing pending on having ncinput example

* - Add non-stopping warning if a manningfile is prescribed while there is also a subgridfile, because then it will be unused!

* - Bugfix in general read_netcdf_quadtree_to_sfincs routine

* - Bugfix that the netcdf manningfile is actually read in

* - Now define 'rghfield' in sfincs_data.f90 rather than sfincs_domain.f90, so we can use that variable for output to netcdf file

* - Add 'manning' as netcdf output in case not a subgrid model, and if manningfile supplied (either binary for regular model, or as netcdf for quadtree
- Tested and working for new quadtree netcdf manningfile input
…ithub.com/Deltares/SFINCS into 272-add-netcdf-quadtree-option-input-for-all-infiltration-options-using-generic-reader
@Leynse Leynse added this to the 2026.02 release milestone May 6, 2026

@Leynse Leynse left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's discuss with @maartenvanormondt what part of this is already redone in #329

Comment thread docs/input.rst
6. The bucket model: linear reservoir with losses

Infiltration is specified with either constant in time values in mm/hr (both uniform and spatially varying), or using more detailed parameters for the Curve Number method, The Green-Ampt method or Horton method.
Spatially uniform infiltration is still specified directly in sfincs.inp with ``qinf``. All modern spatially varying infiltration and bucket-model input should be provided through ``infiltrationfile`` together with ``infiltrationtype``. The older binary keywords (``qinffile``, ``scsfile``, ``smaxfile``, ``sefffile``, ``ksfile``, ``psifile``, ``sigmafile``, ``f0file``, ``fcfile`` and ``kdfile``) remain available for backward compatibility only and should be removed in a future cleanup.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important clarification - netcdf infiltration ONLY works for quadtree models, while the old binary options ONLY work for regular models. So it is not just backward compatibility here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants