-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How long is run_unbiased function in ravefuncs.py expected to take? #2
Comments
Hi ackbar03, That's really strange-- that specific step should not take more than a couple of seconds, if that. One question- are you using GPUs? |
Hi, I'm using GPU. I can see some memory is also occupied in the GPU. However, the addSolvent step is done before the use GPU check in Line 111 in 31df0e0
, I'm not sure if its related. I've added some print statements for debugging to both ravefuncs.py and the relevant Code section in the heavydemo notebook Notebook:
ravefuncs.py:
The output is: |
This is really weird! We have run this multiple times on colab without issues. To clarify, you are running this on your own system with openmm 7.5.1? The only other thing I can think of is that there are version compatibility issues. What is your openmm forcefield package version? I don't think it's a CUDA issue because I don't think the modeller actually uses GPU. I think the next solution would be to run this on your local machine or server using whatever MD package you know works compatibly on it. I (or my co-author Akash) can help you with this-- any MD engine should be fine as long as it is Plumed compatible. The other option is to run this on colab, but while it will work fine for CSP, it will not be enough for your actual system of interest. |
Hi, It seems that I am able to run it directly using a .py file instead of from a Jupiter notebook. I have no idea why. It might be because I had to rerun the cells out of order since the initial run stopped due to erroneous directories and file paths and I wanted to skip the AF2 inference stage. In any case I am able to successfully run the rest of the pipeline. I'm not completely sure what it is I am running yet at the moment though and have yet to look in detail but thanks a lot for your prompt help! |
Hi,
I am running
run_unbiased
inravefuncs.py
via linerave.run_unbiased(on_gpu,plumedfile,dt,temp,freq,nstep,index)
in the "Unbiased simulations" code block. This is taking a long time however.I added some debugging statements and it seems to be stuck at
modeller.addSolvent(forcefield)
in line 98 (alphafold2rave/ravefuncs.py
Line 98 in 31df0e0
for a very long time, upwards of 25 minutes.
Is this normal? How long is this function expected to take?
Thanks
The text was updated successfully, but these errors were encountered: