Repository navigation
CHANGELOG: log the six changes that landed since v0.5.1 - #12
Merged
Merged
Conversation
The Unreleased section still said "Nothing yet. Add user-visible changes here as they land", while six PRs had landed: #7, #10, #6, #8, #9 and #11. Two of them change output and say so in bold, because someone holding results from v0.5.1 is affected: HDx estimates differ now that raw features are binned on their own scale, and the one-vs-rest path returns a uniform vector instead of all-zeros where every class used to clip to zero. The MLPE change is cost only and the entry says the estimate is unchanged. The Tests entry says ten of the thirteen new tests fail on v0.5.1, not all thirteen: the three parametrized cv cases already passed and guard against regression rather than capturing the bug. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The
## [Unreleased]section still said:Six PRs had landed since v0.5.1: #7, #10, #6, #8, #9 and #11. This writes them up, following the section layout the v0.5.0 entry uses.
Fixed
Two of the three change output, and the entries say so in bold, because anyone holding results from v0.5.1 is affected:
HDxnow bins raw features on their own scale. On a 6-feature problem it used to return 0.637, 0.632 and 0.708 for true prevalences of 0.1, 0.5 and 0.9 — close to a constant predictor — and now returns 0.097, 0.486 and 0.842. (HDx: bin raw features on their own scale #9)CDE200/200,MS61,MS258,TAC11,MAX10,ACC6,HDy5,T503,X1. (Never return a zero-sum prevalence vector from the one-vs-rest path #10)MLPEis cost only — six estimator fits and fivepredict_probacalls become one of each,fittime over four datasets falls from 1.3037 s to 0.2190 s, and the entry states that the estimate is unchanged. (MLPE: fit the estimator once instead of cross-validating it #6)Documentation, Internal, Tests
The
CDEsensitivity note and its corrected citation (#8), thebin_edgesparameter entry (#11), theMLPEParameters section (#6), and the 3.9 job moving toubuntu-22.04(#7).The Tests entry says ten of the thirteen new tests fail on v0.5.1, not all thirteen. The three parametrized
cvcases already passed there, so they guard against regression rather than capturing the bug — checked by running the new tests against the unpatched code.Not included
The compare links at the foot of the file still point at
github.com/luizfernandolj/mlquantifyrather thancoenlab/mlquantify. GitHub redirects transferred repositories, so they resolve, and fixing them is unrelated to logging these changes — left for its own change.Markdown only; no code and no behaviour change.
🤖 Generated with Claude Code