Repository navigation
unixTime #1269
Description
Prior the recent #1263 , RUN::config.unixTime was being cached across events unless nonzero in EVIO, which was not nice for multi-threading the decoder. But now we likely have many events with unixTime=0, as that was apparently an old DAQ "fix"!
We may want to revert to the previous non-reproducible situation, or reassign unix time in post-processing.
Activity
baltzell commentedon May 18, 2026
What depends on unix time?
baltzell commentedon May 20, 2026
Looks like it's probably at the CODA block level; the first event in each block contains valid unix time.