Mission products

The

The Mission Data Products described in this chapter are:

• different flavors of sky maps, i.e., maps of the full signal received from the sky, processed via the DPC pipelines; these represent the best view of the sky at the Planck frequencies that the DPCs could produce at this time;
• catalogues of point sources, one per frequency band, and of the SZ clusters (of which there are several compiled with different extraction methods);
• astrophysical component maps (with more that one map for some components), which attempt to separate the different astrophysical components, namely the CMB (various examples obtained with different extraction methods), and several foregrounds;
• a Dust opacity map and model derived from the dust component but using also external information;
• sky power spectra for selected combination of detectors useful for Likelihood studies, and obtained with the DPC's best estimate of the beam window function;
• a CMB power spectrum;
• A set of instrument-level data compiled into the RIMO (Reduced Instrument Model), such as beam properties, noise levels, bandpass profiles, and more. There is one RIMO for each instrument.
• the effective beams … Should this be here or in ancillary data?

Two software packages are also included as Mission Products:

• the Likelihood code package, which is itself split into a software package and a data package,
• the Unit Conversion and Color Correction (UcCC) package Should this be here or in the software utilities section?, which is used together with the bandpass profiles in the RIMO.

There are no low-level science products in this first release of Planck data, in particular no timeline data (raw or processed signal, pointing), and in general no data at the single detector level. Other products of scientific analyses that were built with extensive use of external data are given in Additional products, and mission and payload information are in later chapters.

The data products are packaged into FITS files that contain a main product (e.g., a signal map) and one or more other products to characterize it (e.g., an error map and a hit-count map). Depending on the details of the products, the data are written into a single BINTABLE or a few extensions. The RIMO is also packaged into a FITS file, but given the nature of its different elements it was necessary to use several hundred BINTABLE extensions.

The software is delivered as a tarball of code, and if necessary a second tarball of associated data is also delivered. The details depend on the code and are described elsewhere in this document.

This chapter is divided by type of product. Each section contain a brief description of how each type of product is obtained, while the details of the processing are given in the HFI Data Processing and LFI Data Processing chapters, and any known problems with the product. The list of product files is then given, and sample FITS headers are given and explained.