You can run jobs at different sizes and durations on ACES. The following lists the different queues that you can submit to, describing how many nodes you get, how long you can run, the type of resources you get, and the average wait time.
Jobs are scheduled by Slurm. Each job picks a partition with --partition, which sets the hardware it runs on, and must request a core count and a walltime. Compute nodes in the main pool provide 96 cores and 512 GB of memory. If you give no walltime, the partition's default applies; run scontrol show partition <partition> on a login node to see the default and the maximum for that partition. For node and architecture details see the [ACES Hardware] page; for job files and submission commands see the [ACES Batch System] guide.
The pvc partition's nodes carry 2 to 8 Intel GPU Max cards, depending on the node.
The Grace-Hopper node (gh01) is not a batch partition. You reach it by connecting directly over SSH from an ACES login node.
The nec partition holds one node with 8 NEC Vector Engine Type 20B-P cards. Request cards with --gres=gpu:ve:N (1 to 8), interactively with srun --partition nec ... or in a batch script with #SBATCH --partition=nec.
ACES uses a composable Liqid PCIe fabric, so accelerators (H100, A30, PVC, FPGA, NextSilicon) are attached on demand to a shared pool of Sapphire Rapids compute nodes rather than being fixed to a partition. A node can belong to several partitions at once, so the per-queue node counts overlap and are not additive; they total more than the 110-node compute pool by design. For a live view, run sinfo -s -p <partition> or gpuavail on a login node.