<font size=2 face="Arial">Peter,</font>
<br>
<br><font size=2 face="Arial">you quoted the first page of the OB, have
you looked also at the rest?</font>
<br>
<br><font size=2 face="Arial">It seems to me that the main focus of this
work is largely outside the scope of MOIMS. Only once there will be an
agreement to make the OB a BB, there will maybe the need for a dedicated
MO Service. At that time the MOIMS may play a role.</font>
<br>
<br><font size=2 face="Arial">Regards,</font>
<br>
<br><font size=2 face="Arial">__Mario</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Mario.Merri@esa.int"
<Mario.Merri@esa.int>, "Nestor.Peccia@esa.int" <Nestor.Peccia@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">CESG <cesg-bounces@mailman.ccsds.org>,
"CESG -- CCSDS-Engineering Steering Group (cesg@mailman.ccsds.org)
(cesg@mailman.ccsds.org)" <cesg@mailman.ccsds.org>, "Lee,
Dennis K (332G)" <dennis.k.lee@jpl.nasa.gov>, "Massimo.Bertinelli@esa.int"
<Massimo.Bertinelli@esa.int>, "Andrews, Kenneth S (332B)"
<kenneth.s.andrews@jpl.nasa.gov>, "Enrico.Vassallo@esa.int"
<Enrico.Vassallo@esa.int>, Victor Sank <victor.j.sank@nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">22/08/2017 19:42</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [CESG] V.Vorontsov
Technical Note, Orange Book CCSDS 551.1-O-1 «Correlated Data Generation»</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Ciao Mario,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I am somewhat puzzled by your statement,
even if you are just making it with your "MOIMS AD Hat" on. I
am just wondering why you reject this out of hand as "nothing to do
with MOIMS"? Does this look the same this with your "CESG
member Hat" on? While the OB does talk about combining data
from diverse channels, and also the signal propagation properties, it is
also, quite clearly, addressing the sort of ground data processing that
would appear to be right in the usual mission operations "territory".
To quote from the intro to their OB (<b><i>emphasis added</i></b>):</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">The data receiving stations may include
the relative software-hardware facilities of measuring stations located
on territories of several states, with a common receiving station appointed
MCC. <b><i>The correlated data of improved reliability generated at this
MCC</i></b> may be transferred to MCCs of other Space Agencies. </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I suspect that this could be proposed as
an "MO Service" if there was sufficient interest. Please note
that I am not necessarily endorsing their request for BB status. From
a technical point of view my coding guys, in an earlier analysis, provided
the following feedback. I doubt that the intervening three years
have changed their opinion, but I did ask them for an update:</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">As I've said before, the authors have undoubtedly
worked very hard, but unfortunately have not discovered anything new. They
have developed sub-optimal techniques for problems in which the optimal
techniques are already known. Their new CCSDS document remains hard
to read, both because of issues in translation, and because the authors
are not familiar with the standard signal processing framework in which
these problems lie. In summary, my opinion remains the same as it
did with previous versions of this work: the document does not provide
any technical results of value, and comprehensibility is extremely low,
so we should not be spending time on it. </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">I hope that the various WG chairs and other
experts who are copied on this will weigh in with an informed technical
opinion on the details of what is being proposed. This is not my
field of expertise so I request, and rely on, their technical feedback.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Thanks, Peter</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From: </b>CESG <cesg-bounces@mailman.ccsds.org>
on behalf of Mario Merri <Mario.Merri@esa.int><b><br>
Date: </b>Tuesday, August 22, 2017 at 9:35 AM<b><br>
To: </b>Nestor Peccia <Nestor.Peccia@esa.int><b><br>
Cc: </b>CESG <cesg-bounces@mailman.ccsds.org>, CCSDS Engineering
Steering Group - CESG Exec <cesg@mailman.ccsds.org>, Dennis K Lee
<dennis.k.lee@jpl.nasa.gov>, "Massimo.Bertinelli@esa.int"
<Massimo.Bertinelli@esa.int>, Kenneth Andrews <kenneth.s.andrews@jpl.nasa.gov>,
"Enrico.Vassallo@esa.int" <Enrico.Vassallo@esa.int><b><br>
Subject: </b>Re: [CESG] V.Vorontsov Technical Note, Orange Book CCSDS 551.1-O-1
«Correlated Data Generation»</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Arial">The only thing that I understand well is
that it has nothing to do with the MOIMS.</font><font size=2 face="Calibri">
<br>
</font><font size=2 face="Arial"><br>
Regards,</font><font size=2 face="Calibri"> <br>
</font><font size=2 face="Arial"><br>
__Mario</font><font size=2 face="Calibri"> <br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
From: </font><font size=1 face="sans-serif">Nestor.Peccia@esa.int</font><font size=2 face="Calibri">
</font><font size=1 color=#5f5f5f face="sans-serif"><br>
To: </font><font size=1 face="sans-serif">"CESG
-- CCSDS-Engineering Steering Group \(cesg@mailman.ccsds.org\) \(cesg@mailman.ccsds.org\)"
<cesg@mailman.ccsds.org>, Enrico.Vassallo@esa.int, "Lee, Dennis
K (332G)" <dennis.k.lee@jpl.nasa.gov>, Massimo.Bertinelli@esa.int,
kenneth.s.andrews@jpl.nasa.gov</font><font size=2 face="Calibri"> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Date: </font><font size=1 face="sans-serif">21/08/2017
12:19</font><font size=2 face="Calibri"> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Subject: </font><font size=1 face="sans-serif">[CESG]
V.Vorontsov Technical Note, Orange Book CCSDS 551.1-O-1 «Correlated Data
Generation»</font><font size=2 face="Calibri"> </font><font size=1 color=#5f5f5f face="sans-serif"><br>
Sent by: </font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font><font size=2 face="Calibri">
</font>
<div align=center>
<hr noshade></div>
<br><font size=2 face="Calibri"><br>
<br>
</font><font size=2 face="sans-serif"><br>
Dear all,</font><font size=3 face="Calibri"> </font><font size=2 face="sans-serif"><br>
During the last Technical meeting at San Antonio I had a short discussion
with Prof Vorontsov, who wanted to present the next steps he would like
to do within CCSDS after the issue of Roscosmos OB (Correlated Data Generation).</font><font size=3 face="Calibri">
</font><font size=2 face="sans-serif"><br>
<br>
As there was no russian translator and the ESA staff participated via webex,
I did ask him to produce a TN in english explaining his intentions.</font><font size=3 face="Calibri">
</font><font size=2 face="sans-serif"><br>
<br>
You will find the TN attached below. It is only 3.5 pages.</font><font size=3 face="Calibri">
</font><font size=2 face="sans-serif"><br>
<br>
I have also included the RFM and C&S WG Chairs because the TN
addresses some of their ToRs.</font><font size=3 face="Calibri"> </font><font size=2 face="sans-serif"><br>
<br>
Please let me have your views by 25th September 2017 cob</font><font size=3 face="Calibri">
<br>
<br>
</font><font size=2 face="sans-serif"><br>
<br>
ciaonestor</font><font size=3 face="Calibri"> <br>
<br>
</font><font size=2 face="Calibri"><br>
</font><font size=3 face="Courier New"><br>
This message and any attachments are intended for the use of the addressee
or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
<br>
[attachment "CCSDS_Technical_Note_17_07_07_ENG.doc" deleted by
Mario Merri/esoc/ESA] </font><font size=2 face="Courier New">_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org</font><font size=2 color=blue face="Calibri"><u><br>
</u></font><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><font size=2 color=blue face="Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</u></font></a><font size=2 face="Courier New"><br>
</font>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font>
<br><font size=2 face="Courier New"> </font>
<br>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>