When HyperChem writes MOL2 files, it writes the element correctly, but uses the default atom type (Du) for all atoms. This was a deliberate design compromise, to avoid having to map all of the four HyperChem forcefield type sets (each with completely user definable types!) to the set of types in the current Tripos force field (which could change, though we don't know if a Tripos user can change their definitions or not). At one point we considered making the MOL2 filter read-only because of this, but opted for writing with default types instead. Too bad neither Tripos or Wavefunction offer the ability to assign types based on user-editable rules like HyperChem can. ;-)
[Products] [Sales] [Support] [Science] [News] [Corporate] [Search] [Home]
(c) 2003, Hypercube, Inc. All Rights
Reserved.
1115 NW 4th Street, Gainesville, FL 32601 USA
Phone (352) 371-7744 Fax (352) 371-3662 email
info@hyper.com