Page History

...

• Skeleton CDFs must be delivered as a skeleton table in the ASCII format
• Skeleton CDFs can must be only "pushed" by teams in the "rcs" branch SOLO/RPW/CDF/Skeleton" folder of the ROC "DataPool" Git respository

Once a local copy of the is available (see next question below to know how to get it), the skeleton file(s) to submit must be saved into:

...

• (https://gitlab.obspm.fr/ROC/DataPool)
• Skeleton CDFs can be only "pushed" by teams in the "rcs" branch of the ROC "DataPool" Git respository

RCS software-related questions

How a RCS software must be delivered to the ROC?

The mechanism to deliver RCS software to the ROC is presented in the "ROC Engineering Guidelines for External Users" (REGU) document (see ROC-GEN-SYS-NTT-00019-LES, available in ROC Documents).

In summary:

• RCS software must be delivered with at least the source code and the executable "ready-to-be-used" on the roc-dev server. The executable can be a script or a binary file.
• RCS software must be delivered with the up-to-date documentation (user manual, software specification and design)
  
• RCS software must be delivered with the up-to-date descriptor file (see RCS ICD for more details, available in ROC Documents)
• RCS software must be "pushed" on the "master" branch of the dedicated project in the https://gitlab.obspm.fr/ROC/RCS group. There is one project by RCS
• Every RCS software delivered must be tagged on Git with a version (use "git tag" command for this)
• The ROC team must be informed each time a new version of the software is "pushed"

Then, enter the following commands in the given order:

1. git add skeleton_filepath1 skeleton_filepath2 ... (where "skeleton_filepath1", "skeleton_filepath2", etc. are the relative path to the skeleton files to submit)
2. (git pull)
3. git commit -m "write here a comment to describe what it is done"
4. git push

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 comment is mandatory in the "git commit" command.
• The command "git add --all" can be used to include automatically all the files to commit (use with caution).

ROC Gitlab-related questions

...

...

RCS issue management questions

How can I access to the ROC JIRA projects?

The access is restricted. Creating an account can be requested to Xavier Bonnin.

Where can I submit an issue related to the RCS or the ROC pipelines (software, data products, documentation, etc)?

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:

• A summary
• A description
• An assignee
• The type of task
• The priority
• Eventually the related components (if any)

The following convention shall be used about issue:

...

Where I can submit issues in case of problems?

Any issue related to a given RCS must be submitted using the dedicated issue tracking interface in the RCS project on the "ROC/RCS" gitlab group.

The table below lists the URLs of the issue tracking interface for each RCS:

How can I access to the RCS issue tracking interface?

The access is restricted and must be requested to the RPW ground segment project manager.

RPW Calibration Tables

...

-related questions

How can I deliver my RCT file?

...