202 SyncServer 600 Series User’s Guide 098-00720-000 Revision D1 – February, 2018
Chapter 6 Provisioning
Provisioning Inputs with Manual Entry Controls
Figure 6-14. Expected Pre-notification Times for Pending Leap Events
With the prior discussion as background the added utility of the manual leapsecond
setting can be understood. First, a nuance is added to the basic behavior described
for all manual entries in the section titled General Behavior Associated with Manual
Entry which stated:
If there is currently a qualified time reference that is capable of providing that
particular information, then a manual entry supplying that information will NOT be
used.
In the case of a manual pending leap entry, we amend this to:
If there is currently a qualified time reference that is capable of providing leap
pending information AND the time until the pending leap is within the expected
timeframe for that particular input, then a manual leap pending entry will not be
used.
On the other hand, if a manual leap entry is applied before the expected
timeframe for all qualified inputs in the pool, then the manual entry will be
accepted. In such a case, once the time until the leap moment falls within the
timeframe of any qualified input, the information supplied by that input will
overrule (if needed) the manual setting.
Examples:
If GPS is a qualified reference, manual leap pending input will never be accepted
since GPS is expected to provide leap pending status (typically) many months
prior to the leap moment. There is no formal definition for the timeframe but for
sure there will be plenty of notice and hence there is no reason to accept a
manual entry.
To Next Page
Loading...
