Thanks @CharlesTurner .
Correct.
Done. The dask worker sits in the queue, runs for a second or two and then quits. Error log:
ERROR: Unable to locate a modulefile for 'conda/analysis3-25.08' /g/data/xp65/public/apps/med_conda_scripts/analysis3-25.08.d/bin/python: line 121: /g/data/w42/dr6273/apps/conda/bin/conda/envs/analysis3-25.08/bin/python: Not a directory
/g/data/xp65/public/apps/med_conda_scripts/analysis3-25.08.d/bin/python: line 121: exec: /g/data/w42/dr6273/apps/conda/bin/conda/envs/analysis3-25.08/bin/python: cannot execute: Not a directory
Same result, slightly different error log (note I added a log_directory path so I can see logs). Before I created this post I didn’t have python or job_script_prologue specified. My attempt to debug led me to the forum post you linked to, plus this one. Error log:
/g/data/xp65/public/apps/med_conda_scripts/analysis3-25.08.d/bin/python: line 121: /g/data/w42/dr6273/apps/conda/bin/conda/envs/analysis3-25.08/bin/python: Not a directory
/g/data/xp65/public/apps/med_conda_scripts/analysis3-25.08.d/bin/python: line 121: exec: /g/data/w42/dr6273/apps/conda/bin/conda/envs/analysis3-25.08/bin/python: cannot execute: Not a directory
Same problem (and same error log as #2)… Just in case I’m doing it wrong form the login node, this is what I do: I log in to Gadi, use module load to load analysis3, run python3 and then the script above.