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 performed using dedicated instances of the ROC-SGSE and RODP, deployed on the roc-dev.obspm.fr server.
Moreover, instances 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 the instances is described in the "RCS Interface Validation Pipeline User Manual" (will be provided soon).
- The identifier of the RCS in the descriptor file shall be: "THR_CALBAR", "SCMCAL", "LFR_CALBUT", "TDS_CALBA" or "BICAS"
- The identifier of the RPW L1/HK input datasets shall be the same for the ROC-SGSE and RODP pipelines, i.e.., "SOLO_<LEVEL>_<DESCRIPTOR>, where <LEVEL> is the data processing level ("L1" or "HK") and <DESCRIPTOR> is the prefix of the CDF global attribute descriptor.
- The "L2S" data processing level is no more used for the ROC-SGSE, and shall be replaced by "L2".
RCS INTEGRATION TESTS
The RCS integration tests are performed by the ROC team, using representative enough RCS input/ouput "test" data samples. The objective is to ensure that the RCS produce the same L1R/L2 CDF files, when they run as a "stand-alone" software (i.e., at the RCS team site) and as module of the ROC pipeline (i.e., on the roc server at the LESIA).
The tests consist of calling the RCS with a "pre-prod" instance of the ROC pipelines, in order to re-produce at the LESIA site the expected "test" output data. The ROC will use a "CDF comparison" tool to verify that the L1R/L2 CDF data generated by the RCS at the LESIA are similar to the one provided by the teams.
The "test" data samples shall be delivered by the RCS teams, as specified in the REGU (see ROC-GEN-SYS-NTT-00019-LES in the ROC Documents). The ROC team can however help the teams to identify and supply the input "test" data (for instance, some L2 and L1R output data CDF require input L1/HK CDF that can only by generated by the ROC pipelines).
- There must be one set of "test" data files for each RCS data product and each ROC pipeline (ROC-SGSE or RODP).
- The aim of the integration tests is not to check the validity of the L1R/L2 output data content (e.g., in terms of data quality/calibration), but just to ensure that the behaviour of the RCS is as expected when it is run into the ROC pipelines.
RCS VALIDATION TESTS
The RCS validation tests shall allow the ROC to validate the requirements and specification related to the RCS and their data products.
See ROC System Test Documentation