Home_intro

intro story DELWAQ

DELWAQ

DELWAQ is the engine of the D-Water Quality and D-Ecology programmes of the Delft3D suite. It is based on a rich library from which relevant substances and processes can be selected to quickly put water and sediment quality models together.

The processes library covers many aspects of water quality and ecology, from basic tracers, dissolved oxygen, nutrients, organic matter, inorganic suspended matter, heavy metals, bacteria and organic micro-pollutants, to complex algae and macrophyte dynamics. High performance solvers enable the simulation of long periods, often required to capture the full cycles of the processes being modelled.

The finite volume approach underlying DELWAQ allows it to be coupled to both the structured grid hydrodynamics of the current Delft3D-FLOW engine and the upcoming D-Flow Flexible Mesh engine (1D-2D-3D) of the Delft3D Flexible Mesh Suite (or even other models such as TELEMAC).

'DELWAQ in open source' is our invitation to all leading experts to collaborate in further development and research in the field of water quality, ecology and morphology using Delft3D. Feel free to post your DELWAQ related questions or comments in this dedicated forum space. If you are new to DELWAQ, the tutorial (in the user manual) is a good place to start. A list of DELWAQ related publications is available here.

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ

Cohesive sediments & muddy systems

 


Message Boards

flow-wave non-stationary wavm file time is offset by 1 hr.

michael schaferkotter, modified 4 Years ago.

flow-wave non-stationary wavm file time is offset by 1 hr.

Youngling Posts: 15 Join Date: 9/6/16 Recent Posts
using v4440 we are running a flow-wave coupled non-stationary simulation.

we have noticed in the wavm_runid file, that the TIME is offset by 1hr.
instead of showing 'TIME' as 0, 60, 120, 180, ..., 2880.
the values are instead 60,120, 180, ..., 2880, 2940.

version v3066 did not behave this way.

i believe i have traced this to the 'settimtscale' routine in wave/src/wave_data.f90:

v4440
subroutine settimtscale(wavetime, timtscale_in, modsim, deltcom)
integer :: timtscale_in
integer :: modsim ! 1: stationary, 2: quasi-stationary, 3: non-stationary
real :: deltcom ! used when modsim = 3: Interval of communication FLOW-WAVE
type(wave_time_type) :: wavetime

wavetime%timtscale = timtscale_in
wavetime%timsec = real(wavetime%timtscale) * wavetime%tscale
wavetime%timmin = wavetime%timsec / 60.0
if (modsim == 3) then
wavetime%calctimtscale = wavetime%timtscale + int(deltcom*60.0/wavetime%tscale)
else
wavetime%calctimtscale = wavetime%timtscale
endif
end subroutine settimtscale


v3066

subroutine settimtscale(wavetime, timtscale_in)
integer :: timtscale_in
type(wave_time_type) :: wavetime

wavetime%timtscale = timtscale_in
wavetime%timsec = real(wavetime%timtscale) * wavetime%tscale
wavetime%timmin = wavetime%timsec / 60.0
end subroutine settimtscale

can someone make an explanation for this code change?
Adri Mourits, modified 4 Years ago.

RE: flow-wave non-stationary wavm file time is offset by 1 hr. (Answer)

Yoda Posts: 1221 Join Date: 1/3/11 Recent Posts
Hi Michael,

Suppose that a coupled FLOW-WAVE simulation is done, where FLOW simulates the time interval [0, 120] and a WAVE simulation is performed at t=0, 60, 120.
With a stationary wave simulation, SWAN produces wave data at t=0, 60, 120.
With a non-stationary wave simulation and a timeinterval of 60, SWAN produces wave data belonging to t=60, 120, 180. WAVE feeds this data to FLOW at t=0, 60, 120.

This behaviour is not changed; resulting parameters should still be the same. The only thing that is changed is the times as written to the wavm-file for non-stationary wave simulations:
In revision 4252 and older, the times as written to the wavm-file were t=0, 60, 120. This is wrong, because the results produced by SWAN are at t=60, 120, 180.
This is solved in revision 4253: t=60, 120, 180
In revision 5404, the initial values used by SWAN at the start time of the first wave calculation are added to the wavm-file: t=0, 60, 120, 180.

Regards,

Adri
Dmitry Kushnir, modified 4 Years ago.

RE: flow-wave non-stationary wavm file time is offset by 1 hr.

Jedi Knight Posts: 107 Join Date: 11/9/12 Recent Posts
Hi Adri,

I'm having the similar issue when running DD-FLOW-WAVE simulation with non-stationary WAVE mode, where WAVE is coupled with FLOW in a 30 min time interval.
The problem shown on the screenshot results in a non-readable wave-results file. This problem appears in the tagged source-code versions from 4289 to 6118 .

Regards,

Dmitry
Adri Mourits, modified 4 Years ago.

RE: flow-wave non-stationary wavm file time is offset by 1 hr. (Answer)

Yoda Posts: 1221 Join Date: 1/3/11 Recent Posts
Hi Dmitry,

I solved a bug related to nested wave grids in combination with non-stationary SWAN computation. This is in revision 6580 in the trunk and did not end up in a tagged version yet (I'm working on that). You can try what happens when using the trunk version.

Regards,

Adri
Dmitry Kushnir, modified 4 Years ago.

RE: flow-wave non-stationary wavm file time is offset by 1 hr.

Jedi Knight Posts: 107 Join Date: 11/9/12 Recent Posts
Hi Adri,

Thanks for solving this bug. I've tried to run simulation using the trunk version and all the results have been readable.

Best regards,

Dmitry