Page History

...

Item

Notes

Action-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
Jira
showSummary false
server jira-lesia.obspm.fr JIRA
serverId cb08a004-0694-3237-bcb1-3125e3ed9bc0
key ROCDATPRO-111
Action Rodrigue: Review the ROC-SGSE L1 BP1/BP2 CDF skeletons to ensure that the expected zVariables are defined
Jira
showSummary false
server jira-lesia.obspm.fr JIRA
serverId cb08a004-0694-3237-bcb1-3125e3ed9bc0
key ROCDATPRO-112
Action Xavier: Update the ROC pipeline code in order to write the ROC BP1/BP2 human-readable" values in the LFR L1 CDF
Jira
showSummary false
server jira-lesia.obspm.fr JIRA
serverId cb08a004-0694-3237-bcb1-3125e3ed9bc0
key ROCDATPRO-113

2.

The ROC team wants to start the integration of the RCS software into the pipeline
On the ROC side, a "testing" instance of the pipeline should be available within few weeks to allow RCS teams to check that the software is compliant with the RCS ICD 1.2 (see https://confluence-lesia.obspm.fr/display/ROC/ROC+Documents?preview=/3113240/15761536/ROC-PRO-PIP-ICD-00037-LES_Iss01_Rev02(RPW_Calibration_Software_ICD).Draft.pdf)
On the RCS team side (and LFR in particular), the ROC team asks to check that the software can be run as described in the RCS ICD (i.e., with the right command line interface and using the right environment variables)
The ROC will test the software using the "master" branch of the RCS dedicated repositiory on gitlab (cf. https://gitlab.obspm.fr/ROC/RCS/LFR_CALBUT for LFR)
As explained in the REGU 2.1 (see https://confluence-lesia.obspm.fr/display/ROC/ROC+Documents?preview=/3113240/15761535/ROC-GEN-SYS-NTT-00019-LES_Issue02_Rev01(Engineering_Guidelines_For_External_Users).Draft.pdf) the test will be driven by the ROC and will mainly consist of:
- Retrieve the software directory (e.g. git clone https://gitlab.obspm.fr/ROC/RCS/LFR_CALBUT for the first time or git pull after), if required retrieved the right L1R/L2 master CDF (from Datapool git repo.), the right calibration table files and the corresponding test data (examples of L1/L1R/L2 data products)
- Run the software with the pipeline to check that the calling works as expected (software can be run correctly by the pipeline)
- Compare software output files generated by the pipeline with the corresponding "test" data provided by the RCS team (the pipeline just check that there is the same content. There is no verification of the data quality)
The ROC and LFR teams should start to test the integration around mid-March 2019.

Action Quynh Nhu: Deploy an "testing" instance of the ROC pipeline to help teams to test their RCS calling
Jira
showSummary false
server jira-lesia.obspm.fr JIRA
serverId cb08a004-0694-3237-bcb1-3125e3ed9bc0
key ROCDATPRO-114
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)
Jira
showSummary false
server jira-lesia.obspm.fr JIRA
serverId cb08a004-0694-3237-bcb1-3125e3ed9bc0
key ROCDATPRO-115
Action Rodrigue: Provide L1R/L2 "test" data CDF samples to the ROC
Jira
showSummary false
server jira-lesia.obspm.fr JIRA
serverId cb08a004-0694-3237-bcb1-3125e3ed9bc0
key ROCDATPRO-116

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
Jira
showSummary false
server jira-lesia.obspm.fr JIRA
serverId cb08a004-0694-3237-bcb1-3125e3ed9bc0
key ROCDATPRO-117

...

Space shortcuts

Page tree

Versions Compared

Old Version 9

New Version Current

Key