We recommend contacting Sabalcore Support for building and installing Software. However, you can also build and install software yourself. This section describes various was of installing software. There are four common methods for building/installing software in your Sabalcore account. The most basic method is to manually compile your code using a compiler directly. You can also […]
Category: Section 2) Other Topics
Contains information about additional features of the service including setting up licenses, detailed accounting and reporting and other information.
Memory (RAM) and Swap
Memory (RAM) Access to the memory on each compute node is controlled by how many cores are allocated on each node for a particular job. For example, a job running on 4 cores on a single cobalt node will be able to access 32GB RAM (4 x 8GB). In other words, the RAM on each node is […]
License Server Tunnel
Introduction If you are unfamiliar with the terminology on this page, please contact Sabalcore Support directly for assistance in setting up your license. If you already have a local license server and a valid license file for your software, it is possible to run your application on Sabalcore by connecting to your license server to your […]
Limiting the Wall-time of a Job – qmax
Use the qmax command near the beginning of your PBS script. The qmax command takes a single argument, the maximum walltime a job should run. You can specify the walltime in seconds, minutes, or hours by adding a ‘s’, ‘m’, or ‘h’ suffix to qmax. Seconds are the default. For example, to limit a job to […]
Using Local Scratch Drives on Compute Nodes
A “scratch drive” is a temporary storage area on a compute node which can be accessed by the user. Every node has a local scratch drive. If your application does intensive file I/O, it is recommended that you use the scratch drive or Dynamic Storage Aggregation (DSA) parallel scratch file system. The Scratch Directory The […]
Assigning Job Attributes for Accounting and Tracking
In this article, you will learn how to assign unique attributes to a job that can later be used for accounting purposes. Also see “myusage” and “clui” Certain optional unique Job Attributes can be specified to the job. They are intended to be used for accounting and job tracking by the user. Later, this information […]
Monitor the Progress of a Batch Job
You can monitor the progress of a batch job by viewing it’s standard error and standard output. The output is written to two files which are located in a directory called .pbs_spool. Only running jobs will have files in this directory. The .pbs_spool directory is “hidden” similar to hidden folders in Windows. The “.” must […]
Job Arrays
Job Arrays allows users to submit a series of jobs using a single submission command and a single submission script. A typical use of this is the need to batch process a large number of very similar jobs, which have similar input. A job array is a single job with a list of sub-jobs. Example Job […]