BUG - GLOWS imap_start_time is off

[maxinelasp]

Description of the issue

Per validation document - in some cases, the imap_start_time is offset by 1 second.

In CDF file:
output/data/imap/glows/l1a/2026/04/imap_glows_l1a_hist_20260415-repoint00001_v002.cdf

first_spin_id JSON VALUE CDF VALUE
7210318 {'seconds': 513958088, 'subseconds': 0} 513958089.0
7210326 {'seconds': 513958208, 'subseconds': 0} 513958209.0
7210334 {'seconds': 513958328, 'subseconds': 0} 513958329.0

Per Marek:
"Time-related variables at L1 like, e.g., glows_start_time, imap_start_time should be computed and copied to CDFs without corrections for IMAP clock drift and/or leap seconds. Only epoch, ‘unique_block_identifier’, and ‘unique identifier’ should be corrected."

Steps to reproduce the issue

No response

Expected behavior (What should happen)

No response

Actual behavior (What does happen)

No response

Code Snippet:

Code

Additional notes, affected areas, and suggested fixes

No response