|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Let my try to explain my point in a different way. By assuming that the numbers before the start of Jenkins were 0, Jenkins is making up data, and as a result, plotting wrong results.
To avoid that, instead of using 0 for the initial smoothed value, it should use the first unsmoothed value, or even better the average of the first couple of values
https://en.wikipedia.org/wiki/Exponential_smoothing#Choosing_the_initial_smoothed_value
Also, maybe it would be better to use a shorter time constant. This alone would help reducing the artifacts.
Using a different smoothing algorithm might also help. Exponential isn't good for spotting trends anyway.