On Mon, Sep 25, 2023 at 10:37 AM Chris Albon wrote:
> Hey SJ!
>
> Intuitively one model per wiki has a lot of merit.
>
< if we continued down that path, Lift Wing would eventually be hosting
> 3000+ models (i.e. 330 models per new feature) pretty quickly
>
< But with language agnostic models we
See https://phabricator.wikimedia.org/T347344
On Mon, Sep 25, 2023 at 12:26 PM Aaron Halfaker
wrote:
> It looks like user-scripts running on Wikipedia can no longer use ORES.
> I'm getting a CORS error. You can test this by trying to run the
> following the JS dev console on a Wikimedia page:
It looks like user-scripts running on Wikipedia can no longer use ORES.
I'm getting a CORS error. You can test this by trying to run the
following the JS dev console on a Wikimedia page:
> $.ajax({url: "https://ores.wikimedia.org/v3/scores/
"}).done(function(response){console.log(response)})
Hey SJ!
> Is there a reason to think that separate models for each wiki are more
effective than one general model that sees the name of the wiki as part of
its context?
Intuitively one model per wiki has a lot of merit. The training data comes
from the community that is impacted by the model,
Hi!
I'll leave the comments related to model architecture and behavior to
others (more expert than me), I'd like to comment on the
process/infrastructure parts :)
On Sat, Sep 23, 2023 at 9:03 PM Strainu wrote:
> Hi folks,
>
> So glad to see the old and new ML teams have an open discussion
Hi folks,
So glad to see the old and new ML teams have an open discussion about this
subject.
I understand that the team might prefer to have several tickets for
different issues, but the discussion about the general approach to the
different models is of interest to many people and is more
On Fri, Sep 22, 2023 at 11:34 PM Aaron Halfaker
wrote:
> All fine points. As you can see, I've filed some phab tasks where I saw a
> clear opportunity to do so.
>
Thanks a lot! We are going to review them next week and decide the next
steps, but we'd like to proceed anyway to migrate ores to
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
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.
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
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
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
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
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=damaging
I get {"detail":{"error":{"code":"bad request","message":"model_info query
parameter is not
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
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:
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!
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
On Tue, 8 Aug 2023, 10:45 Tilman Bayer, wrote:
>
> Hi Chris,
>
> On Mon, Aug 7, 2023 at 11:51 AM Chris Albon wrote:
>
>> Hi Tilman,
>>
>> Most of the work is still very experimental. We have hosted a few LLMs on
>> Lift Wing already (StarCoder for example) but they were just running on
>> CPU,
Hi Strainu!
On Fri, Aug 4, 2023 at 3:25 PM Strainu wrote:
> Hi Chris & ML team,
>
> Good to see LiftWing is finally becoming a reality. There are a few things
> in the documentation that I would like to clarify.
>
> 1. In [1], the bot owner is encouraged to move to the revertrisk score.
>
Hi Tilman!
On Tue, Aug 8, 2023 at 5:45 AM Tilman Bayer wrote:
>
> Hi Chris,
>
> On Mon, Aug 7, 2023 at 11:51 AM Chris Albon wrote:
>
>> Hi Tilman,
>>
>> Most of the work is still very experimental. We have hosted a few LLMs on
>> Lift Wing already (StarCoder for example) but they were just
Hi Chris,
On Mon, Aug 7, 2023 at 11:51 AM Chris Albon wrote:
> Hi Tilman,
>
> Most of the work is still very experimental. We have hosted a few LLMs on
> Lift Wing already (StarCoder for example) but they were just running on
> CPU, far too slow for real use cases. But it proves that we can
Hi Tilman,
Most of the work is still very experimental. We have hosted a few LLMs on
Lift Wing already (StarCoder for example) but they were just running on
CPU, far too slow for real use cases. But it proves that we can easily host
LLMs on Lift Wing. We have been pretty quiet about it while we
Hi Strainu,
Here Diego from the WMF Research team,
> 1. In [1], the bot owner is encouraged to move to the revertrisk score.
However, in [2], it's explicitly mentioned that the model should not be
used for "Auto-removing edits that a user makes without another editor in
the loop". So, should bot
On Thu, Aug 3, 2023 at 7:16 AM Chris Albon wrote:
> Hi everybody,
>
> TL;DR We would like users of ORES models to migrate to our new open source
> ML infrastructure, Lift Wing, within the next five months. We are available
> to help you do that, from advice to making code commits. It is
Hi Chris & ML team,
Good to see LiftWing is finally becoming a reality. There are a few things
in the documentation that I would like to clarify.
1. In [1], the bot owner is encouraged to move to the revertrisk score.
However, in [2], it's explicitly mentioned that the model should not be
used
בתאריך יום ו׳, 4 באוג׳ 2023, 13:53, מאת Brian Wolff :
> > Our understanding is that renaming extensions in MediaWiki is a long
> and complicated process, so we'll likely not be able to rename it in the
> foreseeable future.
>
> Why?
>
> Renaming is usually a bad thing because it often confuses
Am Fr., 4. Aug. 2023 um 12:53 Uhr schrieb Brian Wolff :
> > Our understanding is that renaming extensions in MediaWiki is a long
> and complicated process, so we'll likely not be able to rename it in the
> foreseeable future.
>
> Why?
>
> Renaming is usually a bad thing because it often confuses
> Our understanding is that renaming extensions in MediaWiki is a long and
complicated process, so we'll likely not be able to rename it in the
foreseeable future.
Why?
Renaming is usually a bad thing because it often confuses the hell out of
users, but from a technical perspective it is pretty
Great, thank you!
בתאריך יום ו׳, 4 באוג׳ 2023, 11:49, מאת Luca Toscano <
ltosc...@wikimedia.org>:
> Hi Amir!
>
> Answering inline:
>
> On Thu, Aug 3, 2023 at 10:11 PM Amir E. Aharoni <
> amir.ahar...@mail.huji.ac.il> wrote:
>
>>
>> The email says that "All ML models currently accessible on ORES
Hi Amir!
Answering inline:
On Thu, Aug 3, 2023 at 10:11 PM Amir E. Aharoni <
amir.ahar...@mail.huji.ac.il> wrote:
>
> The email says that "All ML models currently accessible on ORES are also
> currently accessible on Lift Wing", and if I understand correctly, this
> means that this feature in
It's possible that I'm very out of touch, but I'll ask anyway :)
As far as I know, the main place where editors of Wikimedia's wiki sites
actually see ORES in action is the filtering and highlighting functionality
on Recent Changes. This functionality is enabled in a limited number of
wikis, but
32 matches
Mail list logo
