-
-
Notifications
You must be signed in to change notification settings - Fork 132
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
local pdb + dssp = error #171
Comments
@a-r-j do you want to fix it or should I have a go at it? |
I've penciled in finishing a few pending PRs today. If you want it fast, I'd appreciate a contribution :) Should be an easy fix: I think it's just missing a
|
Was just about to work on the hotfix, but I see @OliverT1 was quicker than I was :) |
a-r-j
pushed a commit
that referenced
this issue
May 16, 2022
Merged
a-r-j
pushed a commit
that referenced
this issue
May 23, 2022
* adds node name to hover * fixes relative paths (threw errors before) * refactored protein graphs to always have as params: name, pdb_code, pdb_path. Also fixes #171, which was not properly fixed by #172 * fixed notebook execution failure, ran black, fixed docstring * adds test for PR #176: dssp with pdb code or local pdb * ran black, added notebook show_edges visualization, added myself to CONTRIBUTORS.md * dssp now reconstructs a pdb instead of downloading one if none available. pdb_dir default changed to /tmp * re-ran black * fixed tmp security issue. Updated changelog.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using a local pdb file and a ProteinGraphConfig that contains a DSSPConfig, DSSPConfig always tries to download the pdb file, even if it is in the pdb_dir, and throws an error if the name of the pdb file is not a PDB ID.
To Reproduce
Results in:
Whereby this also happens when the file is placed in the pdb_dir:
Expected behavior
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: