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
I found an issue where, any kwargs that are provided to mbuild.load when using gmso as a backend, is not propagated. The issue stems from the following line in mbuild's conversion.py.
Copy the content above and save it to a hexane.mol2 file.
fromgmso.core.topologyimportTopologyfromgmso.external.convert_mbuildimportto_mbuildimportmbuildasmb## With site_type='lj', elements are not inferredgmso_top=Topology.load('hexane.mol2', site_type='lj')
mbuild_compound_using_gmso=to_mbuild(gmso_top)
print('Using gmso.Topology.load')
forparticleinmbuild_compound_using_gmso.particles():
print(particle.element)
print()
## Same with mbuild infers elementprint('Using mbuild.load')
mbuild_compound_using_mbuild_dot_load=mb.load('hexane.mol2', site_type='lj', backend='gmso')
forparticleinmbuild_compound_using_mbuild_dot_load.particles():
print(particle.element)
print()
I found an issue where, any
kwargs
that are provided tombuild.load
when usinggmso
as a backend, is not propagated. The issue stems from the following line in mbuild'sconversion.py
.mbuild/mbuild/conversion.py
Line 431 in a1611f1
Reproduce with non-atomistic mol2 files
Copy the content above and save it to a
hexane.mol2
file.Software versions
0.14.2
)3.9.7
)?unix
The text was updated successfully, but these errors were encountered: