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

updated atoms.coordinates() with atoms.positions #3467 #3576

Closed
wants to merge 1 commit into from
Closed

updated atoms.coordinates() with atoms.positions #3467 #3576

wants to merge 1 commit into from

Conversation

manishsaini6421
Copy link
Contributor

@manishsaini6421 manishsaini6421 commented Mar 28, 2022

Fixes #

Changes made in this Pull Request:

PR Checklist

  • Tests?
  • Docs?
  • CHANGELOG updated?
  • Issue raised/referenced?

@codecov
Copy link

codecov bot commented Mar 28, 2022

Codecov Report

Merging #3576 (355d619) into develop (bf95f9c) will not change coverage.
The diff coverage is 0.00%.

@@           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           
Impacted Files Coverage Δ
package/MDAnalysis/analysis/encore/covariance.py 87.69% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf95f9c...355d619. Read the comment docs.

@@ -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
Copy link
Member

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?

Copy link
Contributor Author

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?

Copy link
Member

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 :)

@orbeckst
Copy link
Member

@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.

@hmacdope
Copy link
Member

@manishsaini6421 there are several other instances of .coordinates to fix, see the original issue #3467 for more info.

Copy link
Member

@hmacdope hmacdope left a 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

@manishsaini6421
Copy link
Contributor Author

@hmacdope Sir,Thanks for your support i'll do it now.

@orbeckst
Copy link
Member

Hi everyone, why was this PR closed?

@manishsaini6421
Copy link
Contributor Author

manishsaini6421 commented Mar 29, 2022

why it is closed?, and my pull request is also under review till now.

EDIT: see #3577 (comment) — please continue work on this PR.

@manishsaini6421
Copy link
Contributor Author

@orbeckst Sir, please check my PR now .

@orbeckst
Copy link
Member

Re-open this PR (you should see a button "Reopen and comment") and close PR #3577.

@lilyminium
Copy link
Member

lilyminium commented Mar 29, 2022

Hi everyone, why was this PR closed?

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...

@lilyminium lilyminium reopened this Mar 29, 2022
@orbeckst
Copy link
Member

@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:

git branch --show-current

should show shiny-new-feature.

Then make sure you have everything from GitHub

git pull

Then say

git status

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.

@manishsaini6421
Copy link
Contributor Author

@orbeckst Sir, there is lot of confusion, please can you fix a meeting so i can do work efficiently.

@IAlibay
Copy link
Member

IAlibay commented Mar 30, 2022

@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.

@hmacdope
Copy link
Member

@manishsaini6421 part of the issue appears to be that you are remaking, deleting or altering the shiny-new-feature branch repeatedly as it no longer contains any of the commits in this PR.

@orbeckst
Copy link
Member

@manishsaini6421 as a starting point for debugging your issue, please answer my questions in #3576 (comment)

@manishsaini6421
Copy link
Contributor Author

@orbeckst Sir, this is because of creating 2nd PR.

@orbeckst orbeckst linked an issue Apr 1, 2022 that may be closed by this pull request
2 tasks
@orbeckst
Copy link
Member

orbeckst commented Apr 1, 2022

This PR is now considered the primary PR for issue #3467 because PR #3479 was closed as stale. Nevertheless, the old PR contains useful information so please consult it.

@orbeckst
Copy link
Member

orbeckst commented Apr 1, 2022

@manishsaini6421 are you still working on this PR?

If not we will close it in 4d as stale.

@orbeckst
Copy link
Member

orbeckst commented Apr 1, 2022

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 orbeckst closed this Apr 1, 2022
@manishsaini6421
Copy link
Contributor Author

@orbeckst ok sir i'll do it but first of all review reqired on #3579 then i can create new PR with another name.

@manishsaini6421
Copy link
Contributor Author

@orbeckst sir can you review it please.

@orbeckst
Copy link
Member

orbeckst commented Apr 1, 2022

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.

@manishsaini6421
Copy link
Contributor Author

@orbeckst In #3579 i have made some changes after review according to changes requested but from last 2 days no one is replying on my comments . sir i am waiting for approval ,can you check it once please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

replace atoms.coordinates() with atoms.positions
5 participants