initial formatting changes complete

docs/merlin6/99-support/known-problems.md

@@ -1,12 +1,4 @@
----
-title: Known Problems
-#tags:
-keywords: "known problems, troubleshooting, illegal instructions, paraview, ansys, shell, opengl, mesa, vglrun, module: command not found, error"
-last_updated: 07 September 2022
-#summary: ""
-sidebar: merlin6_sidebar
-permalink: /merlin6/known-problems.html
----
+# Known Problems
 
 ## Common errors
 
@@ -17,8 +9,8 @@ This is usually because the software was compiled with a set of instructions new
 and it mostly depends on the processor generation.
 
 In example, `merlin-l-001` and `merlin-l-002` contain a newer generation of processors than the old GPUs nodes, or than the Merlin5 cluster.
-Hence, unless one compiles the software with compatibility with set of instructions from older processors, it will not run on old nodes. 
-Sometimes, this is properly set by default at the compilation time, but sometimes is not. 
+Hence, unless one compiles the software with compatibility with set of instructions from older processors, it will not run on old nodes.
+Sometimes, this is properly set by default at the compilation time, but sometimes is not.
 
 For GCC, please refer to [GCC x86 Options](https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html) for compiling options. In case of doubts, contact us.
 
@@ -49,7 +41,7 @@ srun --cpus-per-task=$SLURM_CPUS_PER_TASK python -c "import os; print(os.sched_g
 (base) ❄ [caubet_m@merlin-l-001:/data/user/caubet_m]# sbatch mysbatch_method1
 Submitted batch job 8000813
 
-(base) ❄ [caubet_m@merlin-l-001:/data/user/caubet_m]# cat slurm-8000813.out 
+(base) ❄ [caubet_m@merlin-l-001:/data/user/caubet_m]# cat slurm-8000813.out
 From Slurm v22.05.8 srun does not inherit $SLURM_CPUS_PER_TASK
 {1, 45}
 One has to implicitly specify $SLURM_CPUS_PER_TASK
@@ -72,11 +64,10 @@ echo 'In this example, by setting an environment variable SRUN_CPUS_PER_TASK'
 export SRUN_CPUS_PER_TASK=$SLURM_CPUS_PER_TASK
 srun python -c "import os; print(os.sched_getaffinity(0))"
 
-
 (base) ❄ [caubet_m@merlin-l-001:/data/user/caubet_m]# sbatch mysbatch_method2
 Submitted batch job 8000815
 
-(base) ❄ [caubet_m@merlin-l-001:/data/user/caubet_m]# cat slurm-8000815.out 
+(base) ❄ [caubet_m@merlin-l-001:/data/user/caubet_m]# cat slurm-8000815.out
 From Slurm v22.05.8 srun does not inherit $SLURM_CPUS_PER_TASK
 {1, 45}
 One has to implicitly specify $SLURM_CPUS_PER_TASK
@@ -84,14 +75,13 @@ In this example, by setting an environment variable SRUN_CPUS_PER_TASK
 {1, 2, 3, 4, 45, 46, 47, 48}
 ```
 
-
 ## General topics
 
 ### Default SHELL
 
 In general, **`/bin/bash` is the recommended default user's SHELL** when working in Merlin.
 
-Some users might notice that BASH is not the default SHELL when logging in to Merlin systems, or they might need to run a different SHELL. 
+Some users might notice that BASH is not the default SHELL when logging in to Merlin systems, or they might need to run a different SHELL.
 This is probably because when the PSI account was requested, no SHELL description was specified or a different one was requested explicitly by the requestor.
 Users can check which is the default SHELL specified in the PSI account with the following command:
 
@@ -99,10 +89,10 @@ Users can check which is the default SHELL specified in the PSI account with the
 getent passwd $USER | awk -F: '{print $NF}'
 ```
 
-If SHELL does not correspond to the one you need to use, you should request a central change for it. 
+If SHELL does not correspond to the one you need to use, you should request a central change for it.
 This is because Merlin accounts are central PSI accounts. Hence, **change must be requested via [PSI Service Now](contact.md#psi-service-now)**.
 
-Alternatively, if you work on other PSI Linux systems but for Merlin you need a different SHELL type, a temporary change can be performed during login startup. 
+Alternatively, if you work on other PSI Linux systems but for Merlin you need a different SHELL type, a temporary change can be performed during login startup.
 You can update one of the following files:
 * `~/.login`
 * `~/.profile`
@@ -116,7 +106,7 @@ MY_SHELL=/bin/bash
 exec $MY_SHELL -l
 ```
 
-Notice that available *shells* can be found in the following file: 
+Notice that available *shells* can be found in the following file:
 
 ```bash
 cat /etc/shells