Remove deprecated hole, and completes py2 removal#2778
Remove deprecated hole, and completes py2 removal#2778richardjgowers merged 16 commits intoMDAnalysis:developfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2778 +/- ##
===========================================
+ Coverage 91.12% 91.42% +0.30%
===========================================
Files 179 178 -1
Lines 23844 23479 -365
Branches 3144 3090 -54
===========================================
- Hits 21727 21465 -262
+ Misses 1496 1425 -71
+ Partials 621 589 -32
Continue to review full report at Codecov.
|
orbeckst
left a comment
There was a problem hiding this comment.
Looking great, just a minor comment (asv).
| Analysis of helices with the HELANAL_ algorithm. | ||
|
|
||
| :mod:`~MDAnalysis.analysis.hole` | ||
| :mod:`~MDAnalysis.analysis.hole2.hole` |
There was a problem hiding this comment.
Would be nicer to have a page for the hole2 package instead of going to its module. But can be separate PR if it requires work.
There was a problem hiding this comment.
So it turns out this __init__ text isn't actually used anywhere for docs generation (as far as I can tell), the hole2 package links to: https://www.mdanalysis.org/docs/documentation_pages/analysis/hole2.html#hole-analysis-mdanalysis-analysis-hole2
I can just get rid of the .hole portion if you think it's more appropriate.
There was a problem hiding this comment.
I think hole2 is more appropriate.
It looks as if the doc string requires an update anyway... probably getting rid of most of it and just saying something simple for anyone using help(MDA.analysis). But can be different issue.
There was a problem hiding this comment.
I changed it in fa48e06, but on testing on a page for which docs actually do get built for, it seems like it won't link to anything. Either way if the whole thing is going to get re-written, and considering that these docs don't get built anyways, then it might be good enough for now?
|
@IAlibay sort out the conflicts and we can merge this probably |
|
Hello everyone! I am a MDA. Hole user but I am quite interested in the development of this tool. I have been using this module to run analysis on quite long trajectories, resulting in long computing times. I don't know if this is the place of doing such a question (I am very new at Github, so I don't know the manners here): is there a way to make the code run parallel frames using python multiprocessing, so a single trajectory could be run on multiple threads? I am very new to all of this, sorry if this is not the place for this! |
|
Hi @GeraZerbetto, Welcome to MDA (or at least the github side of things if you are already a use the code 😄 )! Ideally could you ask this question on either the developer or user discussion email lists? Roughly, the way we try to organise things are in the following manner:
|
|
Hi @IAlibay |
Fixes #2541, Towards #2773 and #2739 , Changelog for #2765
Changes made in this Pull Request:
6 - Maturefor 2.x.x.PR Checklist