Closed
Bug 1400187
Opened 8 years ago
Closed 7 years ago
TAAR: Build a module for the ensemble methods
Categories
(Data Platform and Tools :: General, enhancement, P2)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: fhartmann, Unassigned)
References
Details
The Jupyter notebook created earlier [1] should be converted into a general Python module. This module should have extensive test coverage
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1400186
Comment 1•8 years ago
|
||
Florian, are you currently working on this? Are you planning to work on it in Q4?
Flags: needinfo?(fhartmann)
Florian is currently prototyping different approaches for combining the recommendations that the different TAAR modules provide.
Once that is ready to go, Alessio and I are planning to productionize it and evaluate the feasibility of calling all four TAAR modules per recommendation request.
Assuming performance is sufficient and the ensemble method looks promising on a validation set, we aim to have a followup SHIELD study in Q4 to compare addon installations and addon retention between Linear-TAAR and Ensemble-TAAR.
Flags: needinfo?(fhartmann)
Updated•8 years ago
|
Priority: -- → P2
Comment copied over from duplicate bug for a nice history of this approach:
The current execution of the TAAR recommendation driver selects a recommendation strategy based on available user information. Specific availability of fields I.e. other installed addons, Legacy addons installed, telemetry info in our H-base instance determine which of the recommender systems provide the recommendations.
However it is possible to combine the different sources of information by allow each module to contribute a set of recommended addons and accompanying "confidence" of the output. This would allow a reweighting of a finalized recommendation list that integrates more information into the final list that any individual recommender module has access to.
In order to ensure comparable confidence values on recomendations, each module would have to normalize its own confidence score based on the the range and probability density of such a confidence value being produced.
Additionally, the recommendations passed to RecommendationManager would have to include an ordered list of confidence; or provide a list of tuples including confidence per guid in its output.
Updated•8 years ago
|
Assignee: fhartmann → nobody
Comment 5•8 years ago
|
||
Changed to new component, per bug 1425844.
Component: General → Add-on Recommender
Updated•8 years ago
|
Mentor: alessio.placitelli
Comment 6•7 years ago
|
||
This was shipped in the TAARv2 experiment.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•3 years ago
|
Component: Add-on Recommender → General
You need to log in
before you can comment on or make changes to this bug.
Description
•