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: RELEASE_NOTES.md
+1
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,7 @@ Notable changes include:
32
32
* Cleaned up use of std::any in State objects using a visitor pattern to be rigorous ensuring all state entries are handled properly
33
33
during assignement, equality, and cloning operations. This is intended to help ensure our Physics advance during time integration
34
34
is correct.
35
+
* Performance regression testing is now available. All developers are encouraged to run the performance testing suite for any code changes that might impact performance. See documentation for more details.
35
36
36
37
* Build changes / improvements:
37
38
* Distributed source directory must always be built now.
Copy file name to clipboardexpand all lines: docs/build_guide/include/tests.rst.inc
+8-82
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,14 @@
8
8
Basic Smoke Test
9
9
================
10
10
11
-
After a build and install it's recommended to perform a quick smoke test with Spheral to see if the Spheral environment was installed and all of the libraries were built and linked together correctly.
11
+
After a build and install, we recommend you perform a smoke test with Spheral toensure the Spheral environment is installed and linked correctly.
12
12
13
13
From your install directory run:
14
14
::
15
15
16
16
./spheral -c "import Spheral"
17
17
18
-
This will run the Spheral Python process and try importing the Spheral modules. If successful you should see a banner printed with information about the version of Spheral, after which Python exits.
18
+
This will run the Spheral python process andimportthe Spheral modules. If successful, you should see a banner printed with information about the version of Spheral, after which Python exits.
19
19
20
20
[smoke_test-end]
21
21
@@ -24,94 +24,20 @@ This will run the Spheral Python process and try importing the Spheral modules.
24
24
..
25
25
RUNNING ATS
26
26
----------------------------------------
27
-
28
-
[ex_ats_test-start]
29
-
ATS Testing Suite
30
-
=================
31
-
32
-
Spheral uses ATS to execute a suite of parallel tests. To run this on an external system we need to use Spheral's virtual-env installation of ATS, asexternal users will not have access to some LC available scripts.
33
-
34
-
From the install directory run:
35
-
::
36
-
37
-
./.venv/bin/ats -e spheral tests/integration.ats
38
-
39
-
[ex_ats_test-end]
40
-
[lc_ats_test-start]
27
+
[ats_test-start]
41
28
ATS Testing Suite
42
29
=================
43
30
44
-
Spheral uses ATS (the Python Automated Testing System) to execute a suite of parallel tests. During install a script is generated ``spheral-atstest`` which handles calling the ats script in ``/usr/gapps/Spheral/bin``andpassing the generated ``spheral`` executor script to it.
31
+
Spheral uses ATS (Automated Testing System) to execute a suite of parallel tests. During install, a script ``spheral-ats`` is created. This script handles launching allocations and setting appropriate ATSandhardware flags for running the testing suite.
45
32
46
33
From the install directory run:
47
34
::
48
35
49
-
./spheral-atstest tests/integration.ats
50
-
51
-
[lc_ats_test-end]
52
-
53
-
54
-
55
-
..
56
-
ATS FILTER OPTIONS
57
-
----------------------------------------
58
-
59
-
[filter_options-start]
60
-
ATS Filters and Options
61
-
-----------------------
62
-
63
-
Appropriate filters are injected into the spheral-atstest script based on build configurations. However if you are using ats directly or wish to override some of these filters you can pass them as defined below.
64
-
65
-
Non MPI Filter
66
-
..............
67
-
68
-
If Spheral was built without ``MPI`` support we will need to pass a filter to our ``ats`` command to prevent parallel tests from being performed:
69
-
::
70
-
71
-
--filter='"np<2"'
72
-
73
-
This stops the ATS suite from attempting to run any tests that rely on more than one process/rank.
74
-
75
-
Debug Build Filter
76
-
..................
77
-
78
-
If Spheral was built in Debug mode it is recommended to pass the below filter if you value your time.
79
-
::
80
-
81
-
--filter='"level<100"'
82
-
83
-
These filters stack when invoked. So if you are running the test suite on a non-mpi debug build the command would be:
When building Spheral with CUDA support and without MPI support on Blue-OS systems we need to pass --smpi_off to ATS. When using spheral-atstest this flag is injected for you. However, for veboseness the flag is:
105
-
::
106
-
107
-
--addOp "--smpi_off"
108
-
109
-
.. note::
110
-
We need to pass ``--addOp`` as a way to forward the ``-smpi_off`` option to ATS. This is because spheral-atstest uses an intermediate layer to control ATS execution.
36
+
./spheral-ats tests/integration.ats
111
37
112
-
If you are using ATS directly you only need to pass:
38
+
For more information about using ``spheral-ats``, run the following from the install directory:
0 commit comments