Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Question/proposal regarding ADWIN clock
See original GitHub issueHi, I have a question about the clock implemented into the ADWIN drift detector (https://github.com/online-ml/river/blob/main/river/drift/adwin_c.pyx#L215). As I understand it, it will only check for drifts every 32nd time. My guess would be that this is done to increase the speed/performance of the detector, but I haven’t found any mention about this in the original ADWIN paper. If you know more about this or can point me to a paper where the reason for this clock is given, that would be great.
My concern is that this clock period (32) will likely not fit for all scenarios, and there is no (easy) way for a user to change it. So I would propose to make this configurable, similar to the delta parameter. If you agree, I can create a pull request.
Thanks.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Addressed in #1062. Thanks a ton @mvieth!
And thanks for looking into this, help on the drift module doesn’t go unnoticed 😃