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

run nesthd2 with old and new history files

PL
Paul Liu, modified 4 Months ago.

run nesthd2 with old and new history files

Youngling Posts: 10 Join Date: 2/18/14 Recent Posts
For your information, regarding how to run the "nesthd2" successfully on different version of history files.
Most of people can run the  ""nesthd1" without a problem, but not the "nesthd2" because of the old and new history file: "trih-tst.dat".
Let's assume we have two models, one big/coarse one, one fine/small detailed nested one. We have the basic big and small .grd, .enc, . .bnd files are ready to use.

1. I have delft GUI 4.0.1 win32 and 7545 on HPC Linux installed,  I can run the "nesthd1" in the big model with a batch script easily.
nesthd1.exe <nest1.txt  or (nesthd1<nest1.txt under linux)
The nest1.txt file has the required input file names (just a simply and pure txt file):
big.grd
big.enc
 ../fine/small.grd
../fine/small.enc
../fine/small.bnd
nesthd1.adm
big.obs


if you copy the 3 small. files to big model folder, you do not need to define the PATH.
2. By running "nesthd1<nest1.txt" will generate  the "nesthd1.adm" and new "big.obs" file, please go back to include the "big.obs" in your "big.mdf" file, you can using the GUI or matlab dashboard.
3. then run the big model, which will generate, the history file "trih-big.dat"   ......
THE ABOVE batch also works under my HPC linux env version 7545, and widnows cmd evn........
I have some problems to run the NESTHD1 under Dashboard 2.02 (Nesting/nest1_delft3dflow_in_delft3dflow.m file has some issues!)
 
4. you can copy the "nesthd1.adm", and "trih-big.dat", "trih-big.def" to your small model folder, you do not have to, but this will be easier.
5. then, go to your small model folder,  edit a "nest2.txt" file, if you stay at the big model folder, you have to define the small files path.
small.bnd
nesthd1.adm
big 
small.bct
small.bcc
small.dia
0

6. run "nesthd2.exe<nest2.txt', or under Linux "nesthd2<nest2.txt', this will generate the new "small.bct", "small.bcc" files.
7. You have yo include the new bct and bcc fie in your small model small.mdf...... and run the small model......

HOWEVER.   the step #5 doesn't work for the new history file under my 7545 version.
8. But I find we can run it under openearthtool matlab environment:
9. first run oetsetting.m      and then go to big/coarser model folder:
nesthd2('runid','small','inputdir','/home/user/small','admfile','nesthd1.adm','hisfile','trih-big.dat','opt','hydro')
you can go to the small model folder if you copied all three files from big model..
here the trick is: 1) runid, you have to use small or nestted model runid, not the big or coarser one
2) inputdir, should be the small model folder,   and this is very misleading, it actually is the "outputdir", which will save the newly generated small.bct, small.bcc, and small.dia files into that folder automatically. 
10. OR, you can run the nesthd2 under dashboard.     set small model as work directory. then open small.mdf, and go to "Toolbox", -->Nesting.....  
just choose the big model's history file, like trih-big.dat and the nesthd1.adm file, and , then "Run Nesting"...... this will ask you input the name of "small" for .bct file ...........or whatever name you like.
11. then save the whole mdf files..... and run the small file......  
if you have some good or better solutions, please let me know: jpliu AT ncsu.edu
paul