Implementation of from_DOI() - #5454
Conversation
Documentation build overview
10 files changed ·
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #5454 +/- ##
===========================================
+ Coverage 93.87% 93.88% +0.01%
===========================================
Files 182 183 +1
Lines 22510 22650 +140
Branches 3202 3228 +26
===========================================
+ Hits 21131 21265 +134
- Misses 917 921 +4
- Partials 462 464 +2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This diverged from #5436 using |
|
docs still need to be changed and updated |
|
docs for |
orbeckst
left a comment
There was a problem hiding this comment.
Whatever I said on PR #5457 also applies for the common StaticFetcher code here. I assume that once one of these gets merged, the other gets updated accordingly.
More generally though it sounds to me that the original way we thought about organizing fetchers in sub-modules by format (or source) is not useful. The from_xxx() designates the source, the files argument determines the files, so the sub-module (namely, fetch.pdb) is not relevant or really confusing. Perhaps you already have a plan to reorganize everything once the current PRs are merged but if not, I'd suggest to just ditch fetch.pdb and make the fetch_xxx() functions directly available from MDAnalysis.fetch.
| ] | ||
|
|
||
| return paths if not isinstance(pdb_ids, str) else paths[0] | ||
| def from_DOI(doi, file_name, remove_prefix=True, cache_path=None): |
There was a problem hiding this comment.
It's a bit confusing that this lives under fetch.pdb.from_doi() given that it can download any kind of files. The semantics are unclear because when I get a psf I do not "fetch a pdb-formatted file from a DOI".
Perhaps all these functions make more sense directly under fetch, at least fetch.from_doi(..., file="AdK.psf") does not spell a contradictory sentence.
Fixes #5434
Changes made in this Pull Request:
from_DOIusingStaticFetcher()LLM / AI generated code disclosure
LLMs or other AI-powered tools (beyond simple IDE use cases) were used in this contribution: no
PR Checklist
package/CHANGELOGfile updated?package/AUTHORS? (If it is not, add it!)Developers Certificate of Origin
I certify that I can submit this code contribution as described in the Developer Certificate of Origin, under the MDAnalysis LICENSE.