GPS Forums


Reply
Thread Tools Display Modes

Three more years of leap seconds...

 
 
Alan Browne
Guest
Posts: n/a
 
      01-24-2012, 01:29 PM
On 2012-01-24 08:42 , Peter H. Coffin wrote:
> On Mon, 23 Jan 2012 13:00:08 -0800, Wolfgang S. Rupprecht wrote:
>> What I find so frustrating about the whole situation is that this is
>> simply another case of daylight-savings-time. Real computers (read
>> anything but the MS crap), already use seconds since some arbitrary
>> epoch to measure time. The timezone and DST corrections are added by
>> the display routines when the time is presented to the humans. It is
>> amazing (and frustrating) that leap seconds aren't accounted for in this
>> manner too. If one needs to display the time one could just as easily
>> do as GPS systems do and add the accumulated leap seconds in the display
>> routines and internally use a linearly incrementing clock that adds one
>> second per second.

>
> It *shouldn't* cause problems. The NTP protocol datagram has indicators
> that account for leap seconds, which should be telling the recieving
> system "account for this if you haven't already". The actual number of
> seconds in the timestamp isn't itself adjusted, but the indicator is to
> keep the OUTPUT display properly calibrated if it hasn't been informed
> to otherwise."


Wolfgang is more worried about derivative products of the "time"
changing. "Shouldn't" means a programmer _accounted_ for it. Laziness,
budget, ignorance, laissez-faire attitudes (not to mention those who
deem the problem as non-problematic) mean there are oodles of code out
there that don't account for it and that might cause transient issues in
some systems.




--
"We demand rigidly defined areas of doubt and uncertainty."
Douglas Adams - (Could have been a GPS engineer).
 
Reply With Quote
 
 
 
 
oriel36
Guest
Posts: n/a
 
      01-24-2012, 03:39 PM
On Jan 24, 2:26*pm, Alan Browne <alan.bro...@FreelunchVideotron.ca>
wrote:
> On 2012-01-24 02:13 , Sam Wormley wrote:
>
> > Apologies to all for this off topic essay in this leap second
> > thread. -Sam
> >> There is a fellow who lives somewhere in Scotland, named Gerald
> >> Kelleher, who has the annoying habit of interrupting threads on

>
> 1. Trolls are easy to identify as in the recent case.
> 2. Trolls eat, drink and breathe replies.
> 3. Trolls are starved when ignored.
>
> --
> "We demand rigidly defined areas of doubt and uncertainty."
> Douglas Adams - (Could have been a GPS engineer).


Ah,you are basically high tech Peeking Toms and not innovators,in the
end it means that far from being brilliant men,you will simply be the
'leap generation',the dumbest people who had satellites and couldn't
use them properly.

I wasn't appealing to anyone here,I was showing them their fate.
 
Reply With Quote
 
Wolfgang S. Rupprecht
Guest
Posts: n/a
 
      01-24-2012, 03:40 PM

"Peter H. Coffin" <(E-Mail Removed)> writes:
> On Mon, 23 Jan 2012 13:00:08 -0800, Wolfgang S. Rupprecht wrote:
>> What I find so frustrating about the whole situation is that this is
>> simply another case of daylight-savings-time. Real computers (read
>> anything but the MS crap), already use seconds since some arbitrary
>> epoch to measure time. The timezone and DST corrections are added by
>> the display routines when the time is presented to the humans. It is
>> amazing (and frustrating) that leap seconds aren't accounted for in this
>> manner too. If one needs to display the time one could just as easily
>> do as GPS systems do and add the accumulated leap seconds in the display
>> routines and internally use a linearly incrementing clock that adds one
>> second per second.

>
> It *shouldn't* cause problems. The NTP protocol datagram has indicators
> that account for leap seconds, which should be telling the recieving
> system "account for this if you haven't already". The actual number of
> seconds in the timestamp isn't itself adjusted, but the indicator is to
> keep the OUTPUT display properly calibrated if it hasn't been informed
> to otherwise."


