On Wed, 2016-12-28 at 14:01 +0800, Sanjeev Gupta wrote: > > On Tue, Dec 27, 2016 at 11:36 PM, John Sauter <John_Sauter@systemeyes > computerstore.com> wrote: > > > Also note that many large radar systems have built-in simulators, > > > used > > > for system integration during development and for training > > > thereafter. > > > Such simulators need to be able to work using system time that is > > > not > > > the present, say to rerun recorded observations or to simulate > > > future > > > or past scenarios. In both cases, the GPS receiver does not know > > > the > > > correct leap second offset to use. The usual solution is an > > > application-provided table all past leap seconds, plus the next > > leap > > > second (if known). The table is updated manually. > > > > That sounds like a fine solution. It would be nice if the table > > were > > maintained by the group of people who needed it, so that everyone > > wouldn't have to update his own table. > > > > If I have understood you correctly, this is publicly available, based > on the IERS Bulletin C: > > https://www.ietf.org/timezones/data/leap-seconds.list > > -- > Sanjeev Gupta > +65 98551208 http://www.linkedin.com/in/ghane
You have understood me correctly; I was assuming that the radar systems
did not use the NTP format for their leap seconds file.
John Sauter ([email protected])
--
PGP fingerprint E24A D25B E5FE 4914 A603 49EC 7030 3EA1 9A0B 511E
signature.asc
Description: This is a digitally signed message part
_______________________________________________ LEAPSECS mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/leapsecs
