mhm issueshttps://git.ufz.de/groups/mhm/-/issues2024-02-27T14:13:36+01:00https://git.ufz.de/mhm/mhm/-/issues/255Checks: MPI problems with case 04, 05, 07 and 112024-02-27T14:13:36+01:00Sebastian MüllerChecks: MPI problems with case 04, 05, 07 and 11- case 05 and 07 don't work with MPI in general as the used objective functions are not parallelized
- case 04 and 11 are occasionally failing with the intel compilers (always when coming to the write-out routines)
Related:
- https://gi...- case 05 and 07 don't work with MPI in general as the used objective functions are not parallelized
- case 04 and 11 are occasionally failing with the intel compilers (always when coming to the write-out routines)
Related:
- https://git.ufz.de/mhm/mhm/-/issues/93
- https://git.ufz.de/mhm/mhm/-/issues/192
- https://git.ufz.de/mhm/mhm/-/merge_requests/28
- https://git.ufz.de/mhm/mhm/-/merge_requests/170wishlisthttps://git.ufz.de/mhm/mhm/-/issues/254Doc: MacOS install instructions missing netcdf-fortran package2024-02-26T09:47:50+01:00Sebastian MüllerDoc: MacOS install instructions missing netcdf-fortran packageThere is a [new homebrew formula](https://github.com/Homebrew/homebrew-core/commit/6e5d43832dd8680fd58b292b0514bc150244be1c) for [netcdf-fortran](https://formulae.brew.sh/formula/netcdf-fortran).
Before, netcdf-fortran was part of the [...There is a [new homebrew formula](https://github.com/Homebrew/homebrew-core/commit/6e5d43832dd8680fd58b292b0514bc150244be1c) for [netcdf-fortran](https://formulae.brew.sh/formula/netcdf-fortran).
Before, netcdf-fortran was part of the [netcdf formula](https://github.com/Homebrew/homebrew-core/pull/112159).Sebastian MüllerSebastian Müllerhttps://git.ufz.de/mhm/mhm/-/issues/253Parameter in parameter namelist misslabeled2024-02-26T09:47:43+01:00Carla PeterParameter in parameter namelist misslabeledWithin mhm_parameter.nml parameter rootFractionCoefficient_pervious seems not to have been renamed after changes in the parametrization in 2013 (see mo_mpr_smhorizons.f90 for reference).
Instead of the absolute value, the difference to ...Within mhm_parameter.nml parameter rootFractionCoefficient_pervious seems not to have been renamed after changes in the parametrization in 2013 (see mo_mpr_smhorizons.f90 for reference).
Instead of the absolute value, the difference to rootFractionCoefficient_forest is now fitted, so the parameter should be labelled Delta.https://git.ufz.de/mhm/mhm/-/issues/252date information for dynamic fluxes and states in mHM restart file2024-01-17T11:23:03+01:00Friedrich Boeingdate information for dynamic fluxes and states in mHM restart fileFor operational system like the German Drought Monitor it would help if the mHM restart file contains information on the last date of the written fluxes and states e.g. as a global attribute.For operational system like the German Drought Monitor it would help if the mHM restart file contains information on the last date of the written fluxes and states e.g. as a global attribute.https://git.ufz.de/mhm/mrm/-/issues/3initialization between networks in mrm_init not correct2024-01-16T13:33:33+01:00Stephan Thoberinitialization between networks in mrm_init not correctCheck that level1 and leve11 are correctly provided in
https://git.ufz.de/mhm/mrm/-/blob/develop/src/mRM/mo_mrm_init.f90?ref_type=heads#L174
even if l11 is higher resolution than l1.Check that level1 and leve11 are correctly provided in
https://git.ufz.de/mhm/mrm/-/blob/develop/src/mRM/mo_mrm_init.f90?ref_type=heads#L174
even if l11 is higher resolution than l1.https://git.ufz.de/mhm/mhm/-/issues/250pybind: missing variables in get methods2024-02-08T10:12:17+01:00Sebastian Müllerpybind: missing variables in get methodsSome L1 variables calculated by MPR are missing in the getter methods:
- `L1_fSealed(:, 1 : 1, 1 : nLCoverScene)` (already present)
- `L1_alpha(:, 1 : 1, 1 : nLCoverScene)`
- `L1_degDayInc(:, 1 : 1, 1 : nLCoverScene)`
- `L1_degDayMax(:, ...Some L1 variables calculated by MPR are missing in the getter methods:
- `L1_fSealed(:, 1 : 1, 1 : nLCoverScene)` (already present)
- `L1_alpha(:, 1 : 1, 1 : nLCoverScene)`
- `L1_degDayInc(:, 1 : 1, 1 : nLCoverScene)`
- `L1_degDayMax(:, 1 : 1, 1 : nLCoverScene)`
- `L1_degDayNoPre(:, 1 : 1, 1 : nLCoverScene)`
- `L1_degDay(:, 1 : 1, 1 : nLCoverScene)`
- `L1_karstLoss(:, 1 : 1, 1 : 1)`
- `L1_fAsp(:, 1 : 1, 1 : 1)`
- `L1_petLAIcorFactor(:, 1 : nLAI, 1 : nLCoverScene)`
- `L1_HarSamCoeff(:, 1 : 1, 1 : 1)`
- `L1_PrieTayAlpha(:, 1 : nLAI, 1 : 1)`
- `L1_aeroResist(:, 1 : nLAI, 1 : nLCoverScene)`
- `L1_surfResist(:, 1 : nLAI, 1 : 1)`
- `L1_fRoots(:, 1 : nSoilHorizons_mHM, 1 : nLCoverScene)`
- `L1_maxInter(:, 1 : nLAI, 1 : 1)`
- `L1_kfastFlow(:, 1 : 1, 1 : nLCoverScene)`
- `L1_kSlowFlow(:, 1 : 1, 1 : nLCoverScene)`
- `L1_kBaseFlow(:, 1 : 1, 1 : nLCoverScene)`
- `L1_kPerco(:, 1 : 1, 1 : nLCoverScene)`
- `L1_soilMoistFC(:, 1 : nSoilHorizons_mHM, 1 : nLCoverScene)`
- `L1_soilMoistSat(:, 1 : nSoilHorizons_mHM, 1 : nLCoverScene)` (already present)
- `L1_jarvis_thresh_c1(:, 1 : 1, 1 : 1)`
- `L1_soilMoistExp(:, 1 : nSoilHorizons_mHM, 1 : nLCoverScene)`
- `L1_tempThresh(:, 1 : 1, 1 : nLCoverScene)`
- `L1_unsatThresh(:, 1 : 1, 1 : 1)`
- `L1_sealedThresh(:, 1 : 1, 1 : 1)`
- `L1_wiltingPoint(:, 1 : nSoilHorizons_mHM, 1 : nLCoverScene)`
- `L1_No_Count(:, 1:1, 1:1) ! N0 count`
- `L1_bulkDens(:, 1:nSoilHorizons_mHM, 1:nLCoverScene) ! bulk density`
- `L1_latticeWater(:, 1:nSoilHorizons_mHM, 1:nLCoverScene) ! lattice water`
- `L1_COSMICL3(:, 1:nSoilHorizons_mHM, 1:nLCoverScene) ! cosmic L3 parameter`
Also some calculated variables present in the ouput netcdf files are also missing:
- `L1_AET ! sum(aETSoil(horizons)) * fNotSealed + aETCanopy + aETSealed * fSealed`
- `L1_QD ! runoffSeal * fSealed`
- `L1_QIF ! fastRunoff * fNotSealed`
- `L1_QIS ! slowRunoff * fNotSealed`
- `L1_QB ! baseflow * fNotSealed`
- `L1_RECHARGE ! percol * fNotSealed`
- `L1_SOIL_INFIL_N ! infilSoil(horizon) * fNotSealed`
- `L1_AET_N ! aETSoil(horizon) * fNotSealed`Sebastian MüllerSebastian Müllerhttps://git.ufz.de/mhm/mhm/-/issues/249Test domains: check coordinates of meteo files2024-03-26T11:44:18+01:00Sebastian MüllerTest domains: check coordinates of meteo filesWe found a discrepancy in the input files of test domain 2, where the coordinates of latlon.nc differ from the coordinates of pre.nc although they are on the same level.We found a discrepancy in the input files of test domain 2, where the coordinates of latlon.nc differ from the coordinates of pre.nc although they are on the same level.https://git.ufz.de/mhm/mhm-tools/-/issues/6Pre-Proc: Converter nc2asc2023-04-26T13:05:51+02:00Sebastian MüllerPre-Proc: Converter nc2ascWe need a converter from NetCDF files to ascii-grids (DEM, soil-class, landcover).We need a converter from NetCDF files to ascii-grids (DEM, soil-class, landcover).https://git.ufz.de/mhm/mhm-tools/-/issues/5Pre-Proc: add cropping routine for ascii-grids2023-04-26T13:03:36+02:00Sebastian MüllerPre-Proc: add cropping routine for ascii-gridsCropping ascii grids with a given mask (from another ascii grid) should be added as a pre-processor.Cropping ascii grids with a given mask (from another ascii grid) should be added as a pre-processor.https://git.ufz.de/mhm/mhm/-/issues/248mrm_coupling_mode should be removed2023-05-12T15:04:26+02:00Sebastian Müllermrm_coupling_mode should be removedmrm_coupling_mode is hard coded to be 2 since the standalone version of mRM is not further supported (and even broken)
So we should remove this coupling mode and related doubled code (level1 latlon info and level0 info is read twice cur...mrm_coupling_mode is hard coded to be 2 since the standalone version of mRM is not further supported (and even broken)
So we should remove this coupling mode and related doubled code (level1 latlon info and level0 info is read twice currently).wishlist futurehttps://git.ufz.de/mhm/mhm/-/issues/247L2/L1 and L11/L1 cell-factors are never checked to be integer2023-05-12T15:04:36+02:00Sebastian MüllerL2/L1 and L11/L1 cell-factors are never checked to be integerAll levels are created from L0 but they are never checked to have matching cell-sizes.
This creates miscalculations for example when (dis-)aggregating meteo-data from for example a 3km grid (L2) to a 2km grid (L1).
Both grids are totall...All levels are created from L0 but they are never checked to have matching cell-sizes.
This creates miscalculations for example when (dis-)aggregating meteo-data from for example a 3km grid (L2) to a 2km grid (L1).
Both grids are totally fine for a 100m grid on L0 but the averaging of the meteo-data is wrongly calculated.
Same is true for the routing resolutions (L11).wishlisthttps://git.ufz.de/mhm/mhm-tools/-/issues/4Pre-Proc: merge basinex2023-04-26T13:06:17+02:00Sebastian MüllerPre-Proc: merge basinexThe functionality of the separate [basinex](https://github.com/mhm-ufz/basinex/) should be part of mhm-tools.The functionality of the separate [basinex](https://github.com/mhm-ufz/basinex/) should be part of mhm-tools.https://git.ufz.de/mhm/mhm-tools/-/issues/3Pre-Proc: add latlon creation routines2023-04-26T13:06:29+02:00Sebastian MüllerPre-Proc: add latlon creation routinesThe `create_latlon.py` [file](https://git.ufz.de/mhm/mhm/-/blob/v5.12.0/pre-proc/create_latlon.py) should be moved here.The `create_latlon.py` [file](https://git.ufz.de/mhm/mhm/-/blob/v5.12.0/pre-proc/create_latlon.py) should be moved here.https://git.ufz.de/mhm/mhm/-/issues/243Multiple inflow gauges in a single grid is not yet allowed in mHM2024-02-26T09:47:30+01:00Pallav Kumar Shresthapallav-kumar.shrestha@ufz.deMultiple inflow gauges in a single grid is not yet allowed in mHM**Background**
Currently mHM only accepts one inflow gauge per L11 grid.
**Issue**
If there are more than one inflow gauge per L11 grid, it only takes one of the inflow gauge. This obviously leads to error.
Seems we need to add this...**Background**
Currently mHM only accepts one inflow gauge per L11 grid.
**Issue**
If there are more than one inflow gauge per L11 grid, it only takes one of the inflow gauge. This obviously leads to error.
Seems we need to add this feature in the [add_inflow subroutine](https://git.ufz.de/mhm/mhm/-/blob/develop/src/mRM/mo_mrm_pre_routing.f90#L179) ??
Tagging subroutine author @thober here :)wishlistSebastian MüllerSebastian Müllerhttps://git.ufz.de/mhm/mhm/-/issues/240Hourly discharge simulations require that provided Qobs file starts at hour 0...2024-02-26T09:47:22+01:00Oldrich RakovecHourly discharge simulations require that provided Qobs file starts at hour 00 and end at hour 23To print out hourly discharge simulations, current implementation requires that provided Qobs file starts at hour 00 and end at hour 23,
otherwise, mHM provides only daily Qobs file without the `subdaily_discharge` output file.
We wil...To print out hourly discharge simulations, current implementation requires that provided Qobs file starts at hour 00 and end at hour 23,
otherwise, mHM provides only daily Qobs file without the `subdaily_discharge` output file.
We will provide with @shresthp test datawishlistSebastian MüllerSebastian Müllerhttps://git.ufz.de/mhm/mhm/-/issues/237Simple ideas to improve current snow module in mHM2023-05-12T15:05:59+02:00Pallav Kumar Shresthapallav-kumar.shrestha@ufz.deSimple ideas to improve current snow module in mHMI checked the parameterisation of snow process in mHM, MPR. I noticed that `elevation` and `aspect` haven't been used as a predictor variable for estimating effective parameters (betas) for snow.
I was wondering whether adding elevatio...I checked the parameterisation of snow process in mHM, MPR. I noticed that `elevation` and `aspect` haven't been used as a predictor variable for estimating effective parameters (betas) for snow.
I was wondering whether adding elevation and aspect as predictor variables could be "one of the steps" towards improving snow melting in mHM (??).
![220907_snow_and_elevation](/uploads/c5b8715000918e54e8328d551cb6ce27/220907_snow_and_elevation.gif)
Tagging @thober @rkumar @lesewishlist futureSebastian MüllerSebastian Müllerhttps://git.ufz.de/mhm/mhm/-/issues/236Soil horizon (depth) information is missing in mHM output2023-05-12T15:05:01+02:00Pallav Kumar Shresthapallav-kumar.shrestha@ufz.deSoil horizon (depth) information is missing in mHM output**Issue**
Currently, there is no way to get the information on soil horizon depths of mHM output.
**Solution**
Add the soil horizon information in mHM output. This would be -
1. In `mHM_Fluxes_States.nc` file
2. But adding this infor...**Issue**
Currently, there is no way to get the information on soil horizon depths of mHM output.
**Solution**
Add the soil horizon information in mHM output. This would be -
1. In `mHM_Fluxes_States.nc` file
2. But adding this information to `ConfigFile.log` would also make it "more visible" (??)
Tagging @thober and @rkumar here.wishlist futureSebastian MüllerSebastian Müllerhttps://git.ufz.de/mhm/mhm/-/issues/235Theoretical documentation of mHM and its modules2024-02-26T09:47:05+01:00Pallav Kumar Shresthapallav-kumar.shrestha@ufz.deTheoretical documentation of mHM and its modulesIf I am not wrong, as of today, the mHM documentation [page](https://mhm.pages.ufz.de/mhm/latest/) has ample content that would comprise say the "user manual" but lacks the "theoretical documentation". The only exception is an awesomely ...If I am not wrong, as of today, the mHM documentation [page](https://mhm.pages.ufz.de/mhm/latest/) has ample content that would comprise say the "user manual" but lacks the "theoretical documentation". The only exception is an awesomely compiled [chapter on mRM](https://mhm.pages.ufz.de/mhm/latest/m_r_m.html).
This lack of easy access of theory behind mHM has been commented by many external users. The current two options modellers have are 1) to dive in the source code to get the information, or 2) read [Samaniego et al. 2010 WRR paper](https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2008WR007327) where equations have been layed out but might not be best source to get hold of theory behind mHM on first try.
Questions and comments:
1. Would it make sense to compile chapters for different processes of mHM (snow, evaporation, etc.) like the one for mRM?
2. Who should compile the chapters? Perhaps the authors who are still active with us are the best fitted for this?
3. If this becomes a "multi-person" task, should there be a guideline/ general template that we follow, perhaps the mRM chapter. In my opinion this is important as the structure gives better readability? [This is a reference theoretical documentation](https://swat.tamu.edu/media/99192/swat2009-theory.pdf), which has this nice idea of tabulating the variables and parameters related to a process at end of each chapter.
I am pretty sure this will require some planning and time to complete. Just bringing up the topic so that we communicate on this matter.
Tagging @thober, @rkumar and @lese here.wishlistSebastian MüllerSebastian Müllerhttps://git.ufz.de/mhm/mhm/-/issues/234Flexibility to specify starting and ending hours/minutes in mHM name list for...2022-08-26T10:42:28+02:00Husain Najafihusain.najafi@ufz.deFlexibility to specify starting and ending hours/minutes in mHM name list for simulation time periodWith respect to the new mHM developments (reading hourly meteo forcing in particular), a need has been raised to specify hours and minutes for mHM simulation time period (for the given start and end day in mhm.nml). The issue at the mome...With respect to the new mHM developments (reading hourly meteo forcing in particular), a need has been raised to specify hours and minutes for mHM simulation time period (for the given start and end day in mhm.nml). The issue at the moment is that starting and ending period of the model simulations can only be 00:00 and 23:00, respectively.
It would be great if one can specify %H and %M for simulation period for the starting and ending simulation period, something like
eval_Per(1)%H Start
eval_Per(1)%M Start
eval_Per(1)%H End
eval_Per(1)%M End
With that, one can run mHM for more flexible simulation periods (not necessarily as a dividend of 24-hours), e.g. a 36-hour run starting from any hour of ineterst, say e.g. 03:00 AM. This would be of interest for flood forecasting applications or in cases where meteorological data are recorded from any hours/minutes rather than only 00:00.wishlist futurehttps://git.ufz.de/mhm/mhm/-/issues/224Container for Namelist2022-07-07T10:40:24+02:00Sebastian MüllerContainer for NamelistIn order to be able to set configurations dynamically, it would be good to have a type representation for namelists.
There could be a abstract type implementation in FORCES to provide a template for namelists and routines to read or set...In order to be able to set configurations dynamically, it would be good to have a type representation for namelists.
There could be a abstract type implementation in FORCES to provide a template for namelists and routines to read or set values.
ATM we have the following namelists defined in mHM:
```
src/common/mo_common_read_config.F90:
108 ! namelist directories
109: namelist /project_description/ project_details, setup_description, simulation_type, &
110 Conventions, contact, mHM_details, history
111: namelist /directories_general/ dirConfigOut, dirCommonFiles, &
112 dir_Morpho, dir_LCover, &
115 ! namelist spatial & temporal resolution, optimization information
116: namelist /mainconfig/ iFlag_cordinate_sys, resolution_Hydrology, nDomains, L0Domain, write_restart, &
117 read_opt_domain_data
118 ! namelist process selection
119: namelist /processSelection/ processCase
120
121 ! namelist for land cover scenes
122: namelist/LCover/nLcoverScene, LCoverYearStart, LCoverYearEnd, LCoverfName
123
src/common_mHM_mRM/mo_common_mHM_mRM_read_config.f90:
86 ! namelist spatial & temporal resolution, otmization information
87: namelist /mainconfig_mhm_mrm/ timestep, resolution_Routing, optimize, &
88 optimize_restart, opti_method, opti_function, &
90 ! namelist for optimization settings
91: namelist /Optimization/ nIterations, seed, dds_r, sa_temp, sce_ngs, &
92 sce_npg, sce_nps, mcmc_opti, mcmc_error_params
93 ! namelist for time settings
94: namelist /time_periods/ warming_Days, eval_Per
95
src/mHM/mo_mhm_read_config.f90:
160 ! namelist directories
161: namelist /directories_mHM/ &
162 inputFormat_meteo_forcings, &
173 ! optional data used for optimization
174: namelist /optional_data/ &
175 dir_soil_moisture, &
184 ! namelist for pan evaporation
185: namelist /panEvapo/evap_coeff
186
187 ! namelist for night-day ratio of precipitation, referenceET and temperature
188: namelist /nightDayRatio/ read_meteo_weights, &
189 fnight_prec, fnight_pet, fnight_temp, fnight_ssrd, fnight_strd
190 ! name list regarding output
191: namelist /NLoutputResults/ &
192 output_deflate_level, &
src/MPR/mo_mpr_read_config.f90:
234 ! namelist directories
235: namelist /directories_MPR/ dir_gridded_LAI
236 ! namelist soil database
237: namelist /soildata/ iFlag_soilDB, tillageDepth, nSoilHorizons_mHM, soil_Depth
238 ! namelist for LAI related data
239: namelist /LAI_data_information/ inputFormat_gridded_LAI, timeStep_LAI_input
240 ! namelist for land cover scenes
241: namelist /LCover_MPR/ fracSealed_cityArea
242
243 ! namelist parameters
244: namelist /interception1/ canopyInterceptionFactor
245: namelist /snow1/snowTreshholdTemperature, degreeDayFactor_forest, degreeDayFactor_impervious, &
246 degreeDayFactor_pervious, increaseDegreeDayFactorByPrecip, maxDegreeDayFactor_forest, &
247 maxDegreeDayFactor_impervious, maxDegreeDayFactor_pervious
248: namelist /soilmoisture1/ orgMatterContent_forest, orgMatterContent_impervious, orgMatterContent_pervious, &
249 PTF_lower66_5_constant, PTF_lower66_5_clay, PTF_lower66_5_Db, PTF_higher66_5_constant, &
253 rootFractionCoefficient_pervious, infiltrationShapeFactor
254: namelist /soilmoisture2/ orgMatterContent_forest, orgMatterContent_impervious, orgMatterContent_pervious, &
255 PTF_lower66_5_constant, PTF_lower66_5_clay, PTF_lower66_5_Db, PTF_higher66_5_constant, &
259 rootFractionCoefficient_pervious, infiltrationShapeFactor, jarvis_sm_threshold_c1
260: namelist /soilmoisture3/ orgMatterContent_forest, orgMatterContent_impervious, orgMatterContent_pervious, &
261 PTF_lower66_5_constant, PTF_lower66_5_clay, PTF_lower66_5_Db, PTF_higher66_5_constant, &
266 rootFractionCoefficient_clay, FCmin_glob, FCdelta_glob, jarvis_sm_threshold_c1
267: namelist /soilmoisture4/ orgMatterContent_forest, orgMatterContent_impervious, orgMatterContent_pervious, &
268 PTF_lower66_5_constant, PTF_lower66_5_clay, PTF_lower66_5_Db, PTF_higher66_5_constant, &
273 rootFractionCoefficient_clay, FCmin_glob, FCdelta_glob
274: namelist /directRunoff1/ imperviousStorageCapacity
275 ! PET is input, LAI driven correction
276: namelist /PETminus1/ PET_a_forest, PET_a_impervious, PET_a_pervious, PET_b, PET_c
277 ! PET is input, aspect driven correction
278: namelist /PET0/ minCorrectionFactorPET, maxCorrectionFactorPET, aspectTresholdPET
279 ! Hargreaves-Samani
280: namelist /PET1/ minCorrectionFactorPET, maxCorrectionFactorPET, aspectTresholdPET, HargreavesSamaniCoeff
281 ! Priestely-Taylor
282: namelist /PET2/ PriestleyTaylorCoeff, PriestleyTaylorLAIcorr
283 ! Penman-Monteith
284: namelist /PET3/ canopyheigth_forest, canopyheigth_impervious, canopyheigth_pervious, displacementheight_coeff, &
285 roughnesslength_momentum_coeff, roughnesslength_heat_coeff, stomatal_resistance
286: namelist /interflow1/ interflowStorageCapacityFactor, interflowRecession_slope, fastInterflowRecession_forest, &
287 slowInterflowRecession_Ks, exponentSlowInterflow
288: namelist /percolation1/ rechargeCoefficient, rechargeFactor_karstic, gain_loss_GWreservoir_karstic
289: namelist /neutrons1/ Desilets_N0, COSMIC_N0, COSMIC_N1, COSMIC_N2, COSMIC_alpha0, COSMIC_alpha1, COSMIC_L30, COSMIC_L31
290 !
291: namelist /geoparameter/ GeoParam
292
src/mRM/mo_mrm_read_config.f90:
111 ! namelist spatial & temporal resolution, optmization information
112: namelist /mainconfig_mrm/ ALMA_convention, &
113 filenameTotalRunoff, varnameTotalRunoff, gw_coupling
114 ! namelist directories
115: namelist /directories_mRM/ dir_Gauges, dir_Total_Runoff, dir_Bankfull_Runoff
116: namelist /evaluation_gauges/ nGaugesTotal, NoGauges_domain, Gauge_id, gauge_filename
117 ! namelist for inflow gauges
118: namelist /inflow_gauges/ nInflowGaugesTotal, NoInflowGauges_domain, InflowGauge_id, &
119 InflowGauge_filename, InflowGauge_Headwater
120 ! name list regarding output
121: namelist /NLoutputResults/ &
122 output_deflate_level_mrm, &
458
459: namelist /routing1/ muskingumTravelTime_constant, muskingumTravelTime_riverLength, &
460 muskingumTravelTime_riverSlope, muskingumTravelTime_impervious, muskingumAttenuation_riverSlope
461: namelist /routing2/ streamflow_celerity
462: namelist /routing3/ slope_factor
463 !
src/mRM/mo_mrm_riv_temp_class.f90:
155 ! namelist for river temperature configuration
156: namelist /config_riv_temp/ &
157 albedo_water, &
```wishlist futureSebastian MüllerSebastian Müller