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
We currently do outlier detection to remove occasional bad pulses. But that is occasionally insufficient in the presence of bad hardware. You can see this when testing loss of carrier for #9.
We should have an additional layer of defense against bad pulses. If we have had some pulses wherever everything is properly in sync, and then we start getting huge offsets, we should ignore them based on the time between the good offset and the bad offset. For example, if the last good offset was hours ago, then our clock could be off by quite a lot; but if the last good offset was just a minute ago, the clock can't be off by very much. The maximum offset should be some fraction of elapsed period since the last good offset.
The text was updated successfully, but these errors were encountered:
This approach assumes that the PHC is working properly and something has happened to the GPS. But if something went wrong with the PHC, then this will stop the PHC being corrected. In fact that is what happens during loss of carrier on the CM4: the hardware clock runs very fast.
We currently do outlier detection to remove occasional bad pulses. But that is occasionally insufficient in the presence of bad hardware. You can see this when testing loss of carrier for #9.
We should have an additional layer of defense against bad pulses. If we have had some pulses wherever everything is properly in sync, and then we start getting huge offsets, we should ignore them based on the time between the good offset and the bad offset. For example, if the last good offset was hours ago, then our clock could be off by quite a lot; but if the last good offset was just a minute ago, the clock can't be off by very much. The maximum offset should be some fraction of elapsed period since the last good offset.
The text was updated successfully, but these errors were encountered: