RCS Release Opportunity Planning

This page provides to the RCS teams the deadlines at which they can deliver a new software version to the ROC

Context

With the increasing volume of RPW data generated during the Solar Orbiter mission, re-processing and re-delivering new versions of data files become a tedious as well as long work for both the ROC team at LESIA and Solar Orbiter Archive (SOAR) team at ESAC.

To improve the control over the full workflow and minimize the impact of this activity, the ROC team will proceed to RCS updates only at certain dates over the year.

RCS Release Opportunity Planning

Table below gives the deadlines for each RCS release opportunity. E.g. Every new versions of RCS received after February 2, 2024 will have to wait May 3, 2024 to be deployed in and run by the ROC pipeline.

It means that it is the responsibility of the RCS teams to ensure their new software versions are ready to be deployed and run at LESIA before these deadlines. Especially, the validation tests performed by the ROC team using the RCS test data must be passed prior to these dates.

NOTES:

• The dates listed below are not the dates of RPW data re-processing and re-delivering. It might need several days to ROC team to perform the full data re-processing then few more days to ensure the delivery to SOAR.
• This planning only concerns software runs by the ROC at LESIA. Especially, the RPW L3 data provided by the teams  and the summary plots are not concerned for the moment.
• If there is an urgent and motivated reason, the ROC team can decide to deploy and run a RCS software outside of the scope of this planning
• If a RCS software update has no impact on the data produced and does not require to re-generate all the CDF files, then it can be possible to not take account of this planning but after approval by the ROC.
• Procedures defined in REGU remain applicable here