Page History

...

RPW data general questions

Where can I find Solar Orbiter SPICE kernels?

Which standards applied to the RPW data?

The standards for Solar Orbiter science data are defined All SOC-provided Solar Orbiter SPICE kernels retrieved by the ROC are made available in https://rpwissues.lesiacosmos.obspmesa.frint/rocsolarorbiterwiki/datadisplay/private/solo/soc/spice/ (restricted access).

For more details about:

• SOC-provided ancillary data products: https://issues.cosmos.esa.int/solarorbiterwiki/display/SOSP/SOC-Provided+Ancillary+Data+For+Solar+Orbiter
• Solar Orbiter SPICE kernels: https://issues.cosmos.esa.int/solarorbiterwiki/display/SOSP/Solar+Orbiter+SPICE+Kernels
• SPICE software: https://naif.jpl.nasa.gov/naif/index.html

CDF-related questions

What is a "skeleton table"?

SOSP/Metadata+Definition+for+Solar+Orbiter+Science+Data.

Especially, this document provides the conventions in terms of file format, naming and data versioning.

All RPW science data must comply these standards.

N.B. Solar Orbiter science data standards partially rely on the ISTP/IACG CDF guidelines (see https://spdf.gsfc.nasa.gov/sp_use_of_cdf.html).

Where can I find Solar Orbiter SPICE kernels?

All SOC-provided Solar Orbiter SPICE kernels retrieved by the ROC are made available in https://rpw.lesia.obspm.fr/roc/data/private/solo/soc/spice/ (restricted access).

For more details about:

• SOC-provided ancillary data products: https://issues.cosmos.esa.int/solarorbiterwiki/display/SOSP/SOC-Provided+Ancillary+Data+For+Solar+Orbiter
• Solar Orbiter SPICE kernels: https://issues.cosmos.esa.int/solarorbiterwiki/display/SOSP/Solar+Orbiter+SPICE+Kernels
• SPICE software: https://naif.jpl.nasa.gov/naif/index.html

CDF-related questions

What is a "skeleton table"?

A "skeleton table" A "skeleton table" is an ASCII format file used to generate a "master" binary CDF file.

...

More details can be found in https://pypi.org/project/maser4py/.

How to check RPW CDF compliance

...

against Solar Orbiter data standards?

There is no ESA-provided software to check CDF compliance against ESAC Solar Orbiter data standards (SOL-SGS-TN-0009).

...

How to check RPW CDF compliance

...

against NASA ISTP/SPDF data standards?

The NASA-provided software SKTeditor (https://spdf.gsfc.nasa.gov/skteditor/) can be used  to check compliance of CDF file against NASA ISTP/SPDF data standards.

An instance of the SKTeditor is installed in the roc2-dev.obspm.fr server to run CDF check using the dedicated command line interface (see "How to run the NASA SKTeditor CLI  in the roc2-dev.obspm.fr sever?")

...

• 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.

• )
• 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.

How can I deliver my RPW calibration table (RCT) file to ROC ?

The RPW calibration table (RCT) files must be delivered as CDF files in the dedicated SFTP server at LESIAThe 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 packagecalibration table files.

How can I deliver my RPW calibration table (RCT) file to ROC ?

The RPW calibration table (RCT) files must be delivered as CDF files in the dedicated SFTP server at LESIA. Table below gives for each team the user account and target folder to be used to deliver the calibration table files.

...

How to deliver a CDF skeletons file to ROC?

The mechanism to deliver CDF skeletons 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:

• CDF skeletons must be delivered as a skeleton table in the ASCII format
• CDF skeletons must be "pushed" by teams in the "SOLO/RPW/CDF/Skeleton" folder of the ROC "DataPool" Git respository (https://gitlab.obspm.fr/ROC/DataPool)
• CDF skeletons can be only "pushed" by teams in the "rcs" branch of the ROC "DataPool" Git respository

How to deliver RPW L3 CDF files to ROC?

RPW L3 CDF files are not generated by the ROC at LESIA, but they must be delivered to the ROC which will be in charge of validating the files, sharing them in the RPW private/public data servers and deliverying them to Solar Orbiter Archive (SOAR).

There are few rules to follow when deliverying files:

• Make sure that RPW L3 CDF files are compliant with RPW/Solar Orbiter data standards (add link)
• L3 CDF files must be dropped in the dedicated folder in the ROC SFTP server at LESIA (contact ROC team for details)
• The descriptor field of the CDF filename must be appended with the "-cdag" suffix (e.g., "solo_L3_rpw-tnr-fp-cdag_20230102_V01.cdf")

If one these rules are not fullfiled, then the ROC will reject the delivery of RPW L3 CDF files.

What is the software environment used by the ROC at LESIA to run RCS?

Information about the ROC software environment can be found in Software environment

How to deliver a CDF skeletons file to ROC?

The mechanism to deliver CDF skeletons 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:

• CDF skeletons must be delivered as a skeleton table in the ASCII format
• CDF skeletons must be "pushed" by teams in the "SOLO/RPW/CDF/Skeleton" folder of the ROC "DataPool" Git respository (https://gitlab.obspm.fr/ROC/DataPool)
• CDF skeletons can be only "pushed" by teams in the "rcs" branch of the ROC "DataPool" Git respository

RCS-ROC interface-related questions

...