The Herschel products naming convention for exported FITS files takes the following format which depends on the type of product. The generic format is as follows although not all of the items are present in all filenames. See following subsections for the specific formats for the different groups of products.
h<product/instrument><subinst><obsid/od>_<bbid>_<level><type>_<slice>_<timestamp>
where
h stands for Herschel
<product/instrument>: is the product type such as aux for
auxiliary products or the instrument name either hifi, pacs or spire
(note that all letters in the filename are lowercase).
<subinst>: This is only relevant for instrument data. Depending on the instrument and on the
type of product it stands for the subinstrument used, the detector, polarisation mode etc...
<obsid/od>: The observation ID given in decimal
format.
<bbid>: Some observational products are split up
into logic parts of the observation such as building blocks. When this
occurs the bbid is given in hexadecimal format.
<level>: The level of the product is presented
here. Level 0 products are represented by 00,
Level 0.5 by 05, Level 1 by 10, Level 2 by 20, Level 2.5 by 25 and Level 3 by 30.
<type>: This indicates the type of product as given in the meta keyword (attribute) TYPE.
<slice>: When data from an observation need to be split up further than by building block
or in a way unrelated to building block, the number of the slice is given here. If 100 or
less products result from the split then two digits (yy) represent the slices (in time order).
For more than 100 slices then three digits (yyy) are used.
The ordering of the parameters is designed to give a logic ordering of the filenames when listed in a directory.
All product names also contain at the end a 13 digits number which is a <timestamp> that the
system generates when the FITS product is created.
The specific formats per product are given in the following sections.
The filenames of observation products take the generic form of (products split into building blocks and slices):
h<instrument><subinst><obsid>_<bbid>_<level><type>_<slice>_<timestamp>.fits
For products that contain data from the whole observation (i.e., not split up at all) the generic form is:
h<instrument><subinst><obsid>_<level><type>_<timestamp>.fits
For example, hpacs1342188700_20hps3dbs_01_1422300741810.fits is Level 2 Herschel PACS Spectroscopy (3D) cubes Blue slice 01 for observation 1342188700.
For Level 2.5 and Level 3 products which involve more than one observation, the central coordinates of the generated map are used instead of the <obsid>.
For example, hpacs_30HPPJSMAPR_1451_p7409_00_v1.0 is PACS Photometer Scanamorphos Level 3 Red map with central coordinates RA=14h51m DEC=+74d09m.
The majority of the Calibration products have the addition of cal/calibration in the filename, although the names depend very much on the instrument, the subintrument (photometry or espectroscopy) and whether they are calibration files created by the pipeline or about how the observation was carried out (Uplink).
More details on the name of calibration products can be found in Section 3.2, Section 4.2 and Section 5.2.
The filenames of auxiliary products take the generic form:
haux<obsid/od><type>_<timestamp>.fits
For products associated with one obsid the form is
haux<obsid><type>_<timestamp>.fits
Those with data for one operational day take the form
haux<OD><type>_<timestamp>.fits
Some auxiliary products which are valid for a given period like the SIAM product do not follow this naming convention.
A table describing the different types of auxiliary products is in 6.1.
The filename for the quality control report is:
h<instrument><obsid>_quality_v<NN>
For the quality control report summary:
h<instrument><obsid>_quality_summary_v<NN>
For the quality logs:
h<instrument><obsid>_quality_log_v<NN>
where v<NN> stands for the version of the product although it has not changed across the mission and remains
as v1.0 for all quality products.