3. Any feedback on RCS ICD 1.2, REGU 2.1, RDP 1.2 and SOC DPDD template 1.0
4. Next telecon
5. AOB (banish CDF Excel skeleton?)
Discussion items
Time
Item
Who
Notes
5min
General
XB
See slides in roc-rcs-telecon14_roc-status-planning.pdf below for support.
ROC Pipelines
XB
XB says that the ROC pipelines design rework is still in progress. However, the CDF production part is not affected by the rework for now and, hence, he will not wait before producing new ROC-SGSE V3 CDF. This should be done before the end of April 2018. The teams should be ready to test the generation of preliminary ROC-SGSE L1R V3 CDF at this date.
ROC RCS-related planning
XB
Concerning the planning, it still has to be confirmed, but based on a Feb. 2020 launch scenario, RCS teams can expect to deliver the RCS "ready-for-flight" version around April 2019.
Although the ROC man-power issue is still not fixed, XB proposes to have an intermediate delivery step on December 2018. The exact content of this "preliminary ready-for-flight" version has to be detailled, but it might contain at least a first full data processing RCS with partial RCS ICD compliance (TBC).
ESAC DPDD document
XB
There is no feedback from teams concerning the DPDD template document from ESAC (see template here). XB assumes that there is no question or issue concerning this document and will send an email before the next telecon to propose a strategy for the writing of this document. In all cases, the idea is to avoid to many redundancies with data description already provided in existing documents (ESAC has indicated that references can be provided if required).
In practice, the description of RPW science data can be done in this DPDD, but the way the data are generated (including calibration) should be given in the RCS software user manual (SUM).
The case of the L1R data description must be clarified. ESAC indicates that the L1R data should be also described in the DPDD if the RPW team plans to archive it at ESAC. For the moment L1R is assumed to be an "internal" data level for RPW only, but there are possible options to archive them at ESAC too. See also the questions-answers between XB and Pedro Osuna from ESAC in the comments at the bottom of this page.
2. TDS status
DP, JS
DP indicates that creation and delivery of a first version of RCT files should be done before the end of the week. The delivery concerns RCT for a high frequency mode and magnetic component.
The generation of a first set of TDS L1R CDF is possible with the TDS_CALBA 0.8 version. TDS team should be thus ready to generate L1R CDF when ROC will publish ROC-SGSE L1 V3 CDF.
2. Bias status
EJ
First version of RCT files for Bias should be available before the end of March.
2. THR status
QN
QN has to discussed with Milan and Lorenzo about the RCT as well as documentation status for THR.
XB can organize a dedicated meeting with the THR team if required
3.
All
XB has received no feedback from teams concerning the new RCS ICD 1.2, REGU 2.1 and RDP 1.2 versions. It is assumed that there is no issue with this new versions, and the draft will be frozen and officialy released. Applicability of these new versions will be discussed at the next telecon, nevertheless teams are invited to start upgrading of their RCS and CDF skeletons to include new features. Any question can be sent to XB.
4.
All
Next ROC RCS telecon #15 is planned on Monday, 23th of April 2018.
5.
EJ suggest to not used anymore the Excel format to generate the CDF skeleton files (but used ASCII skeleton table files directly). He points out, among other, that the Excel format cannot permit to easily check if skeleton structure is ok and can be converted without error into master binary CDF. XB reminds that the Excel format was initially introduced to support teams, which were not familiar with CDF skeleton concept, and there is no problem from the ROC point of view to abandon this format if teams agree. But, it is admited that it is not an urgent task to do, and the priority should be done first on the achievement of the current open tasks (i.e., RCS CDF science and RCT skeletons, data generation and validation).