Open mattwthompson opened 3 years ago
What @hmacdope wrote up here can hide these warnings from STDOUT/STDERR: https://github.com/asapdiscovery/asapdiscovery/issues/327
from openeye import oechem
errfs = oechem.oeofstream("openeye_My_Workflow_log.txt")
oechem.OEThrow.SetOutputStream(errfs)
oechem.OEThrow.SetLevel(oechem.OEErrorLevel_MIN)
This workaround is needed since they're emitted from OEChem's C++ layer not the standard Python logging locations
Two caveats (from me):
_MIN
to use: https://docs.eyesopen.com/toolkits/python/oechemtk/OESystemConstants/OEErrorLevel.html#OESystem::OEErrorLevelHugo also says, referencing https://github.com/asapdiscovery/asapdiscovery/issues/281
Beware of trying to use OpenEye logging with OMEGA confgen in the same process as well. I did tell OpenEye about this, they may have fixed it in latest release.
Describe the bug
Reproduction
Specifically the output in block 3 is confusing and could be misleading to a newer user - what failed? Why is it a warning if something failed? I got a conformer back and it looks reasonable (in visualization, not just eyeballing coordinates). It's not obvious to the user that these are emitted by OpenEye or how they should be interpreted (or ignored).
Computing environment (please complete the following information):
conda list
: https://gist.github.com/mattwthompson/3157e8f38d73c2d561d5dec356e1a2deAdditional context I couldn't find an open issue about this, but I recall discussions about handling OpenEye output existing already. #596 is related but targeting a different idea.