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
The predicted values are nan #120
Comments
Is this still an issue with the latest version of AlphaFold? Also, does it help to run without relax ( |
When I run with |
Hi, thanks for the additional information, we will investigate and let you know. |
Any update on this topic? I am getting the same error using the multimer protocol |
Is this an issue for all 5 predictions or just some of them? |
just some of them |
It only produced one model and stopped
…Sent from my iPhone
On May 25, 2022, at 3:05 PM, Giangpth ***@***.***> wrote:
just some of them
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Same issue for |
This is also the case when Both stop at
|
I just got approval that I can share the following sequences for debugging purposes. In my case, this
|
It looks like this problem can be fixed by making a small change, which is necessary when you're using jax 0.3.8 or newer, see #513 |
This has been fixed in https://github.com/deepmind/alphafold/releases/tag/v2.2.4. Closing this issue, feel free to reopen this issue or open a new issue if this is still a problem. |
I set up alphafold without docker on our server and ran alphafold with A100 GPU.
During relaxation, "simtk.openmm.OpenMMException: Particle coordinate is nan" error occurred as below
These are files in the output directory.
I checked unrelaxed_model_1.pdb, and found that atom coordinates are written as nan. The below is the part of unrelaxed_model_1.pdb.
So, I loaded the result_model_1.pkl file as dictionary and found that the predicted values are also nan.
I checked that the feature.pkl file is okay and parameters for model are loaded well.
I tested different sequences, but the predicted values were always nan.
I guess something went wrong during prediction, but I cannot figure out what is wrong and how to fix it.
Has anyone faced the same issue?
Can anyone help me to fix it?
The text was updated successfully, but these errors were encountered: