Frequently Asked Questions concering the RCS.
The CDF generation principle for RPW is described here.
For more information about the CDF and skeleton/master mechanism, visit http://cdf.gsfc.nasa.gov/.
Once a local copy of the "rcs" branch of the ROC "DataPool" Git respository is available (see next question below to know how to get it), the skeleton file(s) to submit must be saved into:
Be sure that skeleton files are committed in the "rcs" branch, before pushing to the remote repository. |
Then, enter the following commands in the given order:
The first command will add the skeleton files to the next commit (i.e., here the next files to be uploaded). The second command is optional but highly recommended, and ensure that there is no conflict between the local and the remote repository. The third command perform a local commit (see Git documentation about the commit concept). The fourth command "push" (i.e., upload) the files to the remote repository on the ROC Gitlab server.
NOTES:
The RCS skeleton CDF files must deliver to the ROC team using Git.
The "DataPool" Git respository to use is hosted on the ROC Gitlab server. Before working with this repository, be sure that you have the right access permissions (if not, please contact the ROC team using the roc.support mailing list). To know how to access to this repository, see next question.
To get a local copy of the "DataPool" repository (i.e., clone), enter the following command from a terminal:
git clone https://gitlab.obspm.fr/ROC/DataPool (HTTPS)
or
git clone git@gitlab.obspm.fr:ROC/DataPool (SSH)
If everything goes right, you should have a local folder "DataPool" in your system.
By default, Git will download the "master" branch only. This branch is protected and contain the skeleton/master CDF files actually used by the ROC. In order to submit their skeleton CDF files, the RCS teams must use the dedicated "rcs" branch. |
To switch to the "rcs" branch, enter the following commands in the given order :
The first command creates the local branch "rcs" and switches to this new branch. The second one synchronizes the local branch with the remote branch "origin/rcs" on the ROC Gitlab server. The third command downloads (i.e., merges) data from the remote branch "origin/rcs" into the local branch "rcs.
NOTES:
|
The access is restricted. Creating an account can be requested to Xavier Bonnin.
You can use the dedicated ROC-DATAPROD JIRA Page: https://jira-lesia.obspm.fr/projects/ROCDATPRO/summary.
When creating a new issue, be sure to indicate at least:
The following convention shall be used about issue:
Entity concerned by the issue | Issue summary prefix | Mandatory component(s) |
---|---|---|
BIAS | "[BIA] - " | BIAS |
SCM | "[SCM] - " | SCM |
LFR | "[LFR] - " | LFR |
TDS | "[TDS] - " | TDS |
THR | "[THR] - " | THR |
ROC | "[ROC] - " | ROC |
All entities | "[ALL] - " |
The mechanism to deliver the RPW Calibration Table files (RCT) is described in the "ROC Engineering Guidelines for External Users" document (REGU) [ROC-GEN-SYS-NTT-00019-LES].
The latest issue of the REGU is available in the ROC Documents page.
The list of acronyms are available here: Acronyms and Definitions