- 1 Overview
- 2 Input TOI
- 3 General pipeline structure
- 4 Output TOIs and products
- 5 Examples of clean TOIs
- 6 Trends in the output processing variables
- 7 Flag description
- 8 References
We describe here how the TOIs are processed in order to be used for map production. We do not repeat the general features of the pipeline, which are given in the HFI Data Processing paper Planck-2013-VI. Here we give complementary explanations in some detail. The TOI of each bolometer is processed independently of the other bolometers, so as to keep the noise properties as uncorrelated as possible. The processing involves modifying the TOI itself for the conversion to absorbed power and the correction of glitch tails. It also adds a flag TOI that masks the TOI samples that are not to be projected onto maps for various reasons.
The input TOI consists of the AC-modulated voltage output of the readout of each bolometer. The input has previously been decompressed, and converted from internal digital units to voltages via a constant factor. The TOI has a regular sampling at the acquisition frequency of facq=(180.373700±0.000050)Hz. There are almost no missing data in the TOIs, except for a few hundred samples of 545 and 857 GHz TOIs, which were lost in the on-board compression due to saturation on the Galactic centre crossings.
General pipeline structure
The following figure shows how the initial TOI is transformed and how flags are produced.
Output TOIs and products
A TOI of clean calibrated samples and a combined flag TOI are the outputs of the processing. The clean calibrated TOI is calibrated so as to represent the instantaneous power absorbed by the detector, up to a constant (which will be determined by the mapmaking destriper). It is worth mentioning how the clean calibrated TOI is changed with respect to the input TOI, beyond the basic constant conversion factor from voltage to absorbed power. The demodulation stage allows one to obtain the demodulated bolometer voltage. The nonlinearity correction is a second-order polynomial correction based on the physical but static bolometer model. In order to avoid too much masking after glitches, a glitch tail is subtracted after an occurrence of a glitch in the TOI. The 4-K cooler lines are removed at a series of nine single temporal frequencies. Finally, the temporal response of the bolometer is deconvolved. This affects mostly the high-temporal frequency part of the TOI, although a small but significant low frequency tail (the long time response) is corrected too. Although flagged samples are not projected, their value still influences the valid samples. Hence interpolation procedures introduce some indirect modifications of the TOI. The flag TOI is a combination of a dozen flags with an OR logic. Only unflagged data are projected. The exhaustive list of flags is: CompressionError; NoData; SSO; UnstablePointing; Glitch; BoloPlateFluctuation; RTS; Jump; and PSBab. A complete qualification of the data is obtained at the ring level. If the TOI shows any anomalous behaviour on a given ring, this ring is discarded from projection. A special TOI is also produced as an input to the beam analysis for Mars, Jupiter, and Saturn.
Examples of clean TOIs
Samples of PBR, TOIs, and PSDs of all detectors are shown in this file.
Trends in the output processing variables
Here we show trends in the systematic effects that are dealt with in the TOI processing. The full impact of each of them is analysed in the HFI-Validation section.
The following figure shows the ADC baseline that is used prior to demodulation (a constant offset is removed for clarity). This baseline is obtained by smoothing on an hourtimescale by block-averaging the undemodulated TOI on unflagged samples.
The percentage of flagged data (mostly due to cosmic rays) at the ring level is shown in these examples. No smoothing was applied and only valid rings are shown.
Percentage of flagged data
The complete set of plots is attached here.
Thermal template for decorrelation
A simple linear decorrelation is performed using the two "dark" bolometers as a proxy of the bolometer plate temperature. Coupling coefficients were measured during the CPV phase.
4-K cooler lines variability
The amplitude of the nine 4-K cooler lines at 10, 20, 30, 40, 50, 60, 70, 80, and 17Hz is shown (in aW) for two bolometers in the following figures. The trend is smoothed over 31 ring values after having discarded measurements done at a ring that is discarded for all bolometers.
Amplitude of the nine 4-K cooler lines
The 4-K cooler line coefficients of all bolometers are shown in this file.
The 4-K cooler lines project onto the maps only for a limited fraction of rings, the so-called "resonant rings." This is graphically shown in the following figure. For each ring (fixed pointing period), the spin rate is very stable at about 1rpm. From one ring to another, the spin frequency (shown as diamonds) changes around that value. The sky signal is imprinted at the corresponding spin frequency and its 5400 (60×90) harmonics. If one of the nine 4-K cooler lines happens to coincide with one of the spin frequency harmonics (a resonant ring), it will project a sine-wave systematic onto the maps. The horizontal coloured bars show the zone of influence of a particular 4-K line (labelled on the left side of the plot), when folded around 16.666mHz. When the spin frequency hits one of these zones, we have a resonant ring. The 4-K line coefficient is interpolated for this ring and an estimate of the systematic effect is subtracted from the TOI. Resonant rings are different for different 4-K lines. Note the two-level oscillation pattern of the spin frequency, which is due to the satellite attitude control system.
A piecewise constant value is removed from the TOI if a jump is detected. An example of a jump is shown in the following figure:
The number of jumps per day (all bolometers included) is shown in this figure.
The jumps are uncorrelated from bolometer to bolometer. The total number of jumps detected in the nominal and full mission is shown below.
Trends in noise and signal
Signal (top) and noise (bottom) smoothed over 1 minute. All values falling in a discarded ring are not plotted.
The smooth TOIs of all detectors are shown in this file.
This is not the final version but gives a good idea of power spectra at the detector level of noise TOIs. All PSDs can be seen in this file.
The standard deviation per ring corrected for ring duration bias is given here, one per bolometer using only valid rings. No smoothing is applied (except a 31-point smoothing for the 545 and 857 GHz channels), but values for rings discarded for all bolometers (see below) are not used. The standard deviation is computed on samples valid for mapmaking that are also not affected by the Galaxy or the point-sources using the usual flags. Two examples are shown below.
Standard deviation per ring
The full series of plots is below. Standard deviation of noise TOIs at the ring level.
Note the presence for three bolometers of a two-level noise system. No correction has been made for that effect. See one example below.
An example of the higher-order statistics that are used to unveil rings affected by RTS problems is below.
Some rings are discarded (flagged) from further use (e.g., beam-making, and mapmaking) by using ring statistics (see above and Planck-2013-VI). For each statistic, we compare each ring value to the ring values averaged (RVA) over a large selection of rings (between 3000 and 21700). We also define the modified standard deviation (MSD) of a ring quantity as the standard deviation of that quantity over the rings that deviate by less than five nominal standard deviations. This truncation is necessary to be robust against extremely deviant rings.
More specifically, a ring is discarded if it matches one of the following criteria:
- the | mean-median | deviates from the RVA by more than fifteen times the MSD;
- the standard deviation deviates from the RVA by more than -5 times the MSD (all cases corresponding to almost empty rings) or +15 times the MSD;
- the Kolmogorov-Smirnov test deviates from the RVA by more than 15 times the MSD;
- the ring duration is more than 90 min;
- the ring is contaminated by RTS with an amplitude of more than one standard deviation of the noise.
This last item concerns a few hundreds rings for three bolometers (44_217_6b, 71_217_8a, 74_857_4). Notice that two bolometers are completely discarded for maps, namely 55_545_3 and 70_143_8, which present RTS at all times.
For the three first criteria, a visual inspection of the noise TOI at each of the incriminated rings has shown that all such anomalous rings are due to either a drift, a small jump in the TOI trend, or a sudden change of noise level, the origin of which is unknown at present.
Once the list of discarded rings per bolometer is produced, a common list of discarded rings can be extracted for all bolometers (by using discarded rings for at least half the bolometers). Such rings correspond to identified phenomena, as can be seen in the following table.
Furthermore, an isolated valid ring sandwiched between two common discarded rings becomes discarded as well.
Table of "common discarded rings" of the nominal mission (rings 240-14723).
|Manoeuvre||304 1312 3590 3611 3642 3922 4949 6379 8456 11328|
|Sorption Cooler switchover||11149 11150 11151 11152|
|Rings too long||440 474 509 544 897 898 3589 13333 14627 14653|
|Star tracker switchover||14628 14654|
|Massive glitch event||7665|
The following figure is a summary of the impact of the discarding process for each bolometer (the solid black line is the common discarded ring percentage). The outlier bolometers have some RTS problems, as mentionned above.
Effective integration time
The following figure summarizes the effective integration time per bolometer. For that purpose the number of unflagged samples in non-discarded pointing periods have been used within the nominal mission. The average value is of about 335 days of effective integration time.
These flags are used as inputs to the TOI processing
- The point-source flag (PSflag)
- An earlier version of HFI point-source catalog is read back into a flag TOIs, at a given frequency. In practice, 5 sigma sources are masked within a radius of 1.3 FWHM (9, 7, 5, 5, 5, 5 arcmin at 100,143,217,353,545,857 GHz) TBC.
- the galactic flag (Galflag
- An earlier version of HFI maps is thresholded and apodized. The produced masks are read into flag TOIs. The retained threshold corresponds to a sky coverage of respectively 70, 70, 80, 90, 90, 90% at 100,143,217,353,545,857 GHz.
- Solar System Object flag
- For the TOI flag, Mars, Jupiter, Saturn are flagged up to a radius of NbBeam= 2,3,3,4,4,4 times the fiducial SSO_FWHM with SSO_FWHM= 9, 7, 5, 5, 5, 5 arcmin at 100,143,217,353,545,857 GHz.
- As an input to planet mask for maps, Mars, Jupiter, Saturn are flagged with a radius computed as a coefficient depending on the planet (Factor_per_source) times NbBeam times SSO_FWHM, with Factor_per_source = 1.1, 2.25, 1.25 for Mars, Jupiter, Saturn respectively and NbBeam = 2.25, 4.25, 4.0, 5.0,.6.0, 8.0 at 100, 143, 217, 353, 545, 857 GHz. This flag is called SSOflag4map.
- A small trailing tail is added to the mask to take into account the non-deconvolution of the planet signal which has been replaced by background values. The width of that tail is 10 % of the main flag diameter. The number of samples which are additionnaly flagged are the Factor_per_Source times AddSNafter with (trail) times (Factor_per_source)^3 samples where trail = 10, 30, 20, 20, 30, 40 at 100, 143, 217, 353, 545, 857 GHz.
- Uranus and Neptune together with detected asteroids are masked by HFI. They are masked at the TOI level using an exclusion radius of 1.5 SSO_FWHM. At 857 GHz, 24 asteroids have been detected with HFI : 1Ceres, 2Pallas, 3Juno, 4Vesta, 7Iris, 8Flora, 9Metis, 10Hygiea, 11Parthenope, 12Victoria, 13Egeria, 14Irene, 15Eunomia, 16Psyche, 18Melpomene, 19Fortuna, 20Massalia, 29Amphitrite, 41Daphne, 45Eugenia, 52Europa, 88Thisbe, 704Interamnia, 324Bamberga.
Local maps showing the SSO flag. The colors correspond to the surveys involved in the nominal mission (green = Survey I, yellow = Survey II, red = Survey III).
A FlagTOIproc is produced by the TOIprocessing. It marks measurements which are not reliable for any of the following reasons:
- gap (no valid input data), enlarged by one sample on each side. It flags less than 0.00044% (resp. 0.00062%) of the nominal (resp. complete) mission. It is equivalent to less than 3 (resp. 8) minutes of data.
- "glitch" on dark bolometers: as the thermal template used for decorrelation is computed from these bolometer data, chunks of one minute-length data are discarded for all bolometers if at least 50% of the data for at least one dark bolometer are flagged during this time. It is efficient to flag the data around the maximum of thermal events.
- "glitch" on individual bolometers : samples where the signal from a cosmic ray hit dominates the sky signal at more than 3 are discarded.
- jump as 100 samples are flagged around the computed position of the jump to take into account the error on this reconstructed position.
So the flag produced for the map making, called Total_flag, is defined by:
- Total_flag = UnstablePointing Flag OR FlagTOIproc OR SSOflag4map OR SSOflag seen
where FlagTOIproc = gap OR flag thermal template OR glitch OR jump and for PSB bolometers, FlagTOIproc_AB = FlagTOIproc_A OR FlagTOIproc_B. Note that the Total_flag is then identical for the A and B bolometers of a PSB pair.
At the destriping stage, a more restricted flag, called Total_flag_PS, is used. It is defined by Total_flag_PS = Total_flag OR PS_flag.
- Planck 2013 results. VI. High Frequency Instrument Data Processing, Planck Collaboration, 2014, A&A, 571, A6
- Planck 2013 results. X. HFI energetic particle effects: characterization, removal, and simulation, Planck Collaboration, 2014, A&A, 571, A10
(Planck) High Frequency Instrument
Solar System Object
random telegraphic signal
analog to digital converter
Calibration and Performance Verification
sudden change of the baseline level inside a ring
To be confirmed