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
The 17.0 major release is coming on May 16, 2024! This version brings many exciting improvements to GitLab, but also removes some deprecated features. We are introducing three breaking change windows during which we expect breaking changes to be deployed to GitLab.com. You can read more about it on our blogpost. The second breaking change window begins 2024-04-29 09:00 UTC and ends 2024-05-01 22:00 UTC.
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?