Information related to the RCS testing/validation activity.
INTRODUCTION
The RPW Calibration Software (RCS) will be run into the ROC pipelines, i.e., ROC-SGSE for RPW datasets generated on-ground with the GSE and the RODP for the RPW datasets produced in-flight, using a dedicated interface.
Three series of tests in charge will be performed by the ROC team and in collaboration of the teams, in order to ensure that the RCS works as expected:
- RCS compability tests → Verify that the RCS interface is compliant with the RCS ICD
- RCS integration tests → Verify that the RCS has the expected behaviour and generate the right data products, when run in the ROC pipelines at LESIA
- RCS validation tests → Validate the full RCS testing and data production at LESIA, including the compliance of the data products with the Solar Orbiter data standards (see SOL-SGS-TN-0009 in https://issues.cosmos.esa.int/solarorbiterwiki/display/SOSP/SOC+Documents)
RCS COMPATIBILITY TESTS
The RCS compabitilty tests consist of checking that the software interface is compliant with the RCS ICD specification (see ROC-PRO-PIP-ICD-00037-LES available in ROC Documents).
The tests are run using dedicated instances of the ROC-SGSE and RODP, deployed on the roc-dev.obspm.fr server.
An instance of the RIVP will be made available to the teams to test their software interface compliance, before deliverying to the ROC.
The way to use this instance is described in the RIVP User Manual (will be provided soon).
RCS INTEGRATION TESTS
The RCS integration tests are performed by the ROC team, using representative enough "test" data samples; one set of files for each RCS data product.
The "test" data samples shall be delivered by the RCS teams, in collaboration with the ROC, as specified in the REGU (see ROC-GEN-SYS-NTT-00019-LES in the ROC Documents).
The RCS integration tests consist of running the RCS on a "pre-prod" instance of the ROC pipelines