I agree that it might have more to do with probtrackx itself rather than Qunex.
It seems the reported errors are mostly on A100 and A6000, it would be great if you could try testing with these gpus, so we’d be sure to pinpoint the issue to probtrackx.
Updates on this issue. I found that requesting 128GB of RAM memory for the cluster call allowed me to go past this error:
msi_resources_time=06:00:00; msi_resources_nodes=1; msi_resources_ntaskspernode=24; msi_resources_mem=256000; msi_queue=a100-8; msi_resources_gpu=gpu:a100:1; msi_resources_jobname=PROBTRACKX; \
study_sharedfolder=/home/moanae/shared/project_K99_ChrTMDHCP_qunex02; \
qunex_container dwi_probtrackx_dense_gpu \
--batchfile=${study_sharedfolder}/processing/batch_K99Aim2.txt --ses…
Dear Jure:
I ran into problem running probtrackx_gpu with CUDA 10.1 in Ubuntu 20.4. Below is the command I used:
qunex_container dwi_probtrackx_dense_gpu \
--sessionsfolder="${WORK_DIR}/${STUDY_NAME}/sessions" \
--sessions="${SESSIONS}" \
--omatrix3="yes" \
--overwrite="yes" \
--container="${QUNEX_CONTAINER}" \
--bash_pre="module load CUDA/10.1" \
--bash_post="export DEFAULT_CUDA_VERSION=10.1" \
--bind="/usr/local/cuda-10.1/:/usr/local/cuda/" \
--nv
And below is the error I …
https://www.jiscmail.ac.uk/cgi-bin/wa-jisc.exe?A2=ind2404&L=FSL&P=R55148 https://www.jiscmail.ac.uk/cgi-bin/wa-jisc.exe?A2=ind1902&L=FSL&D=0&P=332507
Thanks!
Best,