Time | Item | Who | Notes |
---|
| ROC-SGSE software and L1/HK data products status | | - According to Jan, there might be an issue concerning the time resolution in the Epoch variable of the ROC-SGSE L1 SWF CDF. It should be nanosec, but microsecond found. Xavier will check that and let Teams know (see action-items)
|
| RCS software and L2R/L2S data products status | All | - L2R dataset is completey abandoned and replaced by the L1R, including for the ROC-SGSE (for the latter it was not fully acted by the ROC). Some documents need to be updated (see action items)
- LFR team said that the L1R will concern the WF data, but also the LFR BP1/BP2 datasets
- As decided during the last meeting on January, the L1R WF datasets must be splitted between E and B data, as for L2 WF datasets
- Xavier indicates that the ROC is interested to have more information about L1R. The TDS and LFR teams has inputs almost ready to be sent concerning the L1R.
|
| RODP software and L1/HK data products status | | - Xavier has started to update the content of the L1/HK CDF datasets to be compliant with the ESA specification defined in SOL-SGS-TN-0009.
- It results the creation of a new set of RPW datasets for the SOLO mission, which is distinct from the ROC-SGSE datasets. Xavier highlighted that it was not possible to use a common set for both SOLO/RPW and ROC-SGSE datasets. Nevertheless, most of the changes might concern the metadata and conventions (e.g., file naming).
- Same work will be done on the L2 CDF datasets. Xavier will update the meta-data, then notify the teams for validation.
|
| Quicklooks and L3/L4 datasets | All | - ROC asks the Teams to provide their needs in terms of quicklooks for their sub-system, to be produced by the pipeline. This concerns mainly L1/HK/L2 datasets. The ROC will start to generate a list for the L1/HK quicklooks, this list will have then to be validated and completed by the Teams.
- First list of quicklooks must be delivered before end of Sept. 2017.
- Same work should be started for the L3/L4 data products.
- ROC has indicated that the L3/L4 data products will be not processed by the ROC pipeline. However it might be interesting to identify if we want to archive and distribute also a part or all of the L3/L4 data at the ROC (e.g., direction-finding THR L3 datasets)
|
| Auxiliary data products | | - ROC will use SPICE kernels provide by the SOC for its pipeline and tools.
- ROC asks to teams to identify their needs in terms of orbit/attitude data. Especially, ROC needs to know if it has to produce CDF ancillary files, since SOC will do. ROC will send a document to be filled by teams to complete the needs.
|
| RCS ICD and guidelines | All |