APES Wind Run Example Results
The Zipped Archive contains the input and output files for each test case.
|
Version of ADCIRC Code |
Zipped Archive |
|
43_03 |
|
|
45_06 |
|
|
45_06 |
|
|
45_06 |
|
|
45_08 |
|
|
45_08 |
|
|
45_08 |
|
|
45_08 |
Information about the naming convention of test cases:
Legacy. Several improvements have been made in recent versions of
ADCIRC, including computation in double precision, the changeover to an
improved algorithm for the integration of area around a node, and a recommended
higher tolerance for iteration convergence. The result of these improvements is
that output from v45.06 is not the same as (is better than) output from earlier
versions using the same input data. In order to confirm that the differences
are due to improvements and not bugs, v45.06 was recompiled to use single
precision and the old area integration algorithm. The input files for the test
cases were run just as they were for previous versions, including their old
convergence tolerances---usually 1e-5. The resulting output data were labeled
“legacy” and are for comparison with old versions of ADCIRC.
Forward. In order to compare the results from
v45.06 with future versions of ADCIRC, the convergence tolerance was changed
from 1e-5 to 1e-10 in the fort.15 files. The code was then run with no changes,
i.e., in the default, as-distributed condition. The results were labeled
“forward” on the results pages; these new input files will be used
for current and future testing of ADCIRC.
Parallel. ADCIRC v45.06 was run in parallel on 2
CPUs to confirm that it gave the same results as in a serial run. The results were
labeled “parallel” on the results pages.
Serial. This is a single processor run of an example problem;
it is the same as the “forward” test of v45.06.
PC. The predictor-corrector time stepping algorithm was
activated by selecting a negative time step. This test was added to the suite
after I inadvertently introduced a bug into the predictor-corrector algorithm
while fixing a different bug. Please note that the predictor-corrector
algorithm has not been applied as broadly as ADCIRC's default time stepping
procedure. Note also that the predictor-corrector algorithm passed on four example
problems (i.e., produced results very similar to “serial” test),
but failed (blew up) on the Shinnecock Inlet problem.
Hot. This test was carried out by cold starting the example
problem and running it until a hot start file was generated, approximately
halfway through. Then it was hot started and run to completion. The results
were compared to the “serial” case, where the simulations start
from cold and run all the way to completion. The purpose was to ensure that a
hotstart does not change or perturb the solution. I discovered and fixed two
hotstart bugs with this test case, one in 2D for input files where NOLIFA != 0,
and another one in 3D.
Jason G. Fleming, December
2005
