Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tools:psc [2023/12/18 14:54] – vsydnor | tools:psc [2024/04/26 10:31] (current) – [Getting an account] will | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Pittsburgh Super Computer ====== | ====== Pittsburgh Super Computer ====== | ||
+ | |||
+ | **General information** | ||
For planned outages see: https:// | For planned outages see: https:// | ||
- | To log in to the supercomputer '' | + | To log in to the supercomputer '' |
+ | , [[: | ||
To test what resources you have access to type '' | To test what resources you have access to type '' | ||
Quick test for interactive queue: '' | Quick test for interactive queue: '' | ||
+ | |||
+ | ===== Getting an account ===== | ||
+ | - https:// | ||
+ | - you [[https:// | ||
+ | - send user account to PI (Finn or Bea) for approval in the project/ | ||
+ | - request matlab access from https:// | ||
+ | |||
+ | ===== Getting data to and from the PSC ===== | ||
+ | |||
You can copy files to/from rhea-PSC via rsync, for example '' | You can copy files to/from rhea-PSC via rsync, for example '' | ||
- | Jobs are submitted on the PSC via sbatch. | + | Alternatively, |
+ | |||
+ | ===== Submitting jobs on the PSC ===== | ||
+ | |||
+ | |||
+ | Jobs are submitted on the PSC via '' | ||
+ | |||
+ | **If you need to run a script that requires command line arguments**, | ||
+ | |||
+ | < | ||
+ | # in your script to be run by the job queue | ||
+ | export bids_dir freesurfer_dir freesurfer_sif license acq_label | ||
+ | do_thing $bids_dir | ||
+ | |||
+ | #in your sbatch call | ||
+ | --export=" | ||
+ | </ | ||
+ | |||
+ | Not sure what resources to request? You can run 1 job with more resources than you think you will need. When the job completes successfully, | ||
- | * -p RM-shared : the partition you are requesting resources from. The most common one is RM-shared, but there is also RM, RM-512, | + | ===== Checking |
- | * --time hh:mm:ss : maximum run time for your job. On RM-shared, the max run time appears to be 48:00:00. If the partition you are requesting is full/backed up, jobs with shorter run times are prioritized over those with longer requested times | + | |
- | * --nodes : The number | + | |
- | * --ntasks-per-node : The number of cores to use per node. Importantly, | + | |
- | * -n : number of cores requested in total (useful if you are requesting >1 node and dividing requested cores over nodes) | + | |
- | * -J " | + | |
- | * -o : output log file name | + | |
- | * -e : error log file name | + | |
- | *//Not sure what resources to request? You can run 1 job with more resources than you think you will need. When the job completes successfully, | + | |
When you have launched some jobs, you can check on whether they are running via '' | When you have launched some jobs, you can check on whether they are running via '' | ||
- | To find the jobid of jobs that you previously ran (that are eitherh | + | To find the jobid of jobs that you previously ran (that are either |
- | If you need to run a script that requires command line arguments, you can export them, for example: | ||
- | '' | ||
* allocation hour calculator: TODO | * allocation hour calculator: TODO |