|
Article in other languages:
|
"JDN" redirects here. For the military IT system, see Joint Data Network.
For the comic book character Julian Gregory Day, see Calendar Man.
Not to be confused with Julian year.
The Julian date (JD) is the interval of time in days and fractions of a day since January 1, 4713 BC Greenwich noon, Julian proleptic calendar.[1] In precise work, the timescale, e.g., Terrestrial Time (TT) or Universal Time (UT), should be specified.[2] The Julian day number (JDN)[3] is the integral part of the Julian date (JD).[4] The day commencing at the above-mentioned epoch is JDN 0. Negative values can be used for preceding dates, though they predate all recorded history. Now, at 21:39, Saturday January 2, 2010 (UTC) the Julian day number is 2455199. A Julian date of 2454115.05486 means that the date and Universal Time is Sunday January 14, 2007 at 13:18:59.9. The decimal parts of a Julian date: Almost 2.5 million Julian days have elapsed since the initial epoch. JDN 2,400,000 was November 16, 1858. JD 2,500,000.0 will occur on August 31, 2132 at noon UT. If the Julian date of noon is applied to the entire midnight-to-midnight civil day centered on that noon,[5] rounding Julian dates (fractional days) for the twelve hours before noon up while rounding those after noon down, then the remainder upon division by 7 represents the day of the week, with 0 representing Monday, 1 representing Tuesday, and so forth. Now at 21:39, Saturday January 2, 2010 (UTC) the nearest noon JDN is 2455199 yielding a remainder of 5. The Julian day number can be considered a very simple calendar, where its calendar date is just an integer. This is useful for reference, computations, and conversions. It allows the time between any two dates in history to be computed by simple subtraction. The Julian day system was introduced by astronomers to provide a single system of dates that could be used when working with different calendars and to unify different historical chronologies. Apart from the choice of the zero point and name, this Julian day and Julian date are not directly related to the Julian calendar, although it is possible to convert any date from one calendar to the other.
Julian DateHistorical Julian dates were recorded relative to GMT or Ephemeris Time, but the International Astronomical Union now recommends that Julian Dates be specified in Terrestrial Time, and that when necessary to specify Julian Dates using a different time scale, that the time scale used be indicated when required, such as JD(UT1). The fraction of the day is found by converting the number of hours, minutes, and seconds after noon into the equivalent decimal fraction. The term Julian date is also used to refer to:
The use of Julian date to refer to the day-of-year (ordinal date) is usually considered to be incorrect although it is widely used that way in the earth sciences and computer programming. AlternativesBecause the starting point is so long ago, numbers in the Julian day can be quite large and cumbersome. A more recent starting point is sometimes used, for instance by dropping the leading digits, in order to fit into limited computer memory with an adequate amount of precision. In the following table, times are given in 24 hour notation.
The Heliocentric Julian Day (HJD) is the same as the Julian day, but adjusted to the frame of reference of the Sun, and thus can differ from the Julian day by as much as 8.3 minutes, that being the time it takes the Sun's light to reach Earth. As two separate astronomical measurements can exist that were taken when the Earth, astronomical objects, and Sun are in a straight line but the Earth was actually on opposite sides of the Sun for the two measurements, that is at one roughly 500 light seconds nearer to the astronomical than the Sun for the first measure, then 500 light seconds further from the astronomical object than the Sun for the second measure, then the subsequent light time error between two Julian Day measures can amount to nearly as much as 1000 seconds different relative to the same Heliocentric Julian Day interval which can make a significant difference when measuring temporal phenomena for short period astronomical objects over long time intervals. The Julian day is sometimes referred to as the Geocentric Julian Day (GJD) in order to distinguish it from HJD. HistoryThe Julian day number is based on the Julian Period proposed by Joseph Scaliger in 1583, at the time of the Gregorian calendar reform, but it is the multiple of three calendar cycles used with the Julian calendar:
Its epoch falls at the last time when all three cycles were in their first year together — Scaliger chose this because it preceded all historical dates. Note: although many references say that the Julian in "Julian day" refers to Scaliger's father, Julius Scaliger, in the introduction to Book V of his Opus de Emendatione Temporum ("Work on the Emendation of Time") he states, "Iulianum vocavimus: quia ad annum Iulianum dumtaxat accomodata est", which translates more or less as "We have called it Julian merely because it is accommodated to the Julian year." This Julian refers to Julius Caesar, who introduced the Julian calendar in 46 BC. In his book Outlines of Astronomy, first published in 1849, the astronomer John Herschel wrote:
Astronomers adopted Herschel's Julian Days in the late nineteenth century, but used the meridian of Greenwich instead of Alexandria, after the former was adopted as the Prime Meridian after the International Meridian Conference in Washington in 1884. This has now become the standard system of Julian days. Julian days are typically used by astronomers to date astronomical observations, thus eliminating the complications resulting from using standard calendar periods like eras, years, or months. They were first introduced into variable star work by Edward Charles Pickering, of the Harvard College Observatory, in 1890.[10] Julian days begin at noon because when Herschel recommended them, the astronomical day began at noon (it did so until 1925). The astronomical day had begun at noon ever since Ptolemy chose to begin the days in his astronomical periods at noon. He chose noon because the transit of the Sun across the observer's meridian occurs at the same apparent time every day of the year, unlike sunrise or sunset, which vary by several hours. Midnight was not even considered because it could not be accurately determined using water clocks. Nevertheless, he double-dated most nighttime observations with both Egyptian days beginning at sunrise and Babylonian days beginning at sunset. This would seem to imply that his choice of noon was not, as is sometimes stated, made in order to allow all observations from a given night to be recorded with the same date. CalculationThe Julian day number can be calculated using the following formulas (integer division is used exclusively, that is, the remainder of all divisions are dropped): The months (M) January to December are 1 to 12. For the year (Y) astronomical year numbering is used, thus 1 BC is 0, 2 BC is −1, and 4713 BC is −4712. D is the day of the month. JDN is the Julian Day Number, which pertains to the noon occurring in the cooresponding calendar date. Converting Gregorian calendar date to Julian Day NumberThe algorithm[11] is valid for all Gregorian calendar dates after November 23, −4713. JDN = (1461 × (Y + 4800 + (M − 14)/12))/4 +(367 × (M − 2 − 12 × ((M − 14)/12)))/12 − (3 × ((Y + 4900 + (M - 14)/12)/100))/4 + D − 32075 Converting Julian calendar date to Julian Day NumberThe algorithm[12] is valid for all values of Y ≥ −4712, that is, for all JD ≥ 0. JDN = 367 × Y − (7 × (Y + 5001 + (M − 9)/7))/4 + (275 × M)/9 + D + 1729777 Finding Julian date given Julian Day Number and time of dayFor the full Julian date, not counting leap seconds (divisions are real numbers):
So, for example, January 1, 2000 at midday corresponds to JD = 2451545.0 The day of the week can be determined from the Julian day number by calculating it modulo 7, where 0 means Monday.
Gregorian calendar from Julian day number
The calculations below (which use integer division [div] and modulo [mod] with positive numbers only) are valid for the whole range of dates since −4800. For dates before 1582, the resulting date components are valid only in the Gregorian proleptic calendar. This is based on the Gregorian calendar but extended to cover dates before its introduction, including the pre-Christian era. For dates in that era (before year 1 AD), astronomical year numbering is used. This includes a year zero, which immediately precedes 1 AD. Astronomical year zero is 1 BC in the proleptic Gregorian calendar and, in general, proleptic Gregorian year (n BC) = astronomical year (Y = 1 − n). For astronomical year Y (Y < 1), the proleptic Gregorian year is (1 - Y) BC.
Please be careful implementing this algorithm in C/C++, using one from http://www.astro.uu.nl/~strous/AA/en/reken/juliaansedag.html results in more straight-forward code.The operations div and mod used here are intended to have the same binary operator priority as the multipication and division, and defined as: You can also use only integers in most of the formula above, by taking J = floor(JD + 0.5), to compute the three integers (Y, M, D). The time of the day is then computed from the fractional day T = frac(JD + 0.5). The additive 0.5 constant can also be adjusted to take the local timezone into account, when computing a astronomical Gregorian date localized in another timezone than UTC. To convert the fractional day into actual hours, minutes, seconds, the astronomical Gregorian calendar uses a constant length of 24 hours per day (i.e. 86400 seconds exactly), ignoring leap seconds inserted or deleted at end of some specific days in the UTC Gregorian calendar. If you want to convert it to actual UTC time, you will need to compensate the UTC leap seconds by adding them to J before restarting the computation (however this adjustment requires a lookup table, because leap seconds are not predictable with a simple formula); you'll also need to finally determine which of the two possible UTC date and time is used at times where leap seconds are added (no final compensation will be needed if negative leap seconds are occurring on the rare possible days that could be shorter than 24 hours). Gregorian calendar from UnixTimeLet 'U' be the UnixTime you want to convert, just follow these easy steps:
where ss are seconds, mm minutes, hh hours. Day, month and year can be calculated as in the section Gregorian calendar from Julian day number, applying calculations to:
and D being:
See also
Footnotes
References
External links
Questions for article: |
This article is from Wikipedia. All text is available under the terms of the GNU Free Documentation License.
IHS Europe: Infrared Heating Systems for Home and Business.