- 1 Overview
- 2 ADC Correction
- 3 Spikes Removal
- 4 Gaps Filling
- 5 Gain Modulation Factor
- 6 Diode Combination
- 7 Planet Flagging
- 8 Photometric Calibration
- 9 Noise
- 10 References
The LFI Level2 Pipeline analyzes each horn of the instrument separately, one pointing period at time, and store results in object the length of an OD. Each diode of the horn is corrected from systematic, differentiated and then combined with its complementary diode in the same radiometer. The horn is then calibrated and the photometric calibration is applied.
Before the run of the Level2 pipeline and to improve the analysis the Mission information and data sampling divisions are stored in the database.
The Mission information is a set of objects, one for each Operational Day (OD, as defined in the glossary), in which are stored Pointing Period data: DPC pointing ID (where 1 is the first pointing of the nominal mission), PSO pointing ID, start OBT of the pointing maneuver, start OBT of the stable pointing, end OBT of the pointing, spin axis ecliptic longitude and latitude.
The sampling information is a set of objects, one for each LFI frequency, in which are stored for each pointing ID: start OBT of the pointing maneuver, start OBT of the stable pointing, end OBT of the pointing, number of samples of the pointing, number of stable samples of the pointing, start sample of the stable pointing and sample number from the start of the nominal mission. Valid samples and OBTs are defined where any of the radiometers from that frequency cohort contain valid data.
During analysis it appeared that white noise and calibration seemed affected by something in common. It turn out to be a non linearity in the Analogic/Digital Converter on board. More on Planck-2013-IIPlanck-2013-III.
The mathematical model represents the digital ADC output as:
where DAE gain, is the DAE offset and is the DAE .is the voltage input, is the
We can model the non-linearity as a function of the input voltage. So we have the apparent inferred voltage and we can link it to the actual input voltage with:
Sinceand we can use the much simpler relation:
and we expect it to be very near to unity for all.
To find the response curve we have only the apparent voltage to work with, so we had to use the inverse response functionand replace the real input voltage with times the time varying gain factor .
If we introduce a small signal on top ofwhich leads to increased detected voltage and corresponding apparent voltage increment:
so carrying out the differentiation respect toto the relation between true and apparent signal voltage leads to:
We now assumeand are fixed and that the variations are due to slow drifts in the gain. So we can isolate the terms:
Combining the equations through the gain factor to remove it:
Rearranging and putting
So there is the expected direct proportionality ofto due to the assumption that the variations in voltage are due to overall gain drift, so the amplitude of voltage and signal will vary together. Then there is the additional differential term which will pull signal amplitude away from the linear relationship. So if we plot measured white noise or dipole gain factor against recovered voltage we should see this linear curve with variations due to local slope changes at particular voltages. The linear part can be taken out and the differential part fitted. This was numerically integrated up to get the inverse response curve, what we need to convert the measured voltages to corrected voltages.
For each of the 44 LFI diodes there is the corresponding object in the Database. Each object contains 4 columns: the input voltages coming from the sky channel and the corresponding linearized output, the input voltages coming from the reference channel and the corresponding linearized output.
Data loaded by the module are used to initialize two different interpolators using CSPLINE and the functions from gsl (GNU Scientific Libraries) libraries. The interpolators are then used to correct each sample.
Some of the LFI receivers exhibit a small artifact with exactly 1 second repetition, which visible in the power spectra. The effect is a set of spikes at 1 Hz and harmonics. The spurious signal is very well modeled and is removed from the timelines. More information can be found in Planck-2013-IIPlanck-2013-III.
The cause of the spikes at 1 Hz and harmonics is a tiny 1 second square wave embedded in affected channels. The method to estimate the 1 Hz signal is to build a template in time domain synchronized with the spurious signal. The first step is dividing each second of data into time bins using OBT. The number of bins is computed using:
where fsamp is the sampling frequency and is 136 at 70 GHz, 80 at 44 GHz and 56 at 30 GHz. Then the bins vector is initialized with time intervals. To avoid aliasing effects template resolution is. We can write the process adding an index to the time sample: lower index denotes the particular time sample, while the upper index labels the bin into which the sample falls. The linear filter can be written as:
Hereis the filter weight which is determined by where within the bin sample lies. If we use with only an upper index to denote the start of each bin, then we can write the filter weight as follows:
In other words, the filter weight is the time sample value minus the start of the bin divided by the width of the bin.
We must estimate the parametersfrom the data. With the assumption that the instrument has stable noise properties, we can use a least square algorithm to estimate the bin values:
This can be represented in matrix equation:
with the following definitions:
With these definitions we have to make use of periodic boundary conditions to obtain the correct results, such that if, and , . Once this is done, we have a symmetric tridiagonal matrix with additional values at the upper right and lower left corners of the matrix. The matrix is solved with LU decomposition. In order to be certain of the numerical accuracy of the result, we can perform a simple iteration. The solving of the linear system and the iterative improvement of the solution are implemented as suggested in Numerical Recipes.
For each of the 44 LFI diodes there is the corresponding object in the Database. Because of the amplitude of the spikes we choose to apply the correction only on the 44 GHz radiometers. Each object contains 3 columns: the bins start time vector, the sky amplitudes and the reference amplitudes.
For each sample the value to be subtracted is computed using:
where k is the index of the bins at a given time.
During the mission some of the data packets were lost (Planck-2013-II). Moreover in two different and very peculiar situations LFI was shutdown and restarted, giving inconsistencies in data sampling. All of those data aren't used for scientific purpose but to avoid discrepancies in data analysis all of the radiometers at the same frequency must have the same samples.
To accomplish this the length of the data stream to be reduced in a specific pointing period is compared with the data stored in the sample information object. If the length is not the same the OBT vector is filled with missing sample times, the data vector is filled with zeros and in the flag column the bit for gap is raised.
Gain Modulation Factor
The pseudo-correlation design of the LFI radiometers allows a dramatic reduction of noise when the and outputs are differenced (see LFI instrument description). The two streams are slightly unbalanced, as one looks at the 2.7 K sky and the other looks at the ~4.5 K reference load. To force the mean of the difference to zero, the load signal is multiplied by the Gain Modulation Factor (R). For each pointing period this factor is computed using (see eq. (3) in LFI description):
Then the data are differenced using:
This value for R minimizes the 1/f and the white noise in the difference timestream. The i index represents the diode and can be 0 or 1.
At this point the maneuver flag bit is set to identify which samples have missing data, using the information stored in the sampling information object. This identifies which data to ignore in the next step of the Pipeline.
The R values are stored in the database. At the same time the mean values ofand are stored in order to be used in other steps of the analysis.
The two complementary diodes of each radiometer are combined. The relative weights of the diodes in the combination are chosen for optimal noise. We assign relative weights to the uncalibrated diode streams based on their first order calibrated noise.
From first order calibration we compute an absolute gain LFI description):. The weights for the two diodes ( = 0 or 1) are:and , subtract an estimated sky signal and calculate the calibrated white noise and , for the pair of diodes (see eq. (6) in
where the weighted calibration constant is given by:
The weights are fixed to a single value per diode for the entire dataset. Small variations in the relative noise of the diodes would in principle suggest recalculating the weights on shorter timescales, however, we decided a time varying weight could possibly induce more significant subtle systematics, so chose a single best estimate for the weights for each diode pair.
|Horn||Weight M-00||Weight M-01||Weight S-10||Weight S-11|
The weights in the table above are used in the formula:
The planets Temperature have been estimated from chunk of samples affected, plus a surrounding region, projected onto a grid (microstripes), by assuming an elliptical Gaussian beam using parameters from instrument database.
Microstripes are a way to extract and store relevant samples for planets detection. Relevant samples are samples affected by the planet plus samples in the neighbor. The search radius to select samples as relevant is 5 deg around the planet position, computed at the pointing period mid time. For each sample we store SCET (Spacecraft Event Time), pointing directions and calibrated temperature. Destriping is applied during application.
Random errors are estimated by taking the variance of samples entering each micromap pixel. This is fast and the major problems (near a bright source the noise gives a larger value and it is difficult to extract the correlation matrix) causes the noise to be overestimated by a factor of two that in this situation is not a major drawback.
The apparent position of Planets as seen from Planck at a given time is derived from JPL Horizon. Position are sampled in tables at steps of 15 minutes and then linearly interpolated at the sampling frequency of each detector. JPL Horizons tables allow also to derive other quantities such as the Planet-Planck distance and the Planet-Sun distance nad the planet angular diameter affecting the apparent brightness of the planet.
The antenna temperature is a function of the dilution factor, according to:
whereand are the observed and reduced , the instantaneous planets angular diameter and the beam full width half maximum.
With the above definitioncould be considered as the for a planet with , but a more convenient view is to take a Reference Dilution factor , as the dilution factor for a standardized planet angular diameter and beam fwhm , , to have:
leading to the following definition of a standardized:
with the advantage of removing variations among different detectors and transits while keeping the value ofsimilar to that seen by the instrument and then allowing a prompt comparison of signals and sensitivities.
The OBT vector found by the search are saved in a set of object, one for each horn. In Level2 Pipeline those OBTs are compared with the OBT vector of the data to raise planet bit flag where needed.
Photometric calibration is the procedure used to convert data from volts to kelvin. The source of the calibration is the well known CMB dipole, caused by the motion of the Solar System with respect to the CMB reference frame. To this signal we add the modulation induced by the orbital motion of Planck around the Sun. The resulting signal is then convoluted with the horn beam to get the observed Dipole.
Beam Convolved Dipole
In computing the beam convolved dipole we used an elegant algorithm to save time and computing power. In computing the cosmological dipole signal it is common to assume a pencil-like beam acting as a Dirac delta function. In this case a dipole timeline is defined as:
whereis the pointing direction, in the observer reference frame and is the dipole axis scaled by the dipole amplitude again in the same reference frame.
In general the true signal would have to be convolved with the beam pattern of the given radiometer, usually described as a fixed map in the beam reference frame or as a time dependent map in the observer reference frame. In this case it is easiest to describe the convolution in the beam reference frame, since the function to be convolved is described by a single vector.
Denoting withthe matrix converting from the observer to the beam reference frame, so that:
the instantaneous dipole direction in the beam reference frame is:
By denoting witha pointing direction in the beam reference frame then:
whereis a normalization costant.
Denoting with, , the three cartesian components of the the integral of the dot product can be decomposed into three independent integrals:
those integrals define a time independent vector characteristic of each radiometer and constant over the mission.
By using this characteristic vector the calculation of the convolved dipole is simply defined by a dot product of the vectorby the dipole axis rotated in the beam reference frame.
In order to simplify the computation and to reduce the amount of data used in the calibration procedure the data are phase binned in map with Nside 256. During phase binning all the data with flagged for maneuvers, planets, gaps and the ones flagged in Level1 analysis as not recoverable are discharged.
The first order calibration values are given by a Least Square Fit between the signal and the dipole. For each pointing a gain () and an offset ( ) values are computed minimizing:
The sum includes samples outside a Galactic mask.
The largest source of error in the fit arises from unmodeled sky signal CMB anisotropy.from
The procedure adopted o correct this effect is described below.
The uncalibrated toibelonging to a pointing period is modeled as
where the unknowns OBT, the gain per PID and the offset per PID, and is the total dipole., and are respectively the signal per
This is a non linearminimization problem. It can be linearized with an iterative procedure: for each iteration step a linearized model toi is build as
whereand and are the gain and sky computed at the previous step of iteration.
A linear fit is performed betweenand to get the new and . The procedure is iterated until convergence.
To reduce the impact of the noise during the iterative procedure the sky estimation is built using data from both radiometers of the same horn.
To improve accuracy given by the iterative algorithm and remove noise from the solution a smoothing algorithm must be performed.
OSGTV is a 3 step smoothing algorithm, implemented with a C++ code.
The gain reconstructed with DaCapo can be expressed as
where thefunction represents temperature fluctuations of the Focal Plane. The time dependence of the “real” gain is modeled as the superposition of a “slow” component, with a time scale of ~3 months, and a “fast” component with a time scale of few PIDs:
The slow component takes into account the seasonal variations of the thermal structure of the spacecraft due to the orbital motion, while the “fast” component describes the thermal effects of the electronics and compressors, as well as single events like the sorption cooler switchover.
To disentangle the components of, we need a parametric “hybrid” approach in three steps.
Step 1. For each PID, we used the 4K total-power and the signal from temperature detectors in the focal plane , subsampled at 1 sample/PID, to track gain changes. This is implemented through a linear fit between and :
where the window lengthof the mobile average is proportional to the variance of the dipole in the considered PID. The resulting gain is:
Step 2. The "fast" componentis recovered as follows: we define a maximum mobile average window length ,and for each PID we compute the variance of on this window. We define a percentile on the ordered variance array and we compute the corresponding value of the variance . The window length for each PID is then computed as
Ifwe impose . With these window lengths a mobile window average is performed on . The averaged gain vector is subtracted to the raw hybrid gain to get .
Step 3. We perform a mobile window average onand we compute the variances of the smoothed array. The mobile window length is computed with a linear interpolation between a minimum length defined in the dipole minima and a maximum defined in the dipole maxima. The array of gain variances is weighted with the variance of the dipole. We set a percentile on the variance array and we find the corresponding variance value . Around this value we search for local maxima of the variance array, and we split the domain of the gain in subsets between consecutive maxima. For each subset we perform a mobile average with the corresponding window length. The "slow" component is given by the union of these subsets.
The last step in TOI processing is the creation of the calibrated stream. For each sample we have:
where t is the time and k is the pointing period, CMB Dipole convolved with the beam, and is the straylight.is the
This pipeline step aims at the reconstruction of the noise parameters from calibrated flight TOI. The goal is two-folds: one the one side we need to know the actual noise properties of our instrument in order to properly take them into account especially during the following processing and analysis steps like map-making and power spectrum estimation. On the other side evaluation of noise properties along the instrument life-time is a way to track down possible variations, anomalies and general deviations from the expected behaviour.
Noise estimation is performed on calibrated data and since we would like to track possible noise variations along mission life-time, we select data in chunks of 5 ODs (Operational Days). These data are processed by the ROMA Iterative Generalized Least Square (IGLS) map-making algorithm which includes a noise estimation tool. In general an IGLS map-making is a quite consuming in terms of time and resources required. However the length of the data is such that running on the DPC cluster in very short time (~1-2 minutes).
The method implemented can be summerized as follows. We model the calibrated TOI as
whereis the noise vector and is the pointing matrix that links a pixel in the map with a sample in the TOI . The zero-th order estimation of the signal is obtained simply rebinning TOI into a map. Then an iterative approach follows in which both signal and noise are estimated according to
whereis the noise covariance matrix in time domain out from iteration . After three iterations convergence is achieved.
We then perform an FFT (Fast Fourier Transform) on the noise time stream out from the iterative approach and then fit the resulting spectrum.
In the very first release of Planck data, once noise spectra were extracted a simply log-periodogram fitting approach was applied to derive the most important noise parameters (white noise level, knee-frequency and slope of the low-frequency noise component). However during mission life-time there were some specific events (e.g. the switch over of the sorption coolers) that we expect were able to cause variation in instrument behaviour and hence in its noise properties. In this respect we have improved our fitting pipeline adding a Monte Carlo Markov Chain approach to estimate noise parameters.
This new approach allows us to improve our noise model. Indeed this can be parametrized by the usual combination of white plusnoise
with three basic noise parameters. However it is also possible to work with a functional form with two more parameters as
This latter could be useful when there are clearly two different behaviour in the low-frequency part of the spectrum where, beside usual radiometricnoise, appears signature of thermal fluctuations induced noise.
As for the white noise part, this is, as before, computed making a simple average of noise spectrum on the last 10% of frequency bins. This percentage works well for almost all radiometers at 44 and 70 GHz but it is indeed quite delicate for the 30 GHz radiometers which show typical values of knee-frequency around 100 mHz and, therefore, require a smaller number to get an un-biased white noise estimation. Once white noise is computed, the code creates Markov Chains for the other parameters. Discarding the burn-in period of the chains we can directly get from the chain samples distribution, the expected value and variance of each noise parameters sampled.
The left panel of the following Figure shows a typical spectrum at 70 GHz with superimposed the simple log-periodogram fit (purple line) and the new MCMC derived spectrum (blue line). The right panel instead shows distribution for knee-frequency and slope derived from the example spectrum.
The final noise parameters
As already reported we know that during the nominal operations there was a quite dramatic change in LFI induced by the switch over of the two sorption coolers and particularly we expect to see the effect of degradation of the performance of the first sorption cooler and the onset of the redundant one.
In the following figure we report a set of noise frequency spectra for three LFI radiometers (LFI28M, LFI24S and LFI18M) from the beginning of the operation till the time of the current data release. Some comments are in order. First of all the white noise level is extremely stable in all the three cases (but this is also true for all the LFI radiometer). Also knee-frequency and low-frequency slope are quite stable till OD 326. After that period spectra show a noise increase and two slopes for the low-frequency part which become more evident for spectra around OD 366 and OD 466 where the first cooler starts to be less effective and produces low-frequency thermal noise. After the switch-over to the redundant cooler data still present (the very last spectrum) thermal noise at very low-frequency. This behaviour is almost present in all radiometers with different trends ranging from the small effect shown by LFI24S to more prominent effect as shown by LFI28M and LFI18M.
- Planck 2013 results. II. Low Frequency Instrument data processing, Planck Collaboration, 2014, A&A, 571, A2
- Planck 2013 results. III. Low Frequency Instrument systematic uncertainties, Planck Collaboration, 2014, A&A, 571, A3
(Planck) Low Frequency Instrument
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.
Data Processing Center
Planck Science Office
analog to digital converter
LFI Data Acquisition Electronics
Cosmic Microwave background