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

Add ability to use system time for timestamps #3

Open
cboulay opened this issue Jan 29, 2024 · 0 comments
Open

Add ability to use system time for timestamps #3

cboulay opened this issue Jan 29, 2024 · 0 comments

Comments

@cboulay
Copy link
Collaborator

cboulay commented Jan 29, 2024

  • Currently SpikeEvent.timestamp is a float but the Blackrock hardware uses int64.
  • Legacy NSP's timestamp field is sample-counts since last reset (30,000 Hz)
  • Gemini timestamp field is PTP time in nanoseconds
  • Most other ezmsg signals / events use system time (time.time()).

We should have a background thread that synchronizes system clock with the hardware clock. This might amount to registering a callback for the heartbeat packets and noting their arrival time, and keeping an SGD regression between the pairs of timestamps.

The clock sync probably only needs to be updated every ~5 seconds.

This was referenced Jan 29, 2024
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

1 participant