| Accessibility Statement

Equipment

Systems

Consulting

RCC staff are available to provide consultation in order to facilitate and optimize the use of RCC's resources.

Equipment

IBM Cluster (pcluster)

Disk Space Usage

Home Directory

The directory that you access when you login to pcluster is your home directory, which is /home/groupname/usernameor /iob_home/groupname/username if you are a member of the Institute of Bioinformatics (IOB).Note that groupname is the name of your group (e.g. abclab) andusernameis your personal username (which is normally your UGA MyID). The default disk space quota on each home directory is 1GB (or 100GB for members of the IOB). The home directory that you access when you login to pcluster is the same that you access when you login to other RCC resources, such as the Linux cluster (rcluster) and the SGI altix.

If you need more disk space for your home directory, please refer to the RCC policy page.

Scratch Space

Users can submit their jobs from the scratch area, located at /scratch/username or at/iob_scratch/username for members of the IOB. There is currently no user quota for the scratch area. Files that are no longer needed for active jobs should be transferred elsewhere (to your home directory or to your local machine). An automatic purging policy for files in /scratch and /iob_scratch may be established in the future if this area fills up with old files.

Local Temporary Space

Each compute node has a 30GB temporary disk space called /lscratch that cannot be directly accessed by the login node pcluster.rcc.uga.edu. Since /lscratch is local to each node, I/O to it from the node is very fast. Temporary files generated by jobs can be written to it (use the subdirectory /lscratch/username ). If your job is I/O intensive, you may consider having your job submission script copy files to /lscratch/username before running the program. However, files in /lscratch are automatically purged. Therefore, it is advisable that your job submission script transfer relevant files out of /lscratch/username before your job ends. The current purging policy implemented is that files that are older than 60 days and not accessed or modified in the past 30 days are deleted. This grace period may be reduced in the future if /lscratch gets too full and thereby not usable by new jobs. Note that because /lscratch is local to each node (and not visible to other nodes), you must use this space with care if running parallel jobs with multiple nodes.

Example

Here is a job submission script that copies the inputfiles (input1.txt and input2.txt) and the serial executable (a.out) to /lscratch/username and then runs the executable from that directory. The output files (output1.txt and output2.txt) are written to the local scratch area as well, and then they are moved back to the user's home directory. At the end of the script, files that are no longer needed (such as the executable a.out and the input files) are deleted:

#!/bin/csh
echo $LOADL_PROCESSOR_LIST
cd /home/groupname/username/subdirectory
cp ./input1.txt ./input2.txt  /lscratch/username
cp ./a.out  /lscratch/username
cd /lscratch/username
time ./a.out
mv ./output1.txt ./output2.txt  /home/groupname/username/subdirectory
rm -f ./a.out ./input1.txt ./input2.txt
exit

Request Consultation

Please initiate requests for help or consultation via our:

request support

Feel free to email or call us (we're in the UGA directory). The quickest way to get support is to use the RCC Support form.

For a complete list of all applications on RCC service, please check the complete list all applications page.