| Item | Notes | Action-items |
|---|
| 1.a | - Fully automatizing the production of L1 CDF is still on-going (test phase)
- Will be triggered every 24h nominally
- New L1 CDF generated if new L0 file (version) is created
- L1 Anomaly status
|
|
| 1.b | - RPW HK CDFs are produced nominally (run every 24h)
|
|
| 1.c | - 200604_RCS_Telecon22.pdf
- During commissioning, production has been done manually "on demand"
- Automatization in progress
- Will be triggered every 24h (see ROB discussion)
- New L1R/L2 CDF (version) generated if:
- Parent L1/HK CDF(s) haven been produced/updated
- New set of SPICE kernels has been released and requires to update geometry computation
- L1R/L2 "cdag" CDFs will be shared on the ROC Web site (private area) as soon as their are produced
- After 3 months, L2 "cdag" CDFs will be copied into the ROC public Web site (https://rpw.lesia.obspm.fr/roc/data/pub/solo/rpw/data/L2/) - "cdag" field will be removed from the filenames - Version of the CDFs will set to "01" - Copy of the files will be delivered to Solar Orbiter public archive at ESAC
| - Action Xavier: Discuss at the ROB telecon about the data sharing (shared only time-stamped)
|
| 1.d | |
|
| 1.e | - Publication of summary plots sent by teams is up-and-running (performed every 24h)
- Implementation of the production at LESIA is still to be done
| - Action RCS teams: Provide before the next telecon to Xavier the list of summary plots expected to be generated
 (the list will be add to RPW Data Products)
|
| 2.a | | |
| 2.b | - Implementation is on-going
- ROC side:
- Inputs/outputs/logs of the "failed" cases will be automatically moved in a dedicated directory (accessible from both ROC and RCS teams)
- Discussion to automatically create an issue on Gitlab with emails to people in charge
| - Action Quynh Nhu: Implement "failed" L1R/L2 CDF prod. in the ROC pipeline
 - Action Xavier: Provide to the Teams a first list of the L1/L1R/L2 CDF points of automated checking implemented or to be implemented in the pipeline
|
| 2.c | - Full automatization of some L1R/L2 CDF productions at LESIA requires to provide context information about RCT to the RCS
- Proposal is
- 1 file per RCS
- JSON format
- File delivered by team in charge
- New version of the file provided with any new RCT file (i.e. droped in the "cal" folder of the RCS team in the ROC SFTP at LESIA)
| - Action RCS Team: To be applied new calibration table file naming convention for the future file delivery
 - Action Xavier: To send before the next RCS telecon an update proposal for the calibration catalog files
|
| 2.d | |
|
| 3. | - ROC RCS-related documentation status:
- RCS ICD 1.3 up-to-date with SPICE kernel/exit code implementation (see ROC Documents)
- REGU update is on-going (to include the new procedures for deliverig RCS-related files via the LESIA SFTP)
- ROC Data Products (RDP) → To be updated
- RCS documentation (see RCS Delivery Status & Action-Items for SRS/UM status)
- RPW L2 data processing status in the "ROC commissioning report"
|
|
| 4. | - ROC Software System Version 5 (RSS5) to be released on end of June 2020
- Include
|
|
| 6. | - Next RCS telecon planned on TBD
|
|
| 7. | |
|