I understand that the NTP on the wire protocol does give a heads up like
that. The problem seems to be that the code in the kernels often has a
hard time jumping the time without upsetting the various frequency/phase
locked loops. It is a tricky business that could be avoided if the leap
seconds were pushed into the time-and-date conversion routines.

-wolfgang
--
g+: https://plus.google.com/114566345864337108516/about
 
Reply With Quote
 
Wolfgang S. Rupprecht
Guest
Posts: n/a
 
      01-24-2012, 03:42 PM

Alan Browne <(E-Mail Removed)> writes:
> Wolfgang is more worried about derivative products of the "time"
> changing. "Shouldn't" means a programmer _accounted_ for it.
> Laziness, budget, ignorance, laissez-faire attitudes (not to mention
> those who deem the problem as non-problematic) mean there are oodles
> of code out there that don't account for it and that might cause
> transient issues in some systems.


Yup. Plus the fact that something that happens once every 18 months
probably isn't going to get all that much testing.

-wolfgang
--
g+: https://plus.google.com/114566345864337108516/about
 
Reply With Quote
 
Alan Browne
Guest
Posts: n/a
 
      01-24-2012, 03:50 PM
On 2012-01-24 11:42 , Wolfgang S. Rupprecht wrote:
>
> Alan Browne<(E-Mail Removed)> writes:
>> Wolfgang is more worried about derivative products of the "time"
>> changing. "Shouldn't" means a programmer _accounted_ for it.
>> Laziness, budget, ignorance, laissez-faire attitudes (not to mention
>> those who deem the problem as non-problematic) mean there are oodles
>> of code out there that don't account for it and that might cause
>> transient issues in some systems.

>
> Yup. Plus the fact that something that happens once every 18 months
> probably isn't going to get all that much testing.


Events can be simulated in testing code. I wrote a lot of code to
simply inject data into other code/computers to see if they processed
properly and handled out of range, anomalies, flags, etc. properly.

I'd bet a lot of programmers look at the issue and determine the effect
to be non-damaging or that the user can tolerate or work-around.

--
"We demand rigidly defined areas of doubt and uncertainty."
Douglas Adams - (Could have been a GPS engineer).
 
Reply With Quote
 
J. J. Lodder
Guest
Posts: n/a
 
      01-25-2012, 09:31 AM
Alan Browne <(E-Mail Removed)> wrote:

> On 2012-01-24 08:42 , Peter H. Coffin wrote:
> > On Mon, 23 Jan 2012 13:00:08 -0800, Wolfgang S. Rupprecht wrote:
> >> What I find so frustrating about the whole situation is that this is
> >> simply another case of daylight-savings-time. Real computers (read
> >> anything but the MS crap), already use seconds since some arbitrary
> >> epoch to measure time. The timezone and DST corrections are added by
> >> the display routines when the time is presented to the humans. It is
> >> amazing (and frustrating) that leap seconds aren't accounted for in this
> >> manner too. If one needs to display the time one could just as easily
> >> do as GPS systems do and add the accumulated leap seconds in the display
> >> routines and internally use a linearly incrementing clock that adds one
> >> second per second.

> >
> > It *shouldn't* cause problems. The NTP protocol datagram has indicators
> > that account for leap seconds, which should be telling the recieving
> > system "account for this if you haven't already". The actual number of
> > seconds in the timestamp isn't itself adjusted, but the indicator is to
> > keep the OUTPUT display properly calibrated if it hasn't been informed
> > to otherwise."

>
> Wolfgang is more worried about derivative products of the "time"
> changing. "Shouldn't" means a programmer _accounted_ for it. Laziness,
> budget, ignorance, laissez-faire attitudes (not to mention those who
> deem the problem as non-problematic) mean there are oodles of code out
> there that don't account for it and that might cause transient issues in
> some systems.


Sounds like a good reason for keeping leap seconds.
The Y2K misery cleared out a lot of programming rubbish too.

I still see nothing here beyond:
We are incompetent, so the rest of the world must adapt to us,

