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

improved unknown attribute errors in atomgroup and atom classes #2573

Conversation

AnshulAngaria
Copy link

Fixes #2565

Changes made in this Pull Request:
Changed error message when an unknown attribute/method is accessed.

PR Checklist

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

Copy link
Member

@zemanj zemanj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are several issues with this PR.

  1. It solves parts of the problem but does not differentiate between generally valid but unavailable versus really unknown properties.
  2. The particular cases of the AtomGroup properties 'fragments', 'fragindices', 'n_fragments', 'unwrap', and, likewise, the Atom properties 'fragment', 'fragindex'need special care, because these are attributes/methods which are generated based on the topology containing bond information. Thus, it doesn't make sense to say that these attributes are missing from the topology because the error is actually due to missing information about bonds.

@orbeckst
Copy link
Member

orbeckst commented Mar 3, 2020

@zemanj , when you take the time to review (thank you!!) and you find that the PR is not ready to be merged, make it a "request changes" instead of a neutral comment as this sends a much clearer message.

Especially for GSoC, we want to communicate clearly with the students. They should ask for clarification if anything is unclear or if they don't know how to move forward.

@zemanj
Copy link
Member

zemanj commented Mar 3, 2020

@orbeckst that was on purpose, see here.

@AnshulAngaria
Copy link
Author

Thanks @orbeckst @zemanj for the response. I understand that someone else was already working on the issue. Right now I have already started working on #2470

@orbeckst
Copy link
Member

orbeckst commented Mar 3, 2020 via email

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.

Improve missing AtomGroup property error messages
4 participants