Skip to content

reporting: factor up defcon calculation#1581

Merged
leondz merged 2 commits intoNVIDIA:mainfrom
leondz:reporting/refactor_dc_calc
Feb 4, 2026
Merged

reporting: factor up defcon calculation#1581
leondz merged 2 commits intoNVIDIA:mainfrom
leondz:reporting/refactor_dc_calc

Conversation

@leondz
Copy link
Collaborator

@leondz leondz commented Jan 29, 2026

implement notes in #1579:

  • drop both calibration.defcon_and_comment() and report_digest.map_absolute_score() and have a single score-to-defcon map function referencing a boundary class from analyze.__init__

to avoid circular imports, esp. btw report_digest and calibration, the mapping fun is in __init__ (where the constants its used with are also found)

Also prune some dead/unaccessed code

@leondz leondz added the reporting Reporting, analysis, and other per-run result functions label Jan 29, 2026
Copy link
Collaborator

@erickgalinkin erickgalinkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would probably be good to have some kind of error handling in case an invalid enum isn't passed ("bounds doesn't have .TERRIBLE" or something) but otherwise LGTM.

@leondz
Copy link
Collaborator Author

leondz commented Feb 2, 2026

Yeah, I had a similar feeling. Maybe this can be expressed in a test

@leondz leondz merged commit f305388 into NVIDIA:main Feb 4, 2026
15 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

reporting Reporting, analysis, and other per-run result functions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants