greenland test group (
performs short (5-day) forward runs on a coarse (20-km) Greenland mesh
(see greenland). Here, we describe the shared framework for
this test group and the 3 test cases.
There are no shared config options for the
greenland test group.
Each of the tests and the
RunModel step require an argument for
velo_solver that can be one of
['sia', 'FO']. When a test is set
up to use the ‘FO’ solver, COMPASS will adjust the namelist accordingly
and add a copy of the
albany_input.yaml input file required by the FO
solver. Running with the FO solver requires building MALI with the Albany
The test group has a shared
namelist.landice file with
a few common namelist options related to time step, run duration and calving,
and a shared
streams.landice file that defines
defines a step for running MALI an initial condition downloaded from
restart_test test cases, the model will run multiple times with
different namelist and streams files. To support this functionality, this step
has an attribute
suffixes, which is a list of suffixes for the these
namelist and streams files. The model runs once for each suffix. The default
compass.landice.tests.greenland.smoke_test.SmokeTest performs a
5-day run on 4 cores. It doesn’t contain any Validation.
performs a 5-day run once on 1 core and once on 4 cores. It ensures that
normalVelocity are identical at the end of the two runs
(as well as with a baseline if one is provided when calling
performs a 5-day run once on 4 cores, then a sequence of a 3-day and a 2-day
run on 4 cores. It ensures that
identical at the end of the two runs (as well as with a baseline if one is
provided when calling compass setup).
The restart step works by creating two different namelist and streams files,
one each with
landice as the suffix and one each with
the suffix. The former perform a 3-day run from the initial condition, while
the latter perform a 2-day restart run beginning with the end of the first.