In this document
- Charging for Bridges use
- Managing multiple grants
- Tracking your usage
- Managing your XSEDE allocation
- Changing your default shell
Charging for Bridges use
Charges for using Bridges depend on the type of node you use, which is determined by the type of allocation you have: "Bridges regular", for Bridges' RSM (128GB) nodes); "Bridges GPU", for Bridges' GPU nodes; or "Bridges large", for Bridges LSM and ESM (3TB and 12TB) nodes.
The RSM nodes are allocated as "Bridges regular". This does not include Bridges' GPU nodes. Service Units are defined in terms of compute resources:
1 SU = 1 core-hour
Bridges contains two kinds of GPU nodes: NVIDIA Tesla K80s and NVIDIA Tesla P100s. Because of the difference in the performance of the nodes, the charges are different for the two types of nodes.
The K80 nodes hold 4 GPU units each, each of which can be allocated separately. Service units (SUs) are defined in terms of GPU-hours:
1 GPU-hour = 1 SU
Note that the use of an entire K80 GPU node for one hour would be charged 4 SUs.
The P100 nodes hold 2 GPU units each, which can be allocated separately. Service units (SUs) are defined in terms of GPU-hours:
1 GPU-hour = 2.5 SUs
Note that the use of an entire P100 node for one hour would be charged 5 SUs.
The LSM and ESM nodes are allocated as "Bridges large". Service Units are defined in terms of memory requested:
1 SU = 1 TB-hour
Managing multiple grants
If you have more than one grant, be sure to charge your usage to the correct one. Usage is tracked by group name.
Find your group names
To find your group names, use the
will list all the groups you belong to.
Find your current group
will list the group you associated with your current session.
Charge to a (non-default) group
Batch jobs and interactive sessions are charged to your primary group by default. To charge your usage to a different group, you must specify the appropriate group with the
-A groupname option to the SLURM sbatch command. See the Running Jobs section of this Guide for more information on batch jobs, interactive sessions and SLURM.
Note that any files created during a job are owned by your primary group, no matter which group is charged for the job.
Change your group for a login session
To change the group which will be charged for usage during a login session, use the
Until you logout (or issue another
newgrp command) , groupname is charged for all usage. All files created during this time will belong to groupname, and their storage is charged against the quota for groupname.
On the next login, your default group is back in effect, and will be charged for usage.
Change your default group permanently
Your primary group is charged with all usage by default. To change your primary group, the group to which your SLURM jobs are charged by default, use the
change_primary_group command. Type:
to see all your groups. Then type
to set groupname as your default group.
Tracking your usage
There are several methods you can use to track your Bridges usage. The xdusage command is available on Bridges. There is a man page for xdusage. The
projects command will also help you keep tabs on your usage. It shows grant information, including usage and the pylon directories associated with the grant.
For more detailed accounting data you can use the Grant Management System. You can also track your usage through the XSEDE User Portal. The xdusage and projects command and the XSEDE Portal accurately reflect the impact of a Grant Renewal but the Grant Management System currently does not.
Managing your XSEDE allocation
- How do I add a user to my grant?
- How can I transfer SUs from Bridges Large to Bridges Regular (or vice versa)?
- How can I request more SUs or storage space on Bridges?
Changing your default shell
change_shell command allows you to change your default shell. This command is only available on the login nodes.
To see which shells are available, type
To change your default shell, type
where newshell is one of the choices output by the
change_shell -l command. You must use the entire pathoutput by
change_shell -l, e.g. /usr/psc/shells/bash. You must log out and back in again for the new shell to take effect.