Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Here are example CDF files for RPW L1 HFR data set (restricted access):


ROC CDF SKELETON CONVERSION PROCEDURE

Conversion of a CDF skeleton from the Excel forrmat 2007 to the skeleton table ASCII format

In order to convert a given Excel CDF skeleton file in the Excel 2007 format "skeleton.xlsx" into a ASCII skeleton table "skeleton.skt", you need to use the MASER-PY "maser4py" python package.

The MASER-PY Python 3 maser4py package can be downloaded following the instructions given here:installed using pip:

pip install maser4py

See https://

...

pypi.

...

python.

...

org/

...

pypi/maser4py for more details.

Conversion of a CDF skeleton table to the master CDF binary file

The maser4py package

...

Read the user manuel, available from the link above, for more information about the module use.

Note that the MASER-PY package program can be also used to generate both the ASCII skeleton and master CDF binary files.
Be sure that the NASA GSFC CDF software distribution V3.6 is installed on your system, and that the "skeletoncdf" program can be called from terminal.
(Visit visit [RD2] to download the GSFC CDF soft.)
Note that if the output CDF master filename is not provided, then skeletoncdf program will named it using the "CDF_NAME" parameter defined in the skeleton header.

...

(Be sure to use the BASH shell.)

For instance to test the GSFC CDF skeletoncdf program, juste Then enter:

skeletoncdf

It should be returned something like

...

SOME RULES TO KEEP IN MIND WHEN EDITING A CDF SKELETON FILE FOR THE ROC

ABOUT CDF VARIABLES

...

  • All of the CDF variables shall be zVariables

...

  • The first variable on the CDF file shall always be "Epoch" (becareful that the variable naming is case sensitive).

...

  • Except "Epoch", all of the variables shall be named using capital letters only, shall start with a letter and shall contain alphanumeric plus underscore and hyphens characters only

...

  • Variables of "Data" type shall be real or integer only: CDF_UINT1, CDF_UINT2, CDF_UINT4, CDF_INT1, CDF_INT2, CDF_INT4, CDF_REAL4, and CDF_REAL8.

...

  • The variables shall always be non-fixed "Record variance" (i.e., "T")

...

  • The "Number Elements" parameter of a given variable is always "1", except for CDF_[U]CHAR data type, where it gives the (maximal) number of characters in the string.

...

  • A scalar variable shall always has a 0 dimension (i.e., "Dims = 0)

ABOUT VARIABLE ATTRIBUTES

...

  • The "DEPEND_0" variable attribute value shall always be "Epoch".

...

...

  • The CDF data type of the following attributes shall match the corresponding zVariable data type: "VALIDMIN", "VALIDMAX", "SCALEMIN", "SCALEMAX", "FILLVAL".

...

  • Make sure to always give a default value for the following attributes: "VALIDMIN", "VALIDMAX", "SCALEMIN", "SCALEMAX", "FILLVAL". If you do not know which values to give to ["VALIDMIN", "VALIDMAX"] you should use the maximal data type encoding values, but not the FILLVAL value (e.g. for a "CDF_UINT1" data type, [0, 254]). Same, if you do not know which default values for the ["SCALEMIN", "SCALEMAX"] set, you should use the ["VALIDMIN", "VALIDMAX"] values. For the FILLVAL, please use the ISTP guideline values as explained above.


ABOUT CDF HEADER

...

  • The DATA ENCODING shall always be "NETWORK"

...

  • The MAJORITY shall always be "COLUMN"

...

  • The FORMAT shall always be "SINGLE"


REFERENCES

...