We'd like to let you know about an upcoming change to ORES that might break your code. We've made some improvements to the way that "model_info" is reported from ORES. Rather than us needing to specify thresholds when we train a model (e.g. "filter_rate_at_recall(min_recall=0.9)"), the system now allows arbitrary queries (e.g. "filter_rate @ recall >= 0.9"). This if more flexible but it may cause problems for anyone who was using the machine-readable thresholds to support a UI in the past. Scores themselves will remain unchanged.
The model info and threshold systems will stay in the current state until we are ready to deploy the newer version to production (probably around Sept. 20th). If you have any questions, please feel free to contact the Scoring Platform Team, via email (ai@lists.wikimedia.net) or IRC (chat.freenode.net:6668 #wikimedia-ai)
-- Zppix Volunteer developer for Wikimedia
Sent from my iPhone
Sorry I ommited some info. The blog post for more info can be found at: https://phabricator.wikimedia.org/phame/post/view/68/more_better_model_infor...
On Aug 31, 2017, at 4:18 PM, zppix e megadev44s.mail@gmail.com wrote:
We'd like to let you know about an upcoming change to ORES that might break your code. We've made some improvements to the way that "model_info" is reported from ORES. Rather than us needing to specify thresholds when we train a model (e.g. "filter_rate_at_recall(min_recall=0.9)"), the system now allows arbitrary queries (e.g. "filter_rate @ recall >= 0.9"). This if more flexible but it may cause problems for anyone who was using the machine-readable thresholds to support a UI in the past. Scores themselves will remain unchanged.
The model info and threshold systems will stay in the current state until we are ready to deploy the newer version to production (probably around Sept. 20th). If you have any questions, please feel free to contact the Scoring Platform Team, via email (ai@lists.wikimedia.net) or IRC (chat.freenode.net:6668 #wikimedia-ai)
-- Zppix Volunteer developer for Wikimedia
Sent from my iPhone
Just to be clear, the blog post contains detailed information about that changes, a demo, and information about how you can test your tool against a server running the updated code. https://ores-misc.wmflabs.org
On Thu, Aug 31, 2017 at 4:20 PM, zppix e megadev44s.mail@gmail.com wrote:
Sorry I ommited some info. The blog post for more info can be found at: https://phabricator.wikimedia.org/phame/post/view/68/more_ better_model_information_and_threshold_optimizations/ On Aug 31, 2017, at 4:18 PM, zppix e megadev44s.mail@gmail.com wrote:
We'd like to let you know about an upcoming change to ORES that might break your code. We've made some improvements to the way that "model_info" is reported from ORES. Rather than us needing to specify thresholds when we train a model (e.g. "filter_rate_at_recall(min_recall=0.9)"), the system now allows arbitrary queries (e.g. "filter_rate @ recall >= 0.9"). This if more flexible but it may cause problems for anyone who was using the machine-readable thresholds to support a UI in the past. Scores themselves will remain unchanged.
The model info and threshold systems will stay in the current state until we are ready to deploy the newer version to production (probably around Sept. 20th). If you have any questions, please feel free to contact the Scoring Platform Team, via email (ai@lists.wikimedia.net) or IRC ( chat.freenode.net:6668 #wikimedia-ai)
-- Zppix Volunteer developer for Wikimedia
Sent from my iPhone
AI mailing list AI@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ai