Skip to content

IDEX Update event time calculation#2664

Open
lacoak21 wants to merge 1 commit intoIMAP-Science-Operations-Center:devfrom
lacoak21:idex_l1a_epoch_calculation_updates
Open

IDEX Update event time calculation#2664
lacoak21 wants to merge 1 commit intoIMAP-Science-Operations-Center:devfrom
lacoak21:idex_l1a_epoch_calculation_updates

Conversation

@lacoak21
Copy link
Contributor

@lacoak21 lacoak21 commented Feb 3, 2026

Change Summary

Overview

The IDEX team realized they were using shcoarse for event time calculation. This was actually the time of the packet calculation and not the time when IDEX triggered.

I think @tech3371 you had this concern in the science team meeting a long time ago but I thought they said we were doing it right! Anyway this is the correct way to do it.

Updated Files

-imap_processing/idex/idex_l1a.py

  • Fix function to handle epoch calculation for science times using event trigger time variables instead of shcoarse and sfine. Continue to use shcoarse and sfine for housekeeping because they do not contain the other variables.

@lacoak21 lacoak21 added this to the January 2026 milestone Feb 3, 2026
@lacoak21 lacoak21 requested a review from tech3371 February 3, 2026 23:00
@lacoak21 lacoak21 self-assigned this Feb 3, 2026
@lacoak21 lacoak21 added this to IMAP Feb 3, 2026
@subagonsouth subagonsouth removed this from the January 2026 milestone Feb 5, 2026
return met_to_ttj2000ns(met)
if coarse_time_sec2 is not None:
# Reconstruct the total seconds from the two 16-bit words
coarse_event_time = 65536 * coarse_time_sec1 + coarse_time_sec2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am little curious why they want to multiply coarse second time with 65536. I have seen this number is CoDICE and they are doing this:

    center_times_seconds = (
        acq_start_seconds + acq_start_subseconds / 65536 + (delta_times / 1e9)
    )

Can you check with them if 65536 should be applied to fine_time_subs instead?

Copy link
Contributor

@tech3371 tech3371 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had one minor question to IDEX team but what you had is good.

p.s. yes, I remember that discussion and I thought I was way off based on response I got. I should have push back more :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants