Skip to content
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

Combined #100 and #139 plus equivalent functionality in main.cpp #146

Merged
merged 6 commits into from
Oct 28, 2022

Conversation

diogomart
Copy link
Member

Here we are merging #139, which prevents the Python process from exiting in case a ligand fails reading, as well as adding the equivalent functionality to main.cpp, to skip ligands when using the --batch option, instead of exiting with pdbqt_parse_error.

The code from #100 is not merged (it implements the same idea #139, but with a custom error). It's "merged" simply to keep it in the commit graph.

everburstSun and others added 5 commits April 8, 2022 08:23
Here we are keeping the code from PR #139 from shazj99,
but PR #100 implemented similar code to catch errors in
Python when the PDBQT parser fails a ligand. PR #100 is
more complex because it creates a custom error.
@diogomart diogomart merged commit 48c7c67 into develop Oct 28, 2022
@diogomart diogomart deleted the parse_pdbqt branch June 15, 2023 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants