Understanding and Managing Your Allocations

Article ID: 265
Last updated: 01 Sep, 2026

As part of applying for a NAS account, you (or your principal investigator) requested an allocation for computing time on HECC systems. Allocations for NAS supercomputing resources are granted per project group ID (GID), and are specified in standard billing units (SBUs).

Usage Charge Methods

System usage is charged as follows:

  • Front-End Systems: Usage is not charged on the front-end systems (such as the PFEs, AFEs, CFEs, CGHFEs, and LFEs). However, remember that these front-end nodes are intended for editing and/or compiling and running short testing jobs—not for running production jobs. If you misuse these systems, your jobs will be terminated.
  • Lou Data Analysis Nodes: Usage is not charged on the Lou data analysis nodes (LDANs), which provide dedicated PBS resources for pre- and post-processing tasks.
  • Compute Nodes: Usage on the Aitken, Cabeus, Electra, and Endeavour compute nodes is charged. The number of SBUs charged to a job is calculated by multiplying the number of total wall-clock hours used by the minimum allocation units (MAUs)—the smallest unit of hardware resource that the Portable Batch System (PBS) will allocate to a job.

SBU rates vary by processor type and system. See Job Accounting for a full list.

To continue running jobs after your SBU allocation has been expended, you will need to request more hours. You can check your remaining SBU balance by running the acct_ytd command. See Job Accounting Utilities for more information.

TIP: You can easily keep track of allocation and usage for all of your GIDs (and monitor all of your PBS jobs) in one central location by logging into the myNAS Portal.

Charging to a Non-Default GID

If you have access to more than one GID, only one of those GIDs is set as your default. The default GID is listed in the /etc/passwd file of each system you have access to. Your jobs will be charged to the default GID unless you specify a different one. If you want to charge your usage to a non-default GID (for example, s0901), add the GID to your PBS script. For example:

#PBS -W group_list=s0901

Understanding Queues

All HECC supercomputers use the Portable Batch System (PBS) to manage both interactive and batch jobs. Aitken and Electra use the same PBS server (pbspl1) and job submission queues. Endeavour and Cabeus' A100 nodes have a separate PBS server (pbspl4) and separate queues. Cabeus' GH200 nodes use a third server (pbs05a) and separate queues.

Although different queues are available on different systems, queues typically have constraints on maximum wall-clock time and/or the number of nodes allowed for a job. Some queues have other constraints or are restricted to serving certain users or GIDs. In addition, mission directorate limits are set on the number of cores available on Aitken and Electra to ensure that each mission directorate can access a fair share of resources.

You can use the qstat command as follows to view various types of information:

qstat -Q
Lists available queues and their constraints on a system.
qstat -Qf
Lists available queues and their constraints on a system.
qstat -W shares=-
Lists mission shares available for each mission.

For more information, see the following articles:

Also read

Contact Us

General User Assistance

Security

  • Report security issues 24x7x365
  • Toll-free: 1-877-NASA-SEC (1-877-627-2732)
  • E-mail: soc@nasa.gov

User Documentation

High-End Computing Capability (HECC) Portfolio Office

NASA High-End Computing Program

Tell Us About It

Our goal is furnish all the information you need to efficiently and effectively use the HECC resources needed for your NASA computational projects.

We welcome your input on features and topics that you would like to see included on this website.

Please send us email with your wish list and other feedback.