CoDICE: add data padding to daily files

[tech3371]

This ticket is related to what Michael (from CoDICE team )noticed during validation. He noticed that CoDICE had little bit of extra data in the daily files due to a 'full' data spanning across daily day boundary.

Action items

• Should SDC do same?
• Which products and at what level will this change effect?

[mstarkey2158]

CoDICE team identifies this as a BLOCKER for upcoming data release

[tech3371]

@mstarkey2158 Can you add some details for questions I posted in the ticket description? Mainly to understand why this is was needed.

[mstarkey2158]

1. The SDC files seem to have epochs that correspond to days other than the day in the filename. This typically occurs at the beginning of the day. For example, if the file date is 20260402, then the first epoch value in the file tends to correspond to the last few minutes of 20260401 (i.e.., '2026-04-01/23:58:00'). At the same time, the last epoch provided in the SDC file is not the last epoch of that particular day. For 4-min data, the last epoch is something like '20260402/23:54:00'. Instead, the last epoch of that day (i.e., '20260402/23:58:00') is included in the cdf file for the following day - 20260403.
2. The other issue regarding the timing is that since the cdf ifle times are based on the packet time. If a given packet is produced onboard very close to the boundary of a day, then the following (or previous) packet could be time-stamped with a different day due to the processing time required to produce and time stamp each packet. This was observed for the lo_sw/nsw-priority packets, where one of the packets was assigned to a different day than the other. The result is that the sw/nsw-priority cdfs would then have a different number of epochs, however, the data contained in those files was taken at the same time and so the epochs should agree.