tquick-tests.rst - pism - [fork] customized build of PISM, the parallel ice sheet model (tillflux branch)
(HTM) git clone git://src.adamsgaard.dk/pism
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) LICENSE
---
tquick-tests.rst (2618B)
---
1 .. include:: ../global.txt
2
3 .. _sec-install-quick-tests:
4
5 Quick tests of the installation
6 ===============================
7
8 Once you’re done with the installation, a few tests can confirm that PISM is functioning
9 correctly.
10
11 #. Try a MPI four process verification run:
12
13 .. code-block:: bash
14
15 mpiexec -n 4 pismv -test G -y 200
16
17 If you see some output and a final ``Writing model state`` ``to file ’unnamed.nc’``
18 then PISM completed successfully. At the end of this run you get measurements of the
19 difference between the numerical result and the exact solution. See :ref:`sec-verif`
20 for more on PISM verification.
21
22 The above "``-n 4``" run should work even if there is only one actual processor (core)
23 on your machine. (In that case MPI will just run multiple processes on the one
24 processor.) This run will also produce a NetCDF output file ``unnamed.nc``, which can
25 be read and viewed by NetCDF tools.
26
27 #. Try an EISMINT II run using the PETSc viewers (under the X window system):
28
29 .. code-block:: none
30
31 pisms -y 5000 -view thk,temppabase,velsurf_mag
32
33 When using such viewers and ``mpiexec`` the additional final option ``-display :0`` is
34 sometimes required to enable MPI to use X, like this:
35
36 .. code-block:: none
37
38 mpiexec -n 2 pisms -y 5000 -view thk,temppabase,velsurf_mag -display :0
39
40 Also ``-drawpause 0.1`` or similar may be needed if the figures are refreshing too fast.
41
42 #. Run a basic suite of software tests. To do this, make sure that NCO_ and Python
43 packages NumPy_ and netcdf4-python_ are installed. Also, the CMake flag
44 ``Pism_BUILD_EXTRA_EXECS`` should be ``ON``. Then run:
45
46 .. code-block:: bash
47
48 make # do this if you changed something with CMake
49 make test
50
51 in the build directory.
52
53 The message at the bottom of the output should say
54
55 ``100% tests passed, 0 tests failed out of XX``
56
57 or similar.
58
59 Feel free to `e-mail us <pism-email_>`_ about any test failures you see. Please run
60
61 .. code-block:: bash
62
63 ctest --output-on-failure > make-test.log
64
65 and send us the ``make-test.log`` that this produces.
66
67 Next steps
68 ==========
69
70 Start with the section :ref:`sec-start`.
71
72 Completely up-to-date documentation can be built from source; see
73 :ref:`sec-install-documentation` for details.
74
75 A final reminder with respect to installation: Let’s assume you have checked out a copy of
76 PISM using Git, :ref:`as described above <git-clone>`. You can then update your copy of PISM
77 to the latest version by running ``git pull`` in the PISM directory and ``make install``
78 in your build directory.