...
For instance, the following table indicates where CDF file name fields come from in the case of the ROC-SGSE.
| Field | Origin |
|---|---|
| SourceName | Copy of the "Source_name" global attributes value in the corresponding Master CDF |
| Level | Copy of the "Level" global attributes value in the corresponding Master CDF |
| Descriptor | Copy of the "Descriptor" global attributes value in the corresponding Master CDF |
| TestId | Copy of the "Test_id" global attributes value in the parent CDF. If more than one parent CDF files is used, they all shall provide the same "Test_id" value. |
| Provider | Copy of the "Provider" global attributes value in the parent CDF. If more than one parent CDF files is used, they all shall provide the same "Provider" value. |
| VXX | Version XX of the current CDF data file, transmitted by the Software and/or from information inside the Master CDFs. |
In all case, the ROC pipelines will automatically check a posteriori the validity of the output file naming, and the consistency with the global attributes saved inside the file.
...
Finally, the teams can find additional CDF routines in the ROC SVN repos.:
...
- github.com/maserlib/maser4idl (IDL routines are available to read/make cdf)