Difference between revisions of "HFI-Validation"
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:Internal overall validation}} | {{DISPLAYTITLE:Internal overall validation}} | ||
| − | |||
| − | |||
The HFI validation is mostly modular. That is, each part of the pipeline, be it timeline processing, map-making, or any other, validates the results of its work at each step of the processing, looking specifically for known issues. In addition, we do additional validation with an eye towards overall system integrity by looking at generic differences between sets of maps, in which most problems will become apparent, whether known or not. Both these are described below. | The HFI validation is mostly modular. That is, each part of the pipeline, be it timeline processing, map-making, or any other, validates the results of its work at each step of the processing, looking specifically for known issues. In addition, we do additional validation with an eye towards overall system integrity by looking at generic differences between sets of maps, in which most problems will become apparent, whether known or not. Both these are described below. | ||
| Line 31: | Line 29: | ||
* Bandpass - The transmission curves, or "bandpass" has shown up in a number of places. This is discussed in {{PlanckPapers|planck2013-p03d|1|the 2013 spectral response paper}}. | * Bandpass - The transmission curves, or "bandpass" has shown up in a number of places. This is discussed in {{PlanckPapers|planck2013-p03d|1|the 2013 spectral response paper}}. | ||
* Saturation - While this is mostly an issue only for Jupiter observations, it should be remembered that the HFI detectors cannot observe arbitrarily bright objects. This is discussed in [[#Saturation|the section below on saturation]]. | * Saturation - While this is mostly an issue only for Jupiter observations, it should be remembered that the HFI detectors cannot observe arbitrarily bright objects. This is discussed in [[#Saturation|the section below on saturation]]. | ||
| + | |||
| + | ==Generic approach to systematics== | ||
| + | |||
| + | <font style="color:red;font-size:300%">This Page is Under Construction</font> | ||
<!-- | <!-- | ||
| − | |||
While we track and try to limit the individual effects listed above, and we do not believe there are other large effects which might compromise the data, we test this using a suite of general difference tests. As an example, the first and second years of Planck observations used almost exactly the same scanning pattern (they differed by one arc-minute at the Ecliptic plane). By differencing them, the fixed sky signal is almost completely removed, and we are left with only time variable signals, such as any gain variations and, of course, the statistical noise. | While we track and try to limit the individual effects listed above, and we do not believe there are other large effects which might compromise the data, we test this using a suite of general difference tests. As an example, the first and second years of Planck observations used almost exactly the same scanning pattern (they differed by one arc-minute at the Ecliptic plane). By differencing them, the fixed sky signal is almost completely removed, and we are left with only time variable signals, such as any gain variations and, of course, the statistical noise. | ||
Revision as of 16:48, 29 January 2015
The HFI validation is mostly modular. That is, each part of the pipeline, be it timeline processing, map-making, or any other, validates the results of its work at each step of the processing, looking specifically for known issues. In addition, we do additional validation with an eye towards overall system integrity by looking at generic differences between sets of maps, in which most problems will become apparent, whether known or not. Both these are described below.
Expected systematics and tests (bottom-up approach)[edit]
Like all experiments, Planck/HFI had a number of "issues" which it needed to track and verify were not compromising the data. While these are discussed in appropriate sections, here we gather them together to give brief summaries of the issues and refer the reader to the appropriate section for more details.
- Cosmic Rays - Unprotected by the atmosphere and more sensitive than previous bolometric experiments, HFI saw to many more cosmic ray hits than previous experiments. These were detected, the worst parts of the data flagged as unusable, and "tails" were modeled and removed. This is described in the section on glitch statistics and in the section on cosmic rays, as well as in the 2013 HFI Cosmic Ray Removal paper[1].
- Elephants - Cosmic rays also hit the HFI 100 mK stage and cause the temperature to vary, inducing small temperature and thus noise variations in the detectors. These are effectively removed with the rest of the thermal fluctuations, described directly below.
- Thermal Fluctuations - HFI is an extremely stable instrument, but there are small thermal fluctuations. These are discussed in the timeline processing section on thermal decorrelation and in the section on 1.6 K and 4 K thermal fluctuations.
- Random Telegraphic Signal (RTS) or Popcorn Noise - Some channels were occasionally affected by what seems to be a baseline which abruptly changes between two levels, which has been variously called popcorn noise or random telegraphic signal. These data are usually flagged. This is described in the section on noise stationarity and the section on Random Telegraphic Signal Noise
- Jumps - Similar to but distinct from popcorn noise, small jumps were occasionally found in the data streams. These data are usually corrected. This is described in the section on jump corrections.
- 4 K Cooler-Induced EM Noise - The 4 K cooler induced noise in the detectors with very specific frequency signatures, which is filtered. This is described in the 2013 HFI DPC Paper[2], the section below on 4K line residuals, and their stability is discussed in the section on 4K cooler line stability.
- Compression - Onboard compression is used to overcome our telemetry bandwidth limitations. This is explained in Planck-Early-IV[3].
- Noise Correlations - Correlations in noise between detectors seems to be negligble but for two polarization sensitive detectors in the same horn. This is discussed in the 2013 HFI Cosmic Ray Removal paper[1].
- Pointing - The final pointing reconstruction for Planck is near the arcsecond level. This is discussed in the 2013 HFI DPC Paper[2].
- Focal Plane Geometry - The relative positions of different horns in the focal plane is reconstructed using planets. This is also discussed in the 2013 HFI DPC paper[2].
- Main Beam - The main beams for HFI are discussed in the 2013 Beams and Transfer function paper[4].
- Ruze Envelope - Random imperfections or dust on the mirrors can increase the size of the beam a bit. This is discussed in the 2013 Beams and Transfer function paper[4].
- Dimpling - The mirror support structure causes a pattern of small imperfections in the beams, which cause small sidelobe responses outside the main beam. This is discussed in the 2013 Beams and Transfer function paper[4].
- Far Sidelobes - Small amounts of light can sometimes hit the detectors from just above the primary or secondary mirrors, or even from reflecting off the baffles. While small, when the Galactic center is in the right position, this can be detected in the highest frequency channels, so this is removed from the data. This is discussed in the 2013 Beams and Transfer function paper[4] and, non-intuitively, the 2013 Zodiacal emission paper[5].
- Planet Fluxes - Comparing the known fluxes of planets with the calibration on the CMB dipole is a useful check of calibration for the CMB channels, and is the primary calibration source for the submillimeter channels. This is done in the 2013 Map-Making and Calibration Paper[6].
- Point Source Fluxes - As with planet fluxes, we also compare fluxes of known, bright point sources with the CMB dipole calibration. This is done in the 2013 Map-Making and Calibration paper[6].
- Time Constants - The HFI bolometers do not react instantaneously to light; there are small time constants, discussed in the 2013 Beams and Transfer function paper[4].
- ADC Correction - The HFI Analog-to-Digital Converters are not perfect, and are not used perfectly. While this is an on-going effort, their effects on the calibration are discussed in the 2013 Map-Making and Calibration paper[7].
- Gain changes with Temperature Changes
- Optical Cross-Talk - This is negligible, as noted in the optical cross-talk note.
- Bandpass - The transmission curves, or "bandpass" has shown up in a number of places. This is discussed in the 2013 spectral response paper[4].
- Saturation - While this is mostly an issue only for Jupiter observations, it should be remembered that the HFI detectors cannot observe arbitrarily bright objects. This is discussed in the section below on saturation.
Generic approach to systematics[edit]
This Page is Under Construction
References[edit]
- ↑ 1.01.1 Planck 2013 results. X. HFI energetic particle effects: characterization, removal, and simulation, Planck Collaboration, 2014, A&A, 571, A10
- ↑ 2.02.12.2 Planck 2013 results. VI. High Frequency Instrument Data Processing, Planck Collaboration, 2014, A&A, 571, A6
- ↑ Planck early results, IV. First assessment of the High Frequency Instrument in-flight performance, Planck HFI Core Team, A&A, 536, A4, (2011).
- ↑ 4.04.14.24.34.44.5 Planck 2013 results. IX. HFI spectral response, Planck Collaboration, 2014, A&A, 571, A9
- ↑ Planck 2013 results. XIV. Zodiacal emission, Planck Collaboration, 2014, A&A, 571, A14
- ↑ 6.06.1 Planck 2013 results. VIII. HFI photometric calibration and Map-making, Planck Collaboration, 2014, A&A, 571, A8
- ↑ Planck 2013 results. VII. HFI time response and beams, Planck Collaboration, 2014, A&A, 571, A7
(Planck) High Frequency Instrument
random telegraphic signal
Cosmic Microwave background
[LFI meaning]: absolute calibration refers to the 0th order calibration for each channel, 1 single number, while the relative calibration refers to the component of the calibration that varies pointing period by pointing period.
analog to digital converter
