PSC Neocortex CS is an AI-focused computing environment for deep learning and data-driven research using Cerebras wafer-scale systems, PSC workflow tools, and Bridges-2-backed storage. It is intended for workloads that benefit from specialized AI acceleration rather than conventional GPU-only training.
For CS-2 workflows, users connect through SSH or Open OnDemand, prepare code and data on the SDF/Superdome Flex host environment, and run validation, compilation, training, or evaluation through the Cerebras software stack. The CS-2 system includes two Cerebras CS-2 accelerators federated with Bridges-2 for persistent data management and supporting compute workflows.
PSC also documents CS-3 access separately. Users with a CS-3 allocation should follow the current PSC Neocortex CS-3 documentation for the appropriate login, job, and storage workflow.
Jobs
Neocortex CS-2 uses Slurm for interactive and batch workloads. The SDFlex host nodes support data preparation, validation, compilation, training, and evaluation workflows for the Cerebras CS-2 systems.
Before submitting a job, identify the appropriate PSC project and select its Unix group:
projects groups newgrp GRANT_IDCommon 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 informationStart an interactive job on either available SDF node with:
interactTo request a specific SDF node, use:
srun --nodelist=sdf-1 --pty bash -iFor CPU-based validation or compilation, request an SDF host node and start the PSC-provided Cerebras container:
srun --pty \ --cpus-per-task=28 \ --kill-on-bad-exit \ singularity shell \ --cleanenv \ --bind /local1/cerebras/data,/local2/cerebras/data,/local3/cerebras/data,/local4/cerebras/data,$PROJECT \ /ocean/neocortex/cerebras/cbcore_latest.sifA CS-2 training or evaluation job must request a Cerebras accelerator. A minimal batch-script header is:
#!/usr/bin/bash #SBATCH --job-name=cs2-job #SBATCH --account=GRANT_ID #SBATCH --time=04:00:00 #SBATCH --gres=cs:cerebras:1 #SBATCH --ntasks=7 #SBATCH --cpus-per-task=14 #SBATCH --output=%x-%j.out newgrp GRANT_ID # Add the Cerebras container and application commands here.Submit and monitor the script with:
sbatch job.sbatch squeue -u $USERThe documented default wall time for normal interactive and batch jobs is four hours, and the maximum wall time is 48 hours. Reservations may use a different duration when approved by the Neocortex team.
See the instructions for running interactive and batch CS-2 jobs, the complete Neocortex compilation and batch-script examples, and the Neocortex reservation and wall-time instructions.
Queue specifications
| Name | Purpose | Nodes | CPU cores / node | GPUs / node | Node RAM | Jobs
30 days
|
Wait Time
30-day trend
|
Wall Time
30-day trend
|
|---|---|---|---|---|---|---|---|---|
| sdf | SDFlex host nodes for CS-2 validation, compilation, training, and evaluation workflows | 2 | Intel Xeon Platinum 8280L | — | — | — | — |
Storage
Neocortex 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.
The SDFlex host used by Neocortex CS workflows also 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 |
|---|---|---|---|---|---|
| Ocean | /ocean | Shared storage | |||
| Project | /ocean/projects/<allocation>/<user> | Project storage | |||
| Jet | /jet/home/PSC_USERNAME | Home; max quota may block login | |||
| Local | /local{1..4} | Cleared after job | Not backed up | Temporary high-speed job I/O |
File Transfer
Neocortex provides data transfer nodes for moving data into and out of the Neocortex environment. PSC documents rsync as the preferred method, with scp not recommended and sftp also supported.
Use data.neocortex.psc.edu for command-line 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 |
| SCP | 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 |
Login to PSC Neocortex CS
Neocortex CS-2 requires a PSC account associated with an active ACCESS or NAIRR project. PSC account creation is normally automatic after a user is added to an approved project and authorized to use Neocortex. The user should receive an email containing their PSC username.
If an expected PSC account was not created automatically, follow the Neocortex account setup instructions. Existing PSC users may need to provide their PSC username to the Neocortex team. Users without an existing PSC account may need to complete the Request a PSC Account form.
Set the initial PSC password or reset a forgotten 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 connect by SSH:
ssh PSC_USERNAME@neocortex.psc.eduPSC supports authentication using either a PSC password or an optional registered SSH public-private key pair. No separate Neocortex-specific two-factor authentication setup is documented for the CS-2 login workflow.
To create an RSA SSH 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 through the PSC SSH Key Management system. PSC User Services verifies the key before installing it on PSC systems.
After logging in, review the projects and Unix groups associated with your account:
projects groupsIf you have access to multiple PSC projects, select the intended project group before accessing project storage or submitting jobs:
newgrp GRANT_ID