Difference between revisions of "Map-making LFI"
Line 13: | Line 13: | ||
Here $f_\mathrm{sample}$ is the sampling frequency of the instrument. The first term corresponds to white noise and the second term to correlated ($1/f$) noise. The noise parameters were determined separately for each radiometer as described in [[TOI-Noise LFI]], assuming they stayed constant over the mission. | Here $f_\mathrm{sample}$ is the sampling frequency of the instrument. The first term corresponds to white noise and the second term to correlated ($1/f$) noise. The noise parameters were determined separately for each radiometer as described in [[TOI-Noise LFI]], assuming they stayed constant over the mission. | ||
− | The detector pointing was reconstructed from satellite pointing, focal-plane geometry, and | + | The detector pointing was reconstructed from satellite pointing, focal-plane geometry, pointing correction (tilt angle), and sample timing, using Level-S simulation software. The same pointing solution (two focal planes) was used as for the LFI flight maps. Due to numerical accuracy, the detector pointing in the noise MC was not exactly the same as for the flight maps, but some data samples (of the order of one in a thousand) whose pointing was near the pixel boundary ended up assigned to the neighboring pixel. During the map-making from the flight data, a gap file was produced to represent the samples that were omitted from map-making due to various flags. This gap files was used in the noise MC instead of the full set of flags. The flight map-making used a destriping mask to exclude regions of strong signal gradients from contributing to the noise baseline solution. These same destriping masks (one for each frequency channel) were used for the noise MC. The same map-making code (Madam) with the same parameter settings was used for the noise MC as for the flight maps. |
+ | |||
The noise was generated internally in the Madam map-making code using a Stochastic Differential Equation (SDE) method, to avoid time-consuming writing and reading noise timelines to/from disk. Noise for each pointing period was generated separately, using a double-precision random number seed constructed from the realization number, radiometer number, and the pointing period number; to allow regeneration of the same noise realization when needed. White noise and $1/f$ noise were generated separately. | The noise was generated internally in the Madam map-making code using a Stochastic Differential Equation (SDE) method, to avoid time-consuming writing and reading noise timelines to/from disk. Noise for each pointing period was generated separately, using a double-precision random number seed constructed from the realization number, radiometer number, and the pointing period number; to allow regeneration of the same noise realization when needed. White noise and $1/f$ noise were generated separately. | ||
The | The |
Revision as of 10:40, 19 October 2012
Noise Monte Carlo Simulation[edit]
Overview[edit]
Calculating and handling full pixel-to-pixel noise covariances in Planck maps if feasible only at low resolution. To support the analysis of high-resolution maps, a Monte Carlo set of noise maps were produced. These noise Monte Carlos were produced at two levels of the analysis: 1) LFI Monte Carlo (MC) as part of the LFI data processing, and 2) Full Focal Plane (FFP) Monte Carlo as part of the joint HFI/LFI data processing. This page describes the LFI noise MC. For the FFP MC, see HL-sims.
Inputs[edit]
The noise MC assumes a three-parameter noise model: white noise level ($\sigma$), slope, and knee frequency ($f_\mathrm{knee}$), so that the noise power spectrum is assumed to have the form
- $ P(f) = \frac{2\sigma^2}{f_\mathrm{sample}}\left[1+\left(\frac{f}{f_\mathrm{knee}}\right)^\mathrm{slope}\right] $.
Here $f_\mathrm{sample}$ is the sampling frequency of the instrument. The first term corresponds to white noise and the second term to correlated ($1/f$) noise. The noise parameters were determined separately for each radiometer as described in TOI-Noise LFI, assuming they stayed constant over the mission.
The detector pointing was reconstructed from satellite pointing, focal-plane geometry, pointing correction (tilt angle), and sample timing, using Level-S simulation software. The same pointing solution (two focal planes) was used as for the LFI flight maps. Due to numerical accuracy, the detector pointing in the noise MC was not exactly the same as for the flight maps, but some data samples (of the order of one in a thousand) whose pointing was near the pixel boundary ended up assigned to the neighboring pixel. During the map-making from the flight data, a gap file was produced to represent the samples that were omitted from map-making due to various flags. This gap files was used in the noise MC instead of the full set of flags. The flight map-making used a destriping mask to exclude regions of strong signal gradients from contributing to the noise baseline solution. These same destriping masks (one for each frequency channel) were used for the noise MC. The same map-making code (Madam) with the same parameter settings was used for the noise MC as for the flight maps.
The noise was generated internally in the Madam map-making code using a Stochastic Differential Equation (SDE) method, to avoid time-consuming writing and reading noise timelines to/from disk. Noise for each pointing period was generated separately, using a double-precision random number seed constructed from the realization number, radiometer number, and the pointing period number; to allow regeneration of the same noise realization when needed. White noise and $1/f$ noise were generated separately.
The
(Planck) Low Frequency Instrument
(Planck) High Frequency Instrument