Riverlab

RE: Problem to find equilibrium under variable discharge

2023-03-09T06:24:20Z

Hi,

The space marching method is something for Liselot to answer... I will reach her. The crash occurs because the size of `Mak` does not match with the number of flownodes (`dx`) and the number of effective size fractions (`nef`). There must be something murky there. Maybe you could stop in debug mode and check what are the dimensions of `Mak`.

Regards,

V

Issue running the base bifurcation example provided in the repository

2023-03-08T15:37:46Z

Hi,

I am exploring the bifurcation options in ELV. Unfortunately, the input file for the bifurcation is not working. Can someone help me with the error codes---

***
Size inputs must be integers. in check_bra, at line 185
The parents are:
1)    check_input, at line 109
2)    ELV, at line 85
3)    run_ELV, at line 53
4)    oh_ELV_please_run, at line 157
5)    main_run_single, at line 37

***

The input file is the same as in svn. But I have attached it here.

Thanks in advance.
Best wishes,
Kifayath

Problem to find equilibrium under variable discharge

2023-03-08T15:38:44Z

Hi,
I have the following question-

1. I have been trying to calculate using the space marching method (initype=52) for unisize sediment single branch problem. For initype 2, the code runs smoothly but with 52 it crashes with the following set of messages-

***
Number of elements must not change. Use [] as one of the size inputs to automatically calculate the appropriate size for that dimension. in sediment_transport, at line 145
The parents are:
1)    march_step_uni, at line 62
2)    ini_equi, at line 130
3)    initial_condition_construction, at line 259
4)    condition_construction, at line 85
5)    ELV, at line 106
6)    run_ELV, at line 53
7)    oh_ELV_please_run, at line 157
8)    main_run_single, at line 37

***

I tried to follow the error code, but could not solve it. What is the problem in this case? I have attached the input file.

Thanks in advance.
Best wishes,
Kifayath

RE: Issue using initial conditions for sediment fractions from restart file

2023-03-01T16:18:37Z

From Willem:

[17:13] Willem OttevangerHi Eki,

I have tested the nourishment with a time series and it appears to work.
Could you let me know if the following files work for you too?

Kind regards,
Willem

nourishment.dad

1	[DredgeFileInformation]
2	FileCreatedBy = Willem Ottevanger
3	FileCreationDate = 01-03-2023
4	FileVersion = 01.02
5	[General]
6	PolygonFile = nourishment.pol
7	InPolygon = 2 # Indicate how to check whether a grid cell is inside polygon 1: all corners (min. area), 2: centre (default), 3: one of the corners (max. area)
8	TimeSeries = nourishment.bct
9	[Nourishment]
10	Name = Nourishment
11	MaxVolRate = 365
12	DistrOverDump = 1
13	Dump = Nourishment1
14	Sediment = Sediment1
15	SedPercentage = 0.0
16	Sediment = Sediment2
17	SedPercentage = 0.0
18	Sediment = Sediment3
19	SedPercentage = 100.0
20	Sediment = Sediment4
21	SedPercentage = 0.0
22	Sediment = Sediment5
23	SedPercentage = 0.0
24	Sediment = Sediment6
25	SedPercentage = 0.0
26	Sediment = Sediment7
27	SedPercentage = 0.0
28	Sediment = Sediment8
29	SedPercentage = 0.0
30	Sediment = Sediment9
31	SedPercentage = 0.0
32	Sediment = Sediment10
33	SedPercentage = 0.0
34	Sediment = Sediment11
35	SedPercentage = 0.0
36	Sediment = Sediment12
37	SedPercentage = 0.0
38	Sediment = Sediment13
39	SedPercentage = 0.0
40	Sediment = Sediment14
41	SedPercentage = 0.0
42	Sediment = Sediment15
43	SedPercentage = 0.0
44	Sediment = Sediment16
45	SedPercentage = 0.0

nourishment.pol

1	Nourishment1
2	5 2
3	-0.560837 4623.072754
4	1.761494 4623.072754
5	1.700382 4596.793457
6	1.578152 4578.092285
7	-0.194153 4578.214355

