You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes something bad (some drop or spike) happen shortly after another change and because it is too close to previous change. I think it would make sense to make it possible to handle results like this.
If the result is kept there, it will spoil average for follow-up results computation.
Describe the solution you'd like
Maybe it would be possible to allow to manually add a change?
The text was updated successfully, but these errors were encountered:
Maybe it would be possible to allow to manually add a change?
Hi @jhutar, if I am not wrong the changes are actually recomputed every time all datasets are recalculated therefore I am not sure that adding a change manually is actually possible in the current implemention.
Sometimes something bad (some drop or spike) happen shortly after another change and because it is too close to previous change
On the other hand, I don't know if this is something that can be takle tweaking the change detection configuration. Any thoughts @johnaohara@willr3 ?
Feature idea.
Sometimes something bad (some drop or spike) happen shortly after another change and because it is too close to previous change. I think it would make sense to make it possible to handle results like this.
If the result is kept there, it will spoil average for follow-up results computation.
Describe the solution you'd like
Maybe it would be possible to allow to manually add a change?
The text was updated successfully, but these errors were encountered: