We would suggest, as with performing a module purge, to conda activate environments explicitly after performing an salloc, and within you scripts that you sbatch. | Code Block |
|---|
[@mblog1]$ salloc -A arcc -t 10:00
salloc: Granted job allocation 1243600
salloc: Nodes mbcpu-025 are ready for job
[@mbcpu-025]$ module purge
[@mbcpu-025]$ module load miniconda3/24.3.0
[@mbcpu-025]$ conda activate py_env
(py_env) [@mbcpu-025]$ python --version
Python 3.12.4
(py_env) [@mbcpu-025]$ conda deactivate
[@mbcpu-025]$ exit
[@mblog1]$ |
Again, since this is now detailed within an sbatch-ed script, ARCC can see and replicate exactly what you are doing when there is an issue. |