Alpha Institutional Partition Retirement

Created by Cesar Arias, Modified on Fri, 18 Sep at 4:01 PM by Cesar Arias

Alpha Cluster: Account & Partition Requirements

Environment: Alpha (Production)  |  Effective: September 21, 2026


Starting Monday, September 21, Alpha is retiring its institutional partitions in favor of account-based scheduling. Please review the changes below.   Jobs that don't follow the new syntax will be rejected at submission.

What's changing
  • The per-institution partitions (columbia, cornell, cuny, mountsinai, nyu, rit, rochester, rpi, suny) are being retired. alpha is now the default partition.
  • Every job must specify an account with --account. Jobs with no resolvable account will be rejected.
  • Accounts with no active project default to the lowest-priority, preemptible burst QoS. Project accounts default to standard.
  • The interactive QoS is being retired from general use. Use test instead for interactive or short testing work.

1. Job submission syntax

Every sbatch / srun submission must include an account and a partition. Jobs with no resolvable account are rejected at submission.

sbatch --account=<your_account> --partition=alpha --qos=standard my_job.sh

2. Finding your account

Don't use your username as the account. Check the accounts available to you with:

sacctmgr show associations where user=$USER format=Account%30,QOS%50

3. Which partition should I use?

PartitionUseNotes
alphaGeneral GPU workDefault. Used for general GPU work. (H100, H200, RTX PRO 6000)
graceCPU-bound workBilled at a lower rate than GPU partitions.  ARM-64 Grace-Grace CPUs
cpuCPU-only jobsx86_64 CPU-only resource

4. QoS quick reference

If you don't specify a QoS, you'll automatically get the default for your account type. burst for institutional accounts, standard for project accounts.

QoSUse forNotes
priorityTime-sensitive workHighest scheduling priority. 2.0× SU cost, 24-hour wall time, up to 64 GPUs
testInteractive sessions, short test jobsScheduled ahead of standard/long (short, cheap jobs). 0.5× SU cost, 2-hour wall time, up to 8 GPUs (1 node)
standardRegular project workDefault for project accounts. 1.0× SU cost, 48-hour wall time, up to 32 GPUs
longLonger cost-sensitive runsLower priority than standard. 0.5× SU cost, 7-day wall time, up to 32 GPUs
burstNo-project / institutional accessFree, lowest priority, preemptible

5. FAQ

Will my currently running jobs be affected?

No. Jobs already running at cutover are not affected.  Only new submissions after Monday, September 21 are subject to the new rules. If you currently rely on an institutional partition without a project account, switch to specifying your project account before then to avoid defaulting to burst.

What happens if I omit --qos?

Nothing breaks.  You'll automatically get your account type's default (burst for institutional accounts, standard for project accounts). Only omitting --account causes a rejection.




For assistance, contact support@empireai.edu.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article