= Supporting Rocky =

Rocky grows through your ﬁnancial support (e.g.,
direct costs built into grants or start up funds). By
contributing to building and maintaining Rocky, you
can assure priority access to the resources you
contribute.

= Node Costs =

Below are examples of node costs. While we update the below list routinely, hardware prices change daily. The below table is meant to give a sense of scale and not a guaranteed cost.

==== Storage Node ====

Storage Nodes are added to our Ceph storage subsystem to provide highly redundant and fault tolerant storage accessible to the Rocky Cluster.

{| class='wikitable'
|-
| Quote Date || January 25, 2023
|-
| Quoted Cost || $12,155.32
|-
| Capacity || 40TB
|-
| Configuration || Dell R740xd 16 x 8TB HDD 4 x 1.9TB M.2 SSD Additional drives to extend backup system.
|}

==== Compute Node ====

{| class='wikitable'
|-
| Quote Date || May 1, 2023
|-
| Quoted Cost || $17000
|-
| Compute || 112 vcpu 512MB ram
|-
| Configuration || Dell R750 2 x Xeon Gold 6330 
|}

2023-04-21T05:03:18Z

Jstratt7:

Rocky Python Prime Array

2023-04-21T04:50:00Z

2023-04-10T17:21:09Z

Jstratt7:

= Anatomy of a Rocky Job =

Setting up a job to run on Rocky starts by creating or uploading your project's files to the project directory within your home directory on Rocky. These files will include the code you've written, any data files needed, and a batch file.

==== Your Code ====

Your code is what is submitted and executed on Rocky's compute nodes. 
It can be written in any of the languages supported by Rocky environment modules (Lmod).

==== Your Data ====

If your job will be processing data, you'll need to upload that data to your project's directory.

Your home directory is shared amongst all compute nodes. No matter which node your job is assigned, it will have access to your data.

==== Batch Script ====

The batch script is a shell script that brings everything together by defining job parameters, loading any environment modules needed, and finally executing your code.

Job parameters are defined one per line and start with <code>#SBATCH</code>. 
All parameters have default values are are optional but most batch scripts will use them.

'''my_job.run'''
<pre>
#!/bin/bash
#SBATCH --job-name=MY_JOB ### Job Name
#SBATCH --output=my_job_%j.out ### File in which to store job output
#SBATCH --time=00:10:00 ### Wall clock time limit in Days-HH:MM:SS
#SBATCH --nodes=1 ### Node count required for the job
#SBATCH --ntasks-per-node=1 ### Number of tasks to be launched per Node
#SBATCH --mem-per-cpu=2G
#SBATCH --cpus-per-task=40

module load R/4.2.1-foss-2022a

Rscript my_code.R
</pre>

= Running Job =

==== Submitting Job ====

Jobs are submitted using the <code>sbatch</code> command and passed your batch script as a parameter. This will add your job to the queue.

<pre>
sbatch my_job.run
</pre>

==== Watching Job ====

While your job is in the queue or being executed you may see it's status using the <code>squeue</code> command. If the job is currently running it will show which node(s) it is assigned.

<pre>
[test_user@rocky7 ~]$ squeue
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
2947 compute_all my_job test_use R 0:05 1 moose1
</pre>

==== Cancelling Job ====

To cancel a job, use the <code>scancel</code> command and pass the JOBID (as returned by <code>squeue</code>).

<pre>
scancel 2947
</pre>

Rocky Job Anatomy

2023-04-10T17:17:48Z

Jstratt7: /* Example Jobs */

= Anatomy of a Rocky Job =

Setting up a job to run on Rocky starts by creating or uploading your project's files to the project directory within your home directory on Rocky. These files will include the code you've written, any data files needed, and a batch file.

==== Your Code ====

Your code is what is submitted and executed on Rocky's compute nodes. 
It can be written in any of the languages supported by Rocky environment modules (Lmod).

==== Your Data ====

If your job will be processing data, you'll need to upload that data to your project's directory.

Your home directory is shared amongst all compute nodes. No matter which node your job is assigned, it will have access to your data.

==== Batch Script ====

The batch script is a shell script that brings everything together by defining job parameters, loading any environment modules needed, and finally executing your code.

Job parameters are defined one per line and start with <code>#SBATCH</code>. 
All parameters have default values are are optional but most batch scripts will use them.

'''my_job.run'''
<pre>
#!/bin/bash
#SBATCH --job-name=MY_JOB ### Job Name
#SBATCH --output=my_job_%j.out ### File in which to store job output
#SBATCH --time=00:10:00 ### Wall clock time limit in Days-HH:MM:SS
#SBATCH --nodes=1 ### Node count required for the job
#SBATCH --ntasks-per-node=1 ### Number of tasks to be launched per Node
#SBATCH --mem-per-cpu=2G
#SBATCH --cpus-per-task=40

module load R/4.2.1-foss-2022a

Rscript my_code.R
</pre>

= Running Job =

==== Submitting Job ====

Jobs are submitted using the <code>sbatch</code> command and passed your batch script as a parameter. This will add your job to the queue.

<pre>
sbatch my_job.run
</pre>

==== Watching Job ====

While your job is in the queue or being executed you may see it's status using the <code>squeue</code> command. If the job is currently running it will show which node(s) it is assigned.

<pre>
[test_user@rocky7 ~]$ squeue
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
2947 compute_all my_job test_use R 0:05 1 moose1
</pre>

==== Cancelling Job ====

To cancel a job, use the <code>scancel</code> command and pass the JOBID (as returned by <code>squeue</code>).

<pre>
scancel 2947
</pre>

= Example Jobs =

==== Python ====
* [[ Rocky_Python_HelloWorld | Hello World ]]

==== R ====
* [[ Rocky_R_HelloWorld | Hello World ]]
* [[ Rocky_R_Prime | Calculate Prime Numbers ]]