BUG - SWAPI L3 job trigger start_date is wrong

[tech3371]

Description of the issue

Hi folks--

I'm looking at the SWAPI L3 coverage. We are only getting proton-sw and pui-he data on days that are the end of ephemeris_reconstructed coverage. These products are HARD deps on ephemeris_reconstructed, and if I'm reading the processing logs correctly, that last day is being passed into the job as the Start Date.

alpha-sw doesn't depend on the ephemeris and is executing fine.

Other dependencies on ephemeris_reconstructed seem to be HARD_NO_TRIGGER, except for idex l1b_sci-1week; mag l1d_norm-srf, l2_norm-srf, l2_burst-srf; ultra l1b_*sensor-de, l1c_*sensor-spacecraftpset, l1c_*sensor-heliopset. All of those have a HARD_NO_TRIGGER on the ephemeris_predicted, so it probably wouldn't be as obvious that they're not triggering on the reconstruct.

I'm still working on getting the go-ahead to process SWAPI with the predict, so maybe that will make this issue go away. But if it's something fixable that would be nice.

Notes: https://github.com/IMAP-Science-Operations-Center/imap_processing/issues/2736#issuecomment-3974613236

--
Jonathan Niehof, Ph.D.
UNH Space Science Center
106 Morse Hall, 8 College Rd., Durham, NH 03824
(603) 862-0649

Steps to reproduce the issue

No response

Expected vs Actual behavior

• determine correct start_date and pass it to the job

Code Snippet (If applicable)

Code

Additional notes, affected areas, and suggested fixes

No response