Hello!
As a next step in the deprecation process of ORES
https://wikitech.wikimedia.org/wiki/ORES the Machine Learning team will
switch the backend of ores.wikimedia.org to ores-legacy, a k8s application
meant to provide a compatibility layer between ORES and Lift Wing so users
that have not yet
Does the new ores-legacy support the same feature set. E.g. features
output, injection, and threshold optimizations. Or is it just prediction?
This will affect some of the systems I need to migrate.
On Fri, Sep 22, 2023, 06:21 Ilias Sarantopoulos <
isarantopou...@wikimedia.org> wrote:
> Hello!
Hi Aaron!
Thanks for following up. The API is almost compatible with what ORES
currently does, but there are limitations (like the max number of revisions
in a batch etc..). The API clearly states when something is not supported,
so you can check its compatibility now making some requests to:
htt
Do you have a tag for filing bugs against ORES-legacy? I can't seem to
find a relevant one in phab.
On Fri, Sep 22, 2023 at 8:39 AM Luca Toscano wrote:
> Hi Aaron!
>
> Thanks for following up. The API is almost compatible with what ORES
> currently does, but there are limitations (like the max
It looks like model_info is not implemented at all. E.g.
https://ores-legacy.wikimedia.org/v3/scores/enwiki?model_info=statistics.thresholds.true.%22maximum+recall+@+precision+%3E=+0.9%22&models=damaging
I get {"detail":{"error":{"code":"bad request","message":"model_info query
parameter is not s
Hi!
The tag 'Machine-Learning-Team' is the one that we pay more attention to :)
Luca
On Fri, Sep 22, 2023 at 5:54 PM Aaron Halfaker
wrote:
> Do you have a tag for filing bugs against ORES-legacy? I can't seem to
> find a relevant one in phab.
>
> On Fri, Sep 22, 2023 at 8:39 AM Luca Toscano
Let's discuss the issue in a Phabricator task, it seems more appropriate
than here (so other folks can chime in etc.. more easily).
>From our traffic analysis there is no current client using model_info, so
we didn't add it to the feature set. We are working on an equivalent
solution in Lift Wing
We could definitely file a task. However, it does seem like highlighting
the features that will no longer be available is an appropriate topic for a
discussion about migration in a technical mailing list.
Is there a good reference for which features have been excluded from
ores-legacy? It looks
On Fri, Sep 22, 2023 at 8:59 PM Aaron Halfaker
wrote:
> We could definitely file a task. However, it does seem like highlighting
> the features that will no longer be available is an appropriate topic for a
> discussion about migration in a technical mailing list.
>
A specific question related
All fine points. As you can see, I've filed some phab tasks where I saw a
clear opportunity to do so.
> as mentioned before all the models that currently run on ORES are
available in both ores-legacy and Lift Wing.
I thought I read that damaging and goodfaith models are going to be
replaced. S
Luca writes:
> Managing several hundreds models for goodfaith and damaging is not very
scalable in a modern micro-service architecture like Lift Wing
> (since we have a model for each supported wiki). We (both Research and
ML) are oriented on having fewer models that manage more languages at the
11 matches
Mail list logo