Reverse anomaly / confirmed detection
Open
@FedericoCeratto is already working on this.
Since May 25, 2020.
discussion
feature
pipeline
- Dominant language
- Python
- Stars
- 61
- Forks
- 33
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
Currently we match fingerprints before detecting the anomaly status of a measurement. As the number of fingerprint increases this could become computationally intensive, especially due to fingerprints in ZZ with body string matching.
We can measure how many confirmed are not detected as anomaly. If the number is very low, we can then reverse the matching: first detect the anomaly status and then look for fprint matches only if anomaly=true
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.