<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Calibri;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:514852291;
mso-list-type:hybrid;
mso-list-template-ids:-1310156374 1159362378 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"\(%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Ah, well, now you raise a good point. <o:p></o:p></p>
<p class="MsoNormal">I wasn’t thinking of 2 different absolute time scales or even 2 different absolute time epochs, associated w 2 (or more) relative times; merely 2 different relative time scales referenced to the same absolute scale/epoch. In my case [1@ABS:2@REL],
you could identify RELTIME_1,….RELTIME_n.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If we try to address your point, it seems you’d need a way to define cross-strapping of the systems. ABSTIME_1,…ABSTIME_n to each of RELTIME_1,…RELTIME_n :<o:p></o:p></p>
<p class="MsoNormal"> RELTIME_1_1<o:p></o:p></p>
<p class="MsoNormal"> RELTIME_1_2<o:p></o:p></p>
<p class="MsoNormal"> :<o:p></o:p></p>
<p class="MsoNormal"> RELTIME_1_n<o:p></o:p></p>
<p class="MsoNormal"> RELTIME_2_1<o:p></o:p></p>
<p class="MsoNormal"> RELTIME_2_2<o:p></o:p></p>
<p class="MsoNormal"> :<o:p></o:p></p>
<p class="MsoNormal"> RELTIME_2_n<o:p></o:p></p>
<p class="MsoNormal"> :<o:p></o:p></p>
<p class="MsoNormal">where the second number refers to the ABSTIME.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">How often would more than one ABSTIME [SYS or SCAL] be used? I can’t think of any examples. However, I do think at least 2 different RELTIME [SYS] would be used somewhat frequently.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheryl<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">"Oltrogge, Daniel" <doltrogge@agi.com><br>
<b>Date: </b>Thursday, October 20, 2016 at 1:46 PM<br>
<b>To: </b>"Gramling, Cheryl J. (GSFC-5950)" <cheryl.j.gramling@nasa.gov>, "moims-nav-exec@mailman.ccsds.org" <moims-nav-exec@mailman.ccsds.org><br>
<b>Subject: </b>RE: [MOIMS-NAV-EXEC] Notional Events requirements from NAV WG</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">You raise a very good point. And that’s fundamentally different that what I’d assembled below.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Any suggestions on how we could potentially reference the different relative times to their respective absolute times in a non-confusing, rigorous way ?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
Dan</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Daniel L. Oltrogge</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">SDC Program Manager & Senior Research Astrodynamicist</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Center for Space Standards and Innovation</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Analytical Graphics Incorporated</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Voice: 719-482-4552; E-mail: oltrogge@agi.com</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gramling, Cheryl J. (GSFC-5950) [mailto:cheryl.j.gramling@nasa.gov]
<br>
<b>Sent:</b> Thursday, October 20, 2016 5:07 AM<br>
<b>To:</b> Oltrogge, Daniel <doltrogge@agi.com>; moims-nav-exec@mailman.ccsds.org<br>
<b>Subject:</b> Re: [MOIMS-NAV-EXEC] Notional Events requirements from NAV WG<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Dan,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I think we need a requirement that more than one relative time may optionally be associated with an event [e.g. the case of UTC relative time and Spacecraft Clock relative time].<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Should it explicitly be stated that both an absolute and a relative time may optionally be associated with an event, or does the “or” in Req 3.a adequately cover that?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks for putting this together.<o:p></o:p></p>
<p class="MsoNormal">Cheryl<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">MOIMS-NAV-EXEC <<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">moims-nav-exec-bounces@mailman.ccsds.org</a>> on behalf of "Oltrogge, Daniel" <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>><br>
<b>Date: </b>Wednesday, October 19, 2016 at 4:57 PM<br>
<b>To: </b>"<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>" <<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>><br>
<b>Subject: </b>[MOIMS-NAV-EXEC] Notional Events requirements from NAV WG</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Particularly for Fran, Dale and Alain (but feedback from all welcomed):<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Here’s a rough draft of the NAV WG requirements for us to send to Colin regarding the events message…<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">(1)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The elements of information that are *<b>not</b>* associated with timing systems that are in the current rough draft Events Message look okay;<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">(2)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>In a parent segment, a global absolute reference epoch <u>
may</u> be specified.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>For this reference epoch, the <b>optional</b> capability is required to specify the time scale upon which this absolute reference epoch is based. If not specified, then the global absolute reference epoch’s time scale shall default
to UTC.<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">(3)<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Multiple events can be declared within a global object.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>For each of these events, the event’s timing <b>may optionally</b> be specified as relative or absolute. If not specified, the event’s timing defaults to absolute.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>When absolute timing is used:<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>i.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>The timescale of that event-unique absolute time
<b>may optionally</b> be set. If not specified, then the event-unique absolute reference epoch’s time scale shall default to UTC.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">c.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>When relative timing is used:<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>i.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>An event-unique absolute reference epoch to which this relative timing is measured
<b>may optionally</b> be specified.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>ii.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>If an event-unique absolute reference epoch is specified, then the time scale upon which that event-unique absolute reference epoch is based
<b>may optionally</b> be specified. If not specified, then the event-unique absolute reference epoch’s time scale shall default to UTC.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>iii.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>If an event-unique absolute reference epoch is not specified, then it is
<b>mandatory</b> that a global absolute reference epoch is specified.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>iv.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>If both a global and an event-unique absolute reference epoch are specified, the event-unique absolute reference epoch shall
<b>override</b> the global absolute reference epoch for that event.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo2">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>v.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>The timescale of the event relative time
<b>may optionally</b> be set. If not specified, then the timescale shall default to UTC seconds.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal"><br>
Dan<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Daniel L. Oltrogge<o:p></o:p></p>
<p class="MsoNormal">SDC Program Manager & Senior Research Astrodynamicist<o:p></o:p></p>
<p class="MsoNormal">Center for Space Standards and Innovation<o:p></o:p></p>
<p class="MsoNormal">Analytical Graphics Incorporated<o:p></o:p></p>
<p class="MsoNormal">Voice: 719-482-4552; E-mail: <a href="mailto:oltrogge@agi.com">
oltrogge@agi.com</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>