Keep heterogeneous evaluation result columns aligned - #4281
Closed
FlorianPfaff wants to merge 17 commits into
Closed
Keep heterogeneous evaluation result columns aligned#4281FlorianPfaff wants to merge 17 commits into
FlorianPfaff wants to merge 17 commits into
Conversation
Contributor
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
FlorianPfaff
force-pushed
the
agent/align-heterogeneous-evaluation-results
branch
from
July 13, 2026 16:38
f0ac388 to
5f8b7c9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Nonefor earlier rowsNonewhen a later row omits a previously seen fieldBug
group_results_by_filter()assumed that every row for a filter contained exactly the same keys. When a later configuration introduced an optional metric, the function indexed a column that had never been initialized and raisedKeyError. When a later configuration omitted a metric, the corresponding list was not extended, so grouped columns represented different numbers of rows and no longer aligned by parameter.Impact
Evaluation and plotting code can now safely consume summaries whose configurations expose different optional metrics. Every grouped column contains exactly one value per sorted row, using
Nonefor unavailable values.Validation
Noneparameter ordering remains unchangedmain; only the grouping helper and its focused test are modifiedA full repository test run was not available in this environment because the checkout could not be downloaded; repository access was provided through the GitHub connector.