intro story Lake

Lake

Lakes and reservoirs are important resources for communities around the globe. They provide food, drinking and irrigation water and can also offer spots for recreation. Under certain conditions lakes can also represent a threat for local communities, such as flooding or limnic eruptions. The ecological state of shallow lakes may be hampered by suspended sediments due to wind driven currents and waves. In deep lakes, stratification can cause undesirable anoxic conditions in the deeper areas. Understanding these systems is crucial to enable a sound management of these water bodies.

 
Delft3D is the state-of-the-art modelling framework for hydrodynamics, water quality, ecology, waves and morphology.
 
Here, in this space, we share knowledge & experiences, and discuss issues related to modelling of lakes.

 

** PLEASE TAG YOUR POST! **

 

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ
Cohesive sediments & muddy systems


 

Message Boards

Coupled FLOW/WAVE with constant wave BC doesn't work without wavecon.runid

ST
Silke Tas, modified 1 Month ago.

Coupled FLOW/WAVE with constant wave BC doesn't work without wavecon.runid

Youngling Posts: 1 Join Date: 3/30/17 Recent Posts
I have set up a coupled FLOW/WAVE model and want to run a couple of different scenarios. The first scenario is based on measurements, so the hydrodynamic boundary conditions are time series based on the measured conditions in the field. I have created a wavecon.runid file with time-varying wave heights and periods. In a different scenario, I want to apply a constant wave height and period for the entire run. So I've created a new directory, copied all files except the wavecon.runid file, defined the correct wave height and period in de runid.mdw file and started the run. Immediately after the start of the simulation, I get the following error: 
forrtl: severe (24): end-of-file during read, unit 36, file [working directory\]wavecon.runid
It seems that the model searches for a wavecon.runid file, and since there is none in the working directory, it creates an empty file called wavecon.runid (which was definitely not present in the directory when I started the run), and when the model tries to read this file, it comes up empty. Q1: Does anyone have an idea why my model cannot run without the wavecon.runid file present?Since this was not the first time I tried to model a scenario with constant wave conditions, I went back to some of my old runs, and I was intrigued to see that in those directories, the file wavecon.runid (filled with time-varying wave conditions, the same file as used for the initial scenario based on the measurements) was present (I must have included this file accidentally when copying the input files to a new directory to test a different scenario). However, the conditions in this wavecon.runid-file were ignored and only the constant wave parameters prescribed in the runid.mdw file were used (so the output files show a constant wave height over the entire duration of the run). The only big difference between those old runs and the new run described above, is that I changed the setting for FLOWBEDLEVEL from "don't use" (in the old runs) to "use but don't extend" (in the run described above). Q2: Does anyone have an idea why the model chose to ignore the wavecon.runid file in this case and used the constant wave parameters defined in the runid.mdw file?
So, two opposite questions, but both situations bug me because I cannot understand why they happen...