Jan
 
Reply With Quote
 
oriel36
Guest
Posts: n/a
 
      01-25-2012, 10:50 AM
On Jan 25, 10:31*am, nos...@de-ster.demon.nl (J. J. Lodder) wrote:
> Alan Browne <alan.bro...@FreelunchVideotron.ca> wrote:
> > On 2012-01-24 08:42 , Peter H. Coffin wrote:
> > > On Mon, 23 Jan 2012 13:00:08 -0800, Wolfgang S. Rupprecht wrote:
> > >> What I find so frustrating about the whole situation is that this is
> > >> simply another case of daylight-savings-time. *Real computers (read
> > >> anything but the MS crap), already use seconds since some arbitrary
> > >> epoch to measure time. *The timezone and DST corrections are addedby
> > >> the display routines when the time is presented to the humans. *Itis
> > >> amazing (and frustrating) that leap seconds aren't accounted for in this
> > >> manner too. *If one needs to display the time one could just as easily
> > >> do as GPS systems do and add the accumulated leap seconds in the display
> > >> routines and internally use a linearly incrementing clock that adds one
> > >> second per second.

>
> > > It *shouldn't* cause problems. The NTP protocol datagram has indicators
> > > that account for leap seconds, which should be telling the recieving
> > > system "account for this if you haven't already". The actual number of
> > > seconds in the timestamp isn't itself adjusted, but the indicator is to
> > > keep the OUTPUT display properly calibrated if it hasn't been informed
> > > to otherwise."

>
> > Wolfgang is more worried about derivative products of the "time"
> > changing. *"Shouldn't" means a programmer _accounted_ for it. *Laziness,
> > budget, ignorance, laissez-faire attitudes (not to mention those who
> > deem the problem as non-problematic) mean there are oodles of code out
> > there that don't account for it and that might cause transient issues in
> > some systems.

>
> Sounds like a good reason for keeping leap seconds.
> The Y2K misery cleared out a lot of programming rubbish too.
>
> I still see nothing here beyond:
> We are incompetent, so the rest of the world must adapt to us,
>
> Jan


Of course you are incompetent but that is by choice and if you are all
so stupid to follow a system based on a continuous string of 24 hour
days in a 365/366 format and still conclude stellar circumpolar motion
equates to daily rotation,no wonder your fate will be similar to the
scientists who couldn't come to terms with the Piltdown Man episode.

You are from the Netherlands and can't understand the nominal
conversion of natural noon cycles to the 1461 AM/PM cycles which cover
4 circuits of the Earth when your countryman explains how the
averaging process takes place -

" Draw a Meridian line upon a floor and then hang two plummets, each
by a small thread or wire, directly over the Meridian, at the distance
of some 2. feet or more one from the other, as the smallness of the
thread will admit. When the middle of the Sun (the Eye being placed
so, as to bring both the threds into one line) appears to be in the
same line exactly you are then immediately to set the Watch, not
precisely to the hour of 12. but by so much less, as is the Aequation
of the day by the Table." Christian Huygens

http://adcs.home.xs4all.nl/Huygens/06/kort-E.html

Only when Harrison came along and created a set of Equation of Time
tables for a leap year and the extra natural noon cycle did the entire
system become complete and this is not rocket science,it takes only
the basic fact of 1461 rotations in 1461 days or one 24 hour rotation
is the same as one day.

The leap second dummies,and you may very well be one of them,have an
accumulative 4 extra rotations for those 1461 days so that since the
year 2000,the leap second guys have now 12 extra rotations up to Feb
29th 2012 that the Earth never had.

Here is what you software guys do,look at the rotation of the Earth
from space over a period of 24 hours within the present calendar
cycle,the day is May 29th 2008 and the Earth turned once that day as
it did the next day until you reach Feb 29th in a number of weeks and
that will be the 1461 st rotation -

http://www.youtube.com/watch?v=JxrIMHKobk0

Ah look,the mind of a programmer is generally wired differently than
those who can interpret observations and few can cross the divide,I
know this through Pascal who accurately commented on why genius is a
combination of mathematical adventure and intuitive restraint at some
times and the opposite at others,the person with the greatest balance
possesses both traits and while many have a strong mathematical
faculty,few have that intuitive sense as Pascal knew it.For these
reasons,every time I explain the highly intuitive spacial awareness
process which makes an astronomer what he is,you mathematicians
perceive it as a threat because it exists outside the confines of your
system.It is not only that the conclusions are wrong,it is the
muddleheaded manner in which these errors are made.

"The reason, therefore, that some intuitive minds are not mathematical
is that they cannot at all turn their attention to the principles of
mathematics. But the reason that mathematicians are not intuitive is
that they do not see what is before them, and that, accustomed to the
exact and plain principles of mathematics, and not reasoning till they
have well inspected and arranged their principles, they are lost in
matters of intuition where the principles do not allow of such
arrangement. They are scarcely seen; they are felt rather than seen;
there is the greatest difficulty in making them felt by those who do
not of themselves perceive them. These principles are so fine and so
numerous that a very delicate and very clear sense is needed to
perceive them, and to judge rightly and justly when they are
perceived, without for the most part being able to demonstrate them in
order as in mathematics, because the principles are not known to us in
the same way, and because it would be an endless matter to undertake
it. We must see the matter at once, at one glance, and not by a
process of reasoning, at least to a certain degree. And thus it is
rare that mathematicians are intuitive and that men of intuition are
mathematicians, because mathematicians wish to treat matters of
intuition mathematically and make themselves ridiculous, wishing to
begin with definitions and then with axioms, which is not the way to
proceed in this kind of reasoning. Not that the mind does not do so,
but it does it tacitly, naturally, and without technical rules; for
the expression of it is beyond all men, and only a few can feel it."
Pascal

 
Reply With Quote
 
Alan Browne
Guest
Posts: n/a
 
      01-25-2012, 03:59 PM
On 2012-01-25 05:31 , J. J. Lodder wrote:
> Alan Browne<(E-Mail Removed)> wrote:
>
>> On 2012-01-24 08:42 , Peter H. Coffin wrote:
>>> On Mon, 23 Jan 2012 13:00:08 -0800, Wolfgang S. Rupprecht wrote:
>>>> What I find so frustrating about the whole situation is that this is
>>>> simply another case of daylight-savings-time. Real computers (read
>>>> anything but the MS crap), already use seconds since some arbitrary
>>>> epoch to measure time. The timezone and DST corrections are added by
>>>> the display routines when the time is presented to the humans. It is
>>>> amazing (and frustrating) that leap seconds aren't accounted for in this
>>>> manner too. If one needs to display the time one could just as easily
>>>> do as GPS systems do and add the accumulated leap seconds in the display
>>>> routines and internally use a linearly incrementing clock that adds one
>>>> second per second.
>>>
>>> It *shouldn't* cause problems. The NTP protocol datagram has indicators
>>> that account for leap seconds, which should be telling the recieving
>>> system "account for this if you haven't already". The actual number of
>>> seconds in the timestamp isn't itself adjusted, but the indicator is to
>>> keep the OUTPUT display properly calibrated if it hasn't been informed
>>> to otherwise."

>>
>> Wolfgang is more worried about derivative products of the "time"
>> changing. "Shouldn't" means a programmer _accounted_ for it. Laziness,
>> budget, ignorance, laissez-faire attitudes (not to mention those who
>> deem the problem as non-problematic) mean there are oodles of code out
>> there that don't account for it and that might cause transient issues in
>> some systems.

>
> Sounds like a good reason for keeping leap seconds.
> The Y2K misery cleared out a lot of programming rubbish too.
>
> I still see nothing here beyond:
> We are incompetent, so the rest of the world must adapt to us,


No it's:

1. The competent - implement appropriate code or other compensation.
2. The indifferent - see no reason for it and justly so.
3. The incompetent - should see that (or fail to check if) they
need to implement appropriate code, but don't and suffer
occasional problems.


