-
Notifications
You must be signed in to change notification settings - Fork 663
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
updated atoms.coordinates() with atoms.positions #3467 #3576
updated atoms.coordinates() with atoms.positions #3467 #3576
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #3576 +/- ##
========================================
Coverage 94.20% 94.20%
========================================
Files 190 190
Lines 24668 24668
Branches 3313 3313
========================================
Hits 23238 23238
Misses 1384 1384
Partials 46 46
Continue to review full report at Codecov.
|
@@ -215,7 +215,7 @@ def covariance_matrix(ensemble, | |||
# Select the same atoms in reference structure | |||
reference_atom_selection = reference.select_atoms( | |||
ensemble.get_atom_selection_string()) | |||
reference_coordinates = reference_atom_selection.atoms.coordinates() | |||
reference_coordinates = reference_atom_selection.atoms.positions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please add a test that check this fix works?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you tell me please, how to add test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@manishsaini6421 please write a function with code that uses this pathway. It should fail with the original .coordinates()
and succeed with the new .positions
. Have a look at the tests in https://github.com/MDAnalysis/mdanalysis/blob/develop/testsuite/MDAnalysisTests/analysis/test_encore.py and more generally throughout https://github.com/MDAnalysis/mdanalysis/tree/develop/testsuite/MDAnalysisTests for ideas :)
@manishsaini6421 please be aware that there's another PR #3479 open which would take precedence over yours. If we don't see any further progress on the other PR within 4 days we will close it as stale on 2022-04-01 and then your PR will be next in line. See #3479 (comment) on the other PR. Thank you for your patience. |
@manishsaini6421 there are several other instances of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment above
@hmacdope Sir,Thanks for your support i'll do it now. |
Hi everyone, why was this PR closed? |
why it is closed?, and my pull request is also under review till now. EDIT: see #3577 (comment) — please continue work on this PR. |
@orbeckst Sir, please check my PR now . |
Re-open this PR (you should see a button "Reopen and comment") and close PR #3577. |
I think it could have been automatically closed by GitHub because @manishsaini6421 made a new PR from the same branch. There can only ever be one PR from branch A to branch B. Edit: maybe not, since #3577 stays open... |
@manishsaini6421 I am slightly confused why your branch manishsaini6421:shiny-new-feature only contains 1 change in this PR but contained 2 changes in the other closer PR #3577. In any case, can you please check that you are on the current branch:
should show shiny-new-feature. Then make sure you have everything from GitHub
Then say
Do you see any changes that are not committed? If so add the changes, commit, and push. In particular, make the changes that I can see in the closed PR https://github.com/MDAnalysis/mdanalysis/pull/3577/files (in benchmarks/benchmarks/analysis/rms.py). Check that the changes show up in this PR. If not, let us know. |
@orbeckst Sir, there is lot of confusion, please can you fix a meeting so i can do work efficiently. |
@manishsaini6421 I'll let the other @MDAnalysis/gsoc-mentors weigh in here, but we generally don't have sufficient time to have focused meetings with individual applicants during the GSoC application period. The mentors all have separate jobs outside of MDAnalysis, usually at academic institutions where teaching is currently at its peak. I would instead suggest that you ask your questions on the mailing list or on discord, where others may get to asynchronously answer your questions. |
@manishsaini6421 part of the issue appears to be that you are remaking, deleting or altering the |
@manishsaini6421 as a starting point for debugging your issue, please answer my questions in #3576 (comment) |
@orbeckst Sir, this is because of creating 2nd PR. |
@manishsaini6421 are you still working on this PR? If not we will close it in 4d as stale. |
I read #3579 (comment) and it looks as if it's not easily possible for @manishsaini6421 to continue working on this PR because their PR #3579 also uses the same branch name "shiny-new-feature". I think there's some misunderstanding for how branching with git works. In any case, I am closing this PR because it's not going to be easy for the contributor to continue. @manishsaini6421 please open a new PR and use a distinct branch name (such as "issue-3467-replace-coordinates"). |
@orbeckst sir can you review it please. |
We want you to do one PR after another. Focus on #3579 ; given that someone is already reviewing it, you just have to wait on the reviews there. This can take some time and we cannot drop other work as soon as there are changes on a PR; it can take a day so be patient, please. Once PR #3579 is merged you can consider opening a new PR for issue #3467 . We are much more impressed with applicants who efficiently complete one problem than ones that open on multiple problems at the same time. Therefore, we are not going to review this closed PR. |
Fixes #
Changes made in this Pull Request:
PR Checklist