3 ms·
I hear you on the AI vs ML thing. I doubt the debate will ever be resolved, but the domain name is .ai so I went with that. The reason to use a full machine le
by orasis 5y ago
I hear you on the AI vs ML thing. I doubt the debate will ever be resolved, but the domain name is .ai so I went with that.
The reason to use a full machine learning model instead of a simple statistical model is three-fold:
1) The framework supports any arbitrary JSON encodable data structure as a variant, this includes nested dictionaries, lists, etc. A full ML model allows capturing the entire complexity of the data stored in the variant - numbers, strings, booleans, etc and those can even be changed and the model will still be able to predict performance.
2) A full ML model allows generalization across complex variants. So if later on you introduce new variants, it may already be imply some things about how that variant will perform. For the most part simple statistical models must learn each variant from scratch.
3) The models don't just seek to make decisions that are a global optimum, like you would do with A/B testing. They are seeking to find a contextual optimum given the current conditions. This type of modeling also requires the generalization that ML gives you.
- gavinray 5y agoThose are really good answers, especially the points about nested JSON structures and generalization. Not sure I understand point #3 -- not familiar with global vs contextual optimum. The idea is that a global optimum is the aggregate optimum across all users, versus a contextual optimum which is the optimum for just the current user/device? Couldn't you do this by doing regressions on a per-user-id basis or similar if that was the case? (I really don't know)