Discussion on RPW science data validation (ROC, THR, BIAS, LFR, SCM, TDS): description, task, workflow validation, human resources / team, responsibilities, constraints, anomalies, .. etc. | All | - Data validation
- Formal validation - How to?
- ROC checks automatically the metadata and structure
- Can also automate the checking of val_min/val_max (out of range values)?
- When formal validation is done → global attribute "Validate = 1" (validate flag)
- Science quality?
Idea: - Check if a value is lower than the sensitivity - Check if a value is constant - Check for discontinuities Teams are in charge of determining the quality flag If quality of the records is enough -> The ROC can set the validate flag to 2 ROC is responsible for the bitmask Science quality verification procedure: - Add a piece of software in the RCS to compute the quality flag - in case of problem -> generate a report to be sent to the scientist in charge
- SCM Problem : Only one quality flag for each x,y,z record (no quality flag by axis) Reference frame
| - Action Milan: Send an email to Alexis Rouillard and the MADAWG concerning the qualit_flag level definition in the SOL-SGS-TN-0009_2_2 document.
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-76 |
---|
|
- Action RCS teams: Define criteria to determine the quality flag
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-77 |
---|
|
- Action RCS teams: Fill the Excel sheets provided by the ROC and send it to XB
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-78 |
---|
|
- Action Xavier : Send a document that allows RCS teams to list the expected values for the bitmask
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-79 |
---|
|
- Action RCS teams: Determinate the bitmask content required to define the science quality flag
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-80 |
---|
|
- Action Xavier: Determine the full procedures for each data product/team
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-81 |
---|
|
- Action SCM team: See how to set the quality flag for each X,Y,Z axis records
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-82 |
---|
|
|
Discussion on RPW flight validation: description, task, workflow validation, human resources / team, responsibilities, constraints, anomalies, .. etc. | All | - roc_validation_workshop_flight_validation_intro_v01.pdf
- ROC has prepared specific Excel sheets for the in-flight validation activities of RPW. The main idea is to list all the activities and related relevant information in order to prepare these tasks (to ensure nothing has been forgotten)
- COMMISSIONING validation activity:
- The reaction wheels filtering should be added somewhere (during interference campaign or antenna rolls?)
- A 8th RPW activity should be asked to MOC to test the nominal working of RPW before the Cruise Phase (CP). Especially, all modes should be tested and run for enough long time (~24h) and nominal modes with other IS instruments should be run. If possible the SBM_DETECTION should be activated (but quick downlink of selective data is not garantuee for now during the NECP and CP phases)
- What about the inter-instrument communication (IIC) validation? Done during NECP or CP? Functional part (checking TM exchanged via S20 should be possible, but it would be difficult for the detection part without event).
| - Action Xavier: Verify with MOC/SOC if IIC/S20 flight validation campaign is planned and when
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-83 |
---|
|
- Action Xavier: Prepare and submit to MOC the 8th activity for RPW
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-84 |
---|
|
- Action teams: submit to the ROC (Xavier) a preliminary version of the "<XXXXX>_flight-data-validation_V<YYY>.xls"
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-85 |
---|
|
|
Splinter session RPW flight configurations | RPW lead CoI teams + Diane and Antonio | —————————————— - During commissioning HK at least every second (or even higher cadence if possible)
- iBoom deployement : In order to synchronize snapshots between LFR and TDS, TDS will increase the time between two snapshots to 11s (instead of 10s)
- Antenna + I-Boom + interference campaign : all sub systems in SBM1+normal mode. Same configuration for LFR and TDS for each campaign.
- LFR : temps entre 2 snapshots 22s
- TDS : 1 snapshot chaque seconde + 1 triggered toutes les 11s —> un snapshot every 11s, one simultaneously with LFR, one without LFR
- SCM agrees with LFR config
- LFR wants to add during interference campaign a configuration to test the reaction wheels effect.
- The LFR document for interference campaign has been transfered to the Bias team for filling its own doc.
—————————————— - The daily 10 min. of SURVEY_BURST mode do not take too much telemetry rate (<5%) so we can let it. But the SBM1 mode has significant telemetry rate.
- For LFR, the main goal is to have the higher cadence as possible for the BP.
- TDS has no specific constraint
- 2 configs for low rate :
1) - LFR :
- no SBM,
- 10 min of SURVEY_BURST,
- time between two snapshots 1800s;
- time between two ASM : 3600s,
- time between BP : 8s;
- time between 2 products : 40s
- TDS :
- Time between 2 RSWF : 1800s;
- Time between 2 TSWF : 7200s
—> cf calculator LOW RATE 1 (TODO : Put the ref)
2) - LFR :
- SBM1 activated
- 10 min of SURVEY_BURST,
- time between two snapshots 3600s;
- time between two ASM : 3600s,
- time between BP : 16s;
- time between 2 products : 60s
—> cf calculator LOW RATE 2 (TODO : Put the ref)
————————————————————— LFR calibration : snapshots every 22 s (change in LFR software in progress).This will have a slight impact on the data rate because currently the same configuration is kept in NORMAL-DEFAULT: 1 snapshot every 300s Action Jan : correct word file with 11s. | - All team will provide word files about antenna, I-Boom and Interference campaign before the end of next week
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCOPE-217 |
---|
|
- Action Antonio : Put on Git the two calculator sheets for the low-rate config.
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCOPE-218 |
---|
|
- Action Diane : Send Action Diane : Send the calculator sheets with the two low rate config to LFR and SCM (TDS already has them).
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCOPE-219 |
---|
|
- Action Antonio : Put on Confluence the page with all the Action Antonio : Put on Confluence the page with all the nominal configs (as well as the fixed parameters) and send the url to the teams.
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCOPE-220 |
---|
|
- Action Diane : Add LFR calibration in the calculator sheet (Action Diane : Add LFR calibration in the calculator sheet (because in low-rate we stay in default for the calibration)
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCOPE-221 |
---|
|
|
Splinter session : ROC validation traceability | CNES + Stephane Papais + Sonny Lion | 1. Sonarqube - Code Analysis Actions to be carried out by LESIA (Sonny Lion) with Stéphane Papais support : - Finalize metrics according to CNES specifications document - Installation of Sonarqube on the ROC Dev platform => November 2018 - Objective on Sonarqube: implement for the RSS3 validation campaign => End of December 2018 - Tests reports perimeter : based on RSS3 | Splinter session : ROC validation traceability | CNES + Stephane Papais + Sonny Lion | - Splinter Segment Sol / ROC : 1. Sonarqube / Analyse des codes Etat des lieux : - Screen shot de métrix en fonction : MUSIC Pas encore de RODP Pipeline - il manque des plugins, à fournir par le CNES (Dominique Bagot) => pour faire des rapports des tests du CNES Actions à réaliser par le LESIA (Sonny) avec le support de Stéphane Papais : - Finaliser les métriques selon le document des specifications du CNES - En Novembre : Installation de Sonarqube sur la plateforme ROC Dev - Finalité ou objectif sur Sonarqube : implémenter pour la campaigne de validation RSS3 => fin décembre 2018 - Périmètre des rapports de tests : RSS3 => Music (Faust / Figaro), ROC-SGSE, LLVM Actions à réaliser par Actions to be taken by Dominique Bagot: - Réaliser l'analyse de codes avec Sonarqube sur le périmètre RSS3 2. Plan de tests / validation : - Realize the code analysis with Sonarqube on RSS3 => December 2018
2. Validation Plan Actions to be carried out by Actions à réaliser par le LESIA (Sonny) : - Définir le périmètre qui fera partie de la campagne de validation et lister les requirements associés - Define the scope that will be part of the validation campaign and list the associated requirements (RSS3)
- Compléter le plan de validation avec les différentes procédures de tests - Complete the validation plan with the different test procedures (test case)
- Compléter la matrice de traçabilité entre le RSSS et les plans de tests - Complete the traceability matrix between the RSSS and the test plans => Sonny Lion
avec le de - Faire les liens entre les différents tests unitaires/intégration et les procédures de tests - Papais
- Make the links between the different unit tests / integration and the test procedures (test case) => Sonny Lion
- Identifier / distinguer les testeurs (techniques ou fonctionnels (beta testeur- Identify / distinguish the testers (technical or functional (beta tester)) => cf.
exemple du projet Taranis - Faire référencer les tests unitaires / intégration- example of the Taranis project
- Referencing unit tests / integration
| - Action Sonny (with support of Stéphane):
- Finalize the metrics according the CNES Quality requirements doc.
Jira |
---|
showSummary | false |
---|
server | jira-lesia.obspm.fr JIRA |
---|
serverId | cb08a004-0694-3237-bcb1-3125e3ed9bc0 |
---|
key | ROCMAN-86 |
---|
|
- Install Sonarqube in the Install Sonarqube in the ROC dev. machine
- Prepare Sonarqube to be used for the RSS3 validation "rehearsal" campaign
- Action Dominique : Do an analysis of the ROC code with Sonarqube in prevision of the RSS3 release
Action Sonny:
- Define the perimeter for the RSS3 validation campaign (and associated requirements)
- Complete the validation plan with the test procedures (test cases)
- Complete the traceability matrux between RSSS and the test plans (with the support of Stéphane)
- Link the unit/integration tests and the test cases
- Identify the actors for the validation campaign
Make reference for the unit/integration tests
| Conclusion | - Planning : - Planning de la campagne de RSS3 : novembre 2018 (à confirmer) - Livraison PTF de RSS3 au CNES : mi-décembre 2018 Cette livraison contiendra : - Logiciels - Documentation (et le niveau de mise à jour des documents) Au moins des versions livrées pour les workshop de specs et de validation - Le LESIA précise qu'il est difficile d'avancer (en raison des contraintes des ressouces RH / manque d'un développeur) sur le développement des outils et la documentation. - Actions à prendre en compte suite au workshop de validation : - Rappel sur les actions du workshop des spécifications et ses échéances à suivre (et documents identifiés à mettre à jour) - Le workshop de validation a permis de définir un roadmap pour les aspects de validation ROC => enrichissement des fichiers excel + traduire dans le plan de validation - Teleconf mensuel avec les participants plus étendus (CNES, LESIA, LeadCoI, Instrument scientis) => cohérence des actions / roadmaps - Prochain workshop validation ? A quand ? Faut-il maintenir s'il y a les teleconfs mensuels - Prochains Consortium meeting à Kiruna (Mars 2019) => la thématiqiue du segment sol à ajouter (présentations + sppliters) pour permettre de suivre des actions du workshop et du roadmap - Validation des données sciences avec les équipes : 1) Compléter les fichiers des validations : 15 décembre 2018 => version finale cible : RSS4 => sa'ssurer la conhérence de la cible : implémentation logiciels / documentation /exigences / périmètre - Operations (A compléter par Diane) - Configurations => fin septembre - Low Rate 2 configuration SBM_Detection (snapshot espacé) - Burst (10 min), normal - TDS => fin septembre - LFR => ? - Validation du telecon mensuel (participants étendus) à mettre en place => mi-octobre pour discuter en octobre 2018 - Mettre en place un working group une réunion mensuelle : ROP et équipe ROC (LESIA et CNES), LeadCoI - Consortium meeting : mars 2019 => thématiques segments sols + splinters |