Access: Monitoring Usage

Home > User Info > Access > Monitoring Usage

Usage monitoring allows you to check the status of your allocation by displaying the used and remaining portions of your allocation. The commands listed on this page provide methods for retrieving project information via the command line. The tgusage command retrieves allocation details, while the myprojects and tgprojects commands, used at SDSC and UC/ANL, respectively, display project specific information.

User preferring a web interface can monitor their usage through the User Portal, which displays information on all TeraGrid resources available through your allocation.

tgusage

You can monitor usage of your TeraGrid allocation with the tgusage list command line tool. Currently, tgusage may be used at:

• IU
• NCSA
• PSC
• SDSC
• TACC
• UC/ANL

If the person running the command is the PI, it will show information for all users for the PI's allocation. Otherwise, it will print out the stats for only the user running the command.

Example of command output:

$ tgusage list --account your_account#

Resource: teragrid
Total Allocation: 99999 SU
Remaining Allocation: 99999 SU

Sub-Allocations:

FIRST LAST MIDDLE (NAME) Total Remaining Used Limit
------------------------ ----- --------- ---- -----
Fname Lname             99999 SU 99999 SU 0 SU 100%

To view a list of tgusage options, type tgusage --help.

Specifying multiple projects using tgusage

TeraGrid users may belong to more than one grant or project, and every job needs to be charged to a specific grant or project. Users can view their list of projects using the 'tgusage' command described above. When a user submits a job it gets charged to their default project (except UC/ANL, which does not support default projects).

When a user wants to charge a job to their non-default project, they need to specify a project at submit time. This requirement applies to OpenPBS/Torque interactive and batch jobs, Globus JobManager-PBS jobs, and Condor-G jobs. The commands below provide examples on how to specify projects in each of these cases.

OpenPBS/Torque

For interactive jobs specify the "-A <projectid>" argument.
For batch jobs add the following line to job scripts: #PBS -A <projectid>

Globus

In RSL specify "(project=<projectid>)".
When executing globus-job-run specify the "-p <projectid>" argument.

Condor-G

Add the following line to the submit description file:
globusrsl = (project=<projectid>)

myprojects (SDSC)

To list your TeraGrid account numbers at SDSC, type myprojects from the command line:

tg-login1:/users/your_username % myprojects

tgprojects (UC/ANL)

At UC/ANL, users can list their projects from the command line using the tgprojects command:

<your_username>@tg-login2:~> tgprojects

Running the tgprojects command displays a listing of your current projects. Your default project is not set automatically. Use the command tgprojects -s <project-id> to set your default project. Specifying 'None' as the project-id will unset the default.

If a project is explicitly specified when you submit a job, that project will be charged for the the usage, whether or not you have a default project set. If no project is specified when the job is submitted, and there is only one project associated with your account, that project is charged for the usage. Otherwise the default project is checked. If set, that project is charged for the usage.

WARNING: If you have multiple projects and have not explicitly specified a project or set a default project, the job submission will fail.