Repository navigation
Description
Description of the issue
Several L2 products have a CDF type of CDF_INT8 for epoch attributes VALIDMAX, VALIDMIN, FILLVAL. These should be CDF_TIME_TT2000 (matching the variable). Apparently this was correct in release 1 and has since slipped. Files SPDF identified:
imap_codice_l2_hi-omni_20260429_v001.0008.cdf
imap_glows_l2_hist_20260429-repoint00233_v002.0036.cdf
imap_idex_l2a_sci-10days_20260430_v003.0020.cdf
imap_mag_l2_burst-dsrf_20260429_v002.0007.cdf
imap_mag_l2_burst-gse_20260429_v002.0007.cdf
imap_mag_l2_burst-gsm_20260429_v002.0007.cdf
imap_mag_l2_burst-rtn_20260429_v002.0007.cdf
imap_mag_l2_burst-srf_20260429_v002.0007.cdf
imap_mag_l2_norm-dsrf_20260429_v002.0008.cdf
imap_mag_l2_norm-gse_20260429_v002.0008.cdf
imap_mag_l2_norm-gsm_20260429_v002.0008.cdf
imap_mag_l2_norm-rtn_20260429_v002.0008.cdf
imap_mag_l2_norm-srf_20260429_v002.0008.cdf
imap_swe_l2_sci_20260429_v002.0004.cdf
It's not clear how this regressed.
The DELTAs (and attributes on them) should remain INT8, just for clarity.
Steps to reproduce the issue
No response
Expected vs Actual behavior
No response
Code Snippet (If applicable)
CodeAdditional notes, affected areas, and suggested fixes
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsValidating
Activity
leowerneck commentedon Oct 20, 2026
The issue was caused by lasp/cdflib#344. I opened lasp/cdflib#349 to address it. We will need to reprocess after it is merged.
Fix accidentally conversion
leowerneck commentedon Oct 20, 2026
Changed status to validating until we generate new data products that confirm the issue has been addressed.
leowerneck commentedon Oct 21, 2026
With #3581 merged, this is now back at the "validating" stage. I'm working on testing the new containers in dev and will post updates here.
leowerneck commentedon Oct 22, 2026
Tests on DEV worked. Holding off on reprocessing until after Data Release 2.