14616d0f9Sopenharmony_ci#	ATOMIC TIME.
24616d0f9Sopenharmony_ci#	The Coordinated Universal Time (UTC) is the reference time scale derived
34616d0f9Sopenharmony_ci#	from The "Temps Atomique International" (TAI) calculated by the Bureau
44616d0f9Sopenharmony_ci#	International des Poids et Mesures (BIPM) using a worldwide network of atomic
54616d0f9Sopenharmony_ci#	clocks. UTC differs from TAI by an integer number of seconds; it is the basis
64616d0f9Sopenharmony_ci#	of all activities in the world.
74616d0f9Sopenharmony_ci#
84616d0f9Sopenharmony_ci#
94616d0f9Sopenharmony_ci#	ASTRONOMICAL TIME (UT1) is the time scale based on the rate of rotation of the earth.
104616d0f9Sopenharmony_ci#	It is now mainly derived from Very Long Baseline Interferometry (VLBI). The various
114616d0f9Sopenharmony_ci#	irregular fluctuations progressively detected in the rotation rate of the Earth lead
124616d0f9Sopenharmony_ci#	in 1972 to the replacement of UT1 by UTC as the reference time scale.
134616d0f9Sopenharmony_ci#
144616d0f9Sopenharmony_ci#
154616d0f9Sopenharmony_ci#	LEAP SECOND
164616d0f9Sopenharmony_ci#	Atomic clocks are more stable than the rate of the earth rotation since the latter
174616d0f9Sopenharmony_ci#	undergoes a full range of geophysical perturbations at various time scales: lunisolar
184616d0f9Sopenharmony_ci#	and core-mantle torques, atmospheric and oceanic effetcs, etc.
194616d0f9Sopenharmony_ci#	Leap seconds are needed to keep the two time scales in agreement, i.e. UT1-UTC smaller
204616d0f9Sopenharmony_ci#	than 0.9 second. Therefore, when necessary a "leap second" is applied to UTC.
214616d0f9Sopenharmony_ci#	Since the adoption of this system in 1972 it has been necessary to add a number of seconds to UTC,
224616d0f9Sopenharmony_ci#	firstly due to the initial choice of the value of the second (1/86400 mean solar day of
234616d0f9Sopenharmony_ci#	the year 1820) and secondly to the general slowing down of the Earth's rotation. It is
244616d0f9Sopenharmony_ci#	theorically possible to have a negative leap second (a second removed from UTC), but so far,
254616d0f9Sopenharmony_ci#	all leap seconds have been positive (a second has been added to UTC). Based on what we know about
264616d0f9Sopenharmony_ci#	the earth's rotation, it is unlikely that we will ever have a negative leap second.
274616d0f9Sopenharmony_ci#
284616d0f9Sopenharmony_ci#
294616d0f9Sopenharmony_ci#	HISTORY
304616d0f9Sopenharmony_ci#	The first leap second was added on June 30, 1972. Until yhe year 2000, it was necessary in average to add a
314616d0f9Sopenharmony_ci#       leap second at a rate of 1 to 2 years. Since the year 2000 leap seconds are introduced with an
324616d0f9Sopenharmony_ci#	average interval of 3 to 4 years due to the acceleration of the Earth rotation speed.
334616d0f9Sopenharmony_ci#
344616d0f9Sopenharmony_ci#
354616d0f9Sopenharmony_ci#	RESPONSABILITY OF THE DECISION TO INTRODUCE A LEAP SECOND IN UTC
364616d0f9Sopenharmony_ci#	The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Center of
374616d0f9Sopenharmony_ci#	the International Earth Rotation and reference System Service (IERS). This center is located at Paris
384616d0f9Sopenharmony_ci#	Observatory. According to international agreements, leap seconds should only be scheduled for certain dates:
394616d0f9Sopenharmony_ci#	first preference is given to the end of December and June, and second preference at the end of March
404616d0f9Sopenharmony_ci#	and September. Since the introduction of leap seconds in 1972, only dates in June and December were used.
414616d0f9Sopenharmony_ci#
424616d0f9Sopenharmony_ci#		Questions or comments to:
434616d0f9Sopenharmony_ci#			Christian Bizouard:  christian.bizouard@obspm.fr
444616d0f9Sopenharmony_ci#			Earth orientation Center of the IERS
454616d0f9Sopenharmony_ci#			Paris Observatory, France
464616d0f9Sopenharmony_ci#
474616d0f9Sopenharmony_ci#
484616d0f9Sopenharmony_ci#
494616d0f9Sopenharmony_ci#    	COPYRIGHT STATUS OF THIS FILE
504616d0f9Sopenharmony_ci#    	This file is in the public domain.
514616d0f9Sopenharmony_ci#
524616d0f9Sopenharmony_ci#
534616d0f9Sopenharmony_ci#	VALIDITY OF THE FILE
544616d0f9Sopenharmony_ci#	It is important to express the validity of the file. These next two dates are
554616d0f9Sopenharmony_ci#	given in units of seconds since 1900.0.
564616d0f9Sopenharmony_ci#
574616d0f9Sopenharmony_ci#	1) Last update of the file.
584616d0f9Sopenharmony_ci#
594616d0f9Sopenharmony_ci#	Updated through IERS Bulletin C (https://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat)
604616d0f9Sopenharmony_ci#
614616d0f9Sopenharmony_ci#	The following line shows the last update of this file in NTP timestamp:
624616d0f9Sopenharmony_ci#
634616d0f9Sopenharmony_ci#$	3913697179
644616d0f9Sopenharmony_ci#
654616d0f9Sopenharmony_ci#	2) Expiration date of the file given on a semi-annual basis: last June or last December
664616d0f9Sopenharmony_ci#
674616d0f9Sopenharmony_ci#	File expires on 28 December 2024
684616d0f9Sopenharmony_ci#
694616d0f9Sopenharmony_ci#	Expire date in NTP timestamp:
704616d0f9Sopenharmony_ci#
714616d0f9Sopenharmony_ci#@	3944332800
724616d0f9Sopenharmony_ci#
734616d0f9Sopenharmony_ci#
744616d0f9Sopenharmony_ci#	LIST OF LEAP SECONDS
754616d0f9Sopenharmony_ci#	NTP timestamp (X parameter) is the number of seconds since 1900.0
764616d0f9Sopenharmony_ci#
774616d0f9Sopenharmony_ci#	MJD: The Modified Julian Day number. MJD = X/86400 + 15020
784616d0f9Sopenharmony_ci#
794616d0f9Sopenharmony_ci#	DTAI: The difference DTAI= TAI-UTC in units of seconds
804616d0f9Sopenharmony_ci#	It is the quantity to add to UTC to get the time in TAI
814616d0f9Sopenharmony_ci#
824616d0f9Sopenharmony_ci#	Day Month Year : epoch in clear
834616d0f9Sopenharmony_ci#
844616d0f9Sopenharmony_ci#NTP Time      DTAI    Day Month Year
854616d0f9Sopenharmony_ci#
864616d0f9Sopenharmony_ci2272060800      10      # 1 Jan 1972
874616d0f9Sopenharmony_ci2287785600      11      # 1 Jul 1972
884616d0f9Sopenharmony_ci2303683200      12      # 1 Jan 1973
894616d0f9Sopenharmony_ci2335219200      13      # 1 Jan 1974
904616d0f9Sopenharmony_ci2366755200      14      # 1 Jan 1975
914616d0f9Sopenharmony_ci2398291200      15      # 1 Jan 1976
924616d0f9Sopenharmony_ci2429913600      16      # 1 Jan 1977
934616d0f9Sopenharmony_ci2461449600      17      # 1 Jan 1978
944616d0f9Sopenharmony_ci2492985600      18      # 1 Jan 1979
954616d0f9Sopenharmony_ci2524521600      19      # 1 Jan 1980
964616d0f9Sopenharmony_ci2571782400      20      # 1 Jul 1981
974616d0f9Sopenharmony_ci2603318400      21      # 1 Jul 1982
984616d0f9Sopenharmony_ci2634854400      22      # 1 Jul 1983
994616d0f9Sopenharmony_ci2698012800      23      # 1 Jul 1985
1004616d0f9Sopenharmony_ci2776982400      24      # 1 Jan 1988
1014616d0f9Sopenharmony_ci2840140800      25      # 1 Jan 1990
1024616d0f9Sopenharmony_ci2871676800      26      # 1 Jan 1991
1034616d0f9Sopenharmony_ci2918937600      27      # 1 Jul 1992
1044616d0f9Sopenharmony_ci2950473600      28      # 1 Jul 1993
1054616d0f9Sopenharmony_ci2982009600      29      # 1 Jul 1994
1064616d0f9Sopenharmony_ci3029443200      30      # 1 Jan 1996
1074616d0f9Sopenharmony_ci3076704000      31      # 1 Jul 1997
1084616d0f9Sopenharmony_ci3124137600      32      # 1 Jan 1999
1094616d0f9Sopenharmony_ci3345062400      33      # 1 Jan 2006
1104616d0f9Sopenharmony_ci3439756800      34      # 1 Jan 2009
1114616d0f9Sopenharmony_ci3550089600      35      # 1 Jul 2012
1124616d0f9Sopenharmony_ci3644697600      36      # 1 Jul 2015
1134616d0f9Sopenharmony_ci3692217600      37      # 1 Jan 2017
1144616d0f9Sopenharmony_ci#
1154616d0f9Sopenharmony_ci#	A hash code has been generated to be able to verify the integrity
1164616d0f9Sopenharmony_ci#	of this file. For more information about using this hash code,
1174616d0f9Sopenharmony_ci#	please see the readme file in the 'source' directory :
1184616d0f9Sopenharmony_ci#	https://hpiers.obspm.fr/iers/bul/bulc/ntp/sources/README
1194616d0f9Sopenharmony_ci#
1204616d0f9Sopenharmony_ci#h	9dac5845 8acd32c0 2947d462 daf4a943 f58d9391
121