Difference between revisions of "Effective Beams"

From Planck PLA Wiki
Jump to: navigation, search
(→‎Product description)
 
(82 intermediate revisions by 5 users not shown)
Line 2: Line 2:
  
 
==Product description==
 
==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.
 
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. They are, by definition, the objects whose convolution with the true CMB sky produce the observed sky map.  
 
It captures the complete information about the difference between the true and observed image of the sky. They are, by definition, the objects whose convolution with the true CMB sky produce the observed sky map.  
  
−
The full algebra involving the effective beams for temperature and polarisation was presented in [[http://arxiv.org/pdf/1005.1929| Mitra, Rocha, Gorski et al.]] <cite>#mitra2010</cite>. Here we summarise the main results. The observed temperature sky <math>\widetilde{\mathbf{T}} </math> is a convolution of the true sky <math>\mathbf{T} </math> and the effective beam <math>\mathbf{B}</math>:
+
Details of the beam processing are given in the respective pages for [[Beams|HFI]] and [[Beams_LFI|LFI]].
  
−
<math>
+
The full algebra involving the effective beams for temperature and polarisation was presented elsewhere{{BibCite|mitra2010}}, and a discussion of its application to Planck data is given in the appropriate LFI {{PlanckPapers|planck2013-p02d}} and HFI {{PlanckPapers|planck2013-p03c}} papers. Relevant details of the processing steps are given in the [[Beams|Effective Beams]] section of this document.
−
\widetilde{\mathbf{T}} \ = \ \Delta\Omega \, \mathbf{B} \cdot \mathbf{T},
 
−
\label{eq:a0}
 
−
</math>
 
  
−
where
+
<!-- Everything from here down to the "Production Process" section should eventually be moved to a new section the Joint Processing pages -->
  
−
<math>
+
===Comparison of the images of compact sources observed by Planck with FEBeCoP products===
−
B_{ij} \ = \ \left( \sum_t A_{ti} \, b(\hat{\mathbf{r}}_j, \hat{\mathbf{p}}_t) \right) / \left({\sum_t A_{ti}} \right) \, ,
 
−
\label{eq:EBT2}
 
−
</math>
 
−
 
 
−
<math>t</math> is time samples, <math>A_{ti}</math> is <math>1</math> if the pointing direction falls in pixel number <math>i</math>, else it is <math>0</math>, <math>\mathbf{p}_t</math> represents the exact pointing direction (not approximated by the pixel centre location), and <math>\hat{\mathbf{r}}_j</math> is the centre of the pixel number <math>j</math>, where the scanbeam <math>b(\hat{\mathbf{r}}_j, \hat{\mathbf{p}}_t)</math> is being evaluated (if the pointing direction falls within the cut-off radius of <math>\sim 2.5 \times</math> FWHM.
 
−
 
 
−
The algebra is a bit more involved for polarised detectors. The observed stokes parameters at a  pixel <math>i</math>, <math>(\widetilde{I}, \widetilde{Q}, \widetilde{U})_i</math>, are related to the true stokes parameters <math>(I, Q, U)_i</math>, by the following relation:
 
−
 
 
−
<math>
 
−
( \widetilde{I} \quad \widetilde{Q} \quad \widetilde{U})_i^T \ = \ \Delta\Omega \sum_j \mathbf{B}_{ij} \cdot (I \quad Q \quad U)_j^T,
 
−
\label{eq:a1}
 
−
</math>
 
−
 
 
−
where the polarised effective beam matrix
 
−
 
 
−
<math>
 
−
\mathbf{B}_{ij} \ = \  \left[ \sum_t A_{tp} \mathbf{w}_t \mathbf{w}^T_t \right]^{-1} \sum_t A_{ti} \, b(\hat{\mathbf{r}}_j, \hat{\mathbf{p}}_t) \, \mathbf{w}_t  \mathbf{W}^T(\hat{\mathbf{n}}_j,\hat{\mathbf{p}}_t) \, ,
 
−
\label{eq:a2}
 
−
</math>
 
−
 
 
−
and <math>\mathbf{w}_t </math>and <math>\mathbf{W}(\hat{\mathbf{r}}_j, \hat{\mathbf{p}}_t) </math> are the the polarisation weight vectors, as defined in \cite{mitra2010}.
 
−
 
 
−
The task is to compute <math>B_{ij}</math> for temperature only beams and the <math>3 \times 3</math> matrices <math>\mathbf{B}_{ij}</math> for each pixel <math>i</math>, at every neighbouring pixel <math>j</math> that fall within the cut-off radius around the the center of the <math>i^\text{th}</math> pixel.
 
−
 
 
−
 
 
−
 
 
−
The effective beam is computed by stacking within a small field around each pixel of the HEALPix sky map.  Due to the particular features of Planck scanning strategy coupled to the beam asymmetries in the focal plane, and data processing of the bolometer and radiometer TOIs, the resulting Planck effective beams vary over the sky.
 
  
−
FEBeCoP, given information on Planck scanning beams and detector pointing during a mission period of interest, provides the pixelized stamps of both the Effective Beam, EB, and the Point Spread Function, PSF, at all positions of the HEALPix-formatted map pixel centres.
 
  
−
----
+
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:
−
 
 
−
===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 30GHz and 100GHz 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 color bar
 
* 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 #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).
Line 58: Line 21:
  
  
−
====30GHz====
+
<gallery widths=350px heights=350px perrow=3 caption="Comparison  images of compact sources and effective beams, PSFs">
−
 
+
File:30.png| '''30GHz'''
−
[[File:30.png | 500px| thumb | center | 30GHz ]]
+
File:44.png| '''44GHz'''
−
 
+
File:70.png| '''70GHz'''
−
====100GHz====
+
File:100.png| '''100GHz'''
−
[[File:100.png | 500px| thumb | center | 100GHz ]]
+
File:143.png| '''143GHz'''
−
 
+
File:217.png| '''217GHz'''
−
 
+
File:353.png| '''353GHz'''
−
 
+
File:545.png| '''545GHz'''
−
 
+
File:857.png| '''857GHz'''
−
<gallery>
 
−
File:30.png|caption|alt=link
 
−
File:100.png|caption| 100GHz
 
 
</gallery>
 
</gallery>
  
  
 +
===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 shy 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 to 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 of the effective beam parameters===
+
[[File:ist_GB.png | 600px| thumb | center| '''Histograms for LFI effective beam parameters''' ]]
 +
[[File:ist_BS_Mars12.png | 600px| thumb | center| '''Histograms for HFI 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 shy 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 to uniformly sample the sky.
 
  
−
Where beam solid angle is estimated according to the definition:  '''4pi* sum(effbeam)/max(effbeam)'''
 
  
−
====LFI====
+
===Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian===
  
−
[[File:ist_GB.png | 500px| thumb | center| Histograms for LFI effective beam parameters ]]
 
  
−
====HFI====
+
* 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.
  
−
[[File:ist_BS_Mars12.png | 500px| thumb | center| Histograms for HFI effective beam parameters ]]
 
  
 +
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of effective beams ellipticity of the best-fit Gaussian">
 +
File:e_030_GB.png| '''ellipticity - 30GHz'''
 +
File:e_044_GB.png| '''ellipticity - 44GHz'''
 +
File:e_070_GB.png| '''ellipticity - 70GHz'''
 +
File:e_100_BS_Mars12.png| '''ellipticity - 100GHz'''
 +
File:e_143_BS_Mars12.png| '''ellipticity - 143GHz'''
 +
File:e_217_BS_Mars12.png| '''ellipticity - 217GHz'''
 +
File:e_353_BS_Mars12.png| '''ellipticity - 353GHz'''
 +
File:e_545_BS_Mars12.png| '''ellipticity - 545GHz'''
 +
File:e_857_BS_Mars12.png| '''ellipticity - 857GHz'''
 +
</gallery>
  
  
−
----
+
<gallery widths=300px heights=220px perrow=3 caption="Sky (relative) variation of effective beams solid angle of the best-fit Gaussian">
−
===Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian===
+
File:solidarc_030_GB.png| '''beam solid angle (relative) variations wrt scanning beam - 30GHz'''
 +
File:solidarc_044_GB.png| '''beam solid angle (relative) variations wrt scanning beam - 44GHz'''
 +
File:solidarc_070_GB.png| '''beam solid angle (relative) variations wrt scanning beam - 70GHz'''
 +
File:solidarc_100_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 100GHz'''
 +
File:solidarc_143_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 143GHz'''
 +
File:solidarc_217_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 217GHz'''
 +
File:solidarc_353_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 353GHz'''
 +
File:solidarc_545_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 545GHz'''
 +
File:solidarc_857_BS_Mars12.png| '''beam solid angle (relative) variations wrt scanning beam - 857GHz'''
 +
</gallery>
  
  
−
====30GH====
+
<gallery widths=300px heights=220px perrow=3 caption="Sky (relative) variation of effective beams fwhm of the best-fit Gaussian">
−
[[File:e_030_GB.png | 520px| thumb | center | Sky variation of effective beams ellipticity of best-fit Gaussian for 30GHz]]
+
File:fwhm_030_GB.png| '''fwhm (relative) variations wrt scanning beam - 30GHz'''
−
[[File:solidarc_030_GB.png | 520px| thumb | center | Sky variation of  effective beams solid angle of best-fit Gaussian for 30GHz relative to scanning beam solid angle]]
+
File:fwhm_044_GB.png| '''fwhm (relative) variations wrt scanning beam - 44GHz'''
 +
File:fwhm_070_GB.png| '''fwhm (relative) variations wrt scanning beam - 70GHz'''
 +
File:fwhm_100_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 100GHz'''
 +
File:fwhm_143_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 143GHz'''
 +
File:fwhm_217_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 217GHz'''
 +
File:fwhm_353_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 353GHz'''
 +
File:fwhm_545_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 545GHz'''
 +
File:fwhm_857_BS_Mars12.png| '''fwhm (relative) variations wrt scanning beam - 857GHz'''
 +
</gallery>
  
  
−
====100GHz====
+
<gallery widths=300px heights=220px perrow=3 caption="Sky variation of effective beams $\psi$ angle of the best-fit Gaussian">
−
[[File:e_100_BS_Mars12.png | 520px| thumb | center | Sky variation of  effective beams ellipticity of best-fit Gaussian for 100GHz]]
+
File:psi_030_GB.png| '''$\psi$ - 30GHz'''
−
[[File:solidarc_100_BS_Mars12.png | 520px| thumb | center | Sky variation of  effective beams solid angle of best-fit Gaussian for 100GHz relative to scanning beam solid angle]]
+
File:psi_044_GB.png| '''$\psi$ - 44GHz'''
 +
File:psi_070_GB.png| '''$\psi$ - 70GHz'''
 +
File:psi_100_BS_Mars12.png| '''$\psi$ - 100GHz'''
 +
File:psi_143_BS_Mars12.png| '''$\psi$ - 143GHz'''
 +
File:psi_217_BS_Mars12.png| '''$\psi$ - 217GHz'''
 +
File:psi_353_BS_Mars12.png| '''$\psi$ - 353GHz'''
 +
File:psi_545_BS_Mars12.png| '''$\psi$ - 545GHz'''
 +
File:psi_857_BS_Mars12.png| '''$\psi$ - 857GHz'''
 +
</gallery>
  
 +
<!--
 +
<gallery widths=500px heights=500px perrow=2 caption="Sky variation of effective beams solid angle and ellipticity of the best-fit Gaussian">
 +
File:e_030_GB.png| '''ellipticity - 30GHz'''
 +
File:solidarc_030_GB.png| '''beam solid angle (relative variations wrt scanning beam - 30GHz'''
 +
File:e_100_BS_Mars12.png| '''ellipticity - 100GHz'''
 +
File:solidarc_100_BS_Mars12.png| '''beam solid angle (relative variations wrt scanning beam - 100GHz'''
 +
</gallery>
 +
-->
  
 +
===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.
  
−
===Statistics of the effective beams computed using FEBeCoP===
+
* 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.
  
−
We tabulate the simple statistics of FWHM, ellipticity, 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.
 
  
  
Line 119: Line 125:
 
|+ '''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 apodized for the CMB channels and oversampled'''
 
|-
 
|-
−
!  '''frequency'''  ||  '''mean(fwhm)''' [arcmin]  ||  '''sd(fwhm)''' [arcmin]  || '''mean(e)'''  ||  '''sd(e)'''  ||  '''mean(psi)''' [degree]  ||  '''sd(psi)''' [degree]  || '''mean(Solid Angle)''' [arcmin<math>^{2}</math>]  ||  '''sd(Solid Angle)''' [arcmin<math>^{2}</math>]
+
!  '''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  
+
| 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  
+
| 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  
+
| 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
+
| 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  
+
| 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  
+
| 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  
+
| 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  
+
| 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  
+
| 857 || 4.325 || 0.055 || 1.393 || 0.076 || 0.876  || 54.779 || 24.244 || 0.193 || 4.63
 
|}
 
|}
  
 
   
 
   
−
----
 
−
===FEBeCoP deliverables===
 
  
  
−
* The derived beam parameters are representative of the DPC NSIDE 2048 healpix maps (they include the pixel window function).
+
====Beam solid angles for the PCCS====
−
* The reported FHWM are derived from the solid angles, under a Gaussian approximation.  The value in the values in parenthesis are the Gaussian fits to the effective beam maps tabulated above.  The former is best used for flux determination, the latter for source identification.
 
−
 
 
−
{|border="1" cellpadding="5" cellspacing="0" align="center" style="text-align:center"
 
−
|+ '''Band averaged beam solid angles'''
 
−
|-
 
−
| '''Band'''  ||  '''Omega_beam''' [arcmin<math>^{2}</math>]  ||  '''Monte Carlo error'''[arcmin<math>^{2}</math>^]  || '''spatial variation''' [arcmin<math>^{2}</math>]  ||  '''bias''' [arcmin<math>^{2}</math>]  || '''FWHM_eff''' (Gaussian fit) [arcmin]
 
−
|-
 
−
| 030 || 1188.513 || --- || 0.842 || --- || 32.34 (32.24)
 
−
|-
 
−
| 044 || 832.946 || --- || 31.774 || --- || 27.12 (27.01)
 
−
|-
 
−
| 070 || 200.742 || --- || 1.027 || --- || 13.31 (13.25)
 
−
|-
 
−
| 100 || 105.78 || --- || 0.31 || --- || 9.66 (9.65)
 
−
|-
 
−
| 143 || 59.95 || --- || 0.25 || --- || 7.27 (7.25)
 
−
|-
 
−
| 217 || 28.45 || --- || 0.27 || --- || 5.01 (4.99)
 
−
|-
 
−
| 353 || 26.71 || --- || 0.25 || --- || 4.86 (4.82)
 
−
|-
 
−
| 545 || 26.54 || --- || 0.34 || --- || 4.84 (4.68)
 
−
|-
 
−
| 857 || 24.24 || --- || 0.19 || --- || 4.63 (4.33)
 
−
|}
 
  
−
----
+
*  <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>.
−
 
 
−
====Beam solid angles for the PCCS====
 
  
−
**  Omega_beam - is the mean beam solid angle of the effective beam, where beam solid angle is estimated according to the definition:  4pi*sum(effbeam)/max(effbeam), i.e. as an integral over the full extent of the effective beam
+
* from <math>\Omega_{eff}</math> we estimate the <math>fwhm_{eff}</math>, under a Gaussian approximation - these are tabulated above
−
** from Omega_beam we estimate the fwhm_eff, 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>.
−
** Omega_beam_1 is the beam solid angle estimated up to a radius equal to 1xfwhm_eff and Omega_beam_2 up to a radius equal to 2xfwhm_eff
 
 
*** 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).
 
*** 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).
  
Line 184: Line 160:
 
{|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'''  ||  '''Omega_beam'''[arcmin<math>^{2}</math>] || '''spatial variation''' [arcmin<math>^{2}</math>] ||  '''Omega_beam_1''' [arcmin<math>^{2}</math>]|| '''spatial variation-1''' [arcmin<math>^{2}</math>] ||  '''Omega_beam_2''' [arcmin<math>^{2}</math>] || '''spatial variation-2''' [arcmin<math>^{2}</math>]  
+
|  '''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  
 
|30 || 1189.513 || 0.842 || 1116.494 || 2.274 || 1188.945 || 0.847  
Line 206: Line 182:
  
 
==Production process==
 
==Production process==
−
------------------------
 
  
−
The methodology for computing effective beams for a scanning CMB experiment like Planck
 
−
was presented in [[http://arxiv.org/pdf/1005.1929| Mitra, Rocha, Gorski et al.]].
 
  
−
FEBeCoP, or Fast Effective Beam Convolution in Pixel space, 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, 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:
 
* 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 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
 
* follow exactly the Planck scanning, and project the intrinsic beam on the sky at each actual sampling position
Line 237: Line 211:
 
===Computational Cost===
 
===Computational Cost===
  
−
The whole computation of the effective beams has been performed at the NERSC Supercomputing Center. In the table below it isn displayed the computation cost on NERSC for nominal mission both in terms of CPU hrs and in Human time.
+
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.
  
 
{|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.The cost in Human time is computed using an arbitrary number of nodes/core on Carver or Hopper 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 ||030 || 044 || 070 || 100 || 143 || 217 || 353 || 545 || 857
Line 246: Line 220:
 
|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 (Human minutes) || 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 (Human 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 hr) || 1 || 1.2 || 1.3 || 3.6 || 4.8 || 4.0 || 4.1 || 4.1 || 3.7  
 
|-
 
|-
−
|Convolution Computation time (Human 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
Line 262: Line 236:
 
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 disc and so it depends on the overall usage of the cluster done 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 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.  
  
  
−
[[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 polarisation axis, different weight factors, (see the instrument [[The RIMO|RIMOs]]):
  
 +
*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}}
 +
 +
 +
<!--
 
*HFI - LFI_RIMO_DX9_PTCOR6 -  {{PLASingleFile|fileType=rimo|name=HFI_RIMO_R1.00.fits|link=The HFI RIMO}}
 
*HFI - LFI_RIMO_DX9_PTCOR6 -  {{PLASingleFile|fileType=rimo|name=HFI_RIMO_R1.00.fits|link=The HFI RIMO}}
 
*LFI - HFI-RIMO-3_16_detilt_t2_ptcor6.fits - {{PLASingleFile|fileType=rimo|name=LFI_RIMO_R1.12.fits|link=The LFI RIMO}}
 
*LFI - HFI-RIMO-3_16_detilt_t2_ptcor6.fits - {{PLASingleFile|fileType=rimo|name=LFI_RIMO_R1.12.fits|link=The LFI RIMO}}
−
 
  
 
{{PLADoc|fileType=rimo|link=The Plank RIMOS}}
 
{{PLADoc|fileType=rimo|link=The Plank RIMOS}}
−
 
+
-->
−
 
 
  
 
===The scanning strategy===
 
===The scanning strategy===
Line 293: Line 268:
 
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 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.
+
* 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.  
−
* HFI: B-spline based on 2 observations of Mars
+
* HFI: [[Beams#Scanning beams|B-Spline, BS]] based on 2 observations of Mars.
 +
 
 +
(see the instrument [[The RIMO|RIMOs]]).
  
−
(see the instrument [[The RIMO|RIMOs]])
+
<!--
  
 
*HFI - LFI_RIMO_DX9_PTCOR6 -  {{PLASingleFile|fileType=rimo|name=HFI_RIMO_R1.00.fits|link=The HFI RIMO}}
 
*HFI - LFI_RIMO_DX9_PTCOR6 -  {{PLASingleFile|fileType=rimo|name=HFI_RIMO_R1.00.fits|link=The HFI RIMO}}
 
*LFI - HFI-RIMO-3_16_detilt_t2_ptcor6.fits - {{PLASingleFile|fileType=rimo|name=LFI_RIMO_R1.12.fits|link=The LFI RIMO}}
 
*LFI - HFI-RIMO-3_16_detilt_t2_ptcor6.fits - {{PLASingleFile|fileType=rimo|name=LFI_RIMO_R1.12.fits|link=The LFI RIMO}}
−
 
+
[[Beams LFI#Effective beams|LFI effective beams]]
 +
-->
  
 
===Beam cutoff radii===
 
===Beam cutoff radii===
Line 323: Line 301:
 
===Map resolution for the derived beam data object===
 
===Map resolution for the derived beam data object===
  
−
* N'_side_' = 1024 for LFI frequency channels
+
* <math>N_{side} = 1024 </math> for LFI frequency channels
−
* N'_side_' = 2048 for HFI frequency channels
+
* <math>N_{side} = 2048 </math> for HFI frequency channels
−
 
 
  
 
==Related products==
 
==Related products==
−
----------------------
 
  
−
 
−
<span style="color:Red">A description of other products that are related and share some commonalities with the product being described here. E.g. if the description is of a generic product (e.g. frequency maps), all the products falling into that type should be listed and referenced.</span>
 
  
 
===Monte Carlo simulations===
 
===Monte Carlo simulations===
Line 344: Line 318:
  
 
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#.
 
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 [[HL-sims#FFP6 data set|FFP6]] [
+
For example [[HL-sims#FFP6 data set|FFP6]]  
  
 
===Beam Window Functions===
 
===Beam Window Functions===
Line 367: Line 341:
  
  
−
====Wl for Planck mission: LFI (left) and HFI (right)====
+
====Beam Window functions, Wl, for Planck mission====
  
−
[[File:plot_dx9_LFI_GB_pix.png | 450px | thumb | left |Beam Window functions, Wl, for LFI channels]]
 
  
−
[[File:plot_dx9_HFI_BS_M12_CMB.png | 600px | thumb | |center |Beam Window functions, Wl, for HFI channels]]
 
  
 +
[[File:plot_dx9_LFI_GB_pix.png | 600px | thumb | center |'''Beam Window functions, Wl, for LFI channels''']]
 +
[[File:plot_dx9_HFI_BS_M12_CMB.png | 600px | thumb | |center |'''Beam Window functions, Wl, for HFI channels''']]
  
−
 
+
== Retrieval of effective beam information from the PLA interface ==
−
 
+
In order to retrieve the effective beam information, the user should:
−
----
+
#Launch the Java interface from the [http://www.sciops.esa.int/index.php?project=planck&page=Planck_Legacy_Archive Planck Legacy Archive]; [[File:PLALink.png| 1000px | thumb | |center |'''Link to PLA Java interface.''']]
 +
#Once the PLA interface is loaded go to '''Sky maps'''; [[File:PLAinterface.png| 600px | thumb | |center |'''PLA java interface.''']]
 +
#On the '''Sky maps''' interface click on the icon on the left of the Effective beams area;
 +
[[File:Skymapsinterface.png| 600px | thumb | |center |'''Sky maps interface on the PLA''']]
 +
#The search interface for effective beams allows the user to retrieve the beam nearest to the input source (name or coordinates), or to retrieve a set of beams in a grid defined by the <math>N_{\rm side}</math> and the size of the region around a source (name or coordinates). The resolution of this grid is defined by the <math>N_{\rm side}</math> parametera and the size of the region is defined by the "Radius of ROI" parameter.[[File:EffectiveBeamsInterface.png| 600px | thumb | |center |'''Link to PLA Java interface.''']]
 +
Once the user proceeds with querying the beams, the PLA software retrieves the appropriate set of effective beams from the database and delivers it in a FITS file containin a HEALPix map of the beam which can be directly downloaded.
  
 
==File Names==
 
==File Names==
  
−
The effective beams are stored as unformatted files in directories with the frequency channel's name, e.g., 100GHz, each subdirectory contains N unformatted files with names beams_###.unf, a beam_index.fits and a beams_run.log. For 100GHz and 143GHz: N=160, for 30, 44, 70 217 and 353GHz: N=128; for 545GHz: N=40; and 857GHz: N=32.
+
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''' <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.
 +
** ''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;
  
−
* beam_index.fits
+
==File format==
−
* beams_run.log
+
The FITS files provided by the PLA contain HEALPix maps of the beams.
  
−
== Retrieval of effective beam information from the PLA interface ==
 
  
−
In order to retrieve the effective beam information, the user should first launch the Java interface from this page:
+
== References ==
−
http://www.sciops.esa.int/index.php?project=planck&page=Planck_Legacy_Archive
 
  
−
One should click on "Sky maps" and then open the "Effective beams" area.
 
−
There is the possibility to either retrieve one beam nearest to the input source (name or coordinates), or to retrieve a set of beams in a grid defined by the Nside and the size of the region around a source (name or coordinates).
 
−
The resolution of this grid is defined by the Nside parameter.
 
−
The size of the region is defined by the "Radius of ROI" parameter.
 
  
−
Once the user proceeds with querying the beams, the PLA software retrieves the appropriate set of effective beams from the database and delivers it in a FITS file which can be directly downloaded.
+
<References />
−
 
 
−
 
 
−
 
 
−
==Meta data==
 
−
<span style="color:Red">A detailed description of the data format of each file, including header keywords for fits files, extension names, column names, formats….</span>
 
−
 
 
−
The data format of the effective beams is unformatted.
 
−
 
 
−
== References ==
 
  
  
−
<biblio force=false>
 
−
#[[References]]
 
−
</biblio>
 
  
  
  
−
[[Category:Mission science products|004]]
+
[[Category:Mission products|004]]

Latest revision as of 12:28, 28 August 2014

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 image of the sky. They 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 elsewhere[1], and a discussion of its application to Planck data is given in the appropriate LFI Planck-2013-IV[2] and HFI Planck-2013-VII[3] 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 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


  • Comparison images of compact sources and effective beams, PSFs

  • 30GHz

  • 44GHz

  • 70GHz

  • 100GHz

  • 143GHz

  • 217GHz

  • 353GHz

  • 545GHz

  • 857GHz


Histograms of the effective beam parameters[edit]

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 shy 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 to 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[edit]

  • 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.


  • Sky variation of effective beams ellipticity of the best-fit Gaussian

  • ellipticity - 30GHz

  • ellipticity - 44GHz

  • ellipticity - 70GHz

  • ellipticity - 100GHz

  • ellipticity - 143GHz

  • ellipticity - 217GHz

  • ellipticity - 353GHz

  • ellipticity - 545GHz

  • ellipticity - 857GHz


  • Sky (relative) variation of effective beams solid angle of the best-fit Gaussian

  • beam solid angle (relative) variations wrt scanning beam - 30GHz

  • beam solid angle (relative) variations wrt scanning beam - 44GHz

  • beam solid angle (relative) variations wrt scanning beam - 70GHz

  • beam solid angle (relative) variations wrt scanning beam - 100GHz

  • beam solid angle (relative) variations wrt scanning beam - 143GHz

  • beam solid angle (relative) variations wrt scanning beam - 217GHz

  • beam solid angle (relative) variations wrt scanning beam - 353GHz

  • beam solid angle (relative) variations wrt scanning beam - 545GHz

  • beam solid angle (relative) variations wrt scanning beam - 857GHz


  • Sky (relative) variation of effective beams fwhm of the best-fit Gaussian

  • fwhm (relative) variations wrt scanning beam - 30GHz

  • fwhm (relative) variations wrt scanning beam - 44GHz

  • fwhm (relative) variations wrt scanning beam - 70GHz

  • fwhm (relative) variations wrt scanning beam - 100GHz

  • fwhm (relative) variations wrt scanning beam - 143GHz

  • fwhm (relative) variations wrt scanning beam - 217GHz

  • fwhm (relative) variations wrt scanning beam - 353GHz

  • fwhm (relative) variations wrt scanning beam - 545GHz

  • fwhm (relative) variations wrt scanning beam - 857GHz


  • Sky variation of effective beams $\psi$ angle of the best-fit Gaussian

  • $\psi$ - 30GHz

  • $\psi$ - 44GHz

  • $\psi$ - 70GHz

  • $\psi$ - 100GHz

  • $\psi$ - 143GHz

  • $\psi$ - 217GHz

  • $\psi$ - 353GHz

  • $\psi$ - 545GHz

  • $\psi$ - 857GHz


Statistics of the effective beams computed using FEBeCoP[edit]

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[edit]

  • [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[edit]

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 scanbeam models and different lengths of datasets.


Pixel Ordered Detector Angles (PODA)[edit]

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 pixels---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[edit]

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[edit]

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[edit]

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)[edit]

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[edit]

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[edit]

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[edit]

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[edit]

  • [math]N_{side} = 1024 [/math] for LFI frequency channels
  • [math]N_{side} = 2048 [/math] 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 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, C'_\ell_'^out^'}, 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#. For example FFP6

Beam Window Functions[edit]

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[edit]

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

Retrieval of effective beam information from the PLA interface[edit]

In order to retrieve the effective beam information, the user should:

  1. Launch the Java interface from the Planck Legacy Archive;
    Link to PLA Java interface.
  2. Once the PLA interface is loaded go to Sky maps;
    PLA java interface.
  3. On the Sky maps interface click on the icon on the left of the Effective beams area;
Sky maps interface on the PLA
  1. The search interface for effective beams allows the user to retrieve the beam nearest to the input source (name or coordinates), or to retrieve a set of beams in a grid defined by the [math]N_{\rm side}[/math] and the size of the region around a source (name or coordinates). The resolution of this grid is defined by the [math]N_{\rm side}[/math] parametera and the size of the region is defined by the "Radius of ROI" parameter.
    Link to PLA Java interface.

Once the user proceeds with querying the beams, the PLA software retrieves the appropriate set of effective beams from the database and delivers it in a FITS file containin a HEALPix map of the beam which can be directly downloaded.

File Names[edit]

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[edit]

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


References[edit]

  1. ↑ 1.01.1 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. ↑ Planck 2013 results: LFI Beams, Planck Collaboration 2013 IV, A&A, in press, (2014).
  3. ↑ Planck 2013 results: HFI time response and beams, Planck Collaboration 2013 VII, A&A, in press, (2014).

Cosmic Microwave background

(Planck) Low Frequency Instrument

(Planck) High Frequency Instrument

Early Release Compact Source Catalog

Full-Width-at-Half-Maximum

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

Ring-Ordered Information (DMC group/object)

Flexible Image Transfer Specification

(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).

Retrieved from ‘https://wiki.cosmos.esa.int/planckpla/index.php?title=Effective_Beams&oldid=8159’