Draft: avoid np.seterr() in fxc
We add 1e-16 to avoid dividing by zero -- instead of hacking np.seterr() which could behave machine-dependently etc. Not a very nice fix though. Can we do better?
Edited by Ask Hjorth Larsen
We add 1e-16 to avoid dividing by zero -- instead of hacking np.seterr() which could behave machine-dependently etc. Not a very nice fix though. Can we do better?