You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we now have direct HARP-->ONIX synchronisation working, I wanted to add an ongoing issue regarding a discussion the ONIX team are having about how HARP timestamps are interpreted.
The gist is that ONIX reports its HARP input timestamps with a 1 second lag. This is because HARP sends its current time along with a timing signal which indicates when the next HARP second will start. Currently the ONIX hardware is agnostic to this and just reports the last received timestamp when it gets the timing signal. This can be easily corrected for in analysis by adding a second to the HARP timestamp.
The reason for adding this issue is as a reminder that in future if the added second is baked into the Bonsai interface and someone updates the package, it might throw synchronisation off by a second.
The text was updated successfully, but these errors were encountered:
As we now have direct HARP-->ONIX synchronisation working, I wanted to add an ongoing issue regarding a discussion the ONIX team are having about how HARP timestamps are interpreted.
The gist is that ONIX reports its HARP input timestamps with a 1 second lag. This is because HARP sends its current time along with a timing signal which indicates when the next HARP second will start. Currently the ONIX hardware is agnostic to this and just reports the last received timestamp when it gets the timing signal. This can be easily corrected for in analysis by adding a second to the HARP timestamp.
The reason for adding this issue is as a reminder that in future if the added second is baked into the Bonsai interface and someone updates the package, it might throw synchronisation off by a second.
The text was updated successfully, but these errors were encountered: