[Dolphin] Remove the distinction between conditional and zero-state.
Previously, we had two copies of each Record, Train, and Rank method for the ranker and each predictor: one that took a query and one that didn't. The idea was that predictors (and therefore the ranker) was set up to either work in a zero-state or condition-based environment, and clients should only call the appropriate methods. This has limitations, in particular, zero-state predictors can't be used in an ensemble model along with condition-based ones. This CL removes the distinction between these methods. Specific changes are as follows: 1. Predictors now only have Train(target, condition) and Rank(condition) methods. The non-condition versions have been deleted. 2. The Ranker's zero-state Train and Rank methods are now just shortcuts for having an empty-string condition. 3. All predictors labelled ZeroStateX have been renamed to just X. It seems most of our predictors won't use the condition and, in order to incorporate a condition, will be wrapped in some kind of ConditionalPredictor. So it makes sense for the default naming to not specify zero-state-ness, as the current names are very verbose. Bug: 921444 Change-Id: I5273715501319cda951b717d755e1abb559d4dd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1670668 Commit-Queue: Tony Yeoman <tby@chromium.org> Reviewed-by:Charles . <charleszhao@chromium.org> Cr-Commit-Position: refs/heads/master@{#671894}
Showing
This diff is collapsed.
Please register or sign in to comment