-
Notifications
You must be signed in to change notification settings - Fork 11
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
Standardization of terms #163
Comments
Agreed :) |
Yes, I think some simple guidelines would be a good idea. Let's post thoughts in this comment thread for now and eventually we can make a wiki page. |
It would be really nice to get this established for PMI2. |
The aforementioned developer guide can be found on the wiki. |
sethaxen
added a commit
that referenced
this issue
Jun 25, 2018
sethaxen
added a commit
that referenced
this issue
Jun 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should standardize nomenclature in PMI. For example, in our current working code:
Should the internal model object be self.m or self.mdl?
Is the crosslink database object passed to XL restraints passed as CrossLinkDataBase or xldb?
What is the base object passed to restraints? PMI Objects or Hierarchies?
The text was updated successfully, but these errors were encountered: