Fix #404: Fix operator precedence in x0 LVLB weights and NaN assertion#406
Draft
Mr-Neutr0n wants to merge 1 commit into
Draft
Fix #404: Fix operator precedence in x0 LVLB weights and NaN assertion#406Mr-Neutr0n wants to merge 1 commit into
Mr-Neutr0n wants to merge 1 commit into
Conversation
…ssertion Signed-off-by: Mr-Neutr0n <64578610+Mr-Neutr0n@users.noreply.github.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
1 participant
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.
Fixes #404
Fixed operator precedence in lvlb_weights expression (line 163: added parentheses so
2. * (1 - alphas_cumprod)evaluates correctly instead of2.0 - alphas_cumprod) and changedassert ... .all()to.any()(line 169) so a single NaN triggers the assertion.No local test suite detected.
This change was prepared with AI assistance under human direction and review.