Update docs from JEDI to JUWELS and JUPITER

Author: lmorgenstern-nv

10-H_CUDA_Graphs_and_Device-initiated_Communication_with_NVSHMEM/tasks/Device-initiated_Communication_with_NVSHMEM/Instructions.ipynb

@@ -49,11 +49,10 @@
         "\n",
         "#### Note\n",
         "\n",
-        "The Slurm installation on JEDI sets `CUDA_VISIBLE_DEVICES` automatically\n",
+        "The Slurm installation on JSC systems sets `CUDA_VISIBLE_DEVICES` automatically\n",
         "so that each spawned process only sees the GPU it should use (see\n",
-        "[Hardware\n",
-        "Configuration](https://apps.fz-juelich.de/jsc/hps/jedi/configuration.html#hardware-configuration)\n",
-        "in the JEDI user documentation). This is not supported for NVSHMEM. The\n",
+        "[Hardware Configuration JUWELS](https://apps.fz-juelich.de/jsc/hps/juwels/configuration.html) or [Hardware Configuration JUPITER](https://apps.fz-juelich.de/jsc/hps/jupiter/configuration.html)\n",
+        "in the user documentation). This is not supported for NVSHMEM. The\n",
         "automatic setting of `CUDA_VISIBLE_DEVICES` can be disabled by setting\n",
         "`CUDA_VISIBLE_DEVICES=0,1,2,3` in the shell that executes srun. With\n",
         "`CUDA_VISIBLE_DEVICES` set all spawned processes can see all GPUs\n",

10-H_CUDA_Graphs_and_Device-initiated_Communication_with_NVSHMEM/tasks/Device-initiated_Communication_with_NVSHMEM/Instructions.md

@@ -36,7 +36,7 @@ Study the performance by glimpsing at the profile generated with
 
 #### Note
 
-The Slurm installation on JEDI sets `CUDA_VISIBLE_DEVICES` automatically so that each spawned process only sees the GPU it should use (see [Hardware Configuration](https://apps.fz-juelich.de/jsc/hps/jedi/configuration.html#hardware-configuration) in the JEDI user documentation). This is not supported for NVSHMEM. The automatic setting of `CUDA_VISIBLE_DEVICES` can be disabled by setting `CUDA_VISIBLE_DEVICES=0,1,2,3` in the shell that executes srun. With `CUDA_VISIBLE_DEVICES` set all spawned processes can see all GPUs listed. This is automatically done for the `sanitize`, `run` and `profile` make targets.
+The Slurm installation on JEDI sets `CUDA_VISIBLE_DEVICES` automatically so that each spawned process only sees the GPU it should use (see [Hardware Configuration JUWELS](https://apps.fz-juelich.de/jsc/hps/juwels/configuration.html) or [Hardware Configuration JUPITER](https://apps.fz-juelich.de/jsc/hps/jupiter/configuration.html) in the user documentation). This is not supported for NVSHMEM. The automatic setting of `CUDA_VISIBLE_DEVICES` can be disabled by setting `CUDA_VISIBLE_DEVICES=0,1,2,3` in the shell that executes srun. With `CUDA_VISIBLE_DEVICES` set all spawned processes can see all GPUs listed. This is automatically done for the `sanitize`, `run` and `profile` make targets.
 
 ### Advanced Task: Use `nvshmemx_float_put_nbi_block`