Setting up Service to Predict Component for Directories |
|||||
Issue descriptionPredict component for directory path. There are 2 steps to set up this service: 1. Train and save the prediction model on collected directory-component mappings. (Proposal: http://bit.ly/directory-mapping-proposal) 2. Set up prediction service in google app engine. e.g. Input [src/third_party/WebKit, src/components/toolbar] Output [[Blink], [UI>Browser>Toolbar]]
,
Mar 16 2017
,
Mar 16 2017
,
Mar 20 2017
,
Mar 23 2017
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/dd31397d353239d91a8330cc88ac8e54195f26f6 commit dd31397d353239d91a8330cc88ac8e54195f26f6 Author: ymzhang <ymzhang@chromium.org> Date: Thu Mar 23 17:38:38 2017 [Component Mapper]Adding directory component prediction service to monorail-predict-staging.appspot.com. Using a smaller issue prediction model for local test purpose. The directory component model might be updated in the future. Proposal about how to predict suggested component for directory. https://goo.gl/xtSMpV Bug= 701551 Change-Id: I1e53a2ca3385f5c2dd9a26b07c7e2550274417e4 Reviewed-on: https://chromium-review.googlesource.com/457457 Reviewed-by: Sean McCullough <seanmccullough@chromium.org> Commit-Queue: Yangmuzi Zhang <ymzhang@chromium.org> [modify] https://crrev.com/dd31397d353239d91a8330cc88ac8e54195f26f6/appengine/monorail-predict/Dockerfile [modify] https://crrev.com/dd31397d353239d91a8330cc88ac8e54195f26f6/appengine/monorail-predict/templates/comment.html [modify] https://crrev.com/dd31397d353239d91a8330cc88ac8e54195f26f6/appengine/monorail-predict/app.yaml [modify] https://crrev.com/dd31397d353239d91a8330cc88ac8e54195f26f6/appengine/monorail-predict/service.py
,
Apr 6 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ymzhang@chromium.org
, Mar 14 2017