You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/users_guide/ocean/test_groups/turbulence_closure.rst
+72-13Lines changed: 72 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,16 +7,75 @@ The ``turbulence_closure`` test group implements studies of the surface layer
7
7
evolution under different kinds of surface forcing for different turbulence
8
8
closures.
9
9
10
-
config_LES_mode = .true.
11
-
config_use_two_equation_turbulence_model = .true.
12
-
config_two_equation_model_choice = 'omega'
13
-
config_use_cvmix = .false.
14
-
config_two_equation_length_min = 0.1
15
-
config_two_equation_tke_min = 1e-10
16
-
config_two_equation_psi_min = 1e-10
17
-
config_tke_ini = 1.0e-30
18
-
config_LES_noise_enable = .true.
19
-
config_LES_noise_max_time = 150
20
-
config_LES_noise_min_level = 5
21
-
config_LES_noise_max_level = 45
22
-
config_LES_noise_perturbation_magnitude = 1e-4
10
+
The domain is periodic in the horizontal dimensions and no-slip at both vertical boundaries.
11
+
12
+
Initial temperature is XX and salinity is XX.
13
+
14
+
Variants of the test case are available at 1-m, 2-m and 10-km horizontal
15
+
resolution. The O(1)m resolution test cases are designed to be run in LES mode
16
+
whereas the O(1)km test cases are designed to be used to test turbulence closures in "standard" MPAS-Ocean.
17
+
18
+
The vertical resolution for the LES test cases is XX whereas the standard resolution test cases have a vertical resolution of XX.
19
+
20
+
There are currently two surface forcing variants available, cooling and evaporation.
21
+
22
+
All test cases have 2 steps,
23
+
``initial_state``, which defines the mesh and initial conditions for the model,
24
+
and ``forward``, which performs time integration of the model. The ``default`` test also has an XX step which performs visualization.
25
+
26
+
27
+
config options
28
+
--------------
29
+
30
+
namelist options
31
+
----------------
32
+
When resolution is XX, LES mode is active with the following config options:
33
+
34
+
.. code-block:: cfg
35
+
36
+
config_LES_mode = .true.
37
+
config_use_two_equation_turbulence_model = .true.
38
+
39
+
# TODO Explain what 'omega' means
40
+
config_two_equation_model_choice = 'omega'
41
+
config_use_cvmix = .false.
42
+
43
+
config_two_equation_length_min = 0.1
44
+
config_two_equation_tke_min = 1e-10
45
+
config_two_equation_psi_min = 1e-10
46
+
config_tke_ini = 1.0e-30
47
+
48
+
config_LES_noise_enable = .true.
49
+
config_LES_noise_max_time = 150
50
+
config_LES_noise_min_level = 5
51
+
config_LES_noise_max_level = 45
52
+
53
+
# TODO Can you provide any guidance here about what appropriate choices
54
+
# might be?
55
+
config_LES_noise_perturbation_magnitude = 1e-4
56
+
57
+
default
58
+
-------
59
+
60
+
The default version of the turbulence closure test case is available for multiple resolutions: ``ocean/baroclinic_channel/1m/default``, ``ocean/baroclinic_channel/2m/default``, ``ocean/baroclinic_channel/10km/default``.
61
+
Simulation times vary for LES mode, XX, and standard mode, XX.
62
+
63
+
decomp_test
64
+
-----------
65
+
66
+
``ocean/turbulence_closure/10km/decomp_test`` runs a short (15 min) integration
67
+
of the model forward in time on 4 (``4proc`` step) and then on 8 processors
68
+
(``8proc`` step) to make sure the resulting prognostic variables are
69
+
bit-for-bit identical between the two runs. Currently, only 10-km horizontal
70
+
resolution is supported.
71
+
72
+
restart_test
73
+
------------
74
+
75
+
``ocean/turbulence_closure/10km/restart_test`` runs a short (10 min)
76
+
integration of the model forward in time (``full_run`` step), saving a restart
77
+
file every 5 minutes. Then, a second run (``restart_run`` step) is performed
78
+
from the restart file 5 minutes into the simulation and prognostic variables
79
+
are compared between the "full" and "restart" runs at minute 10 to make sure
80
+
they are bit-for-bit identical. Currently, only 10-km horizontal resolution is
0 commit comments