[MOIMS-NAV-EXEC] [Attachment Blocked]: RE: NEM - thoughts and more

Fran Martínez Fadrique fmartinez at gmv.com
Mon Aug 27 13:27:50 UTC 2018


An attachment named nemusergeneratorinstaller.zip was removed from this document as it constituted a security hazard. If you require this document, please contact with the sender and arrange an alternate means of receiving it.

System Department

--- Original Message ---

Hi Dan.
Some comments to yours below (implementation related). Alain can possibly provide additional feedback on the events design part. My comments in green.
Best regards,
Fran

From: MOIMS-NAV-EXEC [mailto:moims-nav-exec-bounces at mailman.ccsds.org] On Behalf Of Oltrogge, Daniel
Sent: lunes, 27 de agosto de 2018 14:48
To: Lamy Alain <Alain.Lamy at cnes.fr>; moims-nav-exec at mailman.ccsds.org
Subject: Re: [MOIMS-NAV-EXEC] NEM - thoughts and more

A few comments to the NEM and related questions:


-          Just to reinforce, the NEM should accommodate events consisting of interaction between multiple satellites and multiple ground stations and/or a combination of both.  Things like cross-links or ground-space-space-ground should be accommodated if possible.  I’m not sure what the best way to accommodate this is, though.  One could envision having a keyword which reflects the entire link (JSC_SAT1_SAT1_ESA) or list the composition of the link, for example.  For us to discuss.
This can be easily implemented through the parameters within the event. AT the moment there is no limitation for this. It will depend how the final standard describes the definition of the events if we (after discussions) want to limit the events or parameters scope.

-          The difference between version 1 and 2 may depend on whether we foresee having more than one event contained in the NEM.
In one of my previous e-mails (attached; explanatory details in it) I proposed an alternative layout (I assume that you refer to version 1 and version 2 in section 4.3) that would not require quotes, it is probably closer to the KVN philosophy and imposes no limitations to the number of parameters. Alain’s cases follow with my KVN proposal
EVENT_START
NAME = TRUE_ANOMALY
EPOCH = 2018-04-11T00:00:10
VALUE = 45 [deg]
EVENT_STOP

EVENT = 2018-04-11T00:00:10 TRUE_ANOMALY
value = 45 [deg]

2018-04-11T00:00:10  TRUE_ANOMALY 45
2018-04-11T00:00:10  GROUND_STATION_AOS 10 Kourou

EVENT = 2018-04-11T00:00:10 TRUE_ANOMALY
value = 45 [deg]
EVENT = 2018-04-11T00:00:10 STATION_AOS
station = Kourou
elevation = 10 [deg]

-          In my opinion, strings in version 2 would have to be “” delimited.
Not needed in my proposed approach

-          I disagree that an event shouldn’t have a duration associated with it.  While I do agree that an event should be instantaneous, I only view the duration as associated metadata that can accompany it, rather than requiring two separate NEMs, for example.
For the needed cases, the user is free to associated a parameter ‘duration’ to which the relevant interpretation can be also associated. So, compatible with CSS, yet fulfilling user’s wishes.
EVENT = 2018-04-11T00:00:10 ECLIPSE_START
body = Moon
duration = 323 [s]

Dan

Daniel L. Oltrogge
Director, Center for Space Standards and Innovation
Analytical Graphics, Incorporated
Voice: 719-482-4552   ҉   E-mail: oltrogge at agi.com<mailto:oltrogge at agi.com>

From: MOIMS-NAV-EXEC <moims-nav-exec-bounces at mailman.ccsds.org<mailto:moims-nav-exec-bounces at mailman.ccsds.org>> On Behalf Of Lamy Alain
Sent: 18 Aug 2018 11:34
To: moims-nav-exec at mailman.ccsds.org<mailto:moims-nav-exec at mailman.ccsds.org>
Subject: [MOIMS-NAV-EXEC] NEM - thoughts and more

Hi everyone,

This is a document I was supposed to send a few months ago (action item #33).
I send it as it is, in case some of you have time to read it and think about it.
Frank and Fran have sent lots of ideas (and more than ideas), that I have only partially taken into account.
So there is much more do do.
This document is just the beginning.

Best regards,

Alain



P Please consider the environment before printing this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180827/339104c1/attachment.html>
-------------- next part --------------
An embedded message was scrubbed...
From: =?iso-8859-1?Q?Fran_Mart=EDnez_Fadrique?= <fmartinez at gmv.com>
Subject: RE: [CCSDS] Action 32
Date: Sun, 24 Jun 2018 09:29:34 +0000
Size: 332823
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20180827/339104c1/attachment.mht>


More information about the MOIMS-NAV-EXEC mailing list