changed to show_slurm_qos

Author: RobJY

docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md

@@ -34,22 +34,6 @@ As stated in the tutorial, be sure to only request the compute resources (e.g.,
 Jobs with low GPU utilization will be automatically canceled. The exact threshold is TBD, but enforcement will be very aggressive.
 :::
 
-:::info Maximum number of jobs a user can submit
-This depends on the requested wall time.<br />
-You can check it with the following command:
-```bash
-[NetID@torch-login-b-1 ~]$ sacctmgr show qos cpu48,cpu168,gpu48,gpu168,interactive format=name%16,maxTresPU%32,MaxWall,MaxSubmitJobsPerUser
-            Name                        MaxTRESPU     MaxWall MaxSubmitPU 
----------------- -------------------------------- ----------- ----------- 
-          cpu168               cpu=1000,mem=2000G  7-00:00:00         500 
-           cpu48               cpu=3000,mem=6000G  2-00:00:00        5000 
-          gpu168                       gres/gpu=4  7-00:00:00          50 
-           gpu48                      gres/gpu=16  2-00:00:00        2000 
-     interactive                   cpu=16,mem=60G    06:00:00          20 
-```
-The values above are just an example and they may change without notice, so please check within your account for the most up to date results.
-:::
-
 ## Preemptible jobs on Torch
 On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs.
 

docs/hpc/06_tools_and_software/08_utils.mdx

@@ -104,6 +104,22 @@ As you can see above, `seff` gives information about CPU and memory efficiency t
 Requesting the minimum resources needed for your job can help it spend less time in the queue.
 :::
 
+## `show_slurm_qos`
+This shows the maximum number of cpus/gpus and memory allowed for different wall times.
+```bash
+[NetID@torch-login-b-0 ~]$ show_slurm_qos
+                    Name     MaxWall                MaxTRESPU    Preempt   PreemptExemptTime PreemptMode 
+------------------------ ----------- ------------------------ ---------- ------------------- ----------- 
+               cpu_short    06:00:00          cpu=32,mem=120G                                    cluster 
+                  cpu168  7-00:00:00       cpu=1000,mem=2000G                                    cluster 
+                   cpu48  2-00:00:00       cpu=3000,mem=6000G                                    cluster 
+                 cpuprem  2-00:00:00    cpu=30000,mem=120000G                                    cluster 
+                  gpu168  7-00:00:00               gres/gpu=4                                    cluster 
+                   gpu48  2-00:00:00              gres/gpu=16                                    cluster 
+             interactive    06:00:00           cpu=16,mem=60G                                    cluster
+```
+You can see that, in general, the partitions with shorter wall times will allow the use of greater resources.
+
 {/* coming soon
 ## `rpsquota`