...
The formal definition of the QUALITY_BITMASK CDF zVariable is provided in the "Metadata Definition for Solar Orbiter Science Data" document (SOL-SGS-TN-0009). There is one value per CDF record.
...
WARNING: QUALITY_BITMASK SETTING IS NOT FULLY IMPLEMENTED IN L1 CDF
The QUALITY_BITMASK values CDF_UINT2 zVariable in the RPW L1 CDFs are is set by the RPW operations and data pipeline (RODP) hosted at LESIA.
...
| Bit | Decimal value | Meaning | Justification | Computation | Comment | ||||||||||||||||||
| 1 | BIAS1_SWEEP - ongoing sweep | Ongoing sweep on ANT1 probe | Should be set from 100 ms before the sweep to 1 s after the sweep on a particular probe. | ||||||||||||||||||||
| 2 | BIAS2_SWEEP - ongoing sweep | Ongoing sweep on ANT2 probe | |||||||||||||||||||||
| 3 | BIAS3_SWEEP - ongoing sweep | Ongoing sweep on ANT3 probe | |||||||||||||||||||||
| 4 | EMC QUIET window | SolO payload is in EMC QUIET mode | Known from EMC_MAND_QUIET E-FECS event | ||||||||||||||||||||
| 5 | EMC NOISY window | SolO payload is in EMC NOISY mode | Known from EMC_PREF_NOISY E-FECS event | ||||||||||||||||||||
| 6 | Spacecraft roll manœuvre | Indicate when the spacecraft perform rolls | Known from *_ROLL E-FECS event | ||||||||||||||||||||
| 7 | Thruster firings | Indicate when the plateform thruster firings happen | Known from TMC+WOL E-FECS event | ||||||||||||||||||||
| RPW +Z ANT PA in the line of sight of the HGA during TX ON. | The HGA TX may have an impact on the RPW science measurement quality when the ANT PA in the HGA light of sight | To be determinated by ROC from SPICE computation | Not implemented | ||||||||||||||||||||
| SPICE Heat Shield Door is open | SPICE HSD may have an impact on the RPW +Z ANT bending effect | Known from HSD_SPICE_OPEN E-FECS event | Not implemented | ||||||||||||||||||||
| LFR setting has changed before the end of the current data samples acquisition | According to LFR data acquisition mechanism and CDF structure, it can be impossible for some dataset (i.e., SWF) to take of a LFR setting change - performed via a command execution on-board - in a CDF record time window. Users need nevertheless to be warned when such LFR setting change occurred during a data sample acquisition. | Known from the reception of the TM_LFR_TC_EXE_SUCCESS {YIW00139} S1 TM that confirms the LFR setting change | Not implemented | ||||||||||||||||||||
| Possible SWA-PAS high voltage contamination | SWA-PAS unit may provoke noise on RPW measurements | Inclusion of this event into the bitmask is TBC (quantification of the impact is TBD) | Not implemented | ||||||||||||||||||||
| BIAS1_ | EMC QUIET window | SolO payload is in EMC QUIET mode | Known from EMC_MAND_QUIET E-FECS event | EMC NOISY window | SolO payload is in EMC QUIET mode | Known from EMC_PREF_NOISY E-FECS event | Spacecraft roll manœuvre | Indicate when the spacecraft perform rolls | Known from *_ROLL E-FECS event | Thruster firings | Indicate when the plateform thruster firings happen | Known from TMC+WOL E-FECS event | BIAS1_SWEEP - ongoing sweep | Ongoing sweep on one probe. | Should be set from 100 ms before the sweep to 1 s after the sweep on a particular probe. | BIAS2_SWEEP - ongoing sweep | BIAS3_SWEEP - ongoing sweep | BIAS1_CURRENT_NONCONSTANT | Changes in biasing current may (1) not be instantaneous, and (2) may have uncertain timestamps. | Should be set from 100 ms before to 1 s after any change in bias current on a particular probe (including sweeps). | Not implemented | ||
| BIAS2_CURRENT_NONCONSTANT | |||||||||||||||||||||||
| BIAS3_CURRENT_NONCONSTANT | |||||||||||||||||||||||
For RPW L2 CDF
The zVariable QUALITY_BITMASK is set in the L1 CDF by the RPW data pipeline at LESIA and must not be changed by the RPW Calibration Software (RCS) when producing the L2 CDF. QUALITY_BITMASK bits allocated in L1 CDF must be saved "as is" in L2 CDF. To store information specific to L2 data, please use the dedicated L2_QUALITY_BITMASK CDF_UINT2 zVariable instead.
...
From this initial status, the RCS must then decide in an autonomous way to change or not the value of QUALITY_FLAG records, when transferring the quality information to the output RPW CDF. The RCS decision must rely on relevant data (i.e, QUALITY_BITMASK, other data, parent data, etc.) as explained in the next section.
...
The RCS cannot increase the value of a given QUALITY_FLAG record. Especially, the higher QUALITY_FLAG index (i.e. "4") is not used for L1/L1R/L2 CDF.
...
.
Computation
The detailed computation of the QUALITY_FLAG for each RPW L1R/L2 data product must be given in the RCS Software Requirements Specification (SRS) documents (see RPW Calibration Software Documentation).
...