nourishment.bct

1	location 'Nourishment'
2	time-function 'non-equidistant '
3	reference-time 19940101
4	time-unit 'seconds'
5	interpolation 'block'
6	parameter 'time ' unit ' '
7	parameter 'active ' unit '-'
8	0.0000 1.0
9	536457600.000 1.0
10	820454400.000 1.0

RE: Issue using initial conditions for sediment fractions from restart file

2023-02-22T13:51:08Z

Good afternoon everyone,

I will be following up on Birgits research, which will almost certainly mean that I will be using the same model. Therefore, I was wondering if you had any time to look at the problems Birgit ran in to.

Kind regards,

Eki

RE: Issue with unisize runs in ELV

2023-02-09T11:15:01Z

In addition, I am using flowtype 1 (steady), and steady solver type 1 (energy euler)

Issue with unisize runs in ELV

2023-02-09T11:13:16Z

Hi! I am trying to run a very simple unisize, constant discharge, single branch model in elv to find the equilibrium solution. The inputs look like the following:
input.sed.dk =[2]./1000; input.ini.Fak = [1]; input.ini.fsk = [1];
input.ini.slopeb = 1*1e-4; input.ini.initype=1;

input.bcm.type=1; input.bcm.NFLtype=1; input.bcm.NFLparam=[1e-4,0.05]; Qbk0_base = 0.05; input.bcm.Qbk0_tot = 0.05;

input.bch.uptype=1; input.bch.Q0=2000; input.tra.cr=2 %Engelund Hansen;

input.mor.gsdupdate=7;

input.grd.L=100e3; input.grd.dx=2000; input.frc.Cf=0.004; input.mdv.dt=86400

When I run this (along with the other inputs) input set up to calculate the equilibrium with initype=1, the get_equivals_V gets an error - "Error using optimoptions
Invalid solver specified. Provide a solver name or handle (such as 'fmincon' or @fminunc).
Type DOC OPTIMOPTIONS for a list of solvers."

if I choose initype=2, then the substrate runs out. I am not sure which parameter I am putting in wrong. Any help would be much appreciated.

RE: Parameters responsible for "Warning: Bedlevel exceeds 5% waterdepth"

2023-02-04T13:10:27Z

Beware that the warning does not say that the bed level exceeds 5% of the water depth, but the bed level change exceeds 5% of the water depth. The time step is excessively large or the flow depth is excessively small for morphodynamic update. Depending on the case the message can be ignored or not. For instance, if you are interested in main channel dynamics and the warning occurs in the floodplain during a flood, you may decide that it is better to have a faster simulation with soe innacuracy in the floodplain.

Parameters responsible for "Warning: Bedlevel exceeds 5% waterdepth"

2023-02-04T05:52:23Z

I was wondering which parameters in the morphodynamic model are responsible for the "Warning: Bedlevel exceeds 5% waterdepth" in morphodynamic model. Is it the sediment feed volume, minimum thickness of computation or other parameters in the .mor and .sed files?

RE: Model not taking the sediment data from bcm file

2023-01-31T08:23:15Z

Maybe a sudden increase of the upstream sediment load by 10 times its original value is causing a shock wave that would need a very small time step to be resolved. Sediment may be piling up at the upstream end. Rather than decreasing the time step, I would try gradually increasing the load, if that is acceptable for your research.

RE: Model not taking the sediment data from bcm file

2023-01-31T03:33:48Z

I made the changes as mentioned above. I assigned the IBedCond = 4 at upstream boundary and 1 at downstream boundary. And then I put ICmpCond=0. I am using 2 fractions of sediment with 0.5m thickness each. I ran the model without sediment feed first. I extracted the maximum sediment transport at each timestep among all cross-section and multiplied this by 10 to feed into the new model. When I check the results, I found that there was no sediment feed into the channel after first timestep. The cumulative transport curve showed a big rise at the start and no sediment change in the transport. I checked the .dia file. It is full of Bed change exceeds 5% of waterdepth after ...timesteps and Erosion Shortage at NM. Does this indicate that there is no feed of sediment from the upstream boundary (which I assigned in the .mor and .bcm files) or the values for the parameters need some changes?

