gpu4pyscf icon indicating copy to clipboard operation
gpu4pyscf copied to clipboard

Issue with QM Calculations Terminating Prematurely When Assigned to Individual GPUs

Open ORCAaAaA-ui opened this issue 9 months ago • 3 comments

I am experiencing an issue with running QM calculations on individual GPUs. When assigning QM calculations to separate GPUs, the calculations terminate prematurely without completing. This issue does not occur when running the calculations on a single GPU. I have ensured that each GPU has sufficient memory.

Any recommended steps to further diagnose and resolve this issue?

I appreciate any assistance or guidance on this issue. Thank you.

ORCAaAaA-ui avatar May 15 '24 04:05 ORCAaAaA-ui

@ORCAaAaA-ui How do you assign QM calculations to separate GPUs? Can you share the script here for diagnosing?

wxj6000 avatar May 22 '24 22:05 wxj6000

@ORCAaAaA-ui There are at least two ways to select individual GPU. 1) Use docker. You can specify which GPU is visible when you run docker run. 2) Use CuPy. https://docs.cupy.dev/en/stable/reference/generated/cupy.cuda.Device.html But you can only import gpu4pyscf modules when the device is selected.

When the above PR is merged, one can import GPU4PySCF before the device is selected.

wxj6000 avatar May 26 '24 17:05 wxj6000

@wxj6000 I simply excuted the command, 'export CUDA_VISIBLE_DEVICES=0 or 1', to assign jobs to each GPU.

ORCAaAaA-ui avatar May 30 '24 01:05 ORCAaAaA-ui