Skip to content

fix(codice): mark Lo RGFO/NSO vars as support_data#3292

Merged
tech3371 merged 1 commit into
IMAP-Science-Operations-Center:devfrom
davidt0x:fix/issue-2798-codice-lo-support-vars
Jun 9, 2026
Merged

fix(codice): mark Lo RGFO/NSO vars as support_data#3292
tech3371 merged 1 commit into
IMAP-Science-Operations-Center:devfrom
davidt0x:fix/issue-2798-codice-lo-support-vars

Conversation

@davidt0x

@davidt0x davidt0x commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • mark the CoDICE Lo rgfo_* and nso_* telemetry state variables as support_data instead of data
  • add written-CDF regression checks for the Lo direct-events L1A and L2 products

Why

Issue #2798 called out that these variables are supporting telemetry state, not science data. They were still defined with VAR_TYPE = data in the CoDICE L1A attrs YAML, which also affected the Lo direct-events metadata carried forward into L2.

Validation

  • ./.venv/bin/python -m pytest -q imap_processing/tests/codice/test_codice_l1a.py
  • ./.venv/bin/python -m pytest -q imap_processing/tests/codice/test_codice_l2.py

Fixes #2798

Issue IMAP-Science-Operations-Center#2798 called out that these CoDICE Lo variables are not science data and should not be written with VAR_TYPE=data:

rgfo_half_spin\nrgfo_spin_sector\nrgfo_esa_step\nnso_half_spin\nnso_spin_sector\nnso_esa_step

Update the L1A attribute definitions to mark those variables as support_data, which also fixes the Lo direct-event L2 file for the NSO variables that are carried forward from L1A. Add written-CDF regression checks for both the Lo direct-event L1A file and the Lo direct-event L2 file.
@davidt0x davidt0x marked this pull request as ready for review June 8, 2026 17:03
@davidt0x davidt0x requested a review from tech3371 June 9, 2026 03:49
@tech3371 tech3371 merged commit fa4de7a into IMAP-Science-Operations-Center:dev Jun 9, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CoDICE L2 metadata work

2 participants