From 24dfd77a6afaf91d0cb50a459830f4b60ec2879d Mon Sep 17 00:00:00 2001 From: Martin Schroschk <martin.schroschk@tu-dresden.de> Date: Tue, 24 Jan 2023 09:55:31 +0100 Subject: [PATCH] Beautify: Adjust line length and use inline code --- .../docs/software/mpi_usage_error_detection.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc.zih.tu-dresden.de/docs/software/mpi_usage_error_detection.md b/doc.zih.tu-dresden.de/docs/software/mpi_usage_error_detection.md index 02d9d775e..591f2d4a8 100644 --- a/doc.zih.tu-dresden.de/docs/software/mpi_usage_error_detection.md +++ b/doc.zih.tu-dresden.de/docs/software/mpi_usage_error_detection.md @@ -6,14 +6,14 @@ applications with this interface is error prone and often time consuming. Some u may only manifest on some platforms or some application runs, which further complicates the detection of these errors. Thus, special debugging tools for MPI applications exist that automatically check whether an application conforms to the MPI standard and whether its MPI calls -are safe. At ZIH, we maintain and support MUST for this task, though different types of these tools -exist (see last section). +are safe. At ZIH, we maintain and support **MUST** for this task, though different types of these +tools exist (see last section). ## MUST [MUST](https://itc.rwth-aachen.de/must/) checks if your application conforms to the MPI standard and will issue warnings if there are errors or non-portable constructs. You can apply MUST -without modifying your source code, though we suggest to add the debugging flag "-g" during +without modifying your source code, though we suggest to add the debugging flag `-g` during compilation. See also [MUST Introduction Slides](misc/parallel_debugging_must.pdf). @@ -50,8 +50,8 @@ marie@login$ mustrun --must:mpiexec srun --must:np -n -n <number of MPI processe Besides replacing the `srun` command you need to be aware that **MUST always allocates an extra process**, i.e. if you issue a `mustrun --must:mpiexec srun --must:np -n -n 4 ./<your binary>` then -MUST will start **5 processes** instead. This is usually not critical. However, in interactive and batch -jobs **make sure to allocate an extra CPU for this task**. +MUST will start **5 processes** instead. This is usually not critical. However, in interactive and +batch jobs **make sure to allocate an extra CPU for this task**. Suppose your application is called `fancy-program` and is normally run with 4 processes. The MUST workflow should then be -- GitLab