Spec says AM1BCC-ELF10 charges are used; Toolkit does not
See original GitHub issueDescribe the bug
The specification says that AM1BCC-ELF10 charges are used in SMIRNOFF. This is not currently the case.

To Reproduce
Output The full error message (may be large, that’s fine. Better to paste too much than too little.)
Computing environment (please complete the following information):
- Operating system
- Output of running
conda list
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
OpenFF Toolkit Documentation
Additionally, ParameterAttribute documentation no longer appears incorrectly in classes where it is used. Fixes Issue #397.
Read more >molcharge Appendix: Complete list of -method options
am1bccelf10 charging is designed to average the AM1BCC charges from 10 ... This method should not be used for intermolecular interactions.
Read more >OpenFF Toolkit Documentation - Read the Docs
If not, the quickest way to get started is to install the Miniconda distribution, a lightweight, minimal installation of Python and the Conda ......
Read more >Molecule — OpenFF Toolkit 0.11.4+0.g516048f4.dirty ...
This method reports an improper for each trivalent atom in the molecule, whether or not any given force field would assign it improper...
Read more >R.E.D. I FAQ - q4md-forcefieldtools.org
In my opinion the PDB file generated by "antechamber" (with the RESP charges in it), can NOT be used in charge visualization in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think this is an area of where the spec isn’t really behaving as a spec and more of an implementation detail as well. Ideally the spec should just state whether it should state the charge method (i.e AM1, AM1BCC) and the ideal number of conformers + any pruning (e.g. ELF) that should take place.
For the record, this should be fixed in the 0.11.0 release.