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/sphinx_doc/building.rst
+6-6
Original file line number
Diff line number
Diff line change
@@ -33,10 +33,10 @@ ERF uses the paradigm that different executables are built in different subdirec
33
33
using gmake (see below), the user/developer should build in the directory of the selected problem. When using
34
34
cmake (see below), separate executables are built for all of the problem directories listed in ``Exec/CMakeLists.txt``.
35
35
The problem directories within ``Exec`` are sorted into 1) science-relevant setups, such as ``ABL`` for modeling the atmospheric
36
-
boundary layer or ``DensityCurrent`` for running the standard density current test case, etc, 2) regression tests in
37
-
``Exec/RegTests`` that are used for testing specific known aspects of the code functionality, such as boundary conditions or
38
-
Rayleigh damping, and 3) tests for features under development in ``Exec/DevTests``, such as moving terrain. There is a
39
-
README in each problem directory that describes the purpose/role of that problem.
36
+
boundary layer or ``DensityCurrent`` for running the standard density current test case, etc, 2) dry and moist regression tests in
37
+
``Exec/DryRegTests`` and ``Exec/MoistRegTests`` respectively, that are used for testing specific known aspects of the code functionality,
38
+
such as boundary conditions or Rayleigh damping, and 3) tests for features under development in ``Exec/DevTests``, such as moving terrain.
39
+
There is a README in each problem directory that describes the purpose/role of that problem.
40
40
41
41
GNU Make
42
42
~~~~~~~~
@@ -70,7 +70,7 @@ or if using tcsh,
70
70
71
71
setenv AMREX_HOME /path/to/external/amrex
72
72
73
-
#. ``cd`` to the desired build directory, e.g. ``ERF/Exec/RegTests/IsentropicVortex/``
73
+
#. ``cd`` to the desired build directory, e.g. ``ERF/Exec/DryRegTests/IsentropicVortex/``
74
74
75
75
#. Edit the ``GNUmakefile``; options include
76
76
@@ -130,7 +130,7 @@ or if using tcsh,
130
130
131
131
The name of the resulting executable (generated by the GNUmake system) encodes several of the build characteristics, including dimensionality of the problem, compiler name, and whether MPI and/or OpenMP were linked with the executable.
132
132
Thus, several different build configurations may coexist simultaneously in a problem folder.
133
-
For example, the default build in ``ERF/Exec/RegTests/IsentropicVortex`` will look
133
+
For example, the default build in ``ERF/Exec/DryRegTests/IsentropicVortex`` will look
134
134
like ``ERF3d.gnu.MPI.ex``, indicating that this is a 3-d version of the code, made with
0 commit comments