-
Notifications
You must be signed in to change notification settings - Fork 107
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
Protein_ligand.ipynb #94
Comments
I am also facing the same problem. A few days ago I subscribed to google colabs which allows me to running 24 hours. but with a small GPU capacity. As a result, I tuned my molecular dynamic with 50 ns for 10 hours, always encountering errors. I repeated it again, still in the same condition, namely the error in the middle of the road. Can you give an explanation/confirm of how much GPU capacity is needed and what is the maximum running time (I mean, the length of running (regarding nanoseconds) and waiting time (regarding total length, for example 10, 20 or 24 hours)? Thank you for your assistance and I look forward to your valuable input. |
hi pablo |
I am currently utilizing the Protein_ligand.ipynb.
However, I have encountered a notification from Colab indicating that the GPU is not being utilized during the runtime. Additionally, I am observing a simulation efficiency rate of approximately 95ns/day.
Could you please confirm if this efficiency rate is within the expected range for the given setup? Furthermore, I would appreciate any advice on how to ensure that the GPU is being actively employed during the simulation to potentially enhance the computational speed.
Thank you for your assistance and I look forward to your valuable input.
The text was updated successfully, but these errors were encountered: