Ultra ena rates l1b#2386
Merged
lacoak21 merged 2 commits intoIMAP-Science-Operations-Center:devfrom Nov 6, 2025
Merged
Conversation
laspsandoval
approved these changes
Nov 6, 2025
Contributor
laspsandoval
left a comment
There was a problem hiding this comment.
Thanks for doing this Luisa.
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.
Change Summary
Overview
The spin edges were getting converted to uint16. This was causing the spins to roll over when it reached the max uint16 val. This was causing ena_rates to be an array of zeros because none of the spins were within the spin_edges.
unconverted spins [140309 140310 140311 ... 146033 146034 146035] converted spins [ 9237 9238 9239 ... 14961 14962 14963]This was a remanent of when the spin_number was uint8. @laspsandoval helped me confirm this was the correct way to fix this issue.
Updated Files