--
"We demand rigidly defined areas of doubt and uncertainty."
Douglas Adams - (Could have been a GPS engineer).
 
Reply With Quote
 
oriel36
Guest
Posts: n/a
 
      01-30-2012, 07:36 PM
On Jan 25, 4:59*pm, Alan Browne <alan.bro...@FreelunchVideotron.ca>
wrote:
> On 2012-01-25 05:31 , J. J. Lodder wrote:
>
>
>
>
>
>
>
>
>
> > Alan Browne<alan.bro...@FreelunchVideotron.ca> *wrote:

>
> >> On 2012-01-24 08:42 , Peter H. Coffin wrote:
> >>> On Mon, 23 Jan 2012 13:00:08 -0800, Wolfgang S. Rupprecht wrote:
> >>>> What I find so frustrating about the whole situation is that this is
> >>>> simply another case of daylight-savings-time. *Real computers (read
> >>>> anything but the MS crap), already use seconds since some arbitrary
> >>>> epoch to measure time. *The timezone and DST corrections are addedby
> >>>> the display routines when the time is presented to the humans. *Itis
> >>>> amazing (and frustrating) that leap seconds aren't accounted for in this
> >>>> manner too. *If one needs to display the time one could just as easily
> >>>> do as GPS systems do and add the accumulated leap seconds in the display
> >>>> routines and internally use a linearly incrementing clock that adds one
> >>>> second per second.

>
> >>> It *shouldn't* cause problems. The NTP protocol datagram has indicators
> >>> that account for leap seconds, which should be telling the recieving
> >>> system "account for this if you haven't already". The actual number of
> >>> seconds in the timestamp isn't itself adjusted, but the indicator is to
> >>> keep the OUTPUT display properly calibrated if it hasn't been informed
> >>> to otherwise."

>
> >> Wolfgang is more worried about derivative products of the "time"
> >> changing. *"Shouldn't" means a programmer _accounted_ for it. *Laziness,
> >> budget, ignorance, laissez-faire attitudes (not to mention those who
> >> deem the problem as non-problematic) mean there are oodles of code out
> >> there that don't account for it and that might cause transient issues in
> >> some systems.

>
> > Sounds like a good reason for keeping leap seconds.
> > The Y2K misery cleared out a lot of programming rubbish too.

>
> > I still see nothing here beyond:
> > We are incompetent, so the rest of the world must adapt to us,

>
> No it's:
>
> * *1. The competent - implement appropriate code or other compensation.
> * *2. The indifferent - see no reason for it and justly so.
> * *3. The incompetent - should see that (or fail to check if) they
> * * * need to implement appropriate code, but don't and suffer
> * * * occasional problems.
>
> --
> "We demand rigidly defined areas of doubt and uncertainty."
> Douglas Adams - (Could have been a GPS engineer).


Incompetence,at least here,equates to being irrelevant as the founding
principles which link timekeeping to planetary dynamics are based on
the conversion of the 1461 natural noon cycles equivalent to 4 orbital
period into 1461 clocks cycles of 24 hours.

Good for Sam to show me that for your area of study the Earth may as
well be flat as opposed to the original men who used timekeeping to
find location on the planet using accurate watches linked with a
planetary rotation rate of 15 degrees per hour a one rotation in 24
hours.It is a matter of intellectual substance you understand as you
look like mere children before astronomers,an airless breed fascinated
by code and watches to bother to look out at where they came from.

William Blake painted a representation of your kind,although it
represents Newton fixated on his right ascension agenda,it could as
well be any of you -

http://www.martinfrost.ws/htmlfiles/newton_blake.jpg

I assure you all that the 'leap second' is a nuisance born of minds
and souls that never bothered to look into the celestial arena and
made sense of what they bodies experience ,that is not an opinion but
a technical certainty.
 
Reply With Quote
 
oriel36
Guest
Posts: n/a
 
      01-30-2012, 07:53 PM
On Jan 25, 4:59*pm, Alan Browne <alan.bro...@FreelunchVideotron.ca>
wrote:
> On 2012-01-25 05:31 , J. J. Lodder wrote:
>
>
>
>
>
>
>
>
>
> > Alan Browne<alan.bro...@FreelunchVideotron.ca> *wrote:

>
> >> On 2012-01-24 08:42 , Peter H. Coffin wrote:
> >>> On Mon, 23 Jan 2012 13:00:08 -0800, Wolfgang S. Rupprecht wrote:
> >>>> What I find so frustrating about the whole situation is that this is
> >>>> simply another case of daylight-savings-time. *Real computers (read
> >>>> anything but the MS crap), already use seconds since some arbitrary
> >>>> epoch to measure time. *The timezone and DST corrections are addedby
> >>>> the display routines when the time is presented to the humans. *Itis
> >>>> amazing (and frustrating) that leap seconds aren't accounted for in this
> >>>> manner too. *If one needs to display the time one could just as easily
> >>>> do as GPS systems do and add the accumulated leap seconds in the display
> >>>> routines and internally use a linearly incrementing clock that adds one
> >>>> second per second.

>
> >>> It *shouldn't* cause problems. The NTP protocol datagram has indicators
> >>> that account for leap seconds, which should be telling the recieving
> >>> system "account for this if you haven't already". The actual number of
> >>> seconds in the timestamp isn't itself adjusted, but the indicator is to
> >>> keep the OUTPUT display properly calibrated if it hasn't been informed
> >>> to otherwise."

>
> >> Wolfgang is more worried about derivative products of the "time"
> >> changing. *"Shouldn't" means a programmer _accounted_ for it. *Laziness,
> >> budget, ignorance, laissez-faire attitudes (not to mention those who
> >> deem the problem as non-problematic) mean there are oodles of code out
> >> there that don't account for it and that might cause transient issues in
> >> some systems.

>
> > Sounds like a good reason for keeping leap seconds.
> > The Y2K misery cleared out a lot of programming rubbish too.

>
> > I still see nothing here beyond:
> > We are incompetent, so the rest of the world must adapt to us,

>
> No it's:
>
> * *1. The competent - implement appropriate code or other compensation.
> * *2. The indifferent - see no reason for it and justly so.
> * *3. The incompetent - should see that (or fail to check if) they
> * * * need to implement appropriate code, but don't and suffer
> * * * occasional problems.
>
> --
> "We demand rigidly defined areas of doubt and uncertainty."
> Douglas Adams - (Could have been a GPS engineer).


My proofreading always lets me down.

People who are so fixated on code or clocks as mere mechanical tools
never look out and make the effort to comprehend where they come from
and having no soul or faith,the Universe and world shrink to
irrelevance until the day somebody discovers that it is the other way
around -

http://www.martinfrost.ws/htmlfiles/newton_blake.jpg

The technical issue where 1461 natural noon cycles equivalent to 4
orbital periods convert to 1461 AM/PM cycles of the 24 hour day
ultimately surface as one day and all its effects reflect the 24hour/
360 degree rotation of the Earth as the men who first worked out the
principles and designed watches based on the planetary cycles and only
the dullest of the dull would imagine an alternative view of of 1465
rotation/1461 day imbalance as you people do.

It is good that I came here via Sam,he is not to blame,he merely
shows my the limitations of the human mind as opposed to genuine
innovation.

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
A positive leap second will be introduced at the end of June 2012 Sam Wormley Global Navigation Satellite Systems 0 01-05-2012 01:20 PM
Observations on using new Garmin 2460LMT vs. 'old' Garmin Quest (from about 5 years ago) Andrew Garmin GPS 39 07-23-2011 01:52 AM
NO positive leap second will be introduced at the end of December2011 Sam Wormley Global Navigation Satellite Systems 22 07-16-2011 04:57 AM
O/T Did Obama put them up to this? BJ General GPS Discussion 2 12-01-2010 12:03 AM


All times are GMT. The time now is 09:56 PM.

1 2 3 4 5 6 7 8 9