| 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 | - RCS Status
- Discrepancy in calibration table index convention between TDS_CALBA and SCMCAL → Fixing in progress by TDS in L1R
- 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)
ROCDATPRO-121
-
Getting issue details...
STATUS
|
| 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
ROCDATPRO-123
-
Getting issue details...
STATUS
(the list will be add to RPW Data Products)
|
| 2.a | - Implemented
- Matrix SCM ↔ Boom → SPICE kernel (FK) not in place
- CI test ok with SPICE kernels
| - Action Xavier: Check with Andrew about SPICE FK with SCM-Boom new matrix
|
| 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)
- readme.txt text file is used to provide contextual information about the issue
- See examples with SCMCAL in https://rpw.lesia.obspm.fr/roc/data/private/issues/rivp/SCMCAL/open/
- Discussion to automatically create an issue on Gitlab with emails to people in charge
- Any Suggestion/comment from Teams is of course welcomed
- No documentation for the moment
| - Action Quynh Nhu: Implement "failed" L1R/L2 CDF prod. in the ROC pipeline
ROCDATPRO-119
-
Getting issue details...
STATUS
- 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
ROCDATPRO-120
-
Getting issue details...
STATUS
|
| 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
- Static file name (former versions will be overwritten)
- 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)
- Contains the validity time range of each RCT file
| - Action RCS Team: To be applied new calibration table file naming convention for the future file delivery
ROCDATPRO-124
-
Getting issue details...
STATUS
- Action Xavier: To send before the next RCS telecon an update proposal for the calibration catalog files
ROCDATPRO-125
-
Getting issue details...
STATUS
|
| 2.d | - ROC will start to implement a first processing of the QUALITY_BITMASK values for L1 CDF
- First list of BITMASK values should be reviewed before implementation
- Some BITMASK values will be specific to L2 products
- RODP will set BITMASK values at L1 level
- RCS will use free bits to add extra BITMASK values in L2 CDFs
- Is the number of bits available enough to store all expected values in QUALITY_BITMASK ?
- See current proposed values in RPW Data Quality Verification
| - Action All: To check and complete if required the list of BITMASK values to be implemented in RPW CDFs before next RCS telecon
- Action Xavier: To see how the other IS teams handle/compute the QUALITY_FLAG zVar in L2.
|
| 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
- First delivery of RPW data products to the ESAC Solar Orbiter public archive
|
|
| 6. | - Next RCS telecon planned on June 2 at 2pm
|
|
| 7. | |
|