CoDICE L3 flight data validation (Phase D)

[jtniehof]

These products were Phase D priorities:

• l3a_lo-partial-densities: runs. Initial instrument team check
  • SDC reprocessing L2 for correct efficiency, which will mean hplus needs to be rechecked
  • SwRI reprocessing validation files to check on fill
  • Scaling changes requested (CoDICE l3a lo-partial-densities: change scaling per Michael feedback imap_L3_processing#71)
• l3a_lo-sw-ratios: running normally, no instrument team requests
• l3a_lo-sw-charge-state-distributions: running normally, no instrument team requests
• l3b_hi-pitch-angle: issue with L2 (BUG - CoDICE L2 Hi-sectored spin_angles dimension and data mismatched #2792, CoDICE: Hi-sectored dimension bug #2865) fixed, need to recheck

These products were deferred from Phase D priority, but were developed "as time allowed" during Phase D, particularly towards the end:

• l3a_lo-direct-events: running, mostly match
  • Some places with fill where SwRI calcuation is non-fill, investigating
  • Some mismatches on normalization, investigating
  • New variables requested (CoDICE Lo L3 DE: more variable carry-through (Phase D deferred) imap_L3_processing#72)
• l3a_lo-3d-distribution: running except for He++, but algorithms need to be updated (current output is not physical)
• l3a_hi-direct-events: running, Initial instrument team check
  • Additional variables requested: CoDICE Hi L3 DE: variable carry-through (Phase D deferred) imap_L3_processing#73
  • Mass correction pending: CoDICE Hi L3 DE: mass correction (Phase D deferred) imap_L3_processing#74

Container last deployed 3/30

[jtniehof]

l3b_hi-pitch angle looks vaguely credible, but we're using a linear scale for the intensity. Probably should be log and have scalemin/scalemax populated.

l2_hi-sectored-intensity probably needs an update (spin_angle array was transposed) which will affect this product.

[jtniehof]

l3a_hi-direct-events chunk check, using imap_codice_l3a_hi-direct-events_20260118_v001.cdf

mass estimate has SCALEMIN/SCALEMAX 0.1-100. Priority index 2 has masses of around 1e-4. Index 4 is 1 to 2 ish. Index 5 is heavy (up to ~9). 0, 1, 3 are all fill.

priority_index_label is just 0-5. If there are expected mass groups we should probably put name/description in here.

ssd_energy is around 1 MeV in priority 4. Should this be a log scale? It's linear.

energy_per_nuc is exactly 13.385 MeV/nuc for all priority 2 events. I'm guessing we don't expect this to be meaningful given the mass estimate. priority 4 is around .3-1 ish MeV/nuc. Again, this is on a linear scale.

[jtniehof]

CoDICE team was queried regarding ancillary files on 1/29, replied 2/11 and I dropped the ball, request in 2/27 for proper handling of these uploads.

[jtniehof]

Uploaded:

imap_codice_lo-energy-per-charge_20241110_v001.csv
imap_codice_mass-coefficient-lookup_20241110_v003.csv
imap_codice_mass-per-charge_20241110_v003.csv

l3a_lo-partial-densities triggered but failed.
l3a_lo-direct-events did not run (there are no l2 inputs)

More fun for next week...