Hacker News new | past | comments | ask | show | jobs | submit login

Why are you trying to sync systems that use leap seconds and ones that don't? It sounds like you've invented your own time system.



Time aligning GPS data with other sensors/systems that record in UTC. I'm combining data from multiple different sources together that I do not control. The duration of the data is long enough that an occasional leap second slips in and offsets things.


So, you just need to set up a scheduled task to download the leap seconds file from the IERS once every six months?


The codebase does pretty much exactly that, yes. Still causes the occasional hiccup though when new data is inevitably not labelled appropriately.

Not exactly the kind of thing that causes catastrophic failure. More so the kind of thing that periodically pops up to be annoying.


Ok, so it's not "keeping them in sync" as you stated in your first post, it's not a "leap second sneaking in" as in your second post. Now it is somehow data that is not labeled, and only becomes a problem during leap seconds. I'm sure you can see how changing your story and lack of details would make someone skeptical that the problem even exists.

If there really is a problem I'm really interested in hearing what it is. But it doesn't sound like you plan to be straight forward about explaining it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: