Difference between revisions of "Effective Beams"

From Planck Legacy Archive Wiki
Jump to: navigation, search
(Comparison of the images of compact sources observed by Planck with FEBeCoP products)
(File format)
 
(26 intermediate revisions by the same user not shown)
Line 34: Line 34:
  
 
===Histograms of the effective beam parameters===
 
===Histograms of the effective beam parameters===
Here we present histograms of the three fit parameters - beam FWHM, ellipticity, and orientation with respect to the local meridian and of the beam solid angle. The sky is sampled (pretty sparsely) at 3072 directions which were chosen as HEALpix nside=16 pixel centers for HFI and at 768 directions which were chosen as HEALpix nside=8 pixel centers for LFI.  These uniformly sample the sky.
+
Here we present histograms of the three fit parameters, i.e., beam FWHM, ellipticity, and orientation with respect to the local meridian, and of the beam solid angle. The sky is uniformly sampled (although fairly sparsely) in 3072 directions that were chosen as HEALPix <i>N</i><sub>side</sub>=16 pixel centres for HFI and in 768 directions that were chosen as HEALPix <i>N</i><sub>side</sub>=8 pixel centres for LFI.
  
Where beam solid angle is estimated according to the definition:  '''<math> 4 \pi \sum</math>(effbeam)/max(effbeam)'''
+
Here the beam solid angle is estimated according to the definition:  "4&pi; &Sigma;(effbeam)/max(effbeam)"
i.e., <math> 4 \pi \sum(B_{ij}) /  max(B_{ij}) </math>
+
i.e., 4&pi; &Sigma;(<i>B<sub>ij</sub></i>) /  max(<i>B<sub>ij</sub></i>).
  
  
[[File:ist_GB.png | 800px| thumb | center| '''Histograms for LFI effective beam parameters''' ]]  
+
[[File:ist_GB.png | 800px| thumb | center| '''Histograms for LFI effective beam parameters.''' ]]  
[[File:ist_BS_Mars12.png | 800px| thumb | center| '''Histograms for HFI effective beam parameters''' ]]
+
[[File:ist_BS_Mars12.png | 800px| thumb | center| '''Histograms for HFI effective beam parameters.''' ]]
  
 
===Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian===
 
===Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian===
* The discontinuities at the Healpix domain edges in the maps are a visual artifact due to the interplay of the discretized effective beam and the Healpix pixel grid.
+
* The discontinuities at the HEALPix domain edges in the maps are a visual artefact due to the interplay of the discretized effective beam and the HEALPix pixel grid.
  
  
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of effective beams ellipticity of the best-fit Gaussian">
+
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of ellipticity of the best-fit Gaussian for the effective beams.">
File:e_030_GB.png| '''ellipticity - 30GHz'''
+
File:e_030_GB.png| '''Ellipticity - 30GHz.'''
File:e_044_GB.png| '''ellipticity - 44GHz'''
+
File:e_044_GB.png| '''Ellipticity - 44GHz.'''
File:e_070_GB.png| '''ellipticity - 70GHz'''
+
File:e_070_GB.png| '''Ellipticity - 70GHz.'''
File:e_100_BS_Mars12.png| '''ellipticity - 100GHz'''
+
File:e_100_BS_Mars12.png| '''Ellipticity - 100GHz.'''
File:e_143_BS_Mars12.png| '''ellipticity - 143GHz'''
+
File:e_143_BS_Mars12.png| '''Ellipticity - 143GHz.'''
File:e_217_BS_Mars12.png| '''ellipticity - 217GHz'''
+
File:e_217_BS_Mars12.png| '''Ellipticity - 217GHz.'''
File:e_353_BS_Mars12.png| '''ellipticity - 353GHz'''
+
File:e_353_BS_Mars12.png| '''Ellipticity - 353GHz.'''
File:e_545_BS_Mars12.png| '''ellipticity - 545GHz'''
+
File:e_545_BS_Mars12.png| '''Ellipticity - 545GHz.'''
File:e_857_BS_Mars12.png| '''ellipticity - 857GHz'''
+
File:e_857_BS_Mars12.png| '''Ellipticity - 857GHz.'''
 
</gallery>
 
</gallery>
  
  
<gallery widths=300px heights=220px perrow=3 caption="Sky (relative) variation of effective beams solid angle of the best-fit Gaussian">
+
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of the relative solid angle of the best-fit Gaussian for the effective beams.">
File:solidarc_030_GB.png| '''beam solid angle (relative) variations wrt scanning beam - 30GHz'''
+
File:solidarc_030_GB.png| '''Relative beam solid angle variations w.r.t. scanning beam - 30GHz.'''
File:solidarc_044_GB.png| '''beam solid angle (relative) variations wrt scanning beam - 44GHz'''
+
File:solidarc_044_GB.png| '''Relative beam solid angle variations w.r.t. scanning beam - 44GHz.'''
File:solidarc_070_GB.png| '''beam solid angle (relative) variations wrt scanning beam - 70GHz'''
+
File:solidarc_070_GB.png| '''Relative  beam solid angle variations w.r.t. scanning beam - 70GHz.'''
File:solidarc_100_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 100GHz'''
+
File:solidarc_100_BS_Mars12.png| '''Relative beam solid angle variations w.r.t. scanning beam - 100GHz.'''
File:solidarc_143_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 143GHz'''
+
File:solidarc_143_BS_Mars12.png| '''Relative beam solid angle variations w.r.t. scanning beam - 143GHz.'''
File:solidarc_217_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 217GHz'''
+
File:solidarc_217_BS_Mars12.png| '''Relative beam solid angle variations w.r.t. scanning beam - 217GHz.'''
File:solidarc_353_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 353GHz'''
+
File:solidarc_353_BS_Mars12.png| '''Relative beam solid angle variations w.r.t. scanning beam - 353GHz.'''
File:solidarc_545_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 545GHz'''
+
File:solidarc_545_BS_Mars12.png| '''Relative beam solid angle variations w.r.t. scanning beam - 545GHz.'''
File:solidarc_857_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 857GHz'''
+
File:solidarc_857_BS_Mars12.png| '''Relative beam solid angle variations w.r.t. scanning beam - 857GHz.'''
 
</gallery>
 
</gallery>
  
  
<gallery widths=300px heights=220px perrow=3 caption="Sky (relative) variation of effective beams fwhm of the best-fit Gaussian">
+
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of the relative FWHM of the best-fit Gaussian for theeffective beams.">
File:fwhm_030_GB.png| '''fwhm (relative) variations wrt scanning beam - 30GHz'''
+
File:fwhm_030_GB.png| '''Relative FWHM variations w.r.t. scanning beam - 30GHz.'''
File:fwhm_044_GB.png| '''fwhm (relative) variations wrt scanning beam - 44GHz'''
+
File:fwhm_044_GB.png| '''Relative FWHM variations w.r.t. scanning beam - 44GHz.'''
File:fwhm_070_GB.png| '''fwhm (relative) variations wrt scanning beam - 70GHz'''
+
File:fwhm_070_GB.png| '''Relative FWHM variations w.r.t. scanning beam - 70GHz.'''
File:fwhm_100_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 100GHz'''
+
File:fwhm_100_BS_Mars12.png| '''Relative FWHM variations w.r.t. scanning beam - 100GHz.'''
File:fwhm_143_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 143GHz'''
+
File:fwhm_143_BS_Mars12.png| '''Relative FWHM variations w.r.t. scanning beam - 143GHz.'''
File:fwhm_217_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 217GHz'''
+
File:fwhm_217_BS_Mars12.png| '''Relative FWHM variations w.r.t. scanning beam - 217GHz.'''
File:fwhm_353_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 353GHz'''
+
File:fwhm_353_BS_Mars12.png| '''Relative FWHM variations w.r.t. scanning beam - 353GHz.'''
File:fwhm_545_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 545GHz'''
+
File:fwhm_545_BS_Mars12.png| '''Relative FWHM variations w.r.t. scanning beam - 545GHz.'''
File:fwhm_857_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 857GHz'''
+
File:fwhm_857_BS_Mars12.png| '''Relative FWHM variations w.r.t. scanning beam - 857GHz.'''
 
</gallery>
 
</gallery>
  
  
 
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of effective beams <math>\psi</math> angle of the best-fit Gaussian">
 
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of effective beams <math>\psi</math> angle of the best-fit Gaussian">
File:psi_030_GB.png| '''<math>\psi</math> - 30GHz'''
+
File:psi_030_GB.png| '''&psi; - 30GHz.'''
File:psi_044_GB.png| '''<math>\psi</math> - 44GHz'''
+
File:psi_044_GB.png| '''&psi; - 44GHz.'''
File:psi_070_GB.png| '''<math>\psi</math> - 70GHz'''
+
File:psi_070_GB.png| '''&psi; - 70GHz.'''
File:psi_100_BS_Mars12.png| '''<math>\psi</math> - 100GHz'''
+
File:psi_100_BS_Mars12.png| '''&psi; - 100GHz.'''
File:psi_143_BS_Mars12.png| '''<math>\psi</math> - 143GHz'''
+
File:psi_143_BS_Mars12.png| '''&psi; - 143GHz.'''
File:psi_217_BS_Mars12.png| '''<math>\psi</math> - 217GHz'''
+
File:psi_217_BS_Mars12.png| '''&psi; - 217GHz.'''
File:psi_353_BS_Mars12.png| '''<math>\psi</math> - 353GHz'''
+
File:psi_353_BS_Mars12.png| '''&psi; - 353GHz.'''
File:psi_545_BS_Mars12.png| '''<math>\psi</math> - 545GHz'''
+
File:psi_545_BS_Mars12.png| '''&psi; - 545GHz.'''
File:psi_857_BS_Mars12.png| '''<math>\psi</math> - 857GHz'''
+
File:psi_857_BS_Mars12.png| '''&psi; - 857GHz.'''
 
</gallery>
 
</gallery>
  
Line 109: Line 109:
 
===Statistics of the effective beams computed using FEBeCoP===
 
===Statistics of the effective beams computed using FEBeCoP===
  
We tabulate the simple statistics of FWHM, ellipticity (e), orientation (<math> \psi</math>) and beam solid angle, (<math> \Omega </math>), for a sample of 3072 and 768 directions on the sky for HFI and LFI data respectively. Statistics shown in the Table are derived from the histograms shown above.
+
Below we tabulate the simple statistics of FWHM, ellipticity (<i>e</i>), orientation (&psi;) and beam solid angle, (&Omega;), for a sample of 3072 and 768 directions on the sky for HFI and LFI data, respectively. Statistics shown in the Table are derived from the histograms shown above.
  
