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
Installation issue #213
Comments
It'd be nice to get a full traceback, not just the last error that you've encountered. |
We changed the name of the example CSV and forgot to update the README, that has now been updated. The correct command is: python3 -m inference --config default_inference_args.yaml --protein_ligand_csv data/protein_ligand_example.csv --out_dir results/user_predictions_small For multiple ligands, you could create a CSV with the same PDB repeated across multiple rows and different ligand files. If you mean multiple ligands at the same time, you'd need to combine them into one SDF file. |
I hope this email finds you well. I want to express my gratitude for
promptly addressing the previous issue.
I have another query regarding the utilization of multiple SMILEs and their
respective fragments for SMILE, along with experimental PDB data. I aim to
employ a different docking procedure to assess the confidence scores for
these SMILEs and PDB data compared to their fragments and PDB.
Consequently, I will have a diverse dataset comprising multiple SMILEs,
Fragments, and PDB data.
Could you kindly provide guidance on the optimal approach for running
DiffDock in this scenario? Currently, I have DiffDock set up, and I'm
contemplating whether updating the dataset in the input file would suffice
for seamless operation.
Thanks & Regards,
Saveena Solanki
Ph.D. Scholar
The Chemosensory Lab
Department of Computational Biology (IIITD)
…On Fri, Apr 26, 2024 at 8:24 PM Jacob Silterra ***@***.***> wrote:
We changed the name of the example CSV and forgot to update the README,
that has now been updated. The correct command is:
python3 -m inference --config default_inference_args.yaml
--protein_ligand_csv data/protein_ligand_example.csv --out_dir
results/user_predictions_small
For multiple ligands, you could create a CSV with the same PDB repeated
across multiple rows and different ligand files. If you mean multiple
ligands at the same time, you'd need to combine them into one SDF file.
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3B3YNOJDBVIYBUGW6SLTXLY7JTDPAVCNFSM6AAAAABGDZBK2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZGU2TINJWGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
ok. what why it was killed it was working before the update and then after not anymore, I was not sure, I almost gave up. I will reinstall the things |
After creating environment and all the dependencies the final command line python3 -m inference.py --config default_inference_args.yaml --protein_ligand_csv data/protein_ligand_example_csv.csv --out_dir results/user_predictions_small
give error terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Aborted (core dumped)
any solution for this ?
one more thing if we have multiple ligand for single PDB how to smoothly run for those?
The text was updated successfully, but these errors were encountered: