Skip to content
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

Open
xiaoya-yaya opened this issue Jun 1, 2021 · 5 comments
Open

[Metrics] Common Metrics - Burstiness #572

xiaoya-yaya opened this issue Jun 1, 2021 · 5 comments
Labels
waiting for author need issue author's feedback

Comments

@xiaoya-yaya
Copy link
Member

Description:

  • Short timeframes of intense activity, followed by a corresponding return to a typical pattern of activity, observed in a project.
  • Burstiness is a way of understanding the cycle of activity in existing metrics, like issues, merge requests, mailing lists, commits, or comments.

Filters

  • Stars
  • Forks
  • Issues or bug reports
  • Labels
  • Downloads
  • Release Tags
  • Change Requests
  • Documentation additions or revisions
  • New Repositories
  • Feature Requests

Instances of Implementation
image
image

Resource

@open-digger-bot
Copy link
Contributor

This issue has not been replied for 24 hours, please pay attention to this issue: @sunshinemingo @wengzhenjie

@xiaoya-yaya xiaoya-yaya changed the title [Metrics] Burstiness [Metrics] Common Metrics - Burstiness Jun 13, 2021
@frank-zsy
Copy link
Contributor

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

@github-actions github-actions bot added the waiting for author need issue author's feedback label Jan 18, 2023
@xiaoya-yaya
Copy link
Member Author

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 scipy have signal.find_peaks() function to identify peaks in curves.

@github-actions github-actions bot added waiting for repliers need other's feedback and removed waiting for author need issue author's feedback labels Jan 18, 2023
@frank-zsy
Copy link
Contributor

Thanks for the input, I found a blog about scipy.signal.find_peaks and it gives a corresponding JavaScript implementation.

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.

@github-actions github-actions bot added waiting for author need issue author's feedback and removed waiting for repliers need other's feedback labels Jan 18, 2023
@birdflyi
Copy link
Contributor

I am quite curious about the predictability of those signal features:

  • the max values or relative ratio sequence of peaks,
  • the interval sequence of peaks,
  • parameter ratio of fractal if fractal exists.

Is there any set of metrics exists like this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for author need issue author's feedback
Projects
None yet
Development

No branches or pull requests

3 participants