Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tools:psc [2024/04/24 12:06] – [Submitting jobs on the PSC] willtools:psc [2026/06/01 15:33] (current) – [Checking hour allocations] will
Line 3: Line 3:
 **General information** **General information**
  
-For planned outages see: https://www.psc.edu/calendar/ +  * To log in to the supercomputer ''ssh userid@bridges2.psc.edu''.  
- +    * For graphical apps (eg. AFNI), see [[:tools:ssh display forwarding]] 
-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 +    * This is world accessible and total independent for either the pitt or UPMC network. **no myapps, [[:tools:globalconnect]], or other [[:admin:remoteaccess]] needed!** 
-, [[:tools:gobalconnect]], 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 
- +  * <wrap tip> use ''%%-p RM-shared --ntasks-per-node=1%%'' for lowest hour burn rate</wrap> 
-To test what resources you have access to type ''projects'' +    * ''RM-shared'' memory limited to ''2GB*$ntasks_per_node'' (will see out-of-memory "oom" errors when exceeding). See [[:tools:slurm]]. 
-Quick test for interactive queue: ''salloc''. See [[:tools:slurm]] for more +  * 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 
 +projects                      # see account information  
 +</code>
 ===== Getting an account ===== ===== Getting an account =====
   - https://operations.access-ci.org/identity/new-user   - https://operations.access-ci.org/identity/new-user
   - you [[https://www.psc.edu/resources/bridges-2/user-guide/|may need (20240424)]] to set a bridges/PSC specific password via reset at https://apr.psc.edu/   - you [[https://www.psc.edu/resources/bridges-2/user-guide/|may need (20240424)]] to set a bridges/PSC specific password via reset at https://apr.psc.edu/
-  - ?? 
   - send user account to PI (Finn or Bea) for approval in the project/grant settings   - send user account to PI (Finn or Bea) for approval in the project/grant settings
 +  - request matlab access from https://www.psc.edu/resources/software/matlab/permission-form/
  
 ===== Getting data to and from the PSC ===== ===== Getting data to and from the PSC =====
Line 28: 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: **If you need to run a script that requires command line arguments**, you can export them, for example:
Line 49: 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. 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    * allocation hour calculator: TODO