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 "skip" issue encountered after running the inference #215
Comments
I had the same issue I directly ran the inference file, but somehow it worked when I used app/main.py |
thanks,i try it |
I had similar issue using DiffDock v1.1.1. However it works using the data examples provided in https://github.com/gcorso/DiffDock/tree/main/data/1a0q:
But it fails with my data:
This raises the following error:
These two files can be used to test after removing the Is there anything wrong in my input data? How can I solve this issue? |
Further test: It fails with
It raises this error:
But it works with
This means the error comes from the PDB file. Note that I also tried to keep in the PDB files only the lines starting with ATOM: AF-P00519-F1-model_v4-truncated.pdb.txt But there is still the same error. The PDB file comes fom the AlphaFold website |
Last test that was successul with this PDB directly directly produced by AlphaFold I ran myself
|
This is possibly because of the protein length restriction (1022) on DiffDock inferences. Refer to this issue #199 |
Thank you @prathithbhargav for this information, I was not aware of this limitation. |
python -m inference --config default_inference_args.yaml --protein_path ./rec_1.pdb --ligand ./ZINC01535869.mol2 --out_dir ./outache/ --inference_steps 20 --samples_per_complex 40 --batch_size 10 --actual_steps 18 --no_final_step_noise
The following error occurred and there was no output. Does anyone know how to solve it?thanks
Skipping complex_0 because of the error:
'X'
HAPPENING | The confidence dataset did not contain ['complex_0']. We are skipping this complex.
1it [00:00, 1.13it/s]
Failed for 0 complexes
Skipped 1 complexes
The text was updated successfully, but these errors were encountered: