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
How is the timestamp for configuration messages determined?
A couple of years ago I ran some tests where I started one of the tests on 2011-11-27 14:26 (GPS time).
Since I started the HiSPARC DAQ at that time a configuration message was generated and sent to the datastore. It can be seen here: http://data.hisparc.nl/api/station/94/config/2011/11/27/
The problem is the timestamp in the configuration is "2011-11-27 15:25" Which is offset by an hour.
The HiSPARC electronics does send a GPS timestamp with the configuration message (ID 42).
Perhaps the HiSPARC DAQ does not use that timestamp and simply adds its own using the local PC time.
The text was updated successfully, but these errors were encountered:
How is the timestamp for configuration messages determined?
A couple of years ago I ran some tests where I started one of the tests on 2011-11-27 14:26 (GPS time).
Since I started the HiSPARC DAQ at that time a configuration message was generated and sent to the datastore. It can be seen here:
http://data.hisparc.nl/api/station/94/config/2011/11/27/
The problem is the timestamp in the configuration is "2011-11-27 15:25" Which is offset by an hour.
The HiSPARC electronics does send a GPS timestamp with the configuration message (ID 42).
Perhaps the HiSPARC DAQ does not use that timestamp and simply adds its own using the local PC time.
The text was updated successfully, but these errors were encountered: