Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GPMF STMP semantics #189

Open
bradh opened this issue Mar 18, 2024 · 1 comment
Open

GPMF STMP semantics #189

bradh opened this issue Mar 18, 2024 · 1 comment

Comments

@bradh
Copy link
Contributor

bradh commented Mar 18, 2024

I'm trying to add "as good as reasonably practical" TAI time stamping - eventually per frame, but for now on each (declared) sync sample. I'm using GPS9 to derive millisecond precision time from day number and millis, adjusting for TAI offset, and then for the difference between CORI and GPS9 values for STMP. So absolute accuracy is never greater than 1ms, but the frame-to-frame timing might be.

Both CORI and GPS9 will repeat, and since GPS9 is not frame synchronous, they might not have the same number of entries in each GPMF chunk - the difference in STMP could potentially be positive or negative, depending on when the sampling happened.

Questions:

Should STMP always be for the first item in the array?

Is the CORI timestamp intended to represent "start of frame", "end of frame" or "sometime during the frame"? I'd like to represent start of frame, so potentially I can adjust using the SHUT value, if needed.

@dnewman-gpsw
Copy link
Collaborator

STMP is the for arrival time of the first sample in the payload.
CORI timestamp is the "start of frame"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants