intro story Coast / Estuary

Coast / Estuary

Coastal systems are among the most dynamic physical systems on earth and are subject to a large variety of forces. The morphodynamic changes occurring to coastlines worldwide are of great interest and importance. These changes occur as a result of the erosion of sediments, its subsequent transport as bed load or suspended load, and eventual deposition. 
 
Estuaries are partly enclosed water bodies that have an open connection to the coast. Estuaries generally have one or more branching channels, intertidal mudflats and/or salt marshes. Intertidal areas are of high ecological importance and trap sediments (sands, silts, clays and organic matter).
Within the Delft3D modelling package a large variation of coastal and estuarine physical and chemical processes can be simulated. These include waves, tidal propagation, wind- or wave-induced water level setup, flow induced by salinity or temperature gradients, sand and mud transport, water quality and changing bathymetry (morphology). Delft3D can also be used operationally e.g. storm, surge and algal bloom forecasting. 
 
On this discussion page you can post questions, research discussions or just share your experience about modelling coastal and/or estuarine systems with Delft3D FM. 
 

** PLEASE TAG YOUR POST! **

 

 

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

 

 

Message Boards

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

MS
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
AA
aliana alis, modified 1 Month ago.

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

Padawan Posts: 28 Join Date: 10/2/20 Recent Posts
Your post has those facts which are not accessible from anywhere else. It’s my humble request to u please keep writing such remarkable articles buffet catering company Crawley
OO
oshen oshen, modified 1 Month ago.

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

Padawan Posts: 69 Join Date: 10/11/20 Recent Posts
We are really grateful for your blog post. You will find a lot of approaches after visiting your post. I was exactly searching for. Thanks for such post and please keep it up. Great work. ozone free air purifier
OO
oshen oshen, modified 1 Month ago.

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

Padawan Posts: 69 Join Date: 10/11/20 Recent Posts
I haven’t any word to appreciate this post.....Really i am impressed from this post....the person who create this post it was a great human..thanks for shared this with us. comprar seguidor Instagram
AA
aliana alis, modified 18 Days ago.

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

Padawan Posts: 28 Join Date: 10/2/20 Recent Posts
Constant exposure can assist players get more effective and successful in relation to of strategizing at hands per hour. http://128.199.176.50/ The thrill of winning ... Situs Judi Bola
OO
oshen oshen, modified 12 Days ago.

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

Padawan Posts: 69 Join Date: 10/11/20 Recent Posts
When you use a genuine service, you will be able to provide instructions, share materials and choose the formatting style. Whatslock Smart Fingerprint Locks
OO
oshen oshen, modified 11 Days ago.

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

Padawan Posts: 69 Join Date: 10/11/20 Recent Posts
Took me time to read all the comments, but I really enjoyed the article. It proved to be Very helpful to me and I am sure to all the commenters here! It’s always nice when you can not only be informed, but also entertained! seo backlinks
OO
oshen oshen, modified 10 Days ago.

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

Padawan Posts: 69 Join Date: 10/11/20 Recent Posts
Awesome article, it was exceptionally helpful! I simply began in this and I'm becoming more acquainted with it better! Cheers, keep doing awesome! https://apnews.com/press-release/ts-newswire/business-tiffany-young-educational-services-professional-services-a0ad8d84a6ed3fc9855cd7baf436a348
OO
oshen oshen, modified 9 Days ago.

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

Padawan Posts: 69 Join Date: 10/11/20 Recent Posts
A very awesome blog post. We are really grateful for your blog post. You will find a lot of approaches after visiting your post. more details