RE: Model not taking the sediment data from bcm file

2023-01-23T09:14:57Z

You cannot fix the bed at an outflowing boundary (in a river case, the downstream end). The bed level will be updated. Only if flow would reverse, the boundary condition would be applied.

As for the bed-composition boundary condition, if you specify the load per size fraction it has no meaning to fix the upstream composition, you are already providing all necessary BC's.

RE: Model not taking the sediment data from bcm file

2023-01-23T05:48:46Z

Thanks a lot. I assigned the IBedCond = 4 at upstream boundary and 1 at downstream boundary. And then I put ICmpCond=0. I can see the sediment feed now in the model. Is it a good idea to fix the bed at the downstream boundary? And how will the model be affected for ICmpCond=0 or 1? I only found a short description in the table of the manual. Would be helpful to be clear on this. Thanks once again.

RE: Model not taking the sediment data from bcm file

2023-01-23T05:31:00Z

The question is then, where are you observing the cumulative load? You could add a cross-section right downstream of the upstream boundary to check the sediment that enters the model. In any case, by comparing the map results, you should find differences between runs.

RE: Model not taking the sediment data from bcm file

2023-01-21T20:14:46Z

I am using ICmpCond=0 and IBedCond=4 for my model. It is running smoothly but again I see no change in the bedload transport. Am I taking wrong reference to see the impact of the sediment feed in the channel? Does the bedload transport remain constant irrespective of the additional sediment for the same discharge? I assume transport remain the same but the bedlevel might vary due to storage for additional sediment. I am a bit confused if it is with the input file or the output interpretation. What could be the best output variable to observe such changes? Thank you

RE: Model not taking the sediment data from bcm file

2023-01-20T05:00:41Z

What is the sediment composition in the upstream end of the domain and what boundary condition for the upstream composition are you imposing? If the initial composition is unisize (it seems based on your explanation) and the boundary condition for composition is fixed, you are not allowing the necessary changes in composition for the sediment transport per size fraction to enter.

In short, check that

1	ICmpCond=0

in the mor-file.

Also, check that you are correctly setting the boundary condition of the bed level upstream to sediment load. That is,

IBedCond

must be 4 or 5.

Model not taking the sediment data from bcm file

2023-01-19T20:42:22Z

I ran a morphodynamic model with varying sediment feed. However, the output is showing the same amount of cumulative bedload transport for all model runs. I assume the model is not taking the sediment feed data and just working on the initial bed composition. I generated a bcm file for sediment feed and flagged this within the mor file. I kept all the other conditions same for all model runs except the sediment feed bcm file. I ran another channel section with varying sediment feed. Both the models are working but the sediment feed doesn't differ for sediment scenarios. Can anyone please suggest what might be causing this? Thanks

RE: Open earth tool for cumulative erosion/deposition map in dflowfm

2022-09-08T09:34:26Z

When using Quickplot, be aware of the option of recording a script by clicking on the 8th icon starting from the left, the one showing a red circle with an "M". Then you can see the commands needed to load data and then plot it, so you can adjust it to your needs.

If you want more freedom, I would suggest you to use the EHY tools. For instance, use <EHY_getGridInfo> to get the grid, <EHY_getMapModelData> to load map-file data, and <EHY_plotMapModelData> to plot it.

Open earth tool for cumulative erosion/deposition map in dflowfm

2022-09-08T05:54:38Z

I want to generate a cumulative erosion/deposition map using the codes available in dflowfm under open earth tools. Can anyone please tell me what is the name of the code for this? I tried to generate the map in quickplot but I couldn't reverse the colorbar in the GUI. Any one of the solutions to the above problems will work for me.
Thank you

RE: Spatially varying initial sediment thickness file assignment

2022-07-21T04:19:58Z

When using the the initial composition file using flag <inicomp> in the mor-file, the initial sediment thickness file under flag <IniSedThick> in the sed-file is overwritten (i.e., not used).