Skip to content

Codice l2 hi sectored dim reversal#2778

Open
lacoak21 wants to merge 2 commits intoIMAP-Science-Operations-Center:devfrom
lacoak21:codice_l2_hi_sectored_dim_reversal
Open

Codice l2 hi sectored dim reversal#2778
lacoak21 wants to merge 2 commits intoIMAP-Science-Operations-Center:devfrom
lacoak21:codice_l2_hi_sectored_dim_reversal

Conversation

@lacoak21
Copy link
Contributor

Change Summary

Overview

Michael realized that the CoDICE hi l2 sectored data had the spin_angle array transposed. The dimensions were elevation_angle by spin sector but they should have been reversed. This PR fixes them.

File changes

imap_processing/codice/codice_l2.py

Transpose array

@lacoak21 lacoak21 added this to the February 2026 milestone Feb 26, 2026
@lacoak21 lacoak21 requested a review from tech3371 February 26, 2026 17:11
@lacoak21 lacoak21 added this to IMAP Feb 26, 2026
@@ -1078,7 +1078,9 @@ def process_hi_sectored(dependencies: ProcessingInputCollection) -> xr.Dataset:
spin_angle = (L2_HI_SECTORED_ANGLE[:, np.newaxis] + elevation_angles) % 360.0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tech3371 Im honestly still pretty confused about this. From my understanding:
This (L2_HI_SECTORED_ANGLE[np.newaxis, :] + elevation_angles) % 360.0 already creates an array that is spin_sector by elevation angle. Unless the variable names are mismatched? I have no understanding of l2 hi sectored code so I was wondering if this change made sense to you? Michael confirmed that the transpose was needed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will look into the details. It's been a while for me and I can look into where we should update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants