Differences

This shows you the differences between two versions of the page.

--- tools:psc [2024/11/08 10:51] – [Pittsburgh Super Computer] will
+++ tools:psc [2026/06/01 15:33] (current) – [Checking hour allocations] will
@@ Line 3: / Line 3: @@
 **General information**
- * To log in to the supercomputer ''ssh userid@bridges2.psc.edu''. This is world accessible and total independent for either the pitt or UPMC network. (**no myapps, [[:tools:globalconnect]], or other [[:admin:remoteaccess]] needed!**)
+  * To log in to the supercomputer ''ssh userid@bridges2.psc.edu''.
+    * For graphical apps (eg. AFNI), see [[:tools:ssh display forwarding]]
+    * This is world accessible and total independent for either the pitt or UPMC network. **no myapps, [[:tools:globalconnect]], or other [[:admin:remoteaccess]] needed!**
   * To test what resources you have access to type ''projects''
-Quick test for interactive queue: ''salloc''. See [[:tools:slurm]] for more
+  * Quick test for interactive queue: ''salloc''. See [[:tools:slurm]] for more
+  * <wrap tip> use ''%%-p RM-shared --ntasks-per-node=1%%'' for lowest hour burn rate</wrap>
+    * ''RM-shared'' memory limited to ''2GB*$ntasks_per_node'' (will see out-of-memory "oom" errors when exceeding). See [[:tools:slurm]].
   * User Guide: https://www.psc.edu/resources/bridges-2/user-guide/
   * For planned outages see: https://www.psc.edu/calendar/
+  * see [[:tools:usage_profiling]] for determining runtime and memory usage
+Command line notes:
 <code=base>
 ssh -Y $USER@bridges2.psc.edu # -Y for X11 display forwarding
@@ Line 29: / Line 35: @@
-Jobs are submitted on the PSC via ''sbatch''. sbatch is part of [[:tools:slurm]]. Usage and links are described on the [[:tools:slurm|slurm wiki page]], including links to [[https://www.psc.edu/resources/bridges-2/user-guide/#system-configuration|PSC's user guide]].
+Jobs are submitted on the PSC via ''sbatch''. sbatch is part of [[:tools:slurm]]. Usage and links are described on the [[:tools:slurm|slurm wiki page]], including links to [[https://www.psc.edu/resources/bridges-2/user-guide/#system-configuration|PSC's user guide]], especially the ''[[https://www.psc.edu/resources/bridges-2/user-guide/#:~:text=Bridges-2%20RM-,nodes,-RM|RM]]'' and ''[[https://www.psc.edu/resources/bridges-2/user-guide/#:~:text=of%20the%20EM-,partition,-EM%20partition|EM]]'' nodes RAM and cores summary table
+<WRAP alert>Jobs run on ''RM'' partition [[https://www.psc.edu/resources/bridges-2/user-guide/#:~:text=jobs%20in%20the%20rm%20partition%20are%20charged%20for%20all%20128%20cores%20on%20every%20node%20they%20use.%20|request the whole node (128 cores), and always bill 128 hours for every hour spent in the node]]. Use ''%%-p RM-shared --ntasks-per-node=N%%'' to restrict to N cores.
+If your job uses a lot of memory, you will see OOM (out-of-memory) errors with any ''RM'' partition. Request and use ''-p EM'' for high memory jobs. </WRAP>
 **If you need to run a script that requires command line arguments**, you can export them, for example:
@@ Line 50: / Line 60: @@
 To find the jobid of jobs that you previously ran (that are either running, completed successfully, or exited with an error),  use ''sacct --starttime yyyy-mm-dd''. This will list the JobID, JobName, Partition, Account, AllocCPUs, State, and ExitCode of the job.
+===== Checking hour allocations =====
+To check the hours of specific job (also see [[:tools:usage_profiling]]) <code> sacct -j <job name>.batch --format=JobID,MaxRSS,AveRSS,TotalCPU </code>
+To check the hours in general: <code> projects </code>
+To check the hours per person: <code> projects --usage-by-user soc230004p </code>
   * allocation hour calculator: TODO