Fixed moving_price conversion from I96F32 to float#3010
Merged
thewhaleking merged 1 commit intoopentensor:stagingfrom Aug 11, 2025
Merged
Conversation
mcjkula
changed the title
moving_price conversion from I96F32 to float
thewhaleking
approved these changes
Aug 11, 2025
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
2 participants
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
SubnetMovingPricestorage usesI96F32format (32 fractional bits), but thecurrent
DynamicInfocallsfixed_to_float()formoving_pricewithout specifyingfractional bits, defaulting to 64 bits.
This causes
moving_pricevalues like 0.05 being incorrectly decoded as 0.00000000001.Related Issue: #3009 (comment)