ialyos
Joined 9 years ago
Joined 9 years ago
I know this because I worked as an ML engineer at an extremely successful company that automated medical coding using deep learning.
The confusion stems from conflating a "perfect solution" with a "human augmented" one.
90% of coding cases are trivial, have low value and can be done by a model. 10% are really subtle and need human expertise.
That's fine. You can make a billion dollar company on low hanging fruit. I think it's best not to conflate the perfect solution with a very good solution.
Original software for it is a bit hard to work with, improvements in https://github.com/ongdexter/ar3_core
I would caution against using nan to always mean infeasible. Instead users should catch experiments outside the feasibility region and return a special infeasible value. This will increase visibility into the behavior of the optimizer, because it leaves nan to be used for values inside the region of constraint that are still problematic (due to bugs, numerical instability, etc)