-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Metrics] Common Metrics - Burstiness #572
Comments
This issue has not been replied for 24 hours, please pay attention to this issue: @sunshinemingo @wengzhenjie |
I can not see what to implement in this metric, the charts just show the event count and the burstiness is just a sense of the smoothness of the charts, is it right? @xiaoya-yaya |
I think this metric provides a perspective for maintainers to observe: to find the peaks of the number of commits, comments, downloads, forks, etc, and then to find connections of facts that are related to the burstiness (release, meetups, etc). The observation could be just based on the observer's sense, at least CHAOSS didn't provide specific methods. However, there are some peak detection methods integrated into python or javascript packages. I know |
Thanks for the input, I found a blog about According to the blog, I think peak detection can be a serious research problem and there are several parameters in the function, so if we want to implement this metric, we may need to look into the peak detection algorithm more carefully. But it is truly a good metric to build a monitor-and-alert system for other metrics. |
I am quite curious about the predictability of those signal features:
Is there any set of metrics exists like this? |
Description:
Filters
Instances of Implementation
Resource
The text was updated successfully, but these errors were encountered: