Sky temperature maps
Contents
General description[edit]
Sky maps give the best estimate of the intensity of the signal from the sky after removal, as far as possible, of known systematic effects and of the dipole signals induced by the motion of the solar system in the CMB and of the Planck satellite in the solar system. Sky maps are provided for the nominal Planck mission and also, separately, for the first two single surveys, the third one being covered only for a small part during the nominal mission.The details of the start and end times of each are given in this table. As a secondary product, maps with estimates of the Zodiacal light and Far-Side-Lobes contamination removed are also provided.
For characterization purposes, are also provided maps covering the nominal survey but each one using only half of the available data. These are the ringhalf_{1|2} maps, which are built using the first and second half of the stable pointing part in each pointing period. These maps are used extensively to investigate the (high frequency) noise properties the maps themselves and of other products described elsewhere (see e.g., the data validation section).
To help in further processing, there are also masks of the Galactic Plane and of point sources, each provided for several different depths.
All sky maps are in Healpix format, with Nside of 2048 for HFI and of 1024 for LFI, in Galactic coordinates, and Nested ordering. The signal is given in units of Kcmb for 33-353 GHz, and of MJy/sr (for a constant $\nu F_\nu$ energy distribution ) for 545 and 857 GHz. Each sky map is packaged into a BINTABLE extension of a FITS file together with a hit-count map (or hit map, for short, giving the number of observation samples that are cumulated in a pixel, all detectors combined) and a variance map (determined from the half-ring maps), and additional information is given in the FITS file header. The structure of the FITS file is given in the FITS file structure section below.
Types of maps[edit]
- Full channel maps
- Full channel maps are built using all the valid detectors of a frequency channel and cover the nominal mission. For HFI, the 143-8 and 545-3 bolometers are rejected entirely as they are seriously affected by RTS noise. Images in the HFI-DPC paper (#planck2013-p03; can be copied here once produced with the final color scheme).
- Single survey maps
- Single survey maps are built using all valid detectors of a frequency channel, but cover separately the different sky surveys.
- Detector set or detector pairs maps
- These are maps built from a subset of the detectors in a frequency channel, typically our of two PSB pairs (i.e., four poloarisation-sensitive bolometers with different orientation on the sky), for HFI in order to extract a single temperature map. While none of these maps are part of the first Planck data release, the concept of detset is used, and thus it is worth mentioning it here. In particular, information by detector set is available at the sky power spectrum level and in the RIMO.
- Half-ring maps
- Half-ring maps are built using only the first or the second half of the stable pointing period data. There are thus two half-ring maps per frequency channel named ringhalf_1 and ringhalf_2 respectively. These maps are built for characterization purposes in order to perform null tests. In particular, the difference between the two half-ring maps at a given frequency give a good estimate of the high frequency noise in the data.
- Masks
- Masks are provided of the Galactic Plane and of the point sources. For the Galactic Plane, eight masks are given covering different fractions of the sky, and for the points sources two masks are given, at the 5 and 10 sigma level, for each Planck frequency channel.
Caveats and known issues[edit]
Map zero-level[edit]
For the 100 to 857 GHz maps, due to recent evolutions in the calibration scheme, the zero levels could not be set to their optimal levels especially for Galactic studies in time for the data release. A recipe for adjusting these zero levels to astrophysical values is given in the HFI Calibration paper #planck2013-p03f .
For the 30, 44 and 70 GHz, maps are corrected for zero level monopole by applying an offset correction, see LFI Calibration paper #planck2013-p02b section 3.4 "Setting the zero levels in the maps". Note that the offset applied is indicated in the header as a comment keyword.
The Zodiacal light and the Far-Side Lobes[edit]
The figures below show the modeled Zodiacal light and Far Side Lobes projected onto the maps; they are simply the difference between the main product and the ZodiCorrected maps for the nominal mission. The units are given in the figures. The heat color table has been used in place of the standard Planck for clarity reasons.
The effects of the FSLs are seen most clearly at the highest frequencies, as structures roughly symmetric about the center of the image, which corresponds to the location of the Galactic Centre, which is in turn the source of most of the radiation that is scattered into the FSLs.
Artifacts near caustics of the scanning strategy[edit]
For the two highest frequencies, the S/N is in some areas is very large. The scanning strategy produces caustics in the hit maps. The exact location of these series of pixels with very high number of hits (~25,000 instead of ~700 on average) may differ from one detector to the other. For most pixels, data from each detector are combined in roughly equal proportions. But near the caustics, the fraction of each detector's may be highly variable. As there are some uncertainties in calibration, detectors responses may not be perfectly aligned which will show up as artefacts in these regions. Examples are shown below.
Production process[edit]
Sky maps are produced by combining appropriately the data of all working detectors in a frequency channel over some period of the mission. They give the best estimate of the signal from the sky (unpolarised) after removal, as far as possible, of known systematic effects and of the dipole signals induced by the motion of the solar system in the CMB and of the Planck satellite in the solar system. In particular, they include the Zodiacal light emission (Zodi for short) and also the scattering from the far-side lobes of the beams (FSL). More on this below.
HFI processing[edit]
The inputs to the mapmaking are TOIs of signal that have been cleaned (as far as possible) of instrumental effects and calibrated in absorbed watts. While the processing involved is described in detail in the TOI processing section, we give a very brief summary here for convenience. That pipeline performs the following operations:
- demodulation
- this is performed around a variable level which is determined from the valid input data (a validity flag from a previous version of the processing is used for this purpose), and the data are converted to engineering units (V) using known conversion coefficients.
- despiking
- using the demodulated data converted to V (by the transfer function) the glitches are identified and fitted with templates. A glitch flag is produced that identifies the strongest part of the glitches, and a timeline of glitch tails is produced from the template fits, and subtracted from the demodulated timeline from step 1. Finally, the flagged ranges are replaced with data from an average over the pointing period (TBC)
- dark template removal
- the two dark bolometers are demodulated and despiked as above; the resulting timelines are then smoothed and used as an indicator of the overall temperature variations of the bolometer plate. Where the variations are consistent with each other, they are combined and removed from the bolometer signal timelines using appropriate coupling coefficients. The few percent of the data where they are not consistent are flagged on the timelines.
- conversion to absorbed power
- the timeline is converted to watts of absorbed power using the bolometer function. This includes a non-linearity correction; removal of the 4K cooler lines: the electromagnetic interference of the 4K cooler with the bolometer readout wires induces some sharp lines in the signal power spectra at frequencies of the 4K cooler's fundamental and its multiples, folded by the signal modulations. Fourier coefficients of the relevant lines are determined on a per-ring basis, and then removed from the data. The quality of the removal depends on the bolometer.
- deconvolution by the time transfer function
- this is done to correct for the non-instantaneous time response of the bolometers. The function itself is modeled using 4 parameters which are adjusted primarily on the planet data and also from comparisons of the northward and southward scans of the Galactic Plane. It is then removed using Fourier techniques, which has the side-effect of increasing the noise at high frequencies.
- jump correction
- removes some (relatively rare: 0.3 jumps per bolometer per pointing period, on average) jumps in the signal baseline. The jumps are detected characterized on smoothed TOIs, and corrected by adding a constant to part of the signal timeline. The origin of the jumps is not known.
The results of this processing are a timeline of signal (in absorbed watts) and a valid data flag timeline for each of the 50 valid bolometers processed; these timelines contain the full sky signal, i.e., including the solar and orbital dipoles, the Zodiacal light, and contributions from the Far-Side lobes. The dipoles are necessary for the flux calibration and are removed at the mapmaking stage. The remaining two bolometers (143-8 and 535-3) show semi-random jumps in the signal level, typically jumping over 2-5 different pseudo-baseline levels, a behavior known as Random Telegraphic Signal, so that these are commonly called the RTS bolometers. Finally, ring-level statistics of different types (mean, median, rms, kurtosis, etc.) are determined on a per-ring basis for all timelines, and a selection based on these statistics is used to discard anomalous rings, which are recorded in a ring-level flag for each valid bolometer timeline.
Throughout this processing, bright planets (Mars, Jupiter, Saturn, Uranus) and bright asteroids are masked in the timeline in order to avoid ringing effects in the processing. Since they move on the sky, the portion of the sky masked during one survey is observed during one, and no hole is left in the final map. In parallel, the planet data are processed in a similar way, but with different parameters for the despiking step, and without the final jump correction step. These results are processed separately to determine the beam shapes and the focal plane geometry.
The pointing is determined starting from the AHF produced by MOC, which gives the direction and orientation of the LOS of a fiducial position in the focal plane at frequencies of 8Hz during stable pointing and 4 Hz during maneuvers (TBC for details, reference). This is interpolated to the times of data observation (ref to method), corrected for the wobble and other time-dependent offsets determined from the observed positions of a large number of sources around the sky, and finally converted to the LOS of each detector using the quaternions in the IMO (which are determined from observations of bright planets - see the Focal plane reconstruction pipeline).
The mapmaking pipeline is described in detail in the Map-making section, and a brief summary is given here for convenience.
The cleaned TOIs of signal of each detector, together with their flags, produced by the TOI processing pipeline, and the TOIs of pointing (quaternions), described in Detectors pointing and beams, are the inputs to the mapmaking step.
The input signal TOIs are expressed in Watts from the sky absorbed by the bolometer, and their associated flags are used to samples or full rings to discard. Are discarded periods of unstable pointing and pointing maneuvers in general, glitched data, transits over bright planets (since they move, the hole flagged during one survey is covered during another sky survey), and some full rings are discarded if their noise properties differ significantly from the nominal value and the few rings of duration longer than 90 min, since the pointing is not sufficiently stable over such long periods (details in Discarded rings section). The preparation of input pointing TOIs is described in Detectors pointing and beams. In brief, the STR (StarTracker) pointing produced by Flight Dynamics is interpolated to the detector sampling frequency in order to obtain a tuple of pointing quaternions for each sample and corrected for certain known effects. The angular offset between the STR line of sight and that of each bolometer is reflected in the Focal Plane Geometry, which is determined from the observation of bright planets. Also, the STR pointing timeline is corrected for slowly varying offsets between the STR and the HFI focal plane using observations of all planets and of other (fixed) bright sources.
Using the pointing TOIs, the signal TOIs are first used to build Healpix rings using the nearest grid point method; each ring containing the combined data of one pointing period. These are then calibrated in brightness, cleaned of the dipole signals, and projected onto Healpix maps as explained in the following sections.
The cleaned TOIs must be calibrated in astrophysical units. At 100-353 GHz, the flux calibration gains are determined for each pointing period (or ring) from the solar-motion dipole after removal of the small dipole induced by the motion of the Planck satellite in the solar system. The solar-motion dipole from WMAP (REF) is used for this purpose. This gain by ring is then smoothed with a window of width 50 rings, which reveals an apparent variation of ~1-2% on a scale of 100s to 1000s of rings for the 100-217 GHz channels, and is applied to the Watt data. At 353GHz, where the solar motion dipole is weaker compared to the signal, no gain variation is detected, and a single fixed gain is applied to all rings. At 545 and 857 GHz the gain is determined from the observation of Uranus and Neptune (Jupiter is not used because its brightness produced some non-linearity in the bolometer response) and comparison to recent models (REF) made explicitly for this mission. A single gain is applied to all rings at these frequencies. Prior to projecting the Healpix rings (HPRs) onto a map, a destriping approach is used to remove low-frequency noise. The noise is modelled as the sum of a white noise component and a constant, or offset, per pointing period which represents the low frequency 1/f noise. The offsets are determined by minimizing the differences between HPRs at their crossings. After subtracting these offsets, calibrated data are projected onto Healpix maps, with the data of each bolometer weighted by a factor of 1/NET of that bolometer, and accounting for the slight different band transmission profiles of the bolometers in each band.
These maps provide the main mission products. A second, reduced, set of maps, cleaned of the Zodiacal emission of the FSL leakage is also produced for the nominal mission and the two single surveys, but not for the half-rings (since the contribution would be the same for the two halves of each ring). For this purpose, the the Zodiacal emission and the FSL contamination, which are not fixed on the sky, are modeled separately at HPR-level, and subtracted from the signal HPR before projecting them onto the maps.
Together with signal maps, hit count and variance maps are also produced. The hit maps give the (integer) number of valid TOI-level samples that contribute to the signal of each pixel. All valid samples are counted in the same way, i.e., there is no weighting factor applied. The variance maps project the white noise estimate, provided by the NETs, in the sky domain.
LFI processing[edit]
LFI maps were constructed with the Madam map-making code, version 3.7.4. The code is based on generalized destriping technique, where the correlated noise component is modeled as a sequence of constant offset, called baselines. A noise filter was used to constrain the baseline solution allowing the use of 1 second baselines.
Radiometers were combined according to the horn-uniform weighting scheme to minimize systematics. The used weights are listed in Map-making. The flagged samples were excluded from the analysis by setting their weights to $C_{w}^{-1}$ = 0. The galaxy region was masked out in the destriping phase, to reduce error arising from strong signal gradients. The polarization component was included in the analysis, although only the temperature maps are released.
A detailed description of the map-making procedure is given in #planck2013-p02. See also section Map-making.
Inputs[edit]
HFI inputs[edit]
- The cleaned TOIs of signal of each detector, together with their flags, produced by the TOI processing pipeline
- The TOIs of pointing (quaternions), described in Detectors pointing and beams
- Bolometer-level characterization data, from the DPC's internal IMO (not distributed)
- Planck orbit data used to compute and remove the earth dipole
- WMAP solar dipole information used to calibrate the CMB channels
- Planet models used to calibrate the Galactic channels.
LFI inputs[edit]
The Madam map-maker takes as an input:
- The calibrated timelines (for details see TOI Processing)
- The detector pointings (for details see Detector pointing)
- The noise information in the form of three-parameter (white noise level ($\sigma$), slope, and knee frequency ($f_\mathrm{knee}$)) noise model (for details see RIMO)
Related products[edit]
Masks[edit]
Masks are provided of
- the Galactic Plane
- 16 masks are provided giving 20, 40, 60, 70, 80, 90, 97, and 99% sky coverage in two different files, one for HFI at Nside=2048 and one for LFI at Nside=1024
- the point sources
- 18 masks are provided, 2 per frequency channel, each masking at the 5 and 10$\sigma$ level; 12 for HFI at Nside=2048 and 6 for LFI at Nside=1024
The masks are apodized, in GALACTIC coordinates, and NESTED ordering. The table below give the filenames.
| Galactic Plane | Point Sources |
|---|---|
| HFI_Mask_GalPlane_2048_R1.10.fits | HFI_Mask_PointSrc_2048_R1.10.fits |
| LFI_Mask_GalPlane_1024_R1.10.fits | LFI_Mask_PointSrc_1024_R1.10.fits |
The (HFI) masks are shows below in a single figure. While this is quite clear for the Galactic Plane masks, it is less so for the point source masks, but it does give a clear perspective on how the latter are distributed over the sky.
Galactic Plane masks
PointSource masks
File names[edit]
The FITS filenames are of the form {H|L}FI_SkyMap_fff_nnnn_R1.nn_{coverage}_{type}.fits, where fff are three digits to indicate the Planck frequency band, and nnnn is the Healpix Nside of the map, coverage indicates which part of the mission is covered, and the optional type indicates the subset of input data used. A full list of products, by their names, is given in the List of products below.
The list of products containing sky maps are given below, grouped by type
| Frequency | FITS file name |
|---|---|
| 30GHz | LFI_SkyMap_030_1024_R1.10_nominal.fits |
| 44GHz | LFI_SkyMap_044_1024_R1.10_nominal.fits |
| 70GHz | LFI_SkyMap_070_1024_R1.10_nominal.fits |
| 100GHz | HFI_SkyMap_100_2048_R1.10_nominal.fits |
| 143GHz | HFI_SkyMap_143_2048_R1.10_nominal.fits |
| 217GHz | HFI_SkyMap_217_2048_R1.10_nominal.fits |
| 353GHz | HFI_SkyMap_353_2048_R1.10_nominal.fits |
| 545GHz | HFI_SkyMap_545_2048_R1.10_nominal.fits |
| 857GHz | HFI_SkyMap_857_2048_R1.10_nominal.fits |
- Zodi and Far-side-lobes corrected maps
HFI_SkyMap_100_2048_R1.nn_nominal_ZodiCorrected.fits HFI_SkyMap_143_2048_R1.nn_nominal_ZodiCorrected.fits HFI_SkyMap_217_2048_R1.nn_nominal_ZodiCorrected.fits HFI_SkyMap_353_2048_R1.nn_nominal_ZodiCorrected.fits HFI_SkyMap_545_2048_R1.nn_nominal_ZodiCorrected.fits HFI_SkyMap_857_2048_R1.nn_nominal_ZodiCorrected.fits
HFI_SkyMap_100_2048_R1.nn_survey_1_ZodiCorrected.fits HFI_SkyMap_143_2048_R1.nn_survey_1_ZodiCorrected.fits HFI_SkyMap_217_2048_R1.nn_survey_1_ZodiCorrected.fits HFI_SkyMap_353_2048_R1.nn_survey_1_ZodiCorrected.fits HFI_SkyMap_545_2048_R1.nn_survey_1_ZodiCorrected.fits HFI_SkyMap_857_2048_R1.nn_survey_1_ZodiCorrected.fits HFI_SkyMap_100_2048_R1.nn_survey_2_ZodiCorrected.fits HFI_SkyMap_143_2048_R1.nn_survey_2_ZodiCorrected.fits HFI_SkyMap_217_2048_R1.nn_survey_2_ZodiCorrected.fits HFI_SkyMap_353_2048_R1.nn_survey_2_ZodiCorrected.fits HFI_SkyMap_545_2048_R1.nn_survey_2_ZodiCorrected.fits HFI_SkyMap_857_2048_R1.nn_survey_2_ZodiCorrected.fits
FITS file structure[edit]
The FITS files for the sky maps contain a minimal primary header with no data, and a BINTABLE extension (EXTENSION 1, EXTNAME = 'FREQ-MAP') containing the data. The structure is shows schematically in the figure at right.
The FREQ-MAP extension contains is a 3-column table of that contain the signal, variance, and hit-count maps, all in Healpix format, in columns 1, 2, and 3, respectively. The number of rows is 50331648 for HFI and 12582912 for LFI, corresponding to the number of pixels in a Healpix map of Nside= 2048 and 1024, respectively (N.B: Npix = 12 Nside^2). The three columns are I_STOKES for the intensity (or temperature) signal, II_COV for the variance, and HIT for the hit-count. The exact order of the columns in the figure is indicative only, and the details can be found in the keywords.
Keywords indicate the coordinate system (GALACTIC), the Healpix ordering scheme (NESTED), the units (K_cmb or MJy/sr) of each column, and of course the frequency channel (FREQ). The COMMENT fields give a one-line summary of the product, and some other information useful for traceability within the DPCs. The original filename is also given in the FILENAME keyword as are the datasum and the md5 checksum for the extension. The BAD_DATA keyword gives the value used by Healpix to indicate pixels for which no signal is present (these will also have a hit-count value of 0). The COMMENT fields give further information including some traceability data for the DPC's. The main parameters are summarised below:
| Column Name | Data Type | Units | Description |
|---|---|---|---|
| 1. EXTNAME = 'FREQ-MAP' : Data columns | |||
| I_STOKES | Real*4 | K_cmb or MJy/sr | The signal map |
| HITS | Int*4 | none | The hit-count map |
| II_COV | Real*4 | K_cmb^2 or (MJy/sr)^2 | The variance map |
| Keywords | |||
| PIXTYPE | string | HEALPIX | |
| COORDSYS | string | GALACTIC | Coordinate system |
| ORDERING | string | NESTED | Healpix ordering |
| NSIDE | Int | 1024 or 2048 | Healpix Nside for LFI and HFI, respectively |
| FIRSTPIX | Int*4 | 0 | First pixel number |
| LASTPIX | Int*4 | 12582911 or 50331647 | Last pixel number, for LFI and HFI, respectively |
| FREQ | string | nnn | The frequency channel |
The same structure applies to all SkyMap products, independent of whether they are full channel, survey of half-ring. The distinction between the types of maps is present in the FITS filename (and in the traceability comment fields).
An example of a frequency map header is given below (LFI, 30 GHz):
XTENSION= 'BINTABLE' / binary table extension BITPIX = 8 / 8-bit bytes NAXIS = 2 / 2-dimensional binary table NAXIS1 = 12 / width of table in bytes NAXIS2 = 12582912 / number of rows in table PCOUNT = 0 / size of special data area GCOUNT = 1 / one data group (required keyword) TFIELDS = 3 / number of fields in each row TTYPE1 = 'I_Stokes' / label for field 1 TFORM1 = 'E ' / data format of field: 4-byte REAL TUNIT1 = 'K_CMB ' / physical unit of field TTYPE2 = 'Hits ' / label for field 2 TFORM2 = 'J ' / data format of field: 4-byte INTEGER TUNIT2 = 'none ' / physical unit of field TTYPE3 = 'II_cov ' / label for field 3 TFORM3 = 'E ' / data format of field: 4-byte REAL TUNIT3 = '(K_CMB)^2' / physical unit of field EXTNAME = 'FREQ-MAP' DATE = '2012-12-12T15:48:55' / file creation date (YYYY-MM-DDThh:mm:ss UT) CHECKSUM= 'NenJQblINblINblI' / HDU checksum updated 2012-12-12T15:48:57 DATASUM = '5363685 ' / data unit checksum updated 2012-12-12T15:48:57 COMMENT COMMENT *** Planck params *** COMMENT PIXTYPE = 'HEALPIX ' / HEALPIX pixelisation ORDERING= 'NESTED ' / Pixel ordering scheme, either RING or NESTED NSIDE = 1024 / Resolution parameter for HEALPIX FIRSTPIX= 0 / First pixel # (0 based) LASTPIX = 12582911 / Last pixel # (0 based) INDXSCHM= 'IMPLICIT' / Indexing: IMPLICIT or EXPLICIT EXTVER = '2 ' PROCVER = 'DX9_Delta' BAD_DATA= -1.6375E+30 FREQ = 30 COORDSYS= 'GALACTIC' FILENAME= 'LFI_SkyMap_030_1024_R1.10_nominal.fits' COMMENT --------------------------------------------------------------------- COMMENT LFI RIMO 10.1 COMMENT Madam version 3.7.4 COMMENT Added monopole offset 0.000365224 to column I_Stokes COMMENT LFI-DMC object: COMMENT TOODI%ACCTOODI%%madam_IQUmap_LFI_calib_30GHz_DX9d_nom_1sec:0% COMMENT TOODI%ACCTOODI%%madam_hit_LFI_calib_30GHz_DX9d_nom_1sec:0% COMMENT TOODI%ACCTOODI%%madam_cov_LFI_calib_30GHz_DX9d_nom_1sec:0% COMMENT --------------------------------------------------------------------- END
References[edit]
<biblio force=false>
</biblio>
Cosmic Microwave background
(Planck) High Frequency Instrument
(Planck) Low Frequency Instrument
Flexible Image Transfer Specification
random telegraphic signal
Data Processing Center
To be confirmed
sudden change of the baseline level inside a ring
Attitude History File
[ESA's] Mission Operation Center [Darmstadt, Germany]
Line Of Sight
Star TRacker
Noise Equivalent Temperature
Data Management Component, the databases used at the HFI and LFI DPCs
