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
$ antechamber -i in.mol2 -fi mol2 -o out.mol2 -fo mol2 -s 2 -at gaff2 -c bcc
Welcome to antechamber 17.3: molecular input file processor.
acdoctor mode is on: check and diagnosis problems in the input file.
-- Check Format for mol2 File --
Status: pass
Info: Finished reading file (in.mol2).
-- Check Unusual Elements --
Status: pass
-- Check Open Valences --
Status: pass
-- Check Geometry --
for those bonded
for those not bonded
Status: pass
-- Check Weird Bonds --
/Users/choderaj/miniconda/bin/to_be_dispatched/antechamber: Fatal Error!
Weird atomic valence (5) for atom (ID: 12, Name: N1).
Please check atomic connectivity.
Even running without request for charges leads to failure
$ antechamber -i in.mol2 -fi mol2 -o out.mol2 -fo mol2
Welcome to antechamber 17.3: molecular input file processor.
acdoctor mode is on: check and diagnosis problems in the input file.
-- Check Format for mol2 File --
Status: pass
-- Check Unusual Elements --
Status: pass
-- Check Open Valences --
Status: pass
-- Check Geometry --
for those bonded
for those not bonded
Status: pass
-- Check Weird Bonds --
/Users/choderaj/miniconda/bin/to_be_dispatched/antechamber: Fatal Error!
Weird atomic valence (5) for atom (ID: 12, Name: N1).
Please check atomic connectivity.
I could not locate the script in this repo used to generate the GAFF mol2 files, so I could not check (1) which AmberTools version, and (2) which options were used.
The text was updated successfully, but these errors were encountered:
Processing the provided Tripos
mol2
file for this molecule by antechamber leads to failure:To reproduce (using AmberTools 18.0):
Even running without request for charges leads to failure
I could not locate the script in this repo used to generate the GAFF mol2 files, so I could not check (1) which AmberTools version, and (2) which options were used.
The text was updated successfully, but these errors were encountered: