Skip to content

DetectSpikeBy(Ssa|Iid) confidence param should be double #4058

Closed

Description

@esso23

This one is pretty simple. Confidence parameter in DetectIidSpike & DetectSpikeBySsa should be of type double. It makes no sense that it is of type Int32 since it is being cast to double when creating SsaSpikeDetector.Options() anyway.

Same thing goes for DetectChangePointBySsa, DetectIidChangePoint and possibly others.

Right now it is not possible to search only for "extreme spikes" (confidence = ~99.9 or even more) using these extension methods.

Thanks
Esso

Activity

  1. esso23 commented on Sep 3, 2019

    @esso23
    ContributorAuthor

    I would recommend raising the priority to highest possible because this renders all the ChangePoint/Spike detection algorithms (almost) useless. We had to modify the ML.NET library and recompile it to be able to use them. We are regularly using confidences like 99.9999999 etc. 99.0 is just waaaay too low for many cases and produces unwanted outputs.
    Also, there is no workaround, as these extension methods are the only way how to call these algorithms, all other methods/classes are either private or internal.

  2. codemzs commented on Sep 3, 2019

    @codemzs
    Member

    @esso23 looking into it now

  3. self-assigned this
    on Sep 3, 2019
  4. esso23 commented on Feb 12, 2021

    @esso23
    ContributorAuthor

    Honesly I can't believe that such an important thing is still not fixed.
    This really makes the entire TimeSeries library unusable in so many real-world scenarios.

  5. ghost locked as resolved and limited conversation to collaborators on Mar 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions