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.

Sign up for GitHub

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

Jump to bottom

Difference between no anomaly found and not able to assign pairs of anomalies #3

Open
Krannich479 opened this issue Jan 17, 2023 · 1 comment
Open

Difference between no anomaly found and not able to assign pairs of anomalies #3

Krannich479 opened this issue Jan 17, 2023 · 1 comment
Assignees
@Krannich479
Labels
enhancement New feature or request

Comments

@Krannich479
Copy link
Collaborator

At the moment there is no distinction between no signal found and too many signals found. If there are more signal anomalies found than the algorithm can pair then this looks just like these are no signals at all in the report. An ad hoc fix until there is a better pairing mechanism is just to better distinguish this these different situations in the std::out.
@Krannich479 Krannich479 added the enhancement New feature or request label Jan 20, 2023
@Krannich479
Copy link
Collaborator Author

Since PR #4 there is at least a feedback to stdout

@Krannich479 Krannich479 self-assigned this Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Krannich479 Krannich479

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Krannich479