Skip to content

Commit f1677d3

Browse files
authored
Merge pull request #10122 from cniethammer/promote_use_of_mpirun_n_option
Use '-n' instead of '-np' option in documentation, examples, and tests
2 parents 1b5dc73 + b05c564 commit f1677d3

File tree

31 files changed

+121
-117
lines changed

31 files changed

+121
-117
lines changed

.github/issue_template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,6 @@ Please describe, in detail, the problem that you are having, including the behav
2828

2929
**Note**: If you include verbatim output (or a code block), please use a [GitHub Markdown](https://help.github.com/articles/creating-and-highlighting-code-blocks/) code block like below:
3030
```shell
31-
shell$ mpirun -np 2 ./hello_world
31+
shell$ mpirun -n 2 ./hello_world
3232
```
3333

docs/developers/frameworks.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ values of parameters:
166166

167167
.. code-block:: sh
168168
169-
shell$ mpirun --mca btl_tcp_frag_size 65536 -np 2 hello_world_mpi
169+
shell$ mpirun --mca btl_tcp_frag_size 65536 -n 2 hello_world_mpi
170170
171171
.. error:: TODO Do we need content here about PMIx and PRTE MCA vars
172172
and corresponding command line switches?

docs/faq/debugging.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ be to assume that the following would immediately work:
209209

210210
.. code-block:: sh
211211
212-
shell$ mpirun -np 4 xterm -e gdb my_mpi_application
212+
shell$ mpirun -n 4 xterm -e gdb my_mpi_application
213213
214214
If running on a personal computer, this will probably work. You can
215215
also use `tmpi <https://github.com/Azrael3000/tmpi>`_ to launch the
@@ -281,7 +281,7 @@ following:
281281
282282
shell$ hostname
283283
arcade.example.come
284-
shell$ mpirun -np 4 --hostfile my_hostfile \
284+
shell$ mpirun -n 4 --hostfile my_hostfile \
285285
-x DISPLAY=arcade.example.com:0 xterm -e gdb my_mpi_application
286286
287287
.. warning:: X traffic is fairly "heavy" |mdash| if you are
@@ -466,15 +466,15 @@ enabled. Then simply run your application with Valgrind, e.g.:
466466

467467
.. code-block:: sh
468468
469-
shell$ mpirun -np 2 valgrind ./my_app
469+
shell$ mpirun -n 2 valgrind ./my_app
470470
471471
Or if you enabled Memchecker, but you don't want to check the
472472
application at this time, then just run your application as
473473
usual. E.g.:
474474

475475
.. code-block:: sh
476476
477-
shell$ mpirun -np 2 ./my_app
477+
shell$ mpirun -n 2 ./my_app
478478
479479
/////////////////////////////////////////////////////////////////////////
480480

@@ -572,7 +572,7 @@ line:
572572

573573
.. code-block:: sh
574574
575-
shell$ mpirun -np 2 valgrind --suppressions=$PREFIX/share/openmpi/openmpi-valgrind.supp
575+
shell$ mpirun -n 2 valgrind --suppressions=$PREFIX/share/openmpi/openmpi-valgrind.supp
576576
577577
More information on suppression-files and how to generate them can be
578578
found in `Valgrind's documentation

docs/faq/general-tuning.rst

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -222,7 +222,7 @@ listed below, and are resolved in the following priority order:
222222

223223
.. code-block:: sh
224224
225-
shell$ mpirun --mca mpi_show_handle_leaks 1 -np 4 a.out
225+
shell$ mpirun --mca mpi_show_handle_leaks 1 -n 4 a.out
226226
227227
This sets the MCA parameter ``mpi_show_handle_leaks`` to the value
228228
of 1 before running ``a.out`` with four processes. In general, the
@@ -245,7 +245,7 @@ listed below, and are resolved in the following priority order:
245245
246246
shell$ OMPI_MCA_mpi_show_handle_leaks=1
247247
shell$ export OMPI_MCA_mpi_show_handle_leaks
248-
shell$ mpirun -np 4 a.out
248+
shell$ mpirun -n 4 a.out
249249
250250
Note that setting environment variables to values with multiple words
251251
requires quoting, such as:
@@ -347,29 +347,29 @@ will typically run the application as:
347347

348348
.. code-block:: sh
349349
350-
shell$ mpirun -np 2 a.out
350+
shell$ mpirun -n 2 a.out
351351
352352
To use the ``foo.conf`` AMCA parameter file, this command line
353353
changes to:
354354

355355
.. code-block:: sh
356356
357-
shell$ mpirun -np 2 --am foo.conf a.out
357+
shell$ mpirun -n 2 --am foo.conf a.out
358358
359359
If the user wants to override a parameter set in ``foo.conf`` they
360360
can add it to the command line:
361361

362362
.. code-block:: sh
363363
364-
shell$ mpirun -np 2 --am foo.conf --mca btl tcp,self a.out
364+
shell$ mpirun -n 2 --am foo.conf --mca btl tcp,self a.out
365365
366366
AMCA parameter files can be coupled if more than one file is to be
367367
used. If we have another AMCA parameter file called ``bar.conf``
368368
that we want to use, we add it to the command line as follows:
369369

370370
.. code-block:: sh
371371
372-
shell$ mpirun -np 2 --am foo.conf:bar.conf a.out
372+
shell$ mpirun -n 2 --am foo.conf:bar.conf a.out
373373
374374
AMCA parameter files are loaded in priority order. This means that
375375
``foo.conf`` AMCA file has priority over the ``bar.conf`` file. So
@@ -423,22 +423,22 @@ will typically run the application as:
423423

424424
.. code-block:: sh
425425
426-
shell$ mpirun -np 2 a.out
426+
shell$ mpirun -n 2 a.out
427427
428428
To use the ``foo.conf`` tuned parameter file, this command line
429429
changes to:
430430

431431
.. code-block:: sh
432432
433-
shell$ mpirun -np 2 --tune foo.conf a.out
433+
shell$ mpirun -n 2 --tune foo.conf a.out
434434
435435
Tuned parameter files can be coupled if more than one file is to be
436436
used. If we have another tuuned parameter file called ``bar.conf``
437437
that we want to use, we add it to the command line as follows:
438438

439439
.. code-block:: sh
440440
441-
shell$ mpirun -np 2 --tune foo.conf,bar.conf a.out
441+
shell$ mpirun -n 2 --tune foo.conf,bar.conf a.out
442442
443443
444444
The contents of tuned files consist of one or more lines, each of

docs/faq/ompio.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ mechanism available in Open MPI to influence a parameter value, e.g.:
8282

8383
.. code-block:: sh
8484
85-
shell$ mpirun --mca fcoll dynamic -np 64 ./a.out
85+
shell$ mpirun --mca fcoll dynamic -n 64 ./a.out
8686
8787
``fs`` and ``fbtl`` components are typically chosen based on the file
8888
system type utilized (e.g. the ``pvfs2`` component is chosen when the
@@ -222,7 +222,7 @@ IMB:
222222

223223
.. code-block:: sh
224224
225-
shell$ mpirun -np 1 ./IMB-IO S_write_indv
225+
shell$ mpirun -n 1 ./IMB-IO S_write_indv
226226
227227
For IMB, use the values obtained for AGGREGATE test cases. Plot the
228228
bandwidth over the message length. The recommended value for

0 commit comments

Comments
 (0)