Goals

  • Discussions about the LFR BP1 decommutation
  • Discussions about the LFR_CALBUT integration into the ROC pipeline (requirements and road map)

Date

Attendees


Agenda

  1. LFR BP1 decommutation
  2. LFR_CALBUT integration into the ROC pipeline (requirements and road map)
  3. AOB



Discussion items

ItemNotesAction-items
1.
  • For now, the L0 data contains the RPW TM LFR BP1/BP2 packet parameters as defined in the RPW ICD (see RPW-SYS-MEB-DPS-ICD-000211-LES). The ROC pipeline just reads from L0 and saved into the corresponding RPW LFR BP1/BP2 L1 CDF
  • The way the the

    PA_LFR_SC_BP1_NVEC_Fi, PA_LFR_SC_BP1_ELLIP_Fi, 

    PA_LFR_SC_BP1_DOP_Fi parameters in the

    TM_LFR_SCIENCE_*_BP1_Fi LFR science packets are stored into the L0/L1 data is not fully clear (i.e., how extracted bits are saved into L0/L1 parameters?)

  • Rodrigue and Thomas will review the L1 CDF skeletons for LFR (starting with ROC-SGSE datasets into https://gitlab.obspm.fr/ROC/DataPool/tree/rcs/GSE/ROC-SGSE/CDF/Excel) and update them if required
  • Xavier will adapt into the ROC Python pipeline the LFR team C++ code to perform the full analysis of the BP parameters. The objective is to provide in the L1 CDF the "human-readable" BP1/BP2 values (not only the ICD-level "raw" decommutation values).
  • The implementation of this feature should not start before mid-March 2019.
  • Action Rodrigue: Send to Xavier the latest version of the C++ program used to analyse and extract the BP1/BP2  "human-readable" values ROCDATPRO-111 - Getting issue details... STATUS
  • Action Rodrigue: Review the ROC-SGSE L1 BP1/BP2 CDF skeletons to ensure that the expected zVariables are defined ROCDATPRO-112 - Getting issue details... STATUS
  • Action Xavier: Update the ROC pipeline code in order to write the ROC BP1/BP2 human-readable" values in the LFR L1 CDF ROCDATPRO-113 - Getting issue details... STATUS
2.
  • Action Quynh Nhu: Deploy an "testing" instance of the ROC pipeline to help teams to test their RCS calling ROCDATPRO-114 - Getting issue details... STATUS
  • Action Rodrigue: Ensure that the LFR_CALBUT software can be called as described in the RCS ICD 1.2 (with the right command line interface and using the reserved env. variables) ROCDATPRO-115 - Getting issue details... STATUS
  • Action Rodrigue: Provide L1R/L2 "test" data CDF samples to the ROC ROCDATPRO-116 - Getting issue details... STATUS
3.
  • Values inside BIAS HK CDF seem to be invalid
  • Xavier has reminded that currently the HK CDF provided HK values in "raw" TM units (conversion is thus required for some parameters to have "physical" values)
  • The ROC plans to provide HK CDF with "physical" values in the next few months. (RCS will be informed).
  • Action Rodrigue:  Check how the BIAS HK parameters are read and processed by the LFR_CALBUT ROCDATPRO-117 - Getting issue details... STATUS

Action items

Open issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Closed issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Attached items