* The derived beam parameters are representative of the DPC NSIDE 1024 and 2048 healpix maps (they include the pixel window function).
+
* The derived beam parameters are representative of the DPC <i>N</i><sub>side</sub> 1024 and 2048 HEALPix maps (including the pixel window function).
* The reported FWHM_eff are derived from the beam solid angles, under a Gaussian approximation. These are best used for flux determination while the  the Gaussian fits to the effective beam maps are more suited for source identification.
+
* The reported FWHM<sub>eff</sub> values are derived from the beam solid angles, under a Gaussian approximation. These are appropriate for flux determination, while the  the Gaussian fits to the effective beam maps are more suited for source identification.
  
  
  
 
{| border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
 
{| border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
|+ '''Statistics of the FEBeCoP Effective Beams Computed with the BS Mars12 apodized for the CMB channels and oversampled'''
+
|+ '''Statistics of the FEBeCoP effective beams computed with the BS Mars12 data apodized for the CMB channels and oversampled.'''
 
|-
 
|-
!  '''frequency''' ||  '''mean(fwhm)''' [arcmin]  ||  '''sd(fwhm)''' [arcmin]  || '''mean(e)'''  ||  '''sd(e)'''  ||  '''mean(<math> \psi</math>)''' [degree]  ||  '''sd(<math> \psi</math>)''' [degree]  || '''mean(<math> \Omega </math>)''' [arcmin<math>^{2}</math>]  ||  '''sd(<math> \Omega </math>)''' [arcmin<math>^{2}</math>] || '''FWHM_eff''' [arcmin]  
+
!  '''Frequency''' [GHz] ||  '''Mean(FWHM)''' [arcmin]  ||  '''&sigma;(FWHM)''' [arcmin]  || '''Mean(<i>e</i>)'''  ||  '''&sigma;(<i>e</i>)'''  ||  '''Mean(&psi;)''' [deg]  ||  '''&sigma;(&psi;)''' [deg]  || '''Mean(&Omega;)''' [arcmin<sup>2</sup>]  ||  '''&sigma;(&Omega;)''' [arcmin<sup>2</sup>] || '''FWHM<sub>eff</sub>''' [arcmin]  
 
|-
 
|-
| 030 || 32.239 || 0.013 || 1.320 || 0.031 || -0.304 || 55.349 || 1189.513 || 0.842 || 32.34
+
| 30 || 32.239 || 0.013 || 1.320 || 0.031 || -0.304 || 55.349 || 1189.513 || 0.842 || 32.34
 
|-
 
|-
| 044 || 27.005 || 0.552 || 1.034 || 0.033 || 0.059 || 53.767 || 832.946 || 31.774  || 27.12
+
| 44 || 27.005 || 0.552 || 1.034 || 0.033 || 0.059 || 53.767 || 832.946 || 31.774  || 27.12
 
|-
 
|-
 
| 070 || 13.252 || 0.033 || 1.223 || 0.026 || 0.587 || 55.066 || 200.742 || 1.027  || 13.31  
 
| 070 || 13.252 || 0.033 || 1.223 || 0.026 || 0.587 || 55.066 || 200.742 || 1.027  || 13.31  
Line 140: Line 140:
 
|}
 
|}
  
 
  
 +
====Beam solid angles for the PCCS====
 +
For the Planck Catalogue of Compact Sources we also need the following definitions.
  
====Beam solid angles for the PCCS====
+
*  &Omega;<sub>eff</sub> - is the mean beam solid angle of the effective beam, where the solid angle is estimated according to the definition "4 &pi; &Sigma;(effbeam)/max(effbeam)", i.e., as an integral over the full extent of the effective beam, 4&pi; &Sigma; (<i>B<sub>ij</sub></i>)/max(<i>B<sub>ij</sub></i>).
 +
 
 +
* From &Omega;<sub>eff</sub> we estimate FWHM<sub>eff</sub>, under a Gaussian approximation - these are tabulated above.
  
* <math>\Omega_{eff}</math> - is the mean beam solid angle of the effective beam, where beam solid angle is estimated according to the definition:  '''<math>4 \pi \sum </math>(effbeam)/max(effbeam)''', i.e. as an integral over the full extent of the effective beam, i.e. <math> 4 \pi \sum(B_{ij}) /  max(B_{ij}) </math>.
+
*&Omega;<sup>(1)</sup><sub>eff</sub> is the beam solid angle estimated up to a radius equal to 1 FWHM<sub>eff</sub> and &Omega;<sup>(2)</sup><sub>eff</sub> up to a radius equal to twice the FWHM<sub>eff</sub>.
  
* from <math>\Omega_{eff}</math> we estimate the <math>fwhm_{eff}</math>, under a Gaussian approximation - these are tabulated above
+
These were estimated according to the procedure followed in the aperture photometry code for the PCCS; if the pixel centre does not lie within the given radius it is not included (so "inclusive=0" in query disc).
** <math>\Omega^{(1)}_{eff}</math> is the beam solid angle estimated up to a radius equal to one <math>fwhm_{eff}</math> and <math>\Omega^{(2)}_{eff}</math> up to a radius equal to twice the <math>fwhm_{eff}</math>.
 
