dump tutorial slides, format later

Author: s-sajid-ali

docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md

@@ -7,15 +7,15 @@ If you are new to using HPC resources and would like to learn about the principl
 ## Partitions on Torch
 `SLURM` partitions on Torch control stakeholder resource access. No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition `QoS`. Jobs within the same partition cannot exceed their assigned resources (`QOSGrpGRES`). User GPU Quotas: Each user has a total GPU quota of 24 GPUs for jobs with wall time < 48 hours (`QOSMaxGRESPerUser`).
 
+:::tip Partitions
+Do not specify partitions manually, except for preemption which is described later.
+:::
+
 Non-stakeholders to temporarily use stakeholder resources (a stakeholder group to temporarily use another group’s resources). Stakeholders retain normal access to their own resources. If non-stakeholders (or other stakeholders) are using them, their jobs may be preempted (canceled) once stakeholders submit new jobs. Public users are allowed to use stakeholder resources only with preemption partitions.
 
 ## Job Submission on Torch
 As stated in the tuturial, always only request the compute resources (e.g., GPUs, CPUs, memory). The `SLURM` scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests.
 
-:::tip Partitions
-Do not specify partitions manually, except for preemption which is described later.
-:::
-
 :::warning Low GPU Utilization Policy
 Jobs with low GPU utilization will be automatically canceled. The exact threshold is TBD, but enforcement will be very aggressive.
 :::