
A High-Resolution Coupled Riverine Flow, Tide, Wind, Wind Wave, and Storm Surge Model for Southern Louisiana and Mississippi, Part I: Model Development and Validation

It emphasizes our transition from the loose coupling with structured-mesh wave models to the tight coupling with the unstructured-mesh version of SWAN. The rectangle in the upper right and the triangle in the lower left are meant to “pop” from the sides of the poster, as shown in the picture to the right. By running on the same unstructured mesh, SWAN and ADCIRC can pass information locally, on the same core or across inter-core boundaries, without the need for global communication.
The poster itself is linked below. For more information about the SWAN+ADCIRC model, please visit my Web pages about the coupling. For a copy of our paper describing the coupled model, please contact me, and I would be happy to send it to you.
FigureGen is a FORTRAN program that creates images for ADCIRC files. It reads output files (fort.63
, fort.64
, maxele.63
, etc.), grid files (fort.14
, etc.), nodal attributes files (fort.13
), etc. It plots contours, contour lines, and vectors. Using FigureGen, you can go directly from the ADCIRC input and output files to a presentation-quality figure, for one or multiple time snaps, without having to use SMS.
The following example depicts the water levels in ArcGIS as Ike moved through the Gulf:
This program started from a script written by Brian Blanton, and it contains code written by John Atkinson, Howard Lander, Chris Szpilka, Zach Cobell, and others. I converted it to FORTRAN because I am more familiar with that language, and I added the capability to plot vectors, among other things. But, at its core, FigureGen behaves like a script, and it uses system calls to tell other software how to generate the figure(s).
Updated 2012/04/12: This is an old page. It persists on this site for posterity, but the information presented below is no longer up-to-date. When you are done here, then please click forward to this page, which describes how to control refraction errors with limiters on the spectral propagation velocities.
Updated 2011/08/30: Added a link to Part 2.
Updated 2010/02/11: Added refraction as a nodal attribute.
At the end of my instruction manual on how to compile and run SWAN+ADCIRC, I noted that wave refraction can cause problems in regions where the resolution of the bathymetry is insufficient. We worked around this problem by turning off the refraction on the local sub-meshes that were not in our region of interest. On this page, I will provide more description of exactly what can go wrong when waves are allowed to refract on coarse meshes, and I will share more details about our work-around.
It should be noted that wave refraction will always be a problem whenever any wave model is applied on a coarse mesh. This is a general numerical problem whenever the user is trying to compute waves turning over more than 90° in one spatial step. This would be a problem with SWAN, WAM, STWAVE or any other wave model, regardless of if/how they are coupled to a circulation model. As we will see, it is the coarse mesh that causes problems with wave refraction.
If you want the coupled model, then please follow the link at the bottom of the ADCIRC website to request the latest release version. Here is an instruction manual on how to compile and run SWAN+ADCIRC.