You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently converters are partially dealt with under the umbrella of topology & coordinate parsers. However they are not completely dealt with properly, for example neither RDKit or OpenMM are covered under gen_topologyparser_attrs.
At the very minimum we should clean this up. Ideally we should look to see if we should just separate out converters and deal with them in a separate way than standard topology/coordinate readers?
The text was updated successfully, but these errors were encountered:
Currently converters are partially dealt with under the umbrella of topology & coordinate parsers. However they are not completely dealt with properly, for example neither RDKit or OpenMM are covered under
gen_topologyparser_attrs
.At the very minimum we should clean this up. Ideally we should look to see if we should just separate out converters and deal with them in a separate way than standard topology/coordinate readers?
The text was updated successfully, but these errors were encountered: