Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
V
verification
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TsunAWI
verification
Commits
694301f2
Commit
694301f2
authored
5 years ago
by
Natalja Rakowsky
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
b8d271ec
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+14
-8
14 additions, 8 deletions
README.md
with
14 additions
and
8 deletions
README.md
+
14
−
8
View file @
694301f2
...
...
@@ -3,9 +3,9 @@ Small test cases for TsunAWI
Usage
-----
*
First clone or download and build the
t
sun
awi
source code. From the
tsunawi
root
directory, clone or download this verification path. If you put it into another location, fine, but
remeber to adjust the exepath, see below.
*
First clone or download and build the
[
T
sun
AWI
source code
](
https://gitlab.awi.de/tsunawi/tsunawi
)
. From the root
directory
tsuawi/
, clone or download this verification path. If you put it into another location, fine, but
reme
m
ber to adjust the exepath, see below.
*
Check ./test_tsunawi.sh if
```
...
...
@@ -37,23 +37,29 @@ Usage
Test cases
----------
All test cases are kept short with a very reduced number of timesteps.
All test cases are kept short with a very reduced number of timesteps. Also the
setups itself are chosen with regard to small mesh size.
IO is (mostly) switched off, only checksums are compared, netcdf or XML support
is not needed.
However, each directory contains a namelist that can be adjusted for more
realistic setups: increase the number of timesteps, switch on IO.
*
bm1_sloping_beach
*
**
bm1_sloping_beach
**
Synthetic benchmark for the runup on a plain beach
https://nctr.pmel.noaa.gov/benchmark/Analytical/index.html
*
bm2_okushiri
*
**
bm2_okushiri
**
Channel experiment simulating the 1983 tsunami that heavily struck the Monai Valley on the Japanese island of Okushiri.
https://nctr.pmel.noaa.gov/benchmark/Laboratory/Laboratory_MonaiValley/index.html
*
global_cosinebell
*
**
global_cosinebell
**
A very coarse global mesh (far too coarse for realistic simulations!),
initialized with a cosine bell at the approximate location of the Lissabon 1755 earthquake and tsunami,
though with increased magnitude of 9.0.
*
global_cosinebell_restart
*
**
global_cosinebell_restart
**
As above, but the simulation is split half way and restarted once, to test this functionality.
Adding test cases
-----------------
Basically, just add a directory with a namelist.tsunami, with write_final_checksums=.true. switched on.
The script test_tsunawi.sh will automatically enter this directory and run TsunAWI.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment