Debug and Development Partitions
The debug and development partitions are strictly reserved for the following activities:
- Code porting
- Code debugging
- Code development
- Job script/workflow management script porting, debugging and/or development
- Production runs (i.e., jobs that are intended to generate final results or data for publication, reporting, or use in further analysis)
- Preparatory or test runs, including but not limited to:
- Warm-up/generation of initial conditions for simulations
- Testing configurations, searching for optimal/stabilitiy parameters, or setting up simulations, even if the results will not be used directly.
- Running simulations or experiments to determine production parameters for AI/ML model training (e.g., hyperparameter tuning, configuration testing, validation of stability under different settings).
- Testing code or scripts in ways that mimic production workloads, such as large-scale simulations or model training, that are not explicitly part of the development or debugging process.
Current available debug and development partitions at Pawsey are:
| Cluster | Name | N. Nodes | Cores per node | Available node-RAM for jobs | GPU chiplets per node | Types of jobs supported | Max Number of Nodes per Job | Max Wall time | Max Number of Concurrent Jobs per User | Max Number of Jobs Submitted per User |
|---|---|---|---|---|---|---|---|---|---|---|
| Setonix | debug | 8 | 2x 64 | 230 GB | n/a | Exclusive for development and debugging of CPU code and workflows. | 4 | 1h | 1 | 4 |
| Setonix | gpu-dev | 20 | 1x 64 | 230 GB | 8 | Exclusive for development and debugging of GPU code and workflows. | - | 4h | - | - |