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

Issue with time zone and astronomic boundary conditions in Delft Dashboard

DL
Daniel Livsey, modified 3 Years ago.

Issue with time zone and astronomic boundary conditions in Delft Dashboard

Youngling Posts: 2 Join Date: 2/23/16 Recent Posts
All,

I am running Delft Dashboard from Matlab and I am trying to generate astronomic boundary conditions from the "Model Maker" toolbox of Delft Dashboard. When I stipulate the "Time Zone (h)" in the "Time Frame" tab, a value used to adjust the astronomic boundary constituents, the boundary condition routine fails and I receive the following error in the Matlab command window, "Assignment has more non-singleton rhs dimensions than non-singleton subscripts". The boundary condition routine runs if I leave "Time Zone (h)" empty.

Has anyone else had this issue and found a solution?

Daniel
AD
A D, modified 3 Years ago.

RE: Issue with time zone and astronomic boundary conditions in Delft Dashbo

Youngling Posts: 15 Join Date: 9/25/17 Recent Posts
Did you manage to resolve the issue?
If not, check the timezone.
DL
Daniel Livsey, modified 3 Years ago.

RE: Issue with time zone and astronomic boundary conditions in Delft Dashbo

Youngling Posts: 2 Join Date: 2/23/16 Recent Posts
Hi A D,

No, I have not resolved the issue. When you say, "check the timezone" I am only aware of the "Time Zone (h)" field in the "Time Frame" tab of Delft Dashboard. Is there another location or field in Delft Dashboard where I may stipulate a timezone? I am trying to use - 8 GMT/UTC (i.e. PST).

Thanks,
Daniel
AD
A D, modified 3 Years ago.

RE: Issue with time zone and astronomic boundary conditions in Delft Dashbo

Youngling Posts: 15 Join Date: 9/25/17 Recent Posts
Nope. As far as I know, that is the only place where you can set it.
I'm not sure what could be wrong with your model.
These are the points mentioned in the FLOW manual under the Local Time Zone section. Just check if you have entered anything wrong.

The time difference between local time and UTC.
The time zone is defined as the time difference (in hours) between
the local time (normally used as the time frame for Delft3D-FLOW)
and Coordinated universal time (UTC). The local Time Zone is used
for for two processes:
To determine the phases in local time of the tidal components
when tide generating forces are included in the simulation, see
Data Group Processes.
To compare the local time of the simulation with the times at
which meteo input is specified, e.g. wind velocities and atmospheric
pressure. These can be specified in a different time zone.

Restrictions:
If open boundaries are used with forcing type Astronomic then dates may not be before
1 January 1900.
The start and stop date must be equal to or larger than the reference date.
The start and stop time must be integer multiples of the time-step.
The simulation stop time must be equal to or larger than the simulation start time.
The time step must be positive.