*** These were estimated according to the procedure followed in the aperture photometry code for the PCCS: if the pixel centre does not lie within the given radius it is not included (so inclusive=0 in query disc).
 
  
  
 
{|border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
 
{|border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
 
|+'''Band averaged beam solid angles'''
 
|+'''Band averaged beam solid angles'''
|  '''Band'''  ||  '''<math>\Omega_{eff}</math>'''[arcmin<math>^{2}</math>] || '''spatial variation''' [arcmin<math>^{2}</math>] ||  '''<math>\Omega^{(1)}_{eff}</math>''' [arcmin<math>^{2}</math>]|| '''spatial variation-1''' [arcmin<math>^{2}</math>] ||  '''<math>\Omega^{(2)}_{eff}</math>''' [arcmin<math>^{2}</math>] || '''spatial variation-2''' [arcmin<math>^{2}</math>]  
+
|  '''Band [GHz]'''  ||  '''&Omega;<sub>eff</sub>'''[arcmin<sup>2</sup>] || '''Spatial variation''' [arcmin<sup>2</sup>] ||  '''&Omega;<sup>(1)</sup><sub>eff</sub>''' [arcmin<sup>2</sup>]|| '''Spatial variation-1''' [arcmin<sup>2</sup>] ||  '''&Omega;<sup>(2)</sup><sub>eff</sub>''' [arcmin<sup>2</sup>] || '''Spatial variation-2''' [arcmin<sup>2</sup>]  
 
|-
 
|-
|30 || 1189.513 || 0.842 || 1116.494 || 2.274 || 1188.945 || 0.847  
+
| 30 || 1189.513 || 0.842 || 1116.494 || 2.274 || 1188.945 || 0.847  
 
|-
 
|-
 
| 44 || 832.946 || 31.774 || 758.684 || 29.701 || 832.168 || 31.811  
 
| 44 || 832.946 || 31.774 || 758.684 || 29.701 || 832.168 || 31.811  
Line 176: Line 177:
  
 
==Production process==
 
==Production process==
FEBeCoP, or Fast Effective Beam Convolution in Pixel space{{BibCite|mitra2010}}, is an approach to representing and computing effective beams (including both intrinsic beam shapes and the effects of scanning) that comprises the following steps:
+
FEBeCoP, the Fast Effective Beam Convolution in Pixel space{{BibCite|mitra2010}}, is an approach for representing and computing effective beams (including both intrinsic beam shapes and the effects of scanning) that comprises the following steps:
* identify the individual detectors' instantaneous optical response function (presently we use elliptical Gaussian fits of Planck beams from observations of planets; eventually, an arbitrary mathematical representation of the beam can be used on input)
+
* identify the individual detectors' instantaneous optical response function (presently we use elliptical Gaussian fits of Planck beams from the observations of planets, but in general, an arbitrary mathematical representation of the beam can be used on input);
* follow exactly the Planck scanning, and project the intrinsic beam on the sky at each actual sampling position
+
* exactly follow the Planck scanning, and project the intrinsic beam on the sky at each actual sampling position;
* project instantaneous beams onto the pixelized map over a small region (typically <2.5 FWHM diameter)
+
* project instantaneous beams onto the pixelized map over a small region (typically <2.5 FWHM in diameter);
* add up all beams that cross the same pixel and its vicinity over the observing period of interest
+
* add up all beams that cross the same pixel and its vicinity over the observing period of interest,
*create a data object of all beams pointed at all N'_pix_' directions of pixels in the map at a resolution at which this precomputation was executed (dimension N'_pix_' x a few hundred)
+
*create a data object of all beams pointed at all <i>N</i><sub>pix</sub> directions of pixels in the map at a resolution at which this precomputation was executed (dimension <i>N</i><sub>pix</sub> times a few hundred);
*use the resulting beam object for very fast convolution of all sky signals with the effective optical response of the observing mission
+
*use the resulting beam object for very fast convolution of all sky signals with the effective optical response of the observing mission.
  
 +
Computation of the effective beams at each pixel for every detector is a challenging task for high resolution experiments. FEBeCoP is an efficient algorithm and implementation, which enabled us to compute the pixel-based effective beams using moderate computational resources. The algorithm used different mathematical and computational techniques to bring down the computation cost to a practical level, so that several estimations of the effective beams were possible for all Planck detectors for different scan and beam models, as well as different lengths of data set.
  
Computation of the effective beams at each pixel for every detector is a challenging task for high resolution experiments. FEBeCoP is an efficient algorithm and implementation which enabled us to compute the pixel based effective beams using moderate computational resources. The algorithm used different mathematical and computational techniques to bring down the computation cost to a practical level, whereby several estimations of the effective beams were possible for all Planck detectors for different scan and beam models, as well as different lengths of datasets.
 
  
 +
===Pixel-ordered detector angles (PODA)===
 +
The main challenge in computing the effective beams is to go through the roughly trillion samples, which becomes severely limited by I/O. In the first stage, for a given data set, ordered lists of pointing angles for each pixel (the pixel-ordered detector angles, PODA) are made. This is an one-time process for each data set. We used computers with large memory and tedious memory management and bookkeeping to make this step efficient.
  
===Pixel Ordered Detector Angles (PODA)===
+
===Effective beam===
The main challenge in computing the effective beams is to go through the trillion samples, which gets severely limited by I/O. In the first stage, for a given dataset, ordered lists of pointing angles for each pixel - the Pixel Ordered Detector Angles (PODA) are made. This is an one-time process for each dataset. We used computers with large memory and used tedious memory management bookkeeping to make this step efficient.
+
The "effBeam" part makes use of the precomputed PODA and unsynchronized reading from the disk to compute the beam. Here we have tried to made sure that no repetition occurs in evaluating any trigonometric quantity.
  
===effBeam===
 
The effBeam part makes use of the precomputed PODA and unsynchronized reading from the disk to compute the beam. Here we tried to made sure that no repetition occurs in evaluating a trigonometric quantity.
 
 
 
One important reason for separating the two steps is that they use different schemes of parallel computing. The PODA part requires parallelisation over time-order-data samples, while the  effBeam part requires distribution of pixels among different computers.
 
  
 +
One important reason for separating the two steps is that they use different parallel computing schemes. The PODA part requires parallelization over time-ordered data samples, while the  effBeam part requires distribution of pixels among different computers.
  
 
===Computational Cost===
 
===Computational Cost===
The computation of the effective beams has been performed at the NERSC Supercomputing Center. The table below shows the computation cost for FEBeCoP processing of the nominal mission.
+
The computation of the effective beams has been performed at the NERSC Supercomputing Center. The table below shows the computational cost for FEBeCoP processing of the nominal mission.
  
 
{|border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
 
{|border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
|+ '''Computational cost for PODA, Effective Beam and  single map convolution. Wall-clock time is given as a guide, as found on the NERSC supercomputers.'''
+
|+ '''Computational cost for PODA, effective beam and  single map convolution. Wall-clock time is given as a guide, as found on the NERSC supercomputers.'''
 
|-
 
|-
|Channel ||030 || 044 || 070 || 100 || 143 || 217 || 353 || 545 || 857
+
|Channel [GHz] ||030 || 044 || 070 || 100 || 143 || 217 || 353 || 545 || 857
 
|-
 
|-
|PODA/Detector Computation time (CPU hrs) || 85 || 100  || 250 || 500 || 500 || 500 || 500 || 500 || 500  
+
|PODA/detector computation time [CPU hrs] || 85 || 100  || 250 || 500 || 500 || 500 || 500 || 500 || 500  
 
|-
 
|-
|PODA/Detector Computation time (wall clock hrs) || 7 || 10  || 20 || 20 || 20 || 20 || 20 || 20 || 20
+
|PODA/detector computation time [wall clock hrs] || 7 || 10  || 20 || 20 || 20 || 20 || 20 || 20 || 20
 
|-  
 
|-  
|Beam/Channel Computation time (CPU hrs) || 900 || 2000 || 2300 || 2800 ||  3800 || 3200 || 3000 || 900 || 1100
+
|Beam/channel computation time [CPU hrs] || 900 || 2000 || 2300 || 2800 ||  3800 || 3200 || 3000 || 900 || 1100
 
|-
 
|-
|Beam/Channel Computation time (wall clock hrs) || 0.5 || 0.8  || 1 || 1.5 || 2 || 1.2 || 1 || 0.5 || 0.5
+
|Beam/channel computation time [wall clock hrs] || 0.5 || 0.8  || 1 || 1.5 || 2 || 1.2 || 1 || 0.5 || 0.5
 
|-
 
|-
|Convolution Computation time (CPU hr) || 1 || 1.2 || 1.3 || 3.6 || 4.8 || 4.0 || 4.1 || 4.1 || 3.7  
+
|convolution computation time [CPU hrs] || 1 || 1.2 || 1.3 || 3.6 || 4.8 || 4.0 || 4.1 || 4.1 || 3.7  
 
|-
 
|-
|Convolution Computation time (wall clock sec) || 1 || 1 || 1 || 4 || 4 || 4 || 4 || 4 || 4  
+
|convolution computation time [wall clock sec] || 1 || 1 || 1 || 4 || 4 || 4 || 4 || 4 || 4  
 
|-
 
|-
|Effective Beam Size (GB) || 173 || 123 || 28 || 187 || 182 || 146 || 132 || 139 || 124
+
|Effective beam size [GB] || 173 || 123 || 28 || 187 || 182 || 146 || 132 || 139 || 124
 
|}
 
|}
  
  
The computation cost, especially for PODA and Convolution, is heavily limited by the I/O capacity of the disc and so it depends on the overall usage of the cluster done by other users.
+
The computation cost, especially for PODA and convolution, is heavily limited by the I/O capacity of the disk and so it depends on the overall usage of the cluster by other users.
  
 
==Inputs==
 
==Inputs==
In order to fix the convention of presentation of the scanning and effective beams, we show the classic view of the Planck focal plane as seen by the incoming CMB photon. The scan direction is marked, and the toward the center of the focal plane is at the 85 deg angle w.r.t spin axis pointing upward in the picture.  
+
In order to describe the convention of presentation of the scanning and effective beams, we show the classic view of the Planck focal plane as seen by incoming CMB photons. The scan direction is marked, and the centre of the focal plane is at an angle of 85&deg; with respect to the spin axis, pointing upward in the picture.  
  
  
[[File:PlanckFocalPlane.png | 500px| thumb | center|'''Planck Focal Plane''']]
+
[[File:PlanckFocalPlane.png | 500px| thumb | center|'''Planck focal plane.''']]
  
  
===The Focal Plane DataBase (FPDB)===
+
===The focal plane database (FPDB)===
The FPDB contains information on each detector, e.g., the orientation of the polarisation axis, different weight factors, (see the instrument [[The RIMO|RIMOs]]):
+
The FPDB contains information on each detector, e.g., the orientation of the polarization axis, and different weight factors. Details are provided in the instrument [[The RIMO|RIMOs]]):
  
*HFI - {{PLASingleFile|fileType=rimo|name=HFI_RIMO_R1.00.fits|link=The HFI RIMO}}
+
*for HFI - {{PLASingleFile|fileType=rimo|name=HFI_RIMO_R1.00.fits|link=the HFI RIMO}};
*LFI - {{PLASingleFile|fileType=rimo|name=LFI_RIMO_R1.12.fits|link=The LFI RIMO}}
+
*for LFI - {{PLASingleFile|fileType=rimo|name=LFI_RIMO_R1.12.fits|link=the LFI RIMO}}.
  
  
Line 246: Line 245:
  
 
===The scanning strategy===
 
===The scanning strategy===
The scanning strategy, the three pointing angle for each detector for each sample: Detector pointings for the nominal mission covers about 15 months of observation from Operational Day (OD) 91 to OD 563 covering 3 surveys and half.
+
The scanning strategy description consists of the three pointing angles for each detector for each sampleDetector pointings for the nominal mission cover about 15 months of observation from Operational Day (OD) 91 to OD 563, covering three and a half surveys.
  
===The scanbeam===
+
===The scanning beam===
The scanbeam modeled for each detector through the observation of planets. Which was assumed to be constant over the whole mission, though FEBeCoP could be used for a few sets of scanbeams too.
+
The "scanbeam" is modelled for each detector through the observation of planets. This was assumed to be constant over the whole mission, although FEBeCoP could be used for a few sets of scanbeams too.
  
* LFI: [[Beams LFI#Main beams and Focalplane calibration|GRASP scanning beam]] - the scanning beams used are based on Radio Frequency Tuned Model (RFTM) smeared to simulate the in-flight optical response.  
+
* For LFI the [[Beams LFI#Main beams and Focalplane calibration|GRASP scanning beams]] are used; these are based on the radio-frequency tuned model (RFTM), smeared to simulate the in-flight optical response.  
* HFI: [[Beams#Scanning beams|B-Spline, BS]] based on 2 observations of Mars.
+
* For HFI the [[Beams#Scanning beams|B-Spline, BS]] beams are used based on two observations of Mars.
  
(see the instrument [[The RIMO|RIMOs]]).
 
  
 
<!--
 
<!--
Line 264: Line 262:
  
 
===Beam cutoff radii===
 
===Beam cutoff radii===
N times geometric mean of FWHM of all detectors in a channel, where N
+
The cutoffs are set to <i>N</i> times the geometric mean of the FWHM of all detectors in a channel, where <i>N</i> is given below.
  
 
{|border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
 
{|border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
|+'''Beam cut off radius'''
+
|+'''Beam cut off radius.'''
| '''channel''' || '''Cutoff Radii in units of fwhm''' || '''fwhm of full beam extent'''  
+
| '''Channel [GHz]''' || '''Cutoff radii in units of FWHM''' || '''FWHM of full beam extent [arcmin]'''  
 
|-
 
|-
|30 - 44 - 70 || 2.5 ||
+
|30, 44, 70 || 2.5 ||
 
|-
 
|-
 
|100 || 2.25 || 23.703699
 
|100 || 2.25 || 23.703699
Line 276: Line 274:
 
|143 || 3 || 21.057402
 
|143 || 3 || 21.057402
 
|-
 
|-
|217-353 || 4 || 18.782754
+
|217, 353 || 4 || 18.782754
 +
|-
 +
|545 || 4 || 18.327635
 
|-
 
|-
|sub-mm || 4 || 18.327635(545GHz) ;  17.093706(857GHz)
+
|857 || 4 || 17.093706  
 
|}
 
|}
  
 
===Map resolution for the derived beam data object===
 
===Map resolution for the derived beam data object===
* <math>N_{side} = 1024 </math> for LFI frequency channels
+
The resolution is
* <math>N_{side} = 2048 </math> for HFI frequency channels
+
* <i>N</i><sub>side</sub> = 1024 for LFI frequency channels, and
 +
* <i>N</i><sub>side</sub> = 2048 for HFI frequency channels.
  
 
==Related products==
 
==Related products==
 
===Monte Carlo simulations===
 
===Monte Carlo simulations===
  
FEBeCoP software enables fast, full-sky convolutions of the sky signals with the Effective beams in pixel domain. Hence, a large number of Monte Carlo simulations of the sky signal maps map convolved with realistically rendered, spatially varying, asymmetric Planck beams can be easily generated. We performed the following steps:
+
FEBeCoP software enables fast, full-sky convolutions of the sky signals with the effective beams in the pixel domain. Hence, a large number of Monte Carlo simulations of the sky signal maps can be easily generated, which are convolved with realistically rendered, spatially varying, asymmetric Planck beams. We performed the following steps:
  
* generate the effective beams with FEBeCoP for all frequencies for dDX9 data and Nominal Mission
+
* generate the effective beams with FEBeCoP for all frequencies for "dDX9" data and the Nominal Mission;
* generate 100 realizations of maps from a fiducial CMB power spectrum
+
* generate 100 realizations of maps from a fiducial CMB power spectrum;
* convolve each one of these maps with the effective beams using FEBeCoP
+
* convolve each one of these maps with the effective beams using FEBeCoP;
* estimate the average of the Power Spectrum of each convolved realization, and 1 <math>\sigma</math> errors
+
* estimate the average of the power spectrum of each convolved realization, and 1 &sigma; errors.
  
  
As FEBeCoP enables fast convolutions of the input signal sky with the effective beam, thousands of simulations are generated. These Monte Carlo simulations of the signal (might it be CMB or a foreground (e.g. dust)) sky along with LevelS+Madam noise simulations were used widely for the analysis of Planck data. A suite of simulations were rendered during the mission tagged as Full Focalplane simulations, FFP#.
+
Since FEBeCoP enables fast convolutions of the input signal sky with the effective beam, thousands of simulations can be generated. These Monte Carlo simulations of the sky signal (which might be CMB or a foreground, e.g., dust) along with LevelS+Madam noise simulations were used widely for the analysis of Planck data. A suite of simulations were rendered during the mission and tagged as full focal-plane simulations, FFP#
For example [[HL-sims#FFP6 data set|FFP6]]  
+
(for example the [[HL-sims#FFP6 data set|FFP6]]).
  
 
===Beam Window Functions===
 
===Beam Window Functions===
The '''Transfer Function''' or the '''Beam Window Function'''  <math> W_l </math> relates the true angular power spectra <math>C_l </math> with the observed angular power spectra <math>\widetilde{C}_l </math>:
+
The "Transfer Function" or the "Beam Window Function", <i>W</i><sub>&#8467;</sub> relates the true angular power spectra <i>C</i><sub>&#8467;</sub> with the observed angular power spectra &#264;<sub>&#8467;</sub>:
  
 
<math>
 
<math>
W_l= \widetilde{C}_l / C_l
+
W_l= \tilde{C}_\ell / C_\ell .
 
\label{eqn:wl1}</math>  
 
\label{eqn:wl1}</math>  
  
Note that, the window function can contain a pixel window function (depending on the definition) and it is {\em not the angular power spectra of the scanbeams}, though, in principle, one may be able to connect them though fairly complicated algebra.
+
Note that, the window function can contain a pixel window function (depending on the definition) and it is <i>not the angular power spectra of the scanbeams</i>, although in principle one may be able to connect them via some complicated algebra.
  
The window functions are estimated by performing Monte-Carlo simulations. We generate several random realisations of the CMB sky starting from a given fiducial <math> C_l </math>, convolve the maps with the pre-computed effective beams, compute the convolved power spectra <math> C^\text{conv}_l </math>, divide by the power spectra of the unconvolved map <math>C^\text{in}_l </math> and average over their ratio. Thus, the estimated window function
+
The window functions are estimated by performing Monte Carlo simulations. We generate several random realizations of the CMB sky, starting from a given fiducial <i>C</i><sub>&#8467;</sub>, convolve the maps with the pre-computed effective beams, compute the convolved power spectra <i>C</i><sub>&#8467;</sub><sup>conv</sup>, divide by the power spectra of the unconvolved map <i>C</i><sub>&#8467;</sub><sup>in</sup> and average over their ratio. Thus, the estimated window function is
  
 
<math>
 
<math>
W^{est}_l = < C^{conv}_l /  C^{in}_l >
+
W^{\rm est}_\ell = < C^{\rm conv}_\ell /  C^{\rm in}_\ell >.
 
\label{eqn:wl2}</math>  
 
\label{eqn:wl2}</math>  
  
For subtle reasons, we perform a more rigorous estimation of the window function by comparing C^{conv}_l with convolved power spectra of the input maps convolved with a symmetric Gaussian beam of comparable (but need not be exact) size and then scaling the estimated window function accordingly.
+
For subtle reasons, we perform a more rigorous estimation of the window function by comparing <i>C</i><sub>&#8467;</sub><sup>conv</sup> with convolved power spectra of the input maps convolved with a symmetric Gaussian beam of comparable (but not necessarily exactly the same) size and then scaling the estimated window function accordingly.
  
 
Beam window functions are provided in the [[The RIMO#Beam Window Functions|RIMO]].  
 
Beam window functions are provided in the [[The RIMO#Beam Window Functions|RIMO]].  
  
  
====Beam Window functions, Wl, for Planck mission====
+
====Beam window functions, <i>W</i><sub>&#8467;</sub>, for the Planck mission.====
[[File:plot_dx9_LFI_GB_pix.png | 600px | thumb | center |'''Beam Window functions, Wl, for LFI channels''']]  
+
[[File:plot_dx9_LFI_GB_pix.png | 600px | thumb | center |'''Beam window functions, <i>W</i><sub>&#8467;</sub>, for LFI channels.''']]  
[[File:plot_dx9_HFI_BS_M12_CMB.png | 600px | thumb | |center |'''Beam Window functions, Wl, for HFI channels''']]
+
[[File:plot_dx9_HFI_BS_M12_CMB.png | 600px | thumb | |center |'''Beam window functions, <i>W</i><sub>&#8467;</sub>, for HFI channels.''']]
  
 
==File Names==
 
==File Names==
The effective beams are provided by the PLA as FITS files containg HEALPix maps of the beams. For the file names the following convention is used:
+
The effective beams are provided in the PLA as FITS files containg HEALPix maps of the beams. For the file names the following convention is used.
*Single beam query: '''beams_FFF_''PixelNumber''.fits'''
+
*Single beam query, "beams_FFF_''PixelNumber''.fits" :
**FFF is the channel frequency (one of '''30''', '''44''', '''70''', '''100''', '''143''', '''217''', '''353''', '''545''', '''857''');  
+
** FFF is the channel frequency (one of "30", "44", "70", "100", "143", "217", "353", "545", "857");  
** ''PixelNumber'' is the number of the pixel to which the beam corresponds (<math>0</math> - <math>12 \times N_{\rm side}^2 - 1</math>). For the LFI <math>N_{\rm side}=1024</math>, for the HFI <math>N_{\rm side}=2048</math>;
+
** "PixelNumber" is the number of the pixel to which the beam corresponds, 0&ndash;12 &times; <i>N</i><sub>side</sub><sup>2</sup> - 1, with <i>N</i><sub>side</sub>=1024 for the LFI and <i>N</i><sub>side</sub>=2048 for the HFI.
*Multiple beam query: '''beams_FFF_''FirstPixelNumber''-''LastPixelNumber''.zip''' <br /> The compressed files contains a set of files with the beams for the pixels covereing the selected region. FFF as for sinle beam query. The naming convention for the beam files contained in the ''.zip'' file is the same as for single beam queries.
+
*Multiple beam query, "beams_FFF_''FirstPixelNumber''-''LastPixelNumber''.zip" .
 +
** The compressed files contains a set of files with the beams for the pixels covereing the selected region, with "FFF" as for sinle beam query and the naming convention for the beam files contained in the ''.zip'' file being the same as for single beam queries;
 
** ''FirstPixelNumber'' is the lowest pixel number for the area covered by the request;
 
** ''FirstPixelNumber'' is the lowest pixel number for the area covered by the request;
** ''LastPixelNumber'' is the highest pixel number for the area covered by the request;
+
** ''LastPixelNumber'' is the highest pixel number for the area covered by the request.
  
 
==File format==
 
==File format==
The FITS files provided by the PLA contain HEALPix maps of the beams.
+
The FITS files provided in the PLA contain HEALPix maps of the beams.
 
 
  
 
== Previous Releases: (2015) and (2013) effective beams ==
 
== Previous Releases: (2015) and (2013) effective beams ==

Latest revision as of 02:01, 22 March 2018


Product description[edit]

The "effective beam" is the average of all scanning beams pointing at a certain direction within a given pixel of the sky map for a given scan strategy. It takes into account the coupling between azimuthal asymmetry of the beam and the uneven distribution of scanning angles across the sky. It captures the complete information about the difference between the true and observed images of the sky. The effective beams are, by definition, the objects whose convolution with the true CMB sky produce the observed sky map.

Details of the beam processing are given in the respective sections for HFI and LFI.

The full algebra involving the effective beams for temperature and polarization was presented in [1], and a discussion of its application to Planck data is given in the appropriate LFI (Planck-2013-IV[2], Planck-2015-A05[3]) and HFI (Planck-2013-VII[4]) papers. Relevant details of the processing steps are given in the Effective Beams section of this document.


Comparison of the images of compact sources observed by Planck with FEBeCoP products[edit]

We show here a comparison of the FEBeCoP-derived effective beams, and associated point spread functions, PSF (the transpose of the beam matrix), to the actual images for a few example compact sources observed by Planck, for all LFI and HFI frequency channels. We show below a few panels of source images organized as follows:

  • Row #1 - DX9 images of four ERCSC objects with their Galactic (l,b) coordinates shown under the colour bar;
  • Row #2 - linear scale FEBeCoP PSFs computed using input scanning beams, Grasp Beams (GBs) for LFI and B-Spline beams (BSs) of Mars12 apodized for the HFI CMB channels and Mars12 for the sub-mm channels (see section "Inputs" below);
  • Row #3 - log scale of #2, PSF iso-contours being shown as solid lines, elliptical Gaussian fit iso-contours shown as broken lines.

Histograms of the effective beam parameters[edit]

Here we present histograms of the three fit parameters, i.e., beam FWHM, ellipticity, and orientation with respect to the local meridian, and of the beam solid angle. The sky is uniformly sampled (although fairly sparsely) in 3072 directions that were chosen as HEALPix Nside=16 pixel centres for HFI and in 768 directions that were chosen as HEALPix Nside=8 pixel centres for LFI.

Here the beam solid angle is estimated according to the definition: "4π Σ(effbeam)/max(effbeam)" i.e., 4π Σ(Bij) / max(Bij).


Histograms for LFI effective beam parameters.
Histograms for HFI effective beam parameters.

Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian[edit]

  • The discontinuities at the HEALPix domain edges in the maps are a visual artefact due to the interplay of the discretized effective beam and the HEALPix pixel grid.






Statistics of the effective beams computed using FEBeCoP[edit]

Below we tabulate the simple statistics of FWHM, ellipticity (e), orientation (ψ) and beam solid angle, (Ω), for a sample of 3072 and 768 directions on the sky for HFI and LFI data, respectively. Statistics shown in the Table are derived from the histograms shown above.

  • The derived beam parameters are representative of the DPC Nside 1024 and 2048 HEALPix maps (including the pixel window function).
  • The reported FWHMeff values are derived from the beam solid angles, under a Gaussian approximation. These are appropriate for flux determination, while the the Gaussian fits to the effective beam maps are more suited for source identification.


Statistics of the FEBeCoP effective beams computed with the BS Mars12 data apodized for the CMB channels and oversampled.
Frequency [GHz] Mean(FWHM) [arcmin] σ(FWHM) [arcmin] Mean(e) σ(e) Mean(ψ) [deg] σ(ψ) [deg] Mean(Ω) [arcmin2] σ(Ω) [arcmin2] FWHMeff [arcmin]
30 32.239 0.013 1.320 0.031 -0.304 55.349 1189.513 0.842 32.34
44 27.005 0.552 1.034 0.033 0.059 53.767 832.946 31.774 27.12
070 13.252 0.033 1.223 0.026 0.587 55.066 200.742 1.027 13.31
100 9.651 0.014 1.186 0.023 -0.024 55.400 105.778 0.311 9.66
143 7.248 0.015 1.036 0.009 0.383 54.130 59.954 0.246 7.27
217 4.990 0.025 1.177 0.030 0.836 54.999 28.447 0.271 5.01
353 4.818 0.024 1.147 0.028 0.655 54.745 26.714 0.250 4.86
545 4.682 0.044 1.161 0.036 0.544 54.876 26.535 0.339 4.84
857 4.325 0.055 1.393 0.076 0.876 54.779 24.244 0.193 4.63


Beam solid angles for the PCCS[edit]

For the Planck Catalogue of Compact Sources we also need the following definitions.

  • Ωeff - is the mean beam solid angle of the effective beam, where the solid angle is estimated according to the definition "4 π Σ(effbeam)/max(effbeam)", i.e., as an integral over the full extent of the effective beam, 4π Σ (Bij)/max(Bij).
  • From Ωeff we estimate FWHMeff, under a Gaussian approximation - these are tabulated above.
  • Ω(1)eff is the beam solid angle estimated up to a radius equal to 1 FWHMeff and Ω(2)eff up to a radius equal to twice the FWHMeff.

These were estimated according to the procedure followed in the aperture photometry code for the PCCS; if the pixel centre does not lie within the given radius it is not included (so "inclusive=0" in query disc).


Band averaged beam solid angles
Band [GHz] Ωeff[arcmin2] Spatial variation [arcmin2] Ω(1)eff [arcmin2] Spatial variation-1 [arcmin2] Ω(2)eff [arcmin2] Spatial variation-2 [arcmin2]
30 1189.513 0.842 1116.494 2.274 1188.945 0.847
44 832.946 31.774 758.684 29.701 832.168 31.811
70 200.742 1.027 186.260 2.300 200.591 1.027
100 105.778 0.311 100.830 0.410 105.777 0.311
143 59.954 0.246 56.811 0.419 59.952 0.246
217 28.447 0.271 26.442 0.537 28.426 0.271
353 26.714 0.250 24.827 0.435 26.653 0.250
545 26.535 0.339 24.287 0.455 26.302 0.337
857 24.244 0.193 22.646 0.263 23.985 0.191

Production process[edit]

FEBeCoP, the Fast Effective Beam Convolution in Pixel space[1], is an approach for representing and computing effective beams (including both intrinsic beam shapes and the effects of scanning) that comprises the following steps:

  • identify the individual detectors' instantaneous optical response function (presently we use elliptical Gaussian fits of Planck beams from the observations of planets, but in general, an arbitrary mathematical representation of the beam can be used on input);
  • exactly follow the Planck scanning, and project the intrinsic beam on the sky at each actual sampling position;
  • project instantaneous beams onto the pixelized map over a small region (typically <2.5 FWHM in diameter);
  • add up all beams that cross the same pixel and its vicinity over the observing period of interest,
  • create a data object of all beams pointed at all Npix directions of pixels in the map at a resolution at which this precomputation was executed (dimension Npix times a few hundred);
  • use the resulting beam object for very fast convolution of all sky signals with the effective optical response of the observing mission.

Computation of the effective beams at each pixel for every detector is a challenging task for high resolution experiments. FEBeCoP is an efficient algorithm and implementation, which enabled us to compute the pixel-based effective beams using moderate computational resources. The algorithm used different mathematical and computational techniques to bring down the computation cost to a practical level, so that several estimations of the effective beams were possible for all Planck detectors for different scan and beam models, as well as different lengths of data set.


Pixel-ordered detector angles (PODA)[edit]

The main challenge in computing the effective beams is to go through the roughly trillion samples, which becomes severely limited by I/O. In the first stage, for a given data set, ordered lists of pointing angles for each pixel (the pixel-ordered detector angles, PODA) are made. This is an one-time process for each data set. We used computers with large memory and tedious memory management and bookkeeping to make this step efficient.

Effective beam[edit]

The "effBeam" part makes use of the precomputed PODA and unsynchronized reading from the disk to compute the beam. Here we have tried to made sure that no repetition occurs in evaluating any trigonometric quantity.


One important reason for separating the two steps is that they use different parallel computing schemes. The PODA part requires parallelization over time-ordered data samples, while the effBeam part requires distribution of pixels among different computers.

Computational Cost[edit]

The computation of the effective beams has been performed at the NERSC Supercomputing Center. The table below shows the computational cost for FEBeCoP processing of the nominal mission.

Computational cost for PODA, effective beam and single map convolution. Wall-clock time is given as a guide, as found on the NERSC supercomputers.
Channel [GHz] 030 044 070 100 143 217 353 545 857
PODA/detector computation time [CPU hrs] 85 100 250 500 500 500 500 500 500
PODA/detector computation time [wall clock hrs] 7 10 20 20 20 20 20 20 20
Beam/channel computation time [CPU hrs] 900 2000 2300 2800 3800 3200 3000 900 1100
Beam/channel computation time [wall clock hrs] 0.5 0.8 1 1.5 2 1.2 1 0.5 0.5
convolution computation time [CPU hrs] 1 1.2 1.3 3.6 4.8 4.0 4.1 4.1 3.7
convolution computation time [wall clock sec] 1 1 1 4 4 4 4 4 4
Effective beam size [GB] 173 123 28 187 182 146 132 139 124


The computation cost, especially for PODA and convolution, is heavily limited by the I/O capacity of the disk and so it depends on the overall usage of the cluster by other users.

Inputs[edit]

In order to describe the convention of presentation of the scanning and effective beams, we show the classic view of the Planck focal plane as seen by incoming CMB photons. The scan direction is marked, and the centre of the focal plane is at an angle of 85° with respect to the spin axis, pointing upward in the picture.


Planck focal plane.


The focal plane database (FPDB)[edit]

The FPDB contains information on each detector, e.g., the orientation of the polarization axis, and different weight factors. Details are provided in the instrument RIMOs):


The scanning strategy[edit]

The scanning strategy description consists of the three pointing angles for each detector for each sample. Detector pointings for the nominal mission cover about 15 months of observation from Operational Day (OD) 91 to OD 563, covering three and a half surveys.

The scanning beam[edit]

The "scanbeam" is modelled for each detector through the observation of planets. This was assumed to be constant over the whole mission, although FEBeCoP could be used for a few sets of scanbeams too.

  • For LFI the GRASP scanning beams are used; these are based on the radio-frequency tuned model (RFTM), smeared to simulate the in-flight optical response.
  • For HFI the B-Spline, BS beams are used based on two observations of Mars.


Beam cutoff radii[edit]

The cutoffs are set to N times the geometric mean of the FWHM of all detectors in a channel, where N is given below.

Beam cut off radius.
Channel [GHz] Cutoff radii in units of FWHM FWHM of full beam extent [arcmin]
30, 44, 70 2.5
100 2.25 23.703699
143 3 21.057402
217, 353 4 18.782754
545 4 18.327635
857 4 17.093706

Map resolution for the derived beam data object[edit]

The resolution is

  • Nside = 1024 for LFI frequency channels, and
  • Nside = 2048 for HFI frequency channels.

Related products[edit]

Monte Carlo simulations[edit]

FEBeCoP software enables fast, full-sky convolutions of the sky signals with the effective beams in the pixel domain. Hence, a large number of Monte Carlo simulations of the sky signal maps can be easily generated, which are convolved with realistically rendered, spatially varying, asymmetric Planck beams. We performed the following steps:

  • generate the effective beams with FEBeCoP for all frequencies for "dDX9" data and the Nominal Mission;
  • generate 100 realizations of maps from a fiducial CMB power spectrum;
  • convolve each one of these maps with the effective beams using FEBeCoP;
  • estimate the average of the power spectrum of each convolved realization, and 1 σ errors.


Since FEBeCoP enables fast convolutions of the input signal sky with the effective beam, thousands of simulations can be generated. These Monte Carlo simulations of the sky signal (which might be CMB or a foreground, e.g., dust) along with LevelS+Madam noise simulations were used widely for the analysis of Planck data. A suite of simulations were rendered during the mission and tagged as full focal-plane simulations, FFP# (for example the FFP6).

Beam Window Functions[edit]

The "Transfer Function" or the "Beam Window Function", W relates the true angular power spectra C with the observed angular power spectra Ĉ:

[math] W_l= \tilde{C}_\ell / C_\ell . \label{eqn:wl1}[/math]

Note that, the window function can contain a pixel window function (depending on the definition) and it is not the angular power spectra of the scanbeams, although in principle one may be able to connect them via some complicated algebra.

The window functions are estimated by performing Monte Carlo simulations. We generate several random realizations of the CMB sky, starting from a given fiducial C, convolve the maps with the pre-computed effective beams, compute the convolved power spectra Cconv, divide by the power spectra of the unconvolved map Cin and average over their ratio. Thus, the estimated window function is

[math] W^{\rm est}_\ell = \lt C^{\rm conv}_\ell / C^{\rm in}_\ell \gt . \label{eqn:wl2}[/math]

For subtle reasons, we perform a more rigorous estimation of the window function by comparing Cconv with convolved power spectra of the input maps convolved with a symmetric Gaussian beam of comparable (but not necessarily exactly the same) size and then scaling the estimated window function accordingly.

Beam window functions are provided in the RIMO.


Beam window functions, W, for the Planck mission.[edit]

Beam window functions, W, for LFI channels.
Beam window functions, W, for HFI channels.

File Names[edit]

The effective beams are provided in the PLA as FITS files containg HEALPix maps of the beams. For the file names the following convention is used.

  • Single beam query, "beams_FFF_PixelNumber.fits" :
    • FFF is the channel frequency (one of "30", "44", "70", "100", "143", "217", "353", "545", "857");
    • "PixelNumber" is the number of the pixel to which the beam corresponds, 0–12 × Nside2 - 1, with Nside=1024 for the LFI and Nside=2048 for the HFI.
  • Multiple beam query, "beams_FFF_FirstPixelNumber-LastPixelNumber.zip" .
    • The compressed files contains a set of files with the beams for the pixels covereing the selected region, with "FFF" as for sinle beam query and the naming convention for the beam files contained in the .zip file being the same as for single beam queries;
    • FirstPixelNumber is the lowest pixel number for the area covered by the request;
    • LastPixelNumber is the highest pixel number for the area covered by the request.

File format[edit]

The FITS files provided in the PLA contain HEALPix maps of the beams.

Previous Releases: (2015) and (2013) effective beams[edit]

2015 Release of effective beams

Product description The effective beam is the average of all scanning beams pointing at a certain direction within a given pixel of the sky map for a given scan strategy. It takes into account the coupling between azimuthal asymmetry of the beam and the uneven distribution of scanning angles across the sky. It captures the complete information about the difference between the true and observed image of the sky. The effective beams are, by definition, the objects whose convolution with the true CMB sky produce the observed sky map.

Details of the beam processing are given in the respective pages for HFI and LFI.

The full algebra involving the effective beams for temperature and polarisation was presented in [1], and a discussion of its application to Planck data is given in the appropriate LFI Planck-2013-IV[2], Planck-2015-A05[3] and HFI Planck-2013-VII[4] papers. Relevant details of the processing steps are given in the Effective Beams section of this document.


Comparison of the images of compact sources observed by Planck with FEBeCoP products We show here a comparison of the FEBeCoP-derived effective beams, and associated point spread functions, PSF (the transpose of the beam matrix), to the actual images of a few compact sources observed by Planck, for all LFI and HFI frequency channels, as an example. We show below a few panels of source images organized as follows:

  • Row #1- DX9 images of four ERCSC objects with their galactic (l,b) coordinates shown under the color bar
  • Row #2- linear scale FEBeCoP PSFs computed using input scanning beams, Grasp Beams, GB, for LFI and B-Spline beams,BS, Mars12 apodized for the CMB channels and the BS Mars12 for the sub-mm channels, for HFI (see section Inputs below).
  • Row #3- log scale of #2; PSF iso-contours shown in solid line, elliptical Gaussian fit iso-contours shown in broken line

Histograms of the effective beam parameters Here we present histograms of the three fit parameters - beam FWHM, ellipticity, and orientation with respect to the local meridian and of the beam solid angle. The sky is sampled (pretty sparsely) at 3072 directions which were chosen as HEALpix nside=16 pixel centers for HFI and at 768 directions which were chosen as HEALpix nside=8 pixel centers for LFI. These uniformly sample the sky.

Where beam solid angle is estimated according to the definition: [math] 4 \pi \sum[/math](effbeam)/max(effbeam) i.e., [math] 4 \pi \sum(B_{ij}) / max(B_{ij}) [/math]


Histograms for LFI effective beam parameters
Histograms for HFI effective beam parameters

Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian

  • The discontinuities at the Healpix domain edges in the maps are a visual artifact due to the interplay of the discretized effective beam and the Healpix pixel grid.






Statistics of the effective beams computed using FEBeCoP

We tabulate the simple statistics of FWHM, ellipticity (e), orientation ([math] \psi[/math]) and beam solid angle, ([math] \Omega [/math]), for a sample of 3072 and 768 directions on the sky for HFI and LFI data respectively. Statistics shown in the Table are derived from the histograms shown above.

  • The derived beam parameters are representative of the DPC NSIDE 1024 and 2048 healpix maps (they include the pixel window function).
  • The reported FWHM_eff are derived from the beam solid angles, under a Gaussian approximation. These are best used for flux determination while the the Gaussian fits to the effective beam maps are more suited for source identification.


Statistics of the FEBeCoP Effective Beams Computed with the BS Mars12 apodized for the CMB channels and oversampled
frequency mean(fwhm) [arcmin] sd(fwhm) [arcmin] mean(e) sd(e) mean([math] \psi[/math]) [degree] sd([math] \psi[/math]) [degree] mean([math] \Omega [/math]) [arcmin[math]^{2}[/math]] sd([math] \Omega [/math]) [arcmin[math]^{2}[/math]] FWHM_eff [arcmin]
030 32.239 0.013 1.320 0.031 -0.304 55.349 1189.513 0.842 32.34
044 27.005 0.552 1.034 0.033 0.059 53.767 832.946 31.774 27.12
070 13.252 0.033 1.223 0.026 0.587 55.066 200.742 1.027 13.31
100 9.651 0.014 1.186 0.023 -0.024 55.400 105.778 0.311 9.66
143 7.248 0.015 1.036 0.009 0.383 54.130 59.954 0.246 7.27
217 4.990 0.025 1.177 0.030 0.836 54.999 28.447 0.271 5.01
353 4.818 0.024 1.147 0.028 0.655 54.745 26.714 0.250 4.86
545 4.682 0.044 1.161 0.036 0.544 54.876 26.535 0.339 4.84
857 4.325 0.055 1.393 0.076 0.876 54.779 24.244 0.193 4.63


Beam solid angles for the PCCS

  • [math]\Omega_{eff}[/math] - is the mean beam solid angle of the effective beam, where beam solid angle is estimated according to the definition: [math]4 \pi \sum [/math](effbeam)/max(effbeam), i.e. as an integral over the full extent of the effective beam, i.e. [math] 4 \pi \sum(B_{ij}) / max(B_{ij}) [/math].
  • from [math]\Omega_{eff}[/math] we estimate the [math]fwhm_{eff}[/math], under a Gaussian approximation - these are tabulated above
    • [math]\Omega^{(1)}_{eff}[/math] is the beam solid angle estimated up to a radius equal to one [math]fwhm_{eff}[/math] and [math]\Omega^{(2)}_{eff}[/math] up to a radius equal to twice the [math]fwhm_{eff}[/math].
      • These were estimated according to the procedure followed in the aperture photometry code for the PCCS: if the pixel centre does not lie within the given radius it is not included (so inclusive=0 in query disc).


Band averaged beam solid angles
Band [math]\Omega_{eff}[/math][arcmin[math]^{2}[/math]] spatial variation [arcmin[math]^{2}[/math]] [math]\Omega^{(1)}_{eff}[/math] [arcmin[math]^{2}[/math]] spatial variation-1 [arcmin[math]^{2}[/math]] [math]\Omega^{(2)}_{eff}[/math] [arcmin[math]^{2}[/math]] spatial variation-2 [arcmin[math]^{2}[/math]]
30 1189.513 0.842 1116.494 2.274 1188.945 0.847
44 832.946 31.774 758.684 29.701 832.168 31.811
70 200.742 1.027 186.260 2.300 200.591 1.027
100 105.778 0.311 100.830 0.410 105.777 0.311
143 59.954 0.246 56.811 0.419 59.952 0.246
217 28.447 0.271 26.442 0.537 28.426 0.271
353 26.714 0.250 24.827 0.435 26.653 0.250
545 26.535 0.339 24.287 0.455 26.302 0.337
857 24.244 0.193 22.646 0.263 23.985 0.191

Production process FEBeCoP, or Fast Effective Beam Convolution in Pixel space[1], is an approach to representing and computing effective beams (including both intrinsic beam shapes and the effects of scanning) that comprises the following steps:

  • identify the individual detectors' instantaneous optical response function (presently we use elliptical Gaussian fits of Planck beams from observations of planets; eventually, an arbitrary mathematical representation of the beam can be used on input)
  • follow exactly the Planck scanning, and project the intrinsic beam on the sky at each actual sampling position
  • project instantaneous beams onto the pixelized map over a small region (typically <2.5 FWHM diameter)
  • add up all beams that cross the same pixel and its vicinity over the observing period of interest
  • create a data object of all beams pointed at all N'_pix_' directions of pixels in the map at a resolution at which this precomputation was executed (dimension N'_pix_' x a few hundred)
  • use the resulting beam object for very fast convolution of all sky signals with the effective optical response of the observing mission


Computation of the effective beams at each pixel for every detector is a challenging task for high resolution experiments. FEBeCoP is an efficient algorithm and implementation which enabled us to compute the pixel based effective beams using moderate computational resources. The algorithm used different mathematical and computational techniques to bring down the computation cost to a practical level, whereby several estimations of the effective beams were possible for all Planck detectors for different scan and beam models, as well as different lengths of datasets.


Pixel Ordered Detector Angles (PODA) The main challenge in computing the effective beams is to go through the trillion samples, which gets severely limited by I/O. In the first stage, for a given dataset, ordered lists of pointing angles for each pixel - the Pixel Ordered Detector Angles (PODA) are made. This is an one-time process for each dataset. We used computers with large memory and used tedious memory management bookkeeping to make this step efficient.

effBeam The effBeam part makes use of the precomputed PODA and unsynchronized reading from the disk to compute the beam. Here we tried to made sure that no repetition occurs in evaluating a trigonometric quantity.


One important reason for separating the two steps is that they use different schemes of parallel computing. The PODA part requires parallelisation over time-order-data samples, while the effBeam part requires distribution of pixels among different computers.


Computational Cost The computation of the effective beams has been performed at the NERSC Supercomputing Center. The table below shows the computation cost for FEBeCoP processing of the nominal mission.

Computational cost for PODA, Effective Beam and single map convolution. Wall-clock time is given as a guide, as found on the NERSC supercomputers.
Channel 030 044 070 100 143 217 353 545 857
PODA/Detector Computation time (CPU hrs) 85 100 250 500 500 500 500 500 500
PODA/Detector Computation time (wall clock hrs) 7 10 20 20 20 20 20 20 20
Beam/Channel Computation time (CPU hrs) 900 2000 2300 2800 3800 3200 3000 900 1100
Beam/Channel Computation time (wall clock hrs) 0.5 0.8 1 1.5 2 1.2 1 0.5 0.5
Convolution Computation time (CPU hr) 1 1.2 1.3 3.6 4.8 4.0 4.1 4.1 3.7
Convolution Computation time (wall clock sec) 1 1 1 4 4 4 4 4 4
Effective Beam Size (GB) 173 123 28 187 182 146 132 139 124


The computation cost, especially for PODA and Convolution, is heavily limited by the I/O capacity of the disc and so it depends on the overall usage of the cluster done by other users.

Inputs In order to fix the convention of presentation of the scanning and effective beams, we show the classic view of the Planck focal plane as seen by the incoming CMB photon. The scan direction is marked, and the toward the center of the focal plane is at the 85 deg angle w.r.t spin axis pointing upward in the picture.


Planck Focal Plane


The Focal Plane DataBase (FPDB)

The FPDB contains information on each detector, e.g., the orientation of the polarisation axis, different weight factors, (see the instrument RIMOs):


The scanning strategy The scanning strategy, the three pointing angle for each detector for each sample: Detector pointings for the nominal mission covers about 15 months of observation from Operational Day (OD) 91 to OD 563 covering 3 surveys and half.

The scanbeam The scanbeam modeled for each detector through the observation of planets. Which was assumed to be constant over the whole mission, though FEBeCoP could be used for a few sets of scanbeams too.

  • LFI: GRASP scanning beam - the scanning beams used are based on Radio Frequency Tuned Model (RFTM) smeared to simulate the in-flight optical response.
  • HFI: B-Spline, BS based on 2 observations of Mars.

(see the instrument RIMOs).


Beam cutoff radii N times geometric mean of FWHM of all detectors in a channel, where N

Beam cut off radius
channel Cutoff Radii in units of fwhm fwhm of full beam extent
30 - 44 - 70 2.5
100 2.25 23.703699
143 3 21.057402
217-353 4 18.782754
sub-mm 4 18.327635(545GHz) ; 17.093706(857GHz)

Map resolution for the derived beam data object

  • [math]N_{side} = 1024 [/math] for LFI frequency channels
  • [math]N_{side} = 2048 [/math] for HFI frequency channels

Related products Monte Carlo simulations

FEBeCoP software enables fast, full-sky convolutions of the sky signals with the Effective beams in pixel domain. Hence, a large number of Monte Carlo simulations of the sky signal maps map convolved with realistically rendered, spatially varying, asymmetric Planck beams can be easily generated. We performed the following steps:

  • generate the effective beams with FEBeCoP for all frequencies for dDX9 data and Nominal Mission
  • generate 100 realizations of maps from a fiducial CMB power spectrum
  • convolve each one of these maps with the effective beams using FEBeCoP
  • estimate the average of the Power Spectrum of each convolved realization, and 1 [math]\sigma[/math] errors


As FEBeCoP enables fast convolutions of the input signal sky with the effective beam, thousands of simulations are generated. These Monte Carlo simulations of the signal (might it be CMB or a foreground (e.g. dust)) sky along with LevelS+Madam noise simulations were used widely for the analysis of Planck data. A suite of simulations were rendered during the mission tagged as Full Focalplane simulations, FFP#. For example FFP6

Beam Window Functions The Transfer Function or the Beam Window Function [math] W_l [/math] relates the true angular power spectra [math]C_l [/math] with the observed angular power spectra [math]\widetilde{C}_l [/math]:

[math] W_l= \widetilde{C}_l / C_l \label{eqn:wl1}[/math]

Note that, the window function can contain a pixel window function (depending on the definition) and it is {\em not the angular power spectra of the scanbeams}, though, in principle, one may be able to connect them though fairly complicated algebra.

The window functions are estimated by performing Monte-Carlo simulations. We generate several random realisations of the CMB sky starting from a given fiducial [math] C_l [/math], convolve the maps with the pre-computed effective beams, compute the convolved power spectra [math] C^\text{conv}_l [/math], divide by the power spectra of the unconvolved map [math]C^\text{in}_l [/math] and average over their ratio. Thus, the estimated window function

[math] W^{est}_l = \lt C^{conv}_l / C^{in}_l \gt \label{eqn:wl2}[/math]

For subtle reasons, we perform a more rigorous estimation of the window function by comparing C^{conv}_l with convolved power spectra of the input maps convolved with a symmetric Gaussian beam of comparable (but need not be exact) size and then scaling the estimated window function accordingly.

Beam window functions are provided in the RIMO.


Beam Window functions, Wl, for Planck mission

Beam Window functions, Wl, for LFI channels
Beam Window functions, Wl, for HFI channels

File Names The effective beams are provided by the PLA as FITS files containg HEALPix maps of the beams. For the file names the following convention is used:

  • Single beam query: beams_FFF_PixelNumber.fits
    • FFF is the channel frequency (one of 30, 44, 70, 100, 143, 217, 353, 545, 857);
    • PixelNumber is the number of the pixel to which the beam corresponds ([math]0[/math] - [math]12 \times N_{\rm side}^2 - 1[/math]). For the LFI [math]N_{\rm side}=1024[/math], for the HFI [math]N_{\rm side}=2048[/math];
  • Multiple beam query: beams_FFF_FirstPixelNumber-LastPixelNumber.zip
    The compressed files contains a set of files with the beams for the pixels covereing the selected region. FFF as for sinle beam query. The naming convention for the beam files contained in the .zip file is the same as for single beam queries.
    • FirstPixelNumber is the lowest pixel number for the area covered by the request;
    • LastPixelNumber is the highest pixel number for the area covered by the request;

File format The FITS files provided by the PLA contain HEALPix maps of the beams.

2013 Release of effective beams

Product description The effective beam is the average of all scanning beams pointing at a certain direction within a given pixel of the sky map for a given scan strategy. It takes into account the coupling between azimuthal asymmetry of the beam and the uneven distribution of scanning angles across the sky. It captures the complete information about the difference between the true and observed image of the sky. The effective beams are, by definition, the objects whose convolution with the true CMB sky produce the observed sky map.

Details of the beam processing are given in the respective pages for HFI and LFI.

The full algebra involving the effective beams for temperature and polarisation was presented in [1], and a discussion of its application to Planck data is given in the appropriate LFI Planck-2013-IV[2], Planck-2015-A05[3] and HFI Planck-2013-VII[4] papers. Relevant details of the processing steps are given in the Effective Beams section of this document.


Comparison of the images of compact sources observed by Planck with FEBeCoP products We show here a comparison of the FEBeCoP-derived effective beams, and associated point spread functions, PSF (the transpose of the beam matrix), to the actual images of a few compact sources observed by Planck, for all LFI and HFI frequency channels, as an example. We show below a few panels of source images organized as follows:

  • Row #1- DX9 images of four ERCSC objects with their galactic (l,b) coordinates shown under the color bar
  • Row #2- linear scale FEBeCoP PSFs computed using input scanning beams, Grasp Beams, GB, for LFI and B-Spline beams,BS, Mars12 apodized for the CMB channels and the BS Mars12 for the sub-mm channels, for HFI (see section Inputs below).
  • Row #3- log scale of #2; PSF iso-contours shown in solid line, elliptical Gaussian fit iso-contours shown in broken line

Histograms of the effective beam parameters Here we present histograms of the three fit parameters - beam FWHM, ellipticity, and orientation with respect to the local meridian and of the beam solid angle. The sky is sampled (pretty sparsely) at 3072 directions which were chosen as HEALpix nside=16 pixel centers for HFI and at 768 directions which were chosen as HEALpix nside=8 pixel centers for LFI. These uniformly sample the sky.

Where beam solid angle is estimated according to the definition: [math] 4 \pi \sum[/math](effbeam)/max(effbeam) i.e., [math] 4 \pi \sum(B_{ij}) / max(B_{ij}) [/math]


Histograms for LFI effective beam parameters
Histograms for HFI effective beam parameters

Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian

  • The discontinuities at the Healpix domain edges in the maps are a visual artifact due to the interplay of the discretized effective beam and the Healpix pixel grid.






Statistics of the effective beams computed using FEBeCoP

We tabulate the simple statistics of FWHM, ellipticity (e), orientation ([math] \psi[/math]) and beam solid angle, ([math] \Omega [/math]), for a sample of 3072 and 768 directions on the sky for HFI and LFI data respectively. Statistics shown in the Table are derived from the histograms shown above.

  • The derived beam parameters are representative of the DPC NSIDE 1024 and 2048 healpix maps (they include the pixel window function).
  • The reported FWHM_eff are derived from the beam solid angles, under a Gaussian approximation. These are best used for flux determination while the the Gaussian fits to the effective beam maps are more suited for source identification.


Statistics of the FEBeCoP Effective Beams Computed with the BS Mars12 apodized for the CMB channels and oversampled
frequency mean(fwhm) [arcmin] sd(fwhm) [arcmin] mean(e) sd(e) mean([math] \psi[/math]) [degree] sd([math] \psi[/math]) [degree] mean([math] \Omega [/math]) [arcmin[math]^{2}[/math]] sd([math] \Omega [/math]) [arcmin[math]^{2}[/math]] FWHM_eff [arcmin]
030 32.239 0.013 1.320 0.031 -0.304 55.349 1189.513 0.842 32.34
044 27.005 0.552 1.034 0.033 0.059 53.767 832.946 31.774 27.12
070 13.252 0.033 1.223 0.026 0.587 55.066 200.742 1.027 13.31
100 9.651 0.014 1.186 0.023 -0.024 55.400 105.778 0.311 9.66
143 7.248 0.015 1.036 0.009 0.383 54.130 59.954 0.246 7.27
217 4.990 0.025 1.177 0.030 0.836 54.999 28.447 0.271 5.01
353 4.818 0.024 1.147 0.028 0.655 54.745 26.714 0.250 4.86
545 4.682 0.044 1.161 0.036 0.544 54.876 26.535 0.339 4.84
857 4.325 0.055 1.393 0.076 0.876 54.779 24.244 0.193 4.63


Beam solid angles for the PCCS

  • [math]\Omega_{eff}[/math] - is the mean beam solid angle of the effective beam, where beam solid angle is estimated according to the definition: [math]4 \pi \sum [/math](effbeam)/max(effbeam), i.e. as an integral over the full extent of the effective beam, i.e. [math] 4 \pi \sum(B_{ij}) / max(B_{ij}) [/math].
  • from [math]\Omega_{eff}[/math] we estimate the [math]fwhm_{eff}[/math], under a Gaussian approximation - these are tabulated above
    • [math]\Omega^{(1)}_{eff}[/math] is the beam solid angle estimated up to a radius equal to one [math]fwhm_{eff}[/math] and [math]\Omega^{(2)}_{eff}[/math] up to a radius equal to twice the [math]fwhm_{eff}[/math].
      • These were estimated according to the procedure followed in the aperture photometry code for the PCCS: if the pixel centre does not lie within the given radius it is not included (so inclusive=0 in query disc).


Band averaged beam solid angles
Band [math]\Omega_{eff}[/math][arcmin[math]^{2}[/math]] spatial variation [arcmin[math]^{2}[/math]] [math]\Omega^{(1)}_{eff}[/math] [arcmin[math]^{2}[/math]] spatial variation-1 [arcmin[math]^{2}[/math]] [math]\Omega^{(2)}_{eff}[/math] [arcmin[math]^{2}[/math]] spatial variation-2 [arcmin[math]^{2}[/math]]
30 1189.513 0.842 1116.494 2.274 1188.945 0.847
44 832.946 31.774 758.684 29.701 832.168 31.811
70 200.742 1.027 186.260 2.300 200.591 1.027
100 105.778 0.311 100.830 0.410 105.777 0.311
143 59.954 0.246 56.811 0.419 59.952 0.246
217 28.447 0.271 26.442 0.537 28.426 0.271
353 26.714 0.250 24.827 0.435 26.653 0.250
545 26.535 0.339 24.287 0.455 26.302 0.337
857 24.244 0.193 22.646 0.263 23.985 0.191

Production process FEBeCoP, or Fast Effective Beam Convolution in Pixel space[1], is an approach to representing and computing effective beams (including both intrinsic beam shapes and the effects of scanning) that comprises the following steps:

  • identify the individual detectors' instantaneous optical response function (presently we use elliptical Gaussian fits of Planck beams from observations of planets; eventually, an arbitrary mathematical representation of the beam can be used on input)
  • follow exactly the Planck scanning, and project the intrinsic beam on the sky at each actual sampling position
  • project instantaneous beams onto the pixelized map over a small region (typically <2.5 FWHM diameter)
  • add up all beams that cross the same pixel and its vicinity over the observing period of interest
  • create a data object of all beams pointed at all N'_pix_' directions of pixels in the map at a resolution at which this precomputation was executed (dimension N'_pix_' x a few hundred)
  • use the resulting beam object for very fast convolution of all sky signals with the effective optical response of the observing mission


Computation of the effective beams at each pixel for every detector is a challenging task for high resolution experiments. FEBeCoP is an efficient algorithm and implementation which enabled us to compute the pixel based effective beams using moderate computational resources. The algorithm used different mathematical and computational techniques to bring down the computation cost to a practical level, whereby several estimations of the effective beams were possible for all Planck detectors for different scan and beam models, as well as different lengths of datasets.


Pixel Ordered Detector Angles (PODA) The main challenge in computing the effective beams is to go through the trillion samples, which gets severely limited by I/O. In the first stage, for a given dataset, ordered lists of pointing angles for each pixel - the Pixel Ordered Detector Angles (PODA) are made. This is an one-time process for each dataset. We used computers with large memory and used tedious memory management bookkeeping to make this step efficient.

effBeam The effBeam part makes use of the precomputed PODA and unsynchronized reading from the disk to compute the beam. Here we tried to made sure that no repetition occurs in evaluating a trigonometric quantity.


One important reason for separating the two steps is that they use different schemes of parallel computing. The PODA part requires parallelisation over time-order-data samples, while the effBeam part requires distribution of pixels among different computers.


Computational Cost The computation of the effective beams has been performed at the NERSC Supercomputing Center. The table below shows the computation cost for FEBeCoP processing of the nominal mission.

Computational cost for PODA, Effective Beam and single map convolution. Wall-clock time is given as a guide, as found on the NERSC supercomputers.
Channel 030 044 070 100 143 217 353 545 857
PODA/Detector Computation time (CPU hrs) 85 100 250 500 500 500 500 500 500
PODA/Detector Computation time (wall clock hrs) 7 10 20 20 20 20 20 20 20
Beam/Channel Computation time (CPU hrs) 900 2000 2300 2800 3800 3200 3000 900 1100
Beam/Channel Computation time (wall clock hrs) 0.5 0.8 1 1.5 2 1.2 1 0.5 0.5
Convolution Computation time (CPU hr) 1 1.2 1.3 3.6 4.8 4.0 4.1 4.1 3.7
Convolution Computation time (wall clock sec) 1 1 1 4 4 4 4 4 4
Effective Beam Size (GB) 173 123 28 187 182 146 132 139 124


The computation cost, especially for PODA and Convolution, is heavily limited by the I/O capacity of the disc and so it depends on the overall usage of the cluster done by other users.

Inputs In order to fix the convention of presentation of the scanning and effective beams, we show the classic view of the Planck focal plane as seen by the incoming CMB photon. The scan direction is marked, and the toward the center of the focal plane is at the 85 deg angle w.r.t spin axis pointing upward in the picture.


Planck Focal Plane


The Focal Plane DataBase (FPDB)

The FPDB contains information on each detector, e.g., the orientation of the polarisation axis, different weight factors, (see the instrument RIMOs):


The scanning strategy The scanning strategy, the three pointing angle for each detector for each sample: Detector pointings for the nominal mission covers about 15 months of observation from Operational Day (OD) 91 to OD 563 covering 3 surveys and half.

The scanbeam The scanbeam modeled for each detector through the observation of planets. Which was assumed to be constant over the whole mission, though FEBeCoP could be used for a few sets of scanbeams too.

  • LFI: GRASP scanning beam - the scanning beams used are based on Radio Frequency Tuned Model (RFTM) smeared to simulate the in-flight optical response.
  • HFI: B-Spline, BS based on 2 observations of Mars.

(see the instrument RIMOs).


Beam cutoff radii N times geometric mean of FWHM of all detectors in a channel, where N

Beam cut off radius
channel Cutoff Radii in units of fwhm fwhm of full beam extent
30 - 44 - 70 2.5
100 2.25 23.703699
143 3 21.057402
217-353 4 18.782754
sub-mm 4 18.327635(545GHz) ; 17.093706(857GHz)

Map resolution for the derived beam data object

  • [math]N_{side} = 1024 [/math] for LFI frequency channels
  • [math]N_{side} = 2048 [/math] for HFI frequency channels

Related products Monte Carlo simulations

FEBeCoP software enables fast, full-sky convolutions of the sky signals with the Effective beams in pixel domain. Hence, a large number of Monte Carlo simulations of the sky signal maps map convolved with realistically rendered, spatially varying, asymmetric Planck beams can be easily generated. We performed the following steps:

  • generate the effective beams with FEBeCoP for all frequencies for dDX9 data and Nominal Mission
  • generate 100 realizations of maps from a fiducial CMB power spectrum
  • convolve each one of these maps with the effective beams using FEBeCoP
  • estimate the average of the Power Spectrum of each convolved realization, and 1 [math]\sigma[/math] errors


As FEBeCoP enables fast convolutions of the input signal sky with the effective beam, thousands of simulations are generated. These Monte Carlo simulations of the signal (might it be CMB or a foreground (e.g. dust)) sky along with LevelS+Madam noise simulations were used widely for the analysis of Planck data. A suite of simulations were rendered during the mission tagged as Full Focalplane simulations, FFP#. For example FFP6

Beam Window Functions The Transfer Function or the Beam Window Function [math] W_l [/math] relates the true angular power spectra [math]C_l [/math] with the observed angular power spectra [math]\widetilde{C}_l [/math]:

[math] W_l= \widetilde{C}_l / C_l \label{eqn:wl1}[/math]

Note that, the window function can contain a pixel window function (depending on the definition) and it is {\em not the angular power spectra of the scanbeams}, though, in principle, one may be able to connect them though fairly complicated algebra.

The window functions are estimated by performing Monte-Carlo simulations. We generate several random realisations of the CMB sky starting from a given fiducial [math] C_l [/math], convolve the maps with the pre-computed effective beams, compute the convolved power spectra [math] C^\text{conv}_l [/math], divide by the power spectra of the unconvolved map [math]C^\text{in}_l [/math] and average over their ratio. Thus, the estimated window function

[math] W^{est}_l = \lt C^{conv}_l / C^{in}_l \gt \label{eqn:wl2}[/math]

For subtle reasons, we perform a more rigorous estimation of the window function by comparing C^{conv}_l with convolved power spectra of the input maps convolved with a symmetric Gaussian beam of comparable (but need not be exact) size and then scaling the estimated window function accordingly.

Beam window functions are provided in the RIMO.


Beam Window functions, Wl, for Planck mission

Beam Window functions, Wl, for LFI channels
Beam Window functions, Wl, for HFI channels

File Names The effective beams are provided by the PLA as FITS files containg HEALPix maps of the beams. For the file names the following convention is used:

  • Single beam query: beams_FFF_PixelNumber.fits
    • FFF is the channel frequency (one of 30, 44, 70, 100, 143, 217, 353, 545, 857);
    • PixelNumber is the number of the pixel to which the beam corresponds ([math]0[/math] - [math]12 \times N_{\rm side}^2 - 1[/math]). For the LFI [math]N_{\rm side}=1024[/math], for the HFI [math]N_{\rm side}=2048[/math];
  • Multiple beam query: beams_FFF_FirstPixelNumber-LastPixelNumber.zip
    The compressed files contains a set of files with the beams for the pixels covereing the selected region. FFF as for sinle beam query. The naming convention for the beam files contained in the .zip file is the same as for single beam queries.
    • FirstPixelNumber is the lowest pixel number for the area covered by the request;
    • LastPixelNumber is the highest pixel number for the area covered by the request;

File format The FITS files provided by the PLA contain HEALPix maps of the beams.



References[edit]

  1. 1.01.11.21.31.41.5 Fast Pixel Space Convolution for Cosmic Microwave Background Surveys with Asymmetric Beams and Complex Scan Strategies: FEBeCoP, S. Mitra, G. Rocha, K. M. Górski, K. M. Huffenberger, H. K. Eriksen, M. A. J. Ashdown, C. R. Lawrence, ApJS, 193, 5-+, (2011).
  2. 2.02.12.2 Planck 2013 results. IV. Low Frequency Instrument beams and window functions, Planck Collaboration, 2014, A&A, 571, A4.
  3. 3.03.13.2 Planck 2015 results. IV. LFI beams and window functions, Planck Collaboration, 2016, A&A, 594, A4.
  4. 4.04.14.2 Planck 2013 results. VII. HFI time response and beams, Planck Collaboration, 2014, A&A, 571, A7.

Cosmic Microwave background

(Planck) Low Frequency Instrument

(Planck) High Frequency Instrument

Early Release Compact Source Catalog

Full-Width-at-Half-Maximum

(Hierarchical Equal Area isoLatitude Pixelation of a sphere, <ref name="Template:Gorski2005">HEALPix: A Framework for High-Resolution Discretization and Fast Analysis of Data Distributed on the Sphere, K. M. Górski, E. Hivon, A. J. Banday, B. D. Wandelt, F. K. Hansen, M. Reinecke, M. Bartelmann, ApJ, 622, 759-771, (2005).

Data Processing Center

Operation Day definition is geometric visibility driven as it runs from the start of a DTCP (satellite Acquisition Of Signal) to the start of the next DTCP. Given the different ground stations and spacecraft will takes which station for how long, the OD duration varies but it is basically once a day.

Planck Legacy Archive

Flexible Image Transfer Specification