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

Include information about why detectors are skipped #1061

Open
erickgalinkin opened this issue Jan 7, 2025 · 0 comments
Open

Include information about why detectors are skipped #1061

erickgalinkin opened this issue Jan 7, 2025 · 0 comments
Assignees
@erickgalinkin
Labels
detectors work on code that inherits from or manages Detector quality-accuracy This affects result quality/reliability reporting Reporting, analysis, and other per-run result functions ux Interface & interaction improvements
Milestone
25.02 Efficiency

Comments

@erickgalinkin
Copy link
Collaborator

Summary

Detectors are sometimes skipped, but there are several reasons this can happen. We do not provide much direct information that helps people understand why the detector is skipped. We should log information that allows users to understand why a detector was skipped e.g. there were no responses
@erickgalinkin erickgalinkin added detectors work on code that inherits from or manages Detector quality-accuracy This affects result quality/reliability reporting Reporting, analysis, and other per-run result functions ux Interface & interaction improvements labels Jan 7, 2025
@erickgalinkin erickgalinkin added this to the 25.02 Efficiency milestone Jan 8, 2025
@erickgalinkin erickgalinkin self-assigned this Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@erickgalinkin erickgalinkin

Labels
detectors work on code that inherits from or manages Detector quality-accuracy This affects result quality/reliability reporting Reporting, analysis, and other per-run result functions ux Interface & interaction improvements
Projects
None yet
Milestone
25.02 Efficiency
Development

No branches or pull requests
1 participant
@erickgalinkin