-
Notifications
You must be signed in to change notification settings - Fork 647
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
bfactors and tempfactors #2833
Comments
It's especially annoying that the PDB format only uses At least in Oct 2019 TPRParser did not actually have either bfactors or tempfactors. ParmedParser uses Tempfactors despite ParmEd calling them bfactors (as does nglview). Personally I prefer bfactors > tempfactors, but the latter seems to be the majority attribute. |
I must learn to search for open issues before opening new ones... |
@lilyminium you are right about the
|
duplicates #1901 |
Expected behavior
I expect attributes representing the same thing to be consistent across file formats.
Actual behavior
For the MMTF format we have the
bfactors
attribute, while for other formats we havetempfactors
(see user guide).From a quick search within the code, I think
bfactors
is also used byTPRParser
andParmEdParser
.In
topologyattrs.py
there are bothclass Tempfactors
andclass Bfactors
. Should the two attributes be merged?The text was updated successfully, but these errors were encountered: