<div dir="ltr"><div><div><div><div><div><div><div><div>No, No, No!<br><br></div>JD, MJD, and ISO-8601 have no meaning if the time scale is not specified (nor the reference position, for that matter).<br><br></div>A time stamp, whether it is expressed in JD, MJD or ISOTime, always HAS to be referenced to a time scale (any time scale) and a reference position.<br></div><div>Like:<br></div>JD 1456344.845 (TT; GEOCENTER)<br></div>2018-04-13T17:26:37 (UTC; TOPOCENTER)<br></div>MJD 56345.345 (TDB; BARYCENTER)<br><br></div>None of these is identified with any specific time scale.<br></div>Though, there is a strong warning that JD and MJD (UTC) are dangerous, especially on days that contain leap seconds.<br><br></div> - Arnold<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">-------------------------------------------------------------------------------------------------------------<br>Arnold H. Rots Chandra X-ray Science Center<br>Smithsonian Astrophysical Observatory tel: +1 617 496 7701<br>60 Garden Street, MS 67 fax: +1 617 495 7356<br>Cambridge, MA 02138 <a href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a><br>USA <a href="http://hea-www.harvard.edu/~arots/" target="_blank">http://hea-www.harvard.edu/~arots/</a><br>--------------------------------------------------------------------------------------------------------------<br><br></div></div></div>
<br><div class="gmail_quote">On Fri, Apr 13, 2018 at 8:42 AM, Paul Harrison <span dir="ltr"><<a href="mailto:paul.harrison@manchester.ac.uk" target="_blank">paul.harrison@manchester.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space"><span class=""><br><div><br><blockquote type="cite"><div>On 2018-04 -13, at 01:10, Arnold Rots <<a href="mailto:arots@cfa.harvard.edu" target="_blank">arots@cfa.harvard.edu</a>> wrote:</div><br class="m_-8968909289194087387Apple-interchange-newline"><div><div style="font-family:Helvetica;font-size:15px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div><div>Since MJD is absolute, the client should ignore the timeOrigin. Actually, it should not even look to see whether there is one.<br><br></div><div>In terms of implementation:<br></div>The common implementation of time is to keep it as either JD or MJD (my code uses MJD, the JPL ephemeris uses JD), as either two doubles or an integer and a double.<br></div>JD and MJD times would then need either nothing or the JD-MJD fixed offset in order to be stored; ISOTime requires a little more; but only when a TimeOffset if provided would the code actually look for a timeOrigin value.<br></div><span style="font-family:Helvetica;font-size:15px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline!important">Or, if that feels more comfortable, you can (arbitrarily) assign a default value for the timeOrigin; can be zero or 10^10 or your favorite prime number.</span><br style="font-family:Helvetica;font-size:15px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"></div></blockquote></div><div><br></div></span><div>I don’t think that in fact things are as simple as this summary presents, both in theory and certainly in practice. I think that it is incorrect to say that MJD is absolute - it is tied to the UTC timescale for working out the whole day, but then there is the problem of leap seconds - is the fractional part of the MJD for 12 noon on a day with a leap second 1/2 or 43200/86401? The Astronomical Almanac in fact discusses MJDs in different timescales, where there fractional part of the day is calculated in the timescale indicated - so I get the feeling that in general there is not even a consensus of definition of MJD that means that a given MJD double value is completely unambiguous on days with leap seconds - The real problem is the measuring in units of day - only seconds have unambiguous definition, and then you do want to specify an origin to be sure what is meant.</div><div><br></div><div>ISOTime is tied to UTC and does have unambiguous representation of time on days with leap seconds, and the textual representation can include any timezone offsets in the representation, so need no origin - and for this reason is probably superior to MJD for representing instants of time in UTC.</div><div><br></div><div>Paul.</div><div><br></div><br><div>
<div><div style="font-size:12px">Dr. Paul Harrison</div><div style="font-size:12px">JBO, Manchester University</div><div style="font-size:12px"><a href="http://www.manchester.ac.uk/jodrellbank" target="_blank">http://www.manchester.ac.uk/<wbr>jodrellbank</a></div></div><div><br></div><br class="m_-8968909289194087387Apple-interchange-newline">
</div>
<br></div></blockquote></div><br></div>