Simplify getting started instructions

Removed instructions for creating a symlink to scratch space and validation commands for compute-node from the getting started guide.

Author: ofuhrer

setup/01-getting-started.md

@@ -20,12 +20,6 @@ cd "$HOME"
 git clone https://github.com/ofuhrer/HPC4WC.git
 ```
 
-If you want direct access to your scratch space from the file browser, create a symlink:
-
-```bash
-ln -sfn "$SCRATCH" "$HOME/scratch"
-```
-
 ## Install the Course Environment
 
 Run the setup script from the JupyterLab terminal:
@@ -35,15 +29,9 @@ cd "$HOME/HPC4WC"
 ./setup/HPC4WC_setup.sh
 ```
 
-The script creates a Python virtual environment under `$SCRATCH`, symlinks it as `$HOME/HPC4WC_venv`, registers the `HPC4WC_kernel` Jupyter kernel, and validates the CPU-side Python stack. It also installs a small `srun` wrapper inside the virtual environment so nested `srun -n ...` commands and `%ipcluster start -n ...` work from the single-task JupyterHub allocation. It does not modify `.bashrc`.
-
-If you need to recreate the environment, or if an older course setup already exists, run:
-
-```bash
-HPC4WC_FORCE=1 ./setup/HPC4WC_setup.sh
-```
+The script creates a Python virtual environment under `$SCRATCH`, symlinks it as `$HOME/HPC4WC_venv`, registers the `HPC4WC_kernel` Jupyter kernel, and validates the CPU-side Python stack.
 
-For terminals, activate the environment with:
+If you need to acces the environment from a terminal, activate the environment with:
 
 ```bash
 source "$HOME/activate_hpc4wc.sh"
@@ -62,12 +50,3 @@ setup/02-test-setup.ipynb
 ```
 
 It checks NumPy, Matplotlib, MPI through `ipyparallel`, CuPy, GT4Py, and the package versions expected for the course.
-
-For a compute-node validation from a Santis login node, submit:
-
-```bash
-cd "$HOME/HPC4WC"
-sbatch setup/validate_on_compute.sh
-```
-
-Validation logs are written below `$SCRATCH/HPC4WC_validation_logs`.