Neocortex SDFlex is the HPE Superdome Flex shared-memory host system associated with PSC Neocortex. It supports memory-heavy CPU work, preprocessing, data staging, validation, compilation, and workflows that benefit from large shared RAM.
SDFlex also serves as the host environment for Neocortex CS workflows, including preparing data, running Cerebras containers, and launching Cerebras training or evaluation jobs.
The system includes 32 Intel Xeon Platinum 8280L processors, 24 TiB RAM, high-bandwidth memory access, and local NVMe storage for high-performance job-local I/O.
Jobs
Neocortex SDFlex uses Slurm for interactive and batch workloads. The sdf partition contains the two SDF execution environments, sdf-1 and sdf-2. Use the login node only for light tasks such as editing files, inspecting allocations, and submitting or monitoring jobs.
Before submitting work, confirm the correct project and Unix group:
projects groups newgrp GROUPIDCommon Slurm commands include:
squeue -u $USER # Show your queued and running jobs squeue -j JOB_ID # Show one job scancel JOB_ID # Cancel a job scontrol show job JOB_ID # Display detailed job informationFor an interactive session on an available SDF node, use:
interactTo request a specific SDF execution environment:
srun --nodelist=sdf-1 --pty bash -iA minimal CPU-only SDFlex batch job can use:
#!/bin/bash #SBATCH --job-name=sdf-example #SBATCH --partition=sdf #SBATCH --account=GROUPID #SBATCH --time=01:00:00 #SBATCH --cpus-per-task=28 #SBATCH --output=%x-%j.out newgrp GROUPID echo "Running on $(hostname)" echo "Local storage: $LOCAL" ./my_programSubmit the script and monitor it with:
sbatch job.sbatch squeue -u $USERCPU-only preprocessing, compilation, data preparation, and memory-intensive SDFlex workloads should not request a Cerebras accelerator. A CS-2 training or evaluation workflow that requires a Cerebras system must additionally request the Cerebras generic resource:
#SBATCH --gres=cs:cerebras:1 #SBATCH --ntasks=7 #SBATCH --cpus-per-task=14The default wall-time value documented for Neocortex reservations is four hours, and the maximum supported wall time is 48 hours. Request only the time needed because shorter jobs are generally easier to schedule.
See the instructions for running interactive, batch, validation, compilation, and Cerebras jobs on Neocortex, the complete Neocortex Slurm and Cerebras job-script examples, and the Neocortex reservation and wall-time instructions.
Queue specifications
Metrics updated 2026-06-16
| Name | Purpose | Nodes | CPU cores / node | GPUs / node | Node RAM | Jobs
30 days
|
Wait Time
30-day trend
|
Wall Time
30-day trend
|
|---|---|---|---|---|---|---|---|---|
| sdf | Large-memory CPU workloads, preprocessing, compilation, data staging, and Cerebras CS-2 host workflows | 2 | Intel Xeon Platinum 8280L | — | 7 | 0 sdf wait time: 0 hours |
|
Storage
Neocortex SDFlex uses PSC's persistent /jet and /ocean filesystems for personal and project data. Use $HOME for small personal files, $PROJECT for project data, and $PROJECT/../shared for files shared with project members.
SDFlex provides node-local storage at /local1 through /local4. These locations are temporary and visible only from the SDFlex compute nodes. Use $LOCAL inside jobs and copy important results back to persistent project storage before the job ends.
If you belong to multiple PSC projects, run newgrp <GROUP_ID> before using $PROJECT for the intended allocation.
File System
| Directory | Path | Quota | Purge | Backup | Notes |
|---|---|---|---|---|---|
| Home | /jet/home/<PSC_USERNAME> | Personal files; max quota may block login | |||
| Project | /ocean/projects/<GRANT_ID>/<PSC_USERNAME> | Project data and shared storage | |||
| Local | /local{1..4} or $LOCAL | Cleared after job | Not backed up | Temporary high-speed SDF job I/O |
File Transfer
Use the Neocortex data transfer node for moving files to and from Neocortex storage. PSC documents rsync as the preferred method; sftp is also supported, and scp is available but not recommended for large transfers.
Use data.neocortex.psc.edu for transfers to project or shared storage, such as locations under /ocean/projects/<GRANT_ID>/. See the Neocortex Data Management and Storage documentation for current examples.
| Supported Methods | Data Transfer Node | URL |
|---|---|---|
| RSYNC | RECOMMENDED | data.neocortex.psc.edu | https://portal.neocortex.psc.edu/docs/CS-2/data-management.html#transferring-data |
| SFTP | data.neocortex.psc.edu | https://portal.neocortex.psc.edu/docs/CS-2/data-management.html#transferring-data |
| SCP | data.neocortex.psc.edu | https://portal.neocortex.psc.edu/docs/CS-2/data-management.html#transferring-data |
Login to Neocortex SDFlex
Neocortex SDFlex requires a PSC account associated with an active ACCESS or NAIRR allocation. PSC account creation is normally automatic after a user is added to an approved project. Look for an account-activation message from PSC containing your PSC username. If an expected account was not created, follow the Neocortex PSC account setup instructions.
Set or reset your PSC password through the PSC Password Change Utility. The PSC username and password are separate from the user’s ACCESS credentials.
Connect through the Neocortex Open OnDemand portal or by SSH:
ssh PSC_USERNAME@neocortex.psc.eduPSC supports password authentication and optional SSH public-key authentication. To create an RSA key pair on a system with OpenSSH, run:
ssh-keygen -t rsa -b 4096 -C "your_email@example.com"Keep the private key secure. Submit only the public key, normally ~/.ssh/id_rsa.pub, through the PSC SSH Key Management system. PSC User Services verifies the key before installing it on PSC systems.
After logging in, list your available PSC projects and Unix groups:
projects groupsIf you belong to more than one project, select the correct project group before using project storage or submitting jobs:
newgrp GROUPID