Re: Julian Day Question [message #48871 is a reply to message #48870] |
Fri, 26 May 2006 09:43   |
Paul Van Delst[1]
Messages: 1157 Registered: April 2002
|
Senior Member |
|
|
kuyper@wizard.net wrote:
> Paul Van Delst wrote:
> ...
>
>> The example on that page is:
>>
>> IDL> print, julday(1,1,1,0,0,0), julday(1,1,1)
>> 1721423.5 1721424
>>
>> The *input* date, 0001-01-01, /should/ be based on how we define dates /now/, starting at
>> midnight. But the reference point for the input date seems to change (to 12noon) when the
>> hours/minutes/seconds are not supplied.
>
>
> It is based upon how dates are defined now - by astronomers.
Yeah, I realised that after I read subsequent posts. And, for that application, it makes
perfect sense.
However, it the two julday results up top still seem inconsistent. If I'm an astronomer
and my day start reference for input to the julday routine is 12 noon, then why do
julday(1,1,1,0,0,0) and julday(1,1,1) provide different results? Doesn't
julday(1,1,1,0,0,0) refer to 0hours, 0minutes, 0seconds beyond the (12noon) start of the
day? Why does providing the ",0,0,0" hh,mm,ss data cause the start reference to suddenly
shift by 12 hours?
paulv
> The Julian
> day starts at 12:00 noon, because that means an entire night's data
> get's tagged with the same Julian date. The Julian date system was
> originally invented to help astronomers match up ancient records of
> astronomical events with modern observations, to get more accurate
> figures for things like the orbital period of a comet. The starting
> point was chosen because calender cycles associated with several
> different popular historical calendar systems all come together on that
> date. This simplifies the process of converting between the Julian date
> and any one of those calendar systems.
>
--
Paul van Delst Ride lots.
CIMSS @ NOAA/NCEP/EMC Eddy Merckx
Ph: (301)763-8000 x7748
Fax:(301)763-8545
|
|
|