From 9b2bea9797883098523e35952dc1a30be6acec57 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 01:30:39 -0700
Subject: [PATCH 01/26] adding gpu metrics collection command

---
 docs/compute/monitoring-resources.md    | 153 +++++++++++++++---------
 docs/getting_started/faq.md             |   2 +-
 docs/software/curc_provided_software.md |   2 +-
 3 files changed, 99 insertions(+), 58 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 8f90e5da..0bb9666a 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -1,59 +1,12 @@
 # Monitoring Resources
 
 CU Research Computing has two main tools which can help users monitor their HPC resources:
-* [Slurmtools](#slurmtools): A [module](./modules.md) that loads a collection of functions to assess recent usage statistics
+* [Slurm commands](#monitoring-through-slurm-commands): Slurm provides built-in commands that allow users to retrieve usage summaries, job efficiency data, job history, and priority.
 * [XDMoD](#xdmod): A web portal for viewing metrics at the system, partition, and user-levels.
 
-## Slurmtools
-Slurmtools is a collection of helper scripts for everyday use of the [SLURM](https://slurm.schedmd.com/overview.html) job scheduler. Slurmtools can be loaded in as a module from any node (including login nodes). Slurmtools can help us understand the following questions:
-* How many core hours (SUs) have I used recently?
-* Who is using all of the SUs on my group's account?
-* What jobs have I run over the past few days?
-* What is my priority?
-* How efficient are my jobs?
-
-### __Step 1__: Log in
-If you have a CURC account, login as you [normally would](../getting_started/logging-in.md) using your identikey and Duo from a terminal: 
-
-```bash
-$ ssh ralphie@login.rc.colorado.edu
-```
-
-### __Step 2__: Load the slurm module for the HPC resource you want to query metrics about (Blanca, Alpine):
-```bash
-$ module load slurm/alpine # substitute alpine for blanca
-```
-
-### __Step 3__: Load the `slurmtools` module
-```bash
-$ module load slurmtools
-```
-
-You will see the following informational message:
-
-```
-You have sucessfully loaded slurmtools, a collection of functions
- to assess recent usage statistics. Available commands include:
-
- 'suacct' (SU usage for each user of a specified account over N days)
-
- 'suuser' (SU usage for a specified user over N days)
-
- 'seff' (CPU and RAM efficiency for a specified job)
-
- 'seff-array' (CPU, RAM, and time efficiency for a specified array job)
-
- 'jobstats' (job statistics for all jobs run by a specified user over N days)
-
- 'levelfs' (current fair share priority for a specified user)
-
-
- Type any command without arguments for usage instructions
- ```
-
-### __Step 4__: Get some metrics!
-
-#### How many Service Units (core hours) have I used?
+## Monitoring Through Slurm Commands
+You can obtain important usage and efficiency metrics directly through Slurm’s built-in commands and answer the following questions:
+### How many Service Units (core hours) have I used?
 
 Type the command name for usage hint:
 ```bash
@@ -85,7 +38,7 @@ This output tells us that:
 * Ralphie's usage by account varied from 3,812 SUs to 15,987 SUs
 
 
-#### Who is using all of the SUs on my groups' account?
+### Who is using all of the SUs on my groups' account?
 
 Type the command name for usage hint:
 ```bash
@@ -121,7 +74,7 @@ This output tells us that:
 * Five users used the account in the past 180 days.
 * Their usage ranged from 24 SUs to 84,216 SUs
 
-#### What jobs have I run over the past few days?
+### What jobs have I run over the past few days?
 
 Type the command name for usage hint:
 ```bash
@@ -166,7 +119,7 @@ This output tells me that:
 * The elapsed times ranged from 0 hours to 1 hour and 48 minutes
 
 
-#### What is my priority?
+### What is my priority?
 
 Type the command name for usage hint:
 ```bash
@@ -212,7 +165,7 @@ What is "Priority"?
 * Your "Fair Share" priority has a half life of 14 days (i.e., it recovers fully in ~1 month with zero usage)
 ```
 
-#### How efficient are my jobs?
+### How efficient are my jobs?
 
 Type the command name for usage hint:
 ```bash
@@ -250,7 +203,7 @@ This output tells us that:
 
 This information is also sent to users who include the `--mail` directive in jobs.
 
-#### How can I check the efficiency of array jobs?
+### How can I check the efficiency of array jobs?
 
 Use the `seff-array` command with the help flag for a usage hint: 
 ```
@@ -303,6 +256,94 @@ The above indicates that all of the jobs displayed less than 40% CPU efficiency,
 If you are not familiar with Job Arrays in SLURM, you can learn more on the ["Scaling Up with job Arrays" page](../running-jobs/job-arrays.md).
 ```
 
+### How can I check memory and GPU utilization for my jobs?
+
+Type the command name for usage hint:
+```
+$ sacct
+```
+```
+Purpose: This command reports detailed accounting information for completed jobs, 
+including CPU, memory, and GPU metrics such as `gpumem` and `gpuutil`.
+```
+To view the maximum GPU resource usage for a job, the command is:
+```
+Usage:
+sacct -j <jobid> -Pno TRESUsageInMax -p
+
+positional arguments:
+  jobid                 Job ID to query.
+
+options:
+  -j <jobid>            Specifies the Slurm job ID you want information about.
+  -P                    Output in pipe-delimited format (parseable).
+  -n                    Removes the header row from the output.
+  -o TRESUsageInMax     Chooses the output field(s). Here, you’re requesting to display maximum resource usage.
+  -p                    Print fields with trailing delimiters (helpful for scripts).
+```
+In order to check the metrics for job 18194943, run: 
+```
+$ sacct -j 18194943 -Pno TRESUsageInMax -p
+```
+This will display the output:
+```
+--------------------------------------------------------
+cpu=00:56:24,energy=0,fs/disk=350130624578,gres/gpumem=38888M,gres/gpuutil=100,mem=10372780K,pages=3465,vmem=10194376K|
+cpu=00:00:00,energy=0,fs/disk=5273,gres/gpumem=0,gres/gpuutil=0,mem=256K,pages=0,vmem=0|
+--------------------------------------------------------
+```
+This tells us:
+| Variable | Description |
+| ------------- |------------|
+|`cpu` | Total CPU time consumed (hours:minutes:seconds).|
+|`energy` | Energy consumed by the job in arbitrary units (often 0 for systems without energy accounting).|
+|`fs/disk` | Amount of disk I/O performed by the job (in bytes). |
+|`gres/gpumem` | Peak GPU memory usage. |
+|`gres/gpuutil` | Peak GPU utilization as a percentage. |
+|`mem` | RAM used by the job. |
+|`pages` | Number of memory pages used. Typically for advanced monitoring; can often be ignored. |
+|`vmem` | Virtual memory used by the job. Includes RAM + swap + memory-mapped files. |
+
+```{note} 
+`sacct` reports two entries for each job: the first line reflects the actual workload (the primary job step) and contains the meaningful resource-usage metrics, while the second line corresponds to Slurm’s lightweight `extern` step, which performs the job’s shell setup and shows negligible usage. The first line is the one users should reference.
+```
+
+Similarly, to view the average GPU resource usage for a job
+```
+Usage:
+sacct -j <jobid> -Pno TRESUsageInAve -p --noconvert
+
+positional arguments:
+  jobid                 Job ID to query.
+
+options:
+  -j <jobid>            Filters the report to only show information for the specified job ID.
+  -P                    Output in pipe-delimited format (parseable).
+  -n                    Removes the header row from the output.
+  -o TRESUsageInAve     Chooses the output field(s). Here, you’re requesting to display average resource usage metrics.
+  -p                    Print fields with trailing delimiters (helpful for scripts).
+  --noconvert           Prevents conversion of the units (e.g., MB → GB), ensuring raw data remains unchanged.
+```
+In order to check average GPU metrics for job 18194943, run:
+```
+$ sacct -j 18194943 -Pno TRESUsageInAve -p --noconvert
+```
+This will display the output:
+```
+--------------------------------------------------------
+cpu=00:56:24,energy=0,fs/disk=350130624578,gres/gpumem=40777023488,gres/gpuutil=100,mem=10621726720,pages=3465,vmem=10439041024|
+cpu=00:00:00,energy=0,fs/disk=5273,gres/gpumem=0,gres/gpuutil=0,mem=262144,pages=0,vmem=0|
+--------------------------------------------------------
+```
+This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of peak usage.
+
+```{important}
+- GPU metrics are currently available only on NVIDIA GPUs. Accessing these metrics requires CUDA 12 or newer.
+- For AMD GPUs, memory usage (`gpumem`) is available, but GPU utilization (`gpuutil`) is not supported.
+- Alpine H200s and Blanca H100 GPUs do not currently support GPU metric collection.
+- Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite value for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
+```
+
 ## XDMoD 
  
 XDMoD is a web portal for viewing metrics at the system-, partition- and user-levels.
diff --git a/docs/getting_started/faq.md b/docs/getting_started/faq.md
index 7c7ca684..e6adc17e 100644
--- a/docs/getting_started/faq.md
+++ b/docs/getting_started/faq.md
@@ -197,7 +197,7 @@ sstat --jobs=your_job_id --format=User,JobName,JobId,MaxRSS
 
 For more information on `sstat` or `sacct` commands, [take a look at our Useful Slurm Commands tutorial.](../running-jobs/slurm-commands.md) Or visit the Slurm reference pages on [sstat](https://slurm.schedmd.com/sstat.html) and [sacct](https://slurm.schedmd.com/sacct.html). 
 
-You can also view information related to service unit (SU) usage and CPU & RAM efficiency by using [slurmtools](../compute/monitoring-resources.md#slurmtools). Note that CPU & RAM efficiency statistics will be included in emails sent when a job completes, if requested. 
+You can also view information related to service unit (SU) usage and CPU & RAM efficiency [here](../compute/monitoring-resources.md#monitoring-through-slurm-commands). Note that CPU & RAM efficiency statistics will be included in emails sent when a job completes, if requested. 
 ::::
 
 ### How can I see my current FairShare priority?
diff --git a/docs/software/curc_provided_software.md b/docs/software/curc_provided_software.md
index 5e29d2e8..2235f011 100644
--- a/docs/software/curc_provided_software.md
+++ b/docs/software/curc_provided_software.md
@@ -127,7 +127,7 @@ Before requesting a software installation, please review our [Software installat
 | [SAMtools](http://www.htslib.org/doc/samtools.html) | 1.16.1 | Samtools is a suite of programs for interacting with high-throughput sequencing data.| 
 | [ScaLAPACK](https://netlib.org/scalapack/) | 2.2.0 |ScaLAPACK is a library of high-performance linear algebra routines for parallel distributed memory machines.| 
 | [Singularity/Apptainer](https://apptainer.org/) | 3.6.4 (D), 3.7.4 |Singularity/Apptainer is a computer program that performs operating-system-level virtualization also known as containerization. [CURC Usage Guide](./containerization.md#apptainer)|
-| [Slurmtools](../compute/monitoring-resources.md#slurmtools) | 0.0.0 |A collection of helper scripts for everyday use of the Slurm job scheduler.|
+| Slurmtools | 0.0.0 |A collection of helper scripts for everyday use of the Slurm job scheduler.|
 | [SQLite](https://sqlite.org/index.html) | 3.36.0, 3.38.01, 3.46.1 |SQLite is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.| 
 | [SRA-Toolkit](https://hpc.nih.gov/apps/sratoolkit.html) | 3.0.0 | The SRA Toolkit and SDK from NCBI is a collection of tools and libraries for using data in the INSDC Sequence Read Archives.| 
 | [STAR](https://github.com/alexdobin/STAR/tree/master) | 2.7.10b | A tool to align RNA-seq data. The STAR algorithm uses suffix arrays, seed clustering, and stitching.| 

From b34206ddb7bbcd004f84879fb65b32bf11dd85d0 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 14:21:26 -0700
Subject: [PATCH 02/26] Update docs/compute/monitoring-resources.md

Co-authored-by: Michael Schneider <m.schneider.programmer@gmail.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 0bb9666a..4e127987 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -260,7 +260,7 @@ If you are not familiar with Job Arrays in SLURM, you can learn more on the ["Sc
 
 Type the command name for usage hint:
 ```
-$ sacct
+$ sacct -h
 ```
 ```
 Purpose: This command reports detailed accounting information for completed jobs, 

From fe66f6e505ff6ea475acbf4632c565a3cde61867 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 14:25:16 -0700
Subject: [PATCH 03/26] Update docs/compute/monitoring-resources.md

Co-authored-by: Michael Schneider <m.schneider.programmer@gmail.com>
---
 docs/compute/monitoring-resources.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 4e127987..92fdce9f 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -276,7 +276,6 @@ positional arguments:
 
 options:
   -j <jobid>            Specifies the Slurm job ID you want information about.
-  -P                    Output in pipe-delimited format (parseable).
   -n                    Removes the header row from the output.
   -o TRESUsageInMax     Chooses the output field(s). Here, you’re requesting to display maximum resource usage.
   -p                    Print fields with trailing delimiters (helpful for scripts).

From 85b18bc6c2c1d0509f981a9d2f526a8131cf3b8c Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 14:25:23 -0700
Subject: [PATCH 04/26] Update docs/compute/monitoring-resources.md

Co-authored-by: Michael Schneider <m.schneider.programmer@gmail.com>
---
 docs/compute/monitoring-resources.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 92fdce9f..4e18d29f 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -317,7 +317,6 @@ positional arguments:
 
 options:
   -j <jobid>            Filters the report to only show information for the specified job ID.
-  -P                    Output in pipe-delimited format (parseable).
   -n                    Removes the header row from the output.
   -o TRESUsageInAve     Chooses the output field(s). Here, you’re requesting to display average resource usage metrics.
   -p                    Print fields with trailing delimiters (helpful for scripts).

From bbe65479962b4eb8c5c5d1efc376d74970d66275 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 14:25:42 -0700
Subject: [PATCH 05/26] Update docs/compute/monitoring-resources.md

Co-authored-by: Michael Schneider <m.schneider.programmer@gmail.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 4e18d29f..69cf30f5 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -310,7 +310,7 @@ This tells us:
 Similarly, to view the average GPU resource usage for a job
 ```
 Usage:
-sacct -j <jobid> -Pno TRESUsageInAve -p --noconvert
+sacct -j <jobid> -pno JobID,TRESUsageInAve --noconvert
 
 positional arguments:
   jobid                 Job ID to query.

From 1b478e7cefdd0b5c02ff91e79e3000b279094f75 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 14:25:49 -0700
Subject: [PATCH 06/26] Update docs/compute/monitoring-resources.md

Co-authored-by: Michael Schneider <m.schneider.programmer@gmail.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 69cf30f5..6dac4327 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -269,7 +269,7 @@ including CPU, memory, and GPU metrics such as `gpumem` and `gpuutil`.
 To view the maximum GPU resource usage for a job, the command is:
 ```
 Usage:
-sacct -j <jobid> -Pno TRESUsageInMax -p
+sacct -j <jobid> -pno JobID,TRESUsageInMax 
 
 positional arguments:
   jobid                 Job ID to query.

From c9639819272ba8980a63c7381dabad7b3b2ce339 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 14:26:34 -0700
Subject: [PATCH 07/26] Update docs/compute/monitoring-resources.md

Co-authored-by: Michael Schneider <m.schneider.programmer@gmail.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 6dac4327..1fb33f16 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -282,7 +282,7 @@ options:
 ```
 In order to check the metrics for job 18194943, run: 
 ```
-$ sacct -j 18194943 -Pno TRESUsageInMax -p
+$ sacct -j 18194943 -pno JobID,TRESUsageInMax 
 ```
 This will display the output:
 ```

From 2627c9d88bb4d3fb5e10da59741e208aea3bf928 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Thu, 11 Dec 2025 14:49:59 -0700
Subject: [PATCH 08/26] updating the output displayed and it's explanation

---
 docs/compute/monitoring-resources.md | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 1fb33f16..4a4f7963 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -277,8 +277,7 @@ positional arguments:
 options:
   -j <jobid>            Specifies the Slurm job ID you want information about.
   -n                    Removes the header row from the output.
-  -o TRESUsageInMax     Chooses the output field(s). Here, you’re requesting to display maximum resource usage.
-  -p                    Print fields with trailing delimiters (helpful for scripts).
+  -o TRESUsageInMax     Chooses the output field(s). Here, you’re requesting to display maximum resource usage for a specific jobid.
 ```
 In order to check the metrics for job 18194943, run: 
 ```
@@ -287,8 +286,9 @@ $ sacct -j 18194943 -pno JobID,TRESUsageInMax
 This will display the output:
 ```
 --------------------------------------------------------
-cpu=00:56:24,energy=0,fs/disk=350130624578,gres/gpumem=38888M,gres/gpuutil=100,mem=10372780K,pages=3465,vmem=10194376K|
-cpu=00:00:00,energy=0,fs/disk=5273,gres/gpumem=0,gres/gpuutil=0,mem=256K,pages=0,vmem=0|
+18194943||
+18194943.batch|cpu=00:56:24,energy=0,fs/disk=350130624578,gres/gpumem=38888M,gres/gpuutil=100,mem=10372780K,pages=3465,vmem=10194376K|
+18194943.extern|cpu=00:00:00,energy=0,fs/disk=5273,gres/gpumem=0,gres/gpuutil=0,mem=256K,pages=0,vmem=0|
 --------------------------------------------------------
 ```
 This tells us:
@@ -304,7 +304,7 @@ This tells us:
 |`vmem` | Virtual memory used by the job. Includes RAM + swap + memory-mapped files. |
 
 ```{note} 
-`sacct` reports two entries for each job: the first line reflects the actual workload (the primary job step) and contains the meaningful resource-usage metrics, while the second line corresponds to Slurm’s lightweight `extern` step, which performs the job’s shell setup and shows negligible usage. The first line is the one users should reference.
+`sacct` shows multiple entries for each job. The primary entry is the one with the `.batch` step, which reflects the actual workload and contains the meaningful resource-usage metrics. The `.extern` entry corresponds to Slurm’s lightweight setup step and will show minimal or negligible usage. Users should reference the `.batch` line when reviewing their job’s resource usage.
 ```
 
 Similarly, to view the average GPU resource usage for a job
@@ -319,26 +319,25 @@ options:
   -j <jobid>            Filters the report to only show information for the specified job ID.
   -n                    Removes the header row from the output.
   -o TRESUsageInAve     Chooses the output field(s). Here, you’re requesting to display average resource usage metrics.
-  -p                    Print fields with trailing delimiters (helpful for scripts).
   --noconvert           Prevents conversion of the units (e.g., MB → GB), ensuring raw data remains unchanged.
 ```
 In order to check average GPU metrics for job 18194943, run:
 ```
-$ sacct -j 18194943 -Pno TRESUsageInAve -p --noconvert
+$ sacct -j 18194943 -pno JobID,TRESUsageInAve --noconvert
 ```
 This will display the output:
 ```
 --------------------------------------------------------
-cpu=00:56:24,energy=0,fs/disk=350130624578,gres/gpumem=40777023488,gres/gpuutil=100,mem=10621726720,pages=3465,vmem=10439041024|
-cpu=00:00:00,energy=0,fs/disk=5273,gres/gpumem=0,gres/gpuutil=0,mem=262144,pages=0,vmem=0|
+18194943||
+18194943.batch|cpu=00:56:24,energy=0,fs/disk=350130624578,gres/gpumem=40777023488,gres/gpuutil=100,mem=10621726720,pages=3465,vmem=10439041024|
+18194943.extern|cpu=00:00:00,energy=0,fs/disk=5273,gres/gpumem=0,gres/gpuutil=0,mem=262144,pages=0,vmem=0|
 --------------------------------------------------------
 ```
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of peak usage.
 
 ```{important}
 - GPU metrics are currently available only on NVIDIA GPUs. Accessing these metrics requires CUDA 12 or newer.
-- For AMD GPUs, memory usage (`gpumem`) is available, but GPU utilization (`gpuutil`) is not supported.
-- Alpine H200s and Blanca H100 GPUs do not currently support GPU metric collection.
+- Currently, AMD GPUs, H200s and Blanca H100 GPUs do not support GPU metric collection.
 - Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite value for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
 ```
 

From d239d0d99eff4b338bbd2da7e252d4f9048039fb Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Mon, 5 Jan 2026 17:24:22 -0700
Subject: [PATCH 09/26] update the note about unsupported GPUs

---
 docs/compute/monitoring-resources.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 4a4f7963..87ae2bb2 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -336,8 +336,9 @@ This will display the output:
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of peak usage.
 
 ```{important}
-- GPU metrics are currently available only on NVIDIA GPUs. Accessing these metrics requires CUDA 12 or newer.
-- Currently, AMD GPUs, H200s and Blanca H100 GPUs do not support GPU metric collection.
+- GPU metrics are currently available only on select NVIDIA GPUs and require CUDA 12 or newer.
+- At this time, GPU memory and utilization metrics are not available on the following configurations: AMD GPUs, GH200s and MIG enables GPUs on Alpine, P100s and A40s on Blanca.
+- Core cluster GPUs (e.g., core-gpu[0-4], viz1, viz2), which power Core Desktop and MATLAB GUI, do not currently support GPU memory or utilization metrics.
 - Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite value for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
 ```
 

From 9e2392c78d626aab4472b40cf5039721ed39e407 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Tue, 6 Jan 2026 13:29:35 -0700
Subject: [PATCH 10/26] Update docs/compute/monitoring-resources.md

Co-authored-by: Brandon  <53541061+b-reyes@users.noreply.github.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 87ae2bb2..f5bccb46 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -5,7 +5,7 @@ CU Research Computing has two main tools which can help users monitor their HPC
 * [XDMoD](#xdmod): A web portal for viewing metrics at the system, partition, and user-levels.
 
 ## Monitoring Through Slurm Commands
-You can obtain important usage and efficiency metrics directly through Slurm’s built-in commands and answer the following questions:
+You can obtain important usage and efficiency metrics directly through Slurm’s built-in commands and answer questions posed by the subsections below. 
 ### How many Service Units (core hours) have I used?
 
 Type the command name for usage hint:

From 9f613de306b8c02679819db5e63dae39c063f655 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Tue, 6 Jan 2026 13:30:48 -0700
Subject: [PATCH 11/26] update "peak" to "max"

Co-authored-by: Brandon  <53541061+b-reyes@users.noreply.github.com>
---
 docs/compute/monitoring-resources.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index f5bccb46..1374575f 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -297,8 +297,8 @@ This tells us:
 |`cpu` | Total CPU time consumed (hours:minutes:seconds).|
 |`energy` | Energy consumed by the job in arbitrary units (often 0 for systems without energy accounting).|
 |`fs/disk` | Amount of disk I/O performed by the job (in bytes). |
-|`gres/gpumem` | Peak GPU memory usage. |
-|`gres/gpuutil` | Peak GPU utilization as a percentage. |
+|`gres/gpumem` | Max GPU memory usage. |
+|`gres/gpuutil` | Max GPU utilization as a percentage. |
 |`mem` | RAM used by the job. |
 |`pages` | Number of memory pages used. Typically for advanced monitoring; can often be ignored. |
 |`vmem` | Virtual memory used by the job. Includes RAM + swap + memory-mapped files. |

From 6a3cb0e4f7fda215257af9797aa49cf8cd7feacf Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Tue, 6 Jan 2026 13:31:34 -0700
Subject: [PATCH 12/26] gramm

Co-authored-by: Brandon  <53541061+b-reyes@users.noreply.github.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 1374575f..1d9ca727 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -339,7 +339,7 @@ This output contains the same fields as in the `TRESUsageInMax` example, but her
 - GPU metrics are currently available only on select NVIDIA GPUs and require CUDA 12 or newer.
 - At this time, GPU memory and utilization metrics are not available on the following configurations: AMD GPUs, GH200s and MIG enables GPUs on Alpine, P100s and A40s on Blanca.
 - Core cluster GPUs (e.g., core-gpu[0-4], viz1, viz2), which power Core Desktop and MATLAB GUI, do not currently support GPU memory or utilization metrics.
-- Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite value for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
+- Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite values for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
 ```
 
 ## XDMoD 

From 5dd7eebcabd5e9fc23d085efcfa668838faa0228 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Tue, 6 Jan 2026 13:33:48 -0700
Subject: [PATCH 13/26] update "peak" to "max"

Co-authored-by: Brandon  <53541061+b-reyes@users.noreply.github.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 1d9ca727..ec85a8cd 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -333,7 +333,7 @@ This will display the output:
 18194943.extern|cpu=00:00:00,energy=0,fs/disk=5273,gres/gpumem=0,gres/gpuutil=0,mem=262144,pages=0,vmem=0|
 --------------------------------------------------------
 ```
-This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of peak usage.
+This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
 
 ```{important}
 - GPU metrics are currently available only on select NVIDIA GPUs and require CUDA 12 or newer.

From 99bf9eb44e789a37cbd20ca857c7d5a5853b7c5b Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 08:55:23 -0700
Subject: [PATCH 14/26] adding modifications based on the review

---
 docs/compute/monitoring-resources.md | 301 +++++++++++++++++++--------
 1 file changed, 209 insertions(+), 92 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index ec85a8cd..518332c2 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -12,7 +12,8 @@ Type the command name for usage hint:
 ```bash
 $ suuser
 ```
-```
+This will display the output:
+```text
 Purpose: This function computes the number of Service Units (SUs)
 consumed by a specified user over N days.
 
@@ -24,7 +25,8 @@ Check usage for the last 365 days:
 ```bash
 $ suuser ralphie 365
 ```
-```
+This will display the output:
+```text
 SU used by user ralphie in the last 365 days:
 Cluster|Account|Login|Proper Name|Used|Energy|
 alpine|admin|ralphie|Ralphie|15987|0|
@@ -44,7 +46,8 @@ Type the command name for usage hint:
 ```bash
 $ suacct
 ```
-```
+This will display the output:
+```text
 Purpose: This function computes the number of Service Units (SUs)
 consumed by each user of a specified account over N days.
 
@@ -59,7 +62,8 @@ Most user accounts follow the naming convention `ucbXXX_ascX`, in this example w
 ```bash
 $ suacct admin 180
 ```
-```
+This will display the output:
+```text
 SU used by account (allocation) admin in the last 180 days:
 Cluster|Account|Login|Proper Name|Used|Energy
 alpine|admin|||763240|0
@@ -80,7 +84,8 @@ Type the command name for usage hint:
 ```bash
 $ jobstats
 ```
-```
+This will display the output:
+```text
 Purpose: This function shows statistics for each job
 run by a specified user over N days.
 
@@ -92,7 +97,8 @@ Check ralphie's jobstats for the past 35 days:
 ```bash
 $ jobstats ralphie 35
 ```
-```
+This will display the output:
+```text
 job stats for user ralphie over past 35 days
 jobid        jobname  partition    qos          account      cpus state    start-date-time     elapsed    wait
 -------------------------------------------------------------------------------------------------------------------
@@ -121,11 +127,22 @@ This output tells me that:
 
 ### What is my priority?
 
+```{important}
+What is "Priority"?
+* Your priority is a number between 0.0 --> 1.0 that defines your relative placement in the queue of scheduled jobs
+* Your priority is computed each time a job is scheduled and reflects the following factors:
+  * Your "Fair Share priority" (the ratio of resources you are allocated versus those you have consumed for a given account)
+  * Your job size (slightly larger jobs have higher priority)
+  * Your time spent in the queue (jobs gain priority the longer they wait)
+  * The partition and qos you choose (this is a minor consideration on CURC systems)
+* Your "Fair Share" priority has a half life of 14 days (i.e., it recovers fully in ~1 month with zero usage)
+```
 Type the command name for usage hint:
 ```bash
 $ levelfs
 ```
-```
+This will display the output:
+```text
 Purpose: This function shows the current fair share priority of a specified user.
 A value of 1 indicates average priority compared to other users in an account.
 A value of < 1 indicates lower than average priority
@@ -141,29 +158,18 @@ Check Ralphie's fair share priority:
 ```bash
 $ levelfs ralphie
 ```
-```
-ralphie
-admin LevelFS: inf
-ucb-general LevelFS: 44.796111
-tutorial1 LevelFS: inf
-ucb-testing LevelFS: inf
+```text
+LevelFS for user ralphie and institution ucb:
+
+Account             LevelFS_User        LevelFS_Inst
+-----------------------------------------------------
+admin               1.016845            1.105260
+ucb-general         inf                 1.105260
 ```
 
 This output tells me:
-* Ralphie hasn't used `admin`, `tutorial1`, or `ucb-testing` for more than a month, and therefore Ralphie has very high ("infinite") priority. 
-* Ralphie has used `ucb-general` but not much. Priority is >> 1 , therefore Ralphie can expect lower-than-average queue waits compared to average ucb-general waits.
-
-
-```{important}
-What is "Priority"?
-* Your priority is a number between 0.0 --> 1.0 that defines your relative placement in the queue of scheduled jobs
-* Your priority is computed each time a job is scheduled and reflects the following factors:
-  * Your "Fair Share priority" (the ratio of resources you are allocated versus those you have consumed for a given account)
-  * Your job size (slightly larger jobs have higher priority)
-  * Your time spent in the queue (jobs gain priority the longer they wait)
-  * The partition and qos you choose (this is a minor consideration on CURC systems)
-* Your "Fair Share" priority has a half life of 14 days (i.e., it recovers fully in ~1 month with zero usage)
-```
+* Ralphie hasn't used `ucb-general` and therefore Ralphie has very high ("infinite") priority. 
+* Ralphie has used `admin` but not much. Priority is >> 1 , therefore Ralphie can expect lower-than-average queue waits compared to average ucb-general waits.
 
 ### How efficient are my jobs?
 
@@ -171,7 +177,8 @@ Type the command name for usage hint:
 ```bash
 $ seff
 ```
-```
+This will display the output:
+```text
 Usage: seff [Options] <Jobid>
        Options:
        -h    Help menu
@@ -179,29 +186,50 @@ Usage: seff [Options] <Jobid>
        -d    Debug mode: display raw Slurm data
 ```
 
-Now check the efficiency of job 8636572:
+Now check the efficiency of job 20522520:
 ```bash
-$ seff 8636572
-```
+$ seff 20522520
 ```
-Job ID: 8636572
+This will display the output:
+```text
+Job ID: 20522520
 Cluster: alpine
 User/Group: ralphie/ralphiegrp
 State: COMPLETED (exit code 0)
 Nodes: 1
-Cores per node: 24
-CPU Utilized: 04:04:05
-CPU Efficiency: 92.18% of 04:24:48 core-walltime
-Job Wall-clock time: 00:11:02
-Memory Utilized: 163.49 MB
-Memory Efficiency: 0.14% of 113.62 GB
+Cores per node: 21
+
+──────── CPU Metrics ────────
+CPU Utilized: 7-14:11:13
+CPU Efficiency: 75.77% of 10-00:27:21 core-walltime
+Job Wall-clock time: 11:27:01
+Memory Utilized: 21.25 GiB
+Memory Efficiency: 27.96% of 76.00 GiB (76.00 GiB/node)
+
+──────── GPU Metrics ────────
+Number of GPUs: 1
+GPU Type: l40
+NOTE: GPU metric availability may vary by GPU type.
+      Please refer to our documentation for details: https://curc.readthedocs.io/en/latest/compute/monitoring-resources.html#how-can-i-check-memory-and-gpu-utilization-for-my-jobs
+Max GPU Utilization: 41%
+Max GPU Memory Utilized: 874.00 MiB
+```
+```{note}
+The `seff` output is divided into two sections: CPU Metrics and GPU Metrics.
+- CPU Metrics are always shown, regardless of the type of job, and summarize CPU utilization, memory usage, and efficiency.
+- GPU Metrics are displayed only for jobs that request GPUs. For CPU-only jobs, this section will not appear.
+The example above is for a GPU job, which is why both CPU and GPU metrics are shown.
 ```
-
 This output tells us that:
-* the 24 cores reserved for this job were 92% utilized (anything > 80% is pretty good)
-* 163.49 MB RAM was used of 113.62 GB RAM reserved (0.14%). This job is "cpu bound" so the memory inefficiency is not a major issue.
+* The 21 CPU cores reserved for this job were ~76% utilized, which is reasonable but slightly below the ideal range (>80%).
+* The job ran for ~11.5 hours wall-clock time, accumulating ~7.6 days of total CPU time, indicating a long-running workload with sustained CPU usage.
+* 21.25 GiB of RAM was used out of 76.00 GiB reserved (~28%), suggesting the job was not memory-bound and could likely run with a smaller memory request.
+* One `L40` GPU was allocated, but maximum GPU utilization was 41%, with only ~874 MiB of GPU memory used, indicating the GPU was underutilized for much of the run.
 
 This information is also sent to users who include the `--mail` directive in jobs.
+```{see also}
+Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting-started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for supported configurations and requirements.
+```
 
 ### How can I check the efficiency of array jobs?
 
@@ -209,7 +237,8 @@ Use the `seff-array` command with the help flag for a usage hint:
 ```
 $ seff-array -h
 ```
-```
+This will display the output:
+```text
 usage: seff-array.py [-h] [-c CLUSTER] [--version] jobid
 
 positional arguments:
@@ -220,37 +249,49 @@ options:
   -c CLUSTER, --cluster CLUSTER
   --version             show program's version number and exit
 ```
-In order to check the efficiency of all jobs in job array 8636572, run the command: 
+In order to check the efficiency of all jobs in job array 14083647, run the command: 
 ```
-$ seff-array 8636572
+$ seff-array 14083647
 ```
 This will display the status of all jobs in the array:
-```
+```text
+--------------------------------------------------------
+Job Information
+ID: 14083647
+Name: vecjob_gpu
+Cluster: alpine
+User/Group: ralphie/ralphiegrp
+Requested CPUs: 1 cores on 1 node(s)
+Requested Memory: 3.75G
+Requested Time: 00:10:00
 --------------------------------------------------------
 Job Status
-COMPLETED: 249
-FAILED: 4
-PENDING: 1
-RUNNING: 22
-TIMEOUT: 4
+COMPLETED: 4
 --------------------------------------------------------
+--------------------------------------------------------
+Finished Job Statistics
+(excludes pending, running, and cancelled jobs)
+Average CPU Efficiency 19.21%
+Average Memory Usage 0.00G
+Average Run-time 3.50s
+---------------------
 ```
  Additionally, `seff-array` will display a histogram of the efficiency statistics all of the jobs in the array, separated into 10% increments. For example: 
-```
+```text
 CPU Efficiency (%)
 ---------------------
-+0.00e+00 - +1.00e+01  [  3]  ▌
-+1.00e+01 - +2.00e+01  [244]  ████████████████████████████████████████
-+2.00e+01 - +3.00e+01  [  8]  █▎
-+3.00e+01 - +4.00e+01  [  2]  ▍
-+4.00e+01 - +5.00e+01  [  0]
-+5.00e+01 - +6.00e+01  [  0]
-+6.00e+01 - +7.00e+01  [  0]
-+7.00e+01 - +8.00e+01  [  0]
-+8.00e+01 - +9.00e+01  [  0]
-+9.00e+01 - +1.00e+02  [  0]
-```
-The above indicates that all of the jobs displayed less than 40% CPU efficiency, with the majority (244/256) demonstrating between 10% and 20% efficiency. This information will also be displayed for memory and time efficiency. 
++0.00e+00 - +1.00e+01  [0]
++1.00e+01 - +2.00e+01  [2]  ████████████████████████████████████████
++2.00e+01 - +3.00e+01  [2]  ████████████████████████████████████████
++3.00e+01 - +4.00e+01  [0]
++4.00e+01 - +5.00e+01  [0]
++5.00e+01 - +6.00e+01  [0]
++6.00e+01 - +7.00e+01  [0]
++7.00e+01 - +8.00e+01  [0]
++8.00e+01 - +9.00e+01  [0]
++9.00e+01 - +1.00e+02  [0]
+```
+The above indicates that all of the jobs displayed less than 30% CPU efficiency, with the jobs evenly split (2/4) between 10%–20% and 20%–30% efficiency. This information will also be displayed for memory and time efficiency.
 
 ```{seealso}
 If you are not familiar with Job Arrays in SLURM, you can learn more on the ["Scaling Up with job Arrays" page](../running-jobs/job-arrays.md).
@@ -258,27 +299,101 @@ If you are not familiar with Job Arrays in SLURM, you can learn more on the ["Sc
 
 ### How can I check memory and GPU utilization for my jobs?
 
-Type the command name for usage hint:
+The `sacct` command provides detailed accounting information for completed jobs, including CPU, memory, and GPU metrics (e.g., `gpumem`, `gpuutil`). To see a list of available options and usage examples, run `sacct` with no arguments.
 ```
 $ sacct -h
 ```
-```
-Purpose: This command reports detailed accounting information for completed jobs, 
-including CPU, memory, and GPU metrics such as `gpumem` and `gpuutil`.
+This will display the output:
+```text
+sacct [<OPTION>]
+     Valid <OPTION> values are:
+     -a, --allusers:
+                   Display jobs for all users. By default, only the
+                   current user's jobs are displayed.  If ran by user root
+                   this is the default.
+     -A, --accounts:
+                   Use this comma separated list of accounts to select jobs
+                   to display.  By default, all accounts are selected.
+     --array:
+                   Expand job arrays. Display array tasks on separate lines
+                   instead of consolidating them to a single line.
+     -b, --brief:
+                   Equivalent to '--format=jobstep,state,error'.
+     -B, --batch-script:
+                   Print batch script of job.
+                   NOTE: AccountingStoreFlags=job_script is required for this
+                   NOTE: Requesting specific job(s) with '-j' is required
+                         for this.
+      .
+      .
+      .
+     -l, --long:
+                   Equivalent to specifying
+                   '--format=jobid,jobidraw,jobname,partition,maxvmsize,
+                             maxvmsizenode,maxvmsizetask,avevmsize,maxrss,
+                             maxrssnode,maxrsstask,averss,maxpages,
+                             maxpagesnode,maxpagestask,avepages,mincpu,
+                             mincpunode,mincputask,avecpu,ntasks,alloccpus,
+                             elapsed,state,exitcode,avecpufreq,reqcpufreqmin,
+                             reqcpufreqmax,reqcpufreqgov,reqmem,
+                             consumedenergy,maxdiskread,maxdiskreadnode,
+                             maxdiskreadtask,avediskread,maxdiskwrite,
+                             maxdiskwritenode,maxdiskwritetask,avediskwrite,
+                             reqtres,alloctres,
+                             tresusageinave,tresusageinmax,tresusageinmaxn,
+                             tresusageinmaxt,tresusageinmin,tresusageinminn,
+                             tresusageinmint,tresusageintot,tresusageoutmax,
+                             tresusageoutmaxn,tresusageoutmaxt,
+                             tresusageoutave,tresusageouttot
+     -n, --noheader:
+                   No header will be added to the beginning of output.
+                   The default is to print a header.
+     --noconvert:
+                   Don't convert units from their original type
+                   (e.g. 2048M won't be converted to 2G).
+     -N, --nodelist:
+                   Display jobs that ran on any of these nodes,
+                   can be one or more using a ranged string.
+     --name:
+                   Display jobs that have any of these name(s).
+     -o, --format:
+                   Comma separated list of fields. (use "--helpformat"
+                   for a list of available fields).
+     -p, --parsable: output will be '|' delimited with a '|' at the end
+     -P, --parsable2: output will be '|' delimited without a '|' at the end
+     -q, --qos:
+                   Only send data about jobs using these qos.  Default is all.
+     -r, --partition:
+                   Comma separated list of partitions to select jobs and
+                   job steps from. The default is all partitions.
+     -s, --state:
+                   Select jobs based on their current state or the state
+                   they were in during the time period given: running (r),
+                   completed (cd), failed (f), timeout (to), resizing (rs),
+                   deadline (dl) and node_fail (nf).
+     -S, --starttime:
+                   Select jobs eligible after this time.  Default is
+                   00:00:00 of the current day, unless '-s' is set then
+                   the default is 'now'.
+     Note, valid start/end time formats are...
+                   HH:MM[:SS] [AM|PM]
+                   MMDD[YY] or MM/DD[/YY] or MM.DD[.YY]
+                   MM/DD[/YY]-HH:MM[:SS]
+                   YYYY-MM-DD[THH:MM[:SS]]
+                   now[{+|-}count[seconds(default)|minutes|hours|days|weeks]]
 ```
 To view the maximum GPU resource usage for a job, the command is:
 ```
 Usage:
-sacct -j <jobid> -pno JobID,TRESUsageInMax 
-
-positional arguments:
-  jobid                 Job ID to query.
-
-options:
-  -j <jobid>            Specifies the Slurm job ID you want information about.
-  -n                    Removes the header row from the output.
-  -o TRESUsageInMax     Chooses the output field(s). Here, you’re requesting to display maximum resource usage for a specific jobid.
+sacct -j <jobid> -pno JobID,TRESUsageInMax
 ```
+Arguments and Options:
+| Arguments | Description |
+| ------------- |------------|
+|`-j <jobid>` | Specifies the Slurm job ID you want information about. Here `jobid` is a positional argument. |
+|`-n` | Removes the header row from the output. |
+|`-o TRESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display maximum resource usage for a specific jobid. |
+
 In order to check the metrics for job 18194943, run: 
 ```
 $ sacct -j 18194943 -pno JobID,TRESUsageInMax 
@@ -304,23 +419,27 @@ This tells us:
 |`vmem` | Virtual memory used by the job. Includes RAM + swap + memory-mapped files. |
 
 ```{note} 
-`sacct` shows multiple entries for each job. The primary entry is the one with the `.batch` step, which reflects the actual workload and contains the meaningful resource-usage metrics. The `.extern` entry corresponds to Slurm’s lightweight setup step and will show minimal or negligible usage. Users should reference the `.batch` line when reviewing their job’s resource usage.
+The `sacct` command may display multiple entries for a single job, depending on how it was submitted and its job structure:
+- `.batch` step: Appears for jobs submitted via `sbatch` and reflects the actual workload of the batch script. This is typically the most relevant entry for CPU, memory, and GPU usage.
+- `.extern` step: A lightweight Slurm setup step that usually shows minimal resource usage.
+- Other job steps or tasks: Jobs submitted via `acompile`, `srun`, or as part of job arrays may not have a `.batch` entry, and each step/task may appear separately.
+
+When reviewing resource usage, users should generally focus on the steps that correspond to their actual workload, rather than relying on all entries indiscriminately.
 ```
 
 Similarly, to view the average GPU resource usage for a job
 ```
 Usage:
 sacct -j <jobid> -pno JobID,TRESUsageInAve --noconvert
-
-positional arguments:
-  jobid                 Job ID to query.
-
-options:
-  -j <jobid>            Filters the report to only show information for the specified job ID.
-  -n                    Removes the header row from the output.
-  -o TRESUsageInAve     Chooses the output field(s). Here, you’re requesting to display average resource usage metrics.
-  --noconvert           Prevents conversion of the units (e.g., MB → GB), ensuring raw data remains unchanged.
 ```
+Arguments and Options:
+| Arguments | Description |
+| ------------- |------------|
+|`-j <jobid>` | Filters the report to only show information for the specified job ID. |
+|`-n` | Removes the header row from the output. |
+|`-o TRESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display maximum resource usage for a specific jobid. |
+|`--noconvert` | Prevents conversion of the units (e.g., MB → GB), ensuring raw data remains unchanged. |
+
 In order to check average GPU metrics for job 18194943, run:
 ```
 $ sacct -j 18194943 -pno JobID,TRESUsageInAve --noconvert
@@ -334,14 +453,12 @@ This will display the output:
 --------------------------------------------------------
 ```
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
-
-```{important}
-- GPU metrics are currently available only on select NVIDIA GPUs and require CUDA 12 or newer.
-- At this time, GPU memory and utilization metrics are not available on the following configurations: AMD GPUs, GH200s and MIG enables GPUs on Alpine, P100s and A40s on Blanca.
-- Core cluster GPUs (e.g., core-gpu[0-4], viz1, viz2), which power Core Desktop and MATLAB GUI, do not currently support GPU memory or utilization metrics.
-- Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite values for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
+```{see also}
+If GPU memory or utilization values appear as zero or infinite, your job may be running on unsupported hardware.
+Refer to ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting-started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for details on supported GPUs, CUDA requirements, and known limitations.
 ```
 
+
 ## XDMoD 
  
 XDMoD is a web portal for viewing metrics at the system-, partition- and user-levels.

From 5d46f04a1297b919dfcbd743aafa3a0304c4bda8 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 09:02:13 -0700
Subject: [PATCH 15/26] adding gpu metrics faq and removing slurmtools
 reference

---
 docs/getting_started/faq.md | 24 +++++++++++++-----------
 1 file changed, 13 insertions(+), 11 deletions(-)

diff --git a/docs/getting_started/faq.md b/docs/getting_started/faq.md
index e6adc17e..c7e7beb9 100644
--- a/docs/getting_started/faq.md
+++ b/docs/getting_started/faq.md
@@ -200,24 +200,26 @@ For more information on `sstat` or `sacct` commands, [take a look at our Useful
 You can also view information related to service unit (SU) usage and CPU & RAM efficiency [here](../compute/monitoring-resources.md#monitoring-through-slurm-commands). Note that CPU & RAM efficiency statistics will be included in emails sent when a job completes, if requested. 
 ::::
 
+### Why am I not seeing GPU memory or utilization metrics for my job?
+::::{dropdown} Show 
+:icon: note
+
+- GPU metrics are available for most NVIDIA GPUs across Alpine and Blanca. At this time, GPU memory and utilization metrics are not available on the following configurations: AMD GPUs and GH200s on Alpine, and the P100s and A40s on Blanca.
+- GPU metrics can only be collected if your code utilizes CUDA 12 or newer.
+- GPU metrics are partially available on MIG-enabled NVIDIA GPUs. You can get GPU utilization values, but GPU memory usage metrics are not reported for individual MIG partitions.
+- Core cluster GPUs (e.g., core-gpu[0-4], viz1, viz2), which power Core Desktop and MATLAB GUI, do not currently support GPU memory or utilization metrics.
+- Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite values for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
+::::
+
 ### How can I see my current FairShare priority?
 ::::{dropdown} Show 
 :icon: note
 
 There are a couple ways you can check your FairShare priority:
 
-1. Using the `levelfs` tool in the `slurmtools` module. `levelfs` shows the current fair share priority of a specified user.
-	
-	You can use this tool by first loading in the `slurmtools` module (available from login nodes):
-	```
-	$ module load slurmtools
-	```
-
-	```{tip}
-	slurmtools is packed with lots of great features and tools like suacct, suuser, jobstats, seff, etc._
-	```
+1. Using the `levelfs` command. `levelfs` shows the current fair share priority of a specified user.
 
-	Then using `levelfs` on your username:
+	Using `levelfs` on your username:
 	```
 	$ levelfs $USER
 	```

From 71fc0d1b1f9db5724482230c57f4b95fec8bfca1 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 09:04:38 -0700
Subject: [PATCH 16/26] remove slurmtools from the table

---
 docs/software/curc_provided_software.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/docs/software/curc_provided_software.md b/docs/software/curc_provided_software.md
index 2235f011..c91ffe82 100644
--- a/docs/software/curc_provided_software.md
+++ b/docs/software/curc_provided_software.md
@@ -127,7 +127,6 @@ Before requesting a software installation, please review our [Software installat
 | [SAMtools](http://www.htslib.org/doc/samtools.html) | 1.16.1 | Samtools is a suite of programs for interacting with high-throughput sequencing data.| 
 | [ScaLAPACK](https://netlib.org/scalapack/) | 2.2.0 |ScaLAPACK is a library of high-performance linear algebra routines for parallel distributed memory machines.| 
 | [Singularity/Apptainer](https://apptainer.org/) | 3.6.4 (D), 3.7.4 |Singularity/Apptainer is a computer program that performs operating-system-level virtualization also known as containerization. [CURC Usage Guide](./containerization.md#apptainer)|
-| Slurmtools | 0.0.0 |A collection of helper scripts for everyday use of the Slurm job scheduler.|
 | [SQLite](https://sqlite.org/index.html) | 3.36.0, 3.38.01, 3.46.1 |SQLite is a C-language library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database engine.| 
 | [SRA-Toolkit](https://hpc.nih.gov/apps/sratoolkit.html) | 3.0.0 | The SRA Toolkit and SDK from NCBI is a collection of tools and libraries for using data in the INSDC Sequence Read Archives.| 
 | [STAR](https://github.com/alexdobin/STAR/tree/master) | 2.7.10b | A tool to align RNA-seq data. The STAR algorithm uses suffix arrays, seed clustering, and stitching.| 

From 7e17ce16b33d37d9cfd0e327aa53785323e51164 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 09:08:44 -0700
Subject: [PATCH 17/26] removing extra space

---
 docs/compute/monitoring-resources.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 518332c2..f8ab2201 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -227,7 +227,7 @@ This output tells us that:
 * One `L40` GPU was allocated, but maximum GPU utilization was 41%, with only ~874 MiB of GPU memory used, indicating the GPU was underutilized for much of the run.
 
 This information is also sent to users who include the `--mail` directive in jobs.
-```{see also}
+```{seealso}
 Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting-started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for supported configurations and requirements.
 ```
 
@@ -453,7 +453,7 @@ This will display the output:
 --------------------------------------------------------
 ```
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
-```{see also}
+```{seealso}
 If GPU memory or utilization values appear as zero or infinite, your job may be running on unsupported hardware.
 Refer to ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting-started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for details on supported GPUs, CUDA requirements, and known limitations.
 ```

From 5bb1eb882acbb98cbacf9a9400854af6e6cb0f55 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 09:15:13 -0700
Subject: [PATCH 18/26] grammar fix

---
 docs/compute/monitoring-resources.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index f8ab2201..f687d468 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -228,7 +228,7 @@ This output tells us that:
 
 This information is also sent to users who include the `--mail` directive in jobs.
 ```{seealso}
-Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting-started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for supported configurations and requirements.
+Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for supported configurations and requirements.
 ```
 
 ### How can I check the efficiency of array jobs?
@@ -455,7 +455,7 @@ This will display the output:
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
 ```{seealso}
 If GPU memory or utilization values appear as zero or infinite, your job may be running on unsupported hardware.
-Refer to ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting-started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for details on supported GPUs, CUDA requirements, and known limitations.
+Refer to ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for details on supported GPUs, CUDA requirements, and known limitations.
 ```
 
 

From 99cc61b298abe03c4b5a0740ffdd1ee8affa0f72 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 09:18:57 -0700
Subject: [PATCH 19/26] Update monitoring-resources.md

---
 docs/compute/monitoring-resources.md | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index f687d468..d213837d 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -227,9 +227,6 @@ This output tells us that:
 * One `L40` GPU was allocated, but maximum GPU utilization was 41%, with only ~874 MiB of GPU memory used, indicating the GPU was underutilized for much of the run.
 
 This information is also sent to users who include the `--mail` directive in jobs.
-```{seealso}
-Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for supported configurations and requirements.
-```
 
 ### How can I check the efficiency of array jobs?
 
@@ -453,11 +450,6 @@ This will display the output:
 --------------------------------------------------------
 ```
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
-```{seealso}
-If GPU memory or utilization values appear as zero or infinite, your job may be running on unsupported hardware.
-Refer to ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-I-not-seeing-GPU-memory-or-utilization-metrics-for-my-job) for details on supported GPUs, CUDA requirements, and known limitations.
-```
-
 
 ## XDMoD 
  

From ecc490f9eb26bfcd6b15cb87751915f3bc0f2833 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 09:23:14 -0700
Subject: [PATCH 20/26] adding the faq references back

---
 docs/compute/monitoring-resources.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index d213837d..ce1e8cf4 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -227,6 +227,9 @@ This output tells us that:
 * One `L40` GPU was allocated, but maximum GPU utilization was 41%, with only ~874 MiB of GPU memory used, indicating the GPU was underutilized for much of the run.
 
 This information is also sent to users who include the `--mail` directive in jobs.
+```{seealso}
+Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-i-not-seeing-gpu-memory-or-utilization-metrics-for-my-job) for supported configurations and requirements.
+```
 
 ### How can I check the efficiency of array jobs?
 
@@ -450,6 +453,10 @@ This will display the output:
 --------------------------------------------------------
 ```
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
+```{seealso}
+If GPU memory or utilization values appear as zero or infinite, your job may be running on unsupported hardware.
+Refer to ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-i-not-seeing-gpu-memory-or-utilization-metrics-for-my-job) for details on supported GPUs, CUDA requirements, and known limitations.
+```
 
 ## XDMoD 
  

From a381203d8e9e15ba973658fe5a72f25f58dff0f4 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 09:42:54 -0700
Subject: [PATCH 21/26] replacing "here" with the section title

---
 docs/getting_started/faq.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/getting_started/faq.md b/docs/getting_started/faq.md
index c7e7beb9..070c6601 100644
--- a/docs/getting_started/faq.md
+++ b/docs/getting_started/faq.md
@@ -197,7 +197,7 @@ sstat --jobs=your_job_id --format=User,JobName,JobId,MaxRSS
 
 For more information on `sstat` or `sacct` commands, [take a look at our Useful Slurm Commands tutorial.](../running-jobs/slurm-commands.md) Or visit the Slurm reference pages on [sstat](https://slurm.schedmd.com/sstat.html) and [sacct](https://slurm.schedmd.com/sacct.html). 
 
-You can also view information related to service unit (SU) usage and CPU & RAM efficiency [here](../compute/monitoring-resources.md#monitoring-through-slurm-commands). Note that CPU & RAM efficiency statistics will be included in emails sent when a job completes, if requested. 
+You can also view information related to service unit (SU) usage and CPU & RAM efficiency [using slurm commands](../compute/monitoring-resources.md#monitoring-through-slurm-commands). Note that CPU & RAM efficiency statistics will be included in emails sent when a job completes, if requested. 
 ::::
 
 ### Why am I not seeing GPU memory or utilization metrics for my job?

From 26eb79c57da46e623c3ca76e7155501c1e7b9a81 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 10:38:48 -0700
Subject: [PATCH 22/26] Apply suggestions from Brandon

Co-authored-by: Brandon  <53541061+b-reyes@users.noreply.github.com>
---
 docs/compute/monitoring-resources.md | 18 +++++++++---------
 docs/getting_started/faq.md          |  9 +++++----
 2 files changed, 14 insertions(+), 13 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index ce1e8cf4..2950cb99 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -137,6 +137,8 @@ What is "Priority"?
   * The partition and qos you choose (this is a minor consideration on CURC systems)
 * Your "Fair Share" priority has a half life of 14 days (i.e., it recovers fully in ~1 month with zero usage)
 ```
+The simplest method to determine your priority on the system is to review your fair share priority. This can be done using the `levelfs` command. 
+
 Type the command name for usage hint:
 ```bash
 $ levelfs
@@ -168,8 +170,8 @@ ucb-general         inf                 1.105260
 ```
 
 This output tells me:
-* Ralphie hasn't used `ucb-general` and therefore Ralphie has very high ("infinite") priority. 
-* Ralphie has used `admin` but not much. Priority is >> 1 , therefore Ralphie can expect lower-than-average queue waits compared to average ucb-general waits.
+* Ralphie hasn't used `ucb-general` and therefore Ralphie has very high ("infinite") fair share priority. 
+* Ralphie has used `admin` but not much. Fair share priority is >> 1 , therefore Ralphie can expect lower-than-average queue waits compared to average ucb-general waits.
 
 ### How efficient are my jobs?
 
@@ -299,7 +301,7 @@ If you are not familiar with Job Arrays in SLURM, you can learn more on the ["Sc
 
 ### How can I check memory and GPU utilization for my jobs?
 
-The `sacct` command provides detailed accounting information for completed jobs, including CPU, memory, and GPU metrics (e.g., `gpumem`, `gpuutil`). To see a list of available options and usage examples, run `sacct` with no arguments.
+The `sacct` command provides detailed accounting information for completed jobs, including CPU, memory, and GPU metrics (e.g., `gpumem`, `gpuutil`). To see a list of available options and usage examples, run `sacct` with the help argument.
 ```
 $ sacct -h
 ```
@@ -384,15 +386,14 @@ sacct [<OPTION>]
 ```
 To view the maximum GPU resource usage for a job, the command is:
 ```
-Usage:
-sacct -j <jobid> -pno JobID,TRESUsageInMax
+$ sacct -j <jobid> -pno JobID,TRESUsageInMax
 ```
 Arguments and Options:
 | Arguments | Description |
 | ------------- |------------|
 |`-j <jobid>` | Specifies the Slurm job ID you want information about. Here `jobid` is a positional argument. |
 |`-n` | Removes the header row from the output. |
-|`-o TRESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display maximum resource usage for a specific jobid. |
+|`-o TJobID,RESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display the JobID and maximum resource usage. |
 
 In order to check the metrics for job 18194943, run: 
 ```
@@ -429,15 +430,14 @@ When reviewing resource usage, users should generally focus on the steps that co
 
 Similarly, to view the average GPU resource usage for a job
 ```
-Usage:
-sacct -j <jobid> -pno JobID,TRESUsageInAve --noconvert
+$ sacct -j <jobid> -pno JobID,TRESUsageInAve --noconvert
 ```
 Arguments and Options:
 | Arguments | Description |
 | ------------- |------------|
 |`-j <jobid>` | Filters the report to only show information for the specified job ID. |
 |`-n` | Removes the header row from the output. |
-|`-o TRESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display maximum resource usage for a specific jobid. |
+|`-o JobID,TRESUsageInAve` | Chooses the output field(s). Here, you’re requesting to display the JobID and average resource usage. |
 |`--noconvert` | Prevents conversion of the units (e.g., MB → GB), ensuring raw data remains unchanged. |
 
 In order to check average GPU metrics for job 18194943, run:
diff --git a/docs/getting_started/faq.md b/docs/getting_started/faq.md
index 070c6601..b32592e9 100644
--- a/docs/getting_started/faq.md
+++ b/docs/getting_started/faq.md
@@ -200,15 +200,16 @@ For more information on `sstat` or `sacct` commands, [take a look at our Useful
 You can also view information related to service unit (SU) usage and CPU & RAM efficiency [using slurm commands](../compute/monitoring-resources.md#monitoring-through-slurm-commands). Note that CPU & RAM efficiency statistics will be included in emails sent when a job completes, if requested. 
 ::::
 
-### Why am I not seeing GPU memory or utilization metrics for my job?
+### Why am I getting unexpected results for my GPU memory or utilization metrics?
 ::::{dropdown} Show 
 :icon: note
 
-- GPU metrics are available for most NVIDIA GPUs across Alpine and Blanca. At this time, GPU memory and utilization metrics are not available on the following configurations: AMD GPUs and GH200s on Alpine, and the P100s and A40s on Blanca.
+Currently, GPU metrics are collected by Slurm. Due to system limitations, there are some scenarios where GPU metric collection is not possible. Thus, the output of `sacct` or `seff` may not match your expectation or what is provided by `nvidia-smi` or `amd-smi`. Below we provide important considerations when reviewing GPU metrics collected by Slurm. 
+- GPU metrics are available for most NVIDIA GPUs across Alpine and Blanca. At this time, GPU memory and utilization metrics are not available on the following GPU types: AMD, GH200s, P100s, and A40s.
 - GPU metrics can only be collected if your code utilizes CUDA 12 or newer.
-- GPU metrics are partially available on MIG-enabled NVIDIA GPUs. You can get GPU utilization values, but GPU memory usage metrics are not reported for individual MIG partitions.
+- GPU metrics are partially available on MIG-enabled NVIDIA GPUs. You can get GPU memory usage values, but GPU utilization metrics are not reported for individual MIG partitions.
 - Core cluster GPUs (e.g., core-gpu[0-4], viz1, viz2), which power Core Desktop and MATLAB GUI, do not currently support GPU memory or utilization metrics.
-- Users running jobs on unsupported GPUs or older CUDA versions will see zeros or infinite values for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
+- Users running jobs on unsupported GPUs or older CUDA versions will see zeros or N/A or infinite values for GPU memory and utilization fields. Make sure your jobs are running on compatible hardware to obtain meaningful GPU metrics.
 ::::
 
 ### How can I see my current FairShare priority?

From 1c0548da9efc37700eaee49f0c2dbb8e3ac83a15 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 10:53:55 -0700
Subject: [PATCH 23/26] updating the faq reference, levelfs output, sacct table

---
 docs/compute/monitoring-resources.md | 30 ++++++++++++++++------------
 1 file changed, 17 insertions(+), 13 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 2950cb99..09af8fa1 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -145,12 +145,15 @@ $ levelfs
 ```
 This will display the output:
 ```text
-Purpose: This function shows the current fair share priority of a specified user.
-A value of 1 indicates average priority compared to other users in an account.
-A value of < 1 indicates lower than average priority
-	(longer than average queue waits)
-A value of > 1 indicates higher than average priority
-	(shorter than average queue waits)
+Purpose: This function shows the current fair share priority of a specified user and their institution.
+A value of 1 indicates actual usage matches expected usage.
+A value of < 1 indicates actual usage is more than expected usage.
+        (longer than average queue waits)
+A value of > 1 indicates actual usage is less than expected usage
+        (shorter than average queue waits)
+Note: It is possible to have high priority in a given account
+      and low priority for your institution as a whole, and vise-versa.
+      Both numbers affect your queue wait times.
 
 Usage: levelfs [userid]
 Hint: levelfs ralphie
@@ -228,9 +231,8 @@ This output tells us that:
 * 21.25 GiB of RAM was used out of 76.00 GiB reserved (~28%), suggesting the job was not memory-bound and could likely run with a smaller memory request.
 * One `L40` GPU was allocated, but maximum GPU utilization was 41%, with only ~874 MiB of GPU memory used, indicating the GPU was underutilized for much of the run.
 
-This information is also sent to users who include the `--mail` directive in jobs.
 ```{seealso}
-Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-i-not-seeing-gpu-memory-or-utilization-metrics-for-my-job) for supported configurations and requirements.
+Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I getting unexpected results for my GPU memory or utilization metrics?"](../getting_started/faq.md#why-am-i-getting-unexpected-gpu-results-for-my-gpu-memory-or-utilization-metrics) for supported configurations and requirements.
 ```
 
 ### How can I check the efficiency of array jobs?
@@ -392,8 +394,9 @@ Arguments and Options:
 | Arguments | Description |
 | ------------- |------------|
 |`-j <jobid>` | Specifies the Slurm job ID you want information about. Here `jobid` is a positional argument. |
-|`-n` | Removes the header row from the output. |
-|`-o TJobID,RESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display the JobID and maximum resource usage. |
+|`p` | Parsable; output will be delimited with a `|` at the end |
+|`n` | Removes the header row from the output. |
+|`o JobID,TRESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display the JobID and maximum resource usage. |
 
 In order to check the metrics for job 18194943, run: 
 ```
@@ -436,8 +439,9 @@ Arguments and Options:
 | Arguments | Description |
 | ------------- |------------|
 |`-j <jobid>` | Filters the report to only show information for the specified job ID. |
-|`-n` | Removes the header row from the output. |
-|`-o JobID,TRESUsageInAve` | Chooses the output field(s). Here, you’re requesting to display the JobID and average resource usage. |
+|`p` | Parsable; output will be delimited with a `|` at the end |
+|`n` | Removes the header row from the output. |
+|`o JobID,TRESUsageInAve` | Chooses the output field(s). Here, you’re requesting to display the JobID and average resource usage. |
 |`--noconvert` | Prevents conversion of the units (e.g., MB → GB), ensuring raw data remains unchanged. |
 
 In order to check average GPU metrics for job 18194943, run:
@@ -455,7 +459,7 @@ This will display the output:
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
 ```{seealso}
 If GPU memory or utilization values appear as zero or infinite, your job may be running on unsupported hardware.
-Refer to ["Why am I not seeing GPU memory or utilization metrics for my job?"](../getting_started/faq.md#why-am-i-not-seeing-gpu-memory-or-utilization-metrics-for-my-job) for details on supported GPUs, CUDA requirements, and known limitations.
+Refer to ["Why am I getting unexpected results for my GPU memory or utilization metrics?"](../getting_started/faq.md#why-am-i-getting-unexpected-gpu-results-for-my-gpu-memory-or-utilization-metrics) for details on supported GPUs, CUDA requirements, and known limitations.
 ```
 
 ## XDMoD 

From e1dcafb521a56dd53a879e1cfe45cae6452ec33a Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 11:03:16 -0700
Subject: [PATCH 24/26] updating the faq link reference

---
 docs/compute/monitoring-resources.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 09af8fa1..384c7883 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -232,7 +232,7 @@ This output tells us that:
 * One `L40` GPU was allocated, but maximum GPU utilization was 41%, with only ~874 MiB of GPU memory used, indicating the GPU was underutilized for much of the run.
 
 ```{seealso}
-Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I getting unexpected results for my GPU memory or utilization metrics?"](../getting_started/faq.md#why-am-i-getting-unexpected-gpu-results-for-my-gpu-memory-or-utilization-metrics) for supported configurations and requirements.
+Not all GPUs support report memory and utilization metrics in `seff` output. See ["Why am I getting unexpected results for my GPU memory or utilization metrics?"](../getting_started/faq.md#why-am-i-getting-unexpected-results-for-my-gpu-memory-or-utilization-metrics) for supported configurations and requirements.
 ```
 
 ### How can I check the efficiency of array jobs?
@@ -459,7 +459,7 @@ This will display the output:
 This output contains the same fields as in the `TRESUsageInMax` example, but here they represent average usage instead of max usage.
 ```{seealso}
 If GPU memory or utilization values appear as zero or infinite, your job may be running on unsupported hardware.
-Refer to ["Why am I getting unexpected results for my GPU memory or utilization metrics?"](../getting_started/faq.md#why-am-i-getting-unexpected-gpu-results-for-my-gpu-memory-or-utilization-metrics) for details on supported GPUs, CUDA requirements, and known limitations.
+Refer to ["Why am I getting unexpected results for my GPU memory or utilization metrics?"](../getting_started/faq.md#why-am-i-getting-unexpected-results-for-my-gpu-memory-or-utilization-metrics) for details on supported GPUs, CUDA requirements, and known limitations.
 ```
 
 ## XDMoD 

From 0aecf2bd00e1cc1a732968e0474efe74122c3bd3 Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 11:06:03 -0700
Subject: [PATCH 25/26] Brandon's suggestion

Co-authored-by: Brandon  <53541061+b-reyes@users.noreply.github.com>
---
 docs/compute/monitoring-resources.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 384c7883..52eb704c 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -118,7 +118,7 @@ jobid        jobname  partition    qos          account      cpus state    start
 8800741      interact ahub         interacti+   ucb-gener+   1    CANCELLE 2021-10-19T08:11:44 01:48:38   0 hrs
 ```
 
-This output tells me that:
+This output tells us that:
 * Ralphie has run 14 jobs in the past 35 days
 * Most jobs had queue waits of < 1 hour
 * The number of cores requested ranged from 1-->8192

From 3f6784642db8e6814bcaa8090d090d136601394c Mon Sep 17 00:00:00 2001
From: mohalkh5 <mokh8410@colorado.edu>
Date: Wed, 7 Jan 2026 11:18:51 -0700
Subject: [PATCH 26/26] updating '\|'

---
 docs/compute/monitoring-resources.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/compute/monitoring-resources.md b/docs/compute/monitoring-resources.md
index 52eb704c..ca3fbb9d 100644
--- a/docs/compute/monitoring-resources.md
+++ b/docs/compute/monitoring-resources.md
@@ -394,7 +394,7 @@ Arguments and Options:
 | Arguments | Description |
 | ------------- |------------|
 |`-j <jobid>` | Specifies the Slurm job ID you want information about. Here `jobid` is a positional argument. |
-|`p` | Parsable; output will be delimited with a `|` at the end |
+|`p` | Parsable; output will be delimited with a '\|' at the end |
 |`n` | Removes the header row from the output. |
 |`o JobID,TRESUsageInMax` | Chooses the output field(s). Here, you’re requesting to display the JobID and maximum resource usage. |
 
@@ -439,7 +439,7 @@ Arguments and Options:
 | Arguments | Description |
 | ------------- |------------|
 |`-j <jobid>` | Filters the report to only show information for the specified job ID. |
-|`p` | Parsable; output will be delimited with a `|` at the end |
+|`p` | Parsable; output will be delimited with a '\|' at the end |
 |`n` | Removes the header row from the output. |
 |`o JobID,TRESUsageInAve` | Chooses the output field(s). Here, you’re requesting to display the JobID and average resource usage. |
 |`--noconvert` | Prevents conversion of the units (e.g., MB → GB), ensuring raw data remains unchanged. |