1. RCS integration status 2. EMC preliminary data 3. ROC pipelines and data product status 4. RCS software and data product status 5. Planning 6. Next RCS telecon 7. AOB
Discussion items
Item
Notes
Action-items
1.
RCS integration
Integration of THR_CALBAR is done (minor corrections to do and test data verification to be implemented)
Integration of LFR_CALBUT is in progress
Integration of TDS_CALBA is in progress
Integration of SCMCAL has started
Integration of BICAS is postponed (not before mid-July)
RCS test data
TBW
Xavier will write a short document describing the RCS verification/validation test activities – Still to be done
Data for May 21 are missing. The CNES team is waiting from input of ADS
Eric will provide more details about EMC during the ROB telecon on at 10am
Data files have been generated using the mission filenaming convention (except free_field part) and with CDF skeleton V04 (only available for the moment in the "roc" branch of the DataPool repository : https://gitlab.obspm.fr/ROC/DataPool/tree/roc)
3.
RODP pipeline
Working with MOC DDS XML files is up-and-running
First version of the DDS Python client has been delivered by the SPICE team at IAS, implementation in the ROC pipeline should be started within few weeks
Export in MEB GSE test log XML files is in progress
Export in ADS GSE ASCII files (usable by the CNES PRESTO tool) is done
New L1 LFR BP1/BP2 computation has been done, but need to be validated
Ancillary data processing is still to be done
ROC-SGSE pipeline
Instance is up-and-running (include processing of ADS GSE ASCII files used for EMC campaign)
RPW data products
RODP L1/HK/L1R/L2 skeleton CDF have been updated to be compliant with ESA standards (doc. still need to be updated). The resulting files are for the moment stored in the "roc" branch of the DataPool repository
ROC-SGSE L1/HK/L1R/L2 skeleton CDF have been merged with the mission skeletons (RODP). The resulting files are for the moment stored in the "roc" branch of the DataPool repository
All RPW skeleton CDF will be stored in a single SOLO/RPW/CDF directory in the DataPool repository
Teams will have to "push" skeleton table in ASCII format (.skt), instead of Excel format (.xlsx). Nevertheless the skeletoncdf tool in "maser4py" python package is maintained if teams want to work with Excel skeletons.