...
All SOC-provided Solar Orbiter SPICE kernels retrieved by the ROC are made available in https://rpw.lesia.obspm.fr/roc/data/private/solo/esa/soc/spice/ (restricted access).
For more details about:
...
For more information about the CDF and skeleton/master mechanism, visit http://cdf.gsfc.nasa.gov/.
How to deliver a skeleton CDF file to the ROC?
The mechanism to deliver skeleton CDF 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:
...
...
...
...
| Info | ||
|---|---|---|
| ||
Every "commit" should be commented to have a traceability of the changes. |
How to generate a skeleton or master CDF file from an Excel format file?
...
More details can be found in https://pypi.org/project/maser4py/.
RCS
...
software and product delivery questions
How a RCS software must be delivered to
...
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).
...
- 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"
How can I deliver my RCS test data package to ROC ?
The RCS test data package is required by the ROC Team to check that a given version of the RCS works as expected. Every version of the RCS software must hence be delivered with its test data package.
The RCS test data package must be delivered using the sftp-lesia.obspm.fr server. Table below gives for each team the user account and target folder to be used to deliver the test data package.
| Team in charge | RCS name | SFTP user account | Target folder in the SFTP server |
|---|---|---|---|
| BIAS | BICAS | solbia | /obs/solbia/testdata |
| LFR | LFR_CALBUT | sollfr | /obs/sollfr/testdata |
| SCM | SCMCAL | solscm | /obs/solscm/testdata |
| TDS | TDS_CALBA | soltds | /obs/soltds/testdata |
| THR | THR_CALBAR | solthr | /obs/solthr/testdata |
| Info | ||
|---|---|---|
| ||
|
How can I deliver my RPW calibration table file to ROC ?
The RPW calibration table files must be delivered as CDF files in the dedicated SFTP server at LESIA.
The mechanism to deliver the RPW calibration table files 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.
How to deliver a skeleton CDF file to ROC?
The mechanism to deliver skeleton CDF 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:
- Skeleton CDFs must be delivered as a skeleton table in the ASCII format
- Skeleton CDFs must be "pushed" by teams in the "SOLO/RPW/CDF/Skeleton" folder of the ROC "DataPool" Git respository (https://gitlab.obspm.fr/ROC/DataPool)
- Skeleton CDFs can be only "pushed" by teams in the "rcs" branch of the ROC "DataPool" Git respository
| Info | ||
|---|---|---|
| ||
Every "commit" should be commented to have a traceability of the changes. |
RCS-ROC interface-related questions
What is the descriptor file?
...
RPW Calibration Tables-related questions
How can I deliver my RPW calibration table file?
The RPW calibration table files must be delivered as CDF files in the dedicated SFTP server at LESIA.
The mechanism to deliver the RPW calibration table files is described in the "ROC Engineering Guidelines for External Users" document (REGU) [ROC-GEN-SYS-NTT-00019-LES].
...
Miscellaneous questions
Where I can find the list of acronyms relative to the ROC project?
...