Why
hpc/slurm_array_template.sh has generic laptop/HPC defaults (4h, 8 CPUs, 32G, GPU directive commented). Those are not a verified allocation for any named cluster.
What to do
On the actual cluster:
- Fill in real
#SBATCH time, CPUs, memory, partition, account, and GPU if needed.
- Set
ASLA_MODULES and ASLA_CONDA_ENV (or equivalent) so jobs find the same Python as local tests.
- Confirm
python scripts/hpc_preflight.py still passes on the login node.
- Submit a dry-run array first:
sbatch --export=ALL,ASLA_SITE_COMMAND_TEMPLATE=hpc/site_command.template,ASLA_REAL_TRAIN_EVAL=/path/to/your_train_and_eval.py hpc/slurm_array_template.sh
- Inspect
logs/ and results/hpc/*/command.txt.
- Only then submit with
ASLA_EXECUTE=1.
The array must remain 1-N where N is the current manifest length (currently 45).
Acceptance
Files
hpc/slurm_array_template.sh
hpc/ADAPTATION_CHECKLIST.md
data/HPC_CHECKLIST.md
Do not fabricate
- Enable
--execute in the template by default
- Change array bounds without regenerating the manifest
Why
hpc/slurm_array_template.shhas generic laptop/HPC defaults (4h,8CPUs,32G, GPU directive commented). Those are not a verified allocation for any named cluster.What to do
On the actual cluster:
#SBATCHtime, CPUs, memory, partition, account, and GPU if needed.ASLA_MODULESandASLA_CONDA_ENV(or equivalent) so jobs find the same Python as local tests.python scripts/hpc_preflight.pystill passes on the login node.logs/andresults/hpc/*/command.txt.ASLA_EXECUTE=1.The array must remain
1-NwhereNis the current manifest length (currently 45).Acceptance
hpc/ADAPTATION_CHECKLIST.mdASLA_EXECUTE=1Files
hpc/slurm_array_template.shhpc/ADAPTATION_CHECKLIST.mddata/HPC_CHECKLIST.mdDo not fabricate
--executein the template by default