Most of the time using the PyBel (Openbabel 3.1.0) api in enzy_htp to protonate ligand will give a file with "HETATM" lines. (e.g.: test/preparation/test_protonate.py::test_pybel_protonate_pdb_ligand_4CO)
But in the case of 4NEG, PyBel gives "ATOM" lines while parsing the ligand HEZ. (e.g.: test/preparation/test_protonate.py::test_fix_pybel_output)
There is no obvious reason PyBel treats these 2 ligand files differently.
This causes a bug that _fix_pybel_output cant read the protonated ligand from PyBel in the current version of enzy_htp.
Most of the time using the PyBel (Openbabel 3.1.0) api in enzy_htp to protonate ligand will give a file with "HETATM" lines. (e.g.: test/preparation/test_protonate.py::test_pybel_protonate_pdb_ligand_4CO) But in the case of 4NEG, PyBel gives "ATOM" lines while parsing the ligand HEZ. (e.g.: test/preparation/test_protonate.py::test_fix_pybel_output) There is no obvious reason PyBel treats these 2 ligand files differently.
This causes a bug that _fix_pybel_output cant read the protonated ligand from PyBel in the current version of enzy_htp.