Requirements on bandpass resolution and measurement precision for LiteBIRD
S. Giardiello, A. Carones, T. Ghigna, L. Pagano, F. Piacentini, L. Montier, R. Takaku, E. Calabrese, D. Adak, E. Allys, A. Anand, J. Aumont, M. Ballardini, A. J. Banday, R. B. Barreiro, N. Bartolo, S. Basak, M. Bersanelli, A. Besnard, M. Bortolami, T. Brinckmann, F. J. Casas

TL;DR
This paper assesses how inaccuracies in instrument bandpass knowledge affect the measurement of the tensor-to-scalar ratio r in the LiteBIRD satellite, establishing resolution and error thresholds to keep systematic biases below the mission's budget.
Contribution
It introduces a pipeline to evaluate the impact of bandpass uncertainties on r measurement and determines specific resolution and error limits for LiteBIRD's channels to control systematic bias.
Findings
Resolution ≤ 1.5 GHz limits bias on r
Measurement error σ ≤ 0.0089 is acceptable
NILC method allows relaxing σ to 0.05
Abstract
In this work, we study the impact of an imperfect knowledge of the instrument bandpasses on the estimate of the tensor-to-scalar ratio in the context of the next-generation LiteBIRD satellite. We develop a pipeline to integrate over the bandpass transmission in both the time-ordered data (TOD) and the map-making processing steps. We introduce the systematic effect by having a mismatch between the ``real'', high resolution bandpass , entering the TOD, and the estimated one , used in the map-making. We focus on two aspects: the effect of degrading the resolution, and the addition of a Gaussian error to . To reduce the computational load of the analysis, the two effects are explored separately, for three representative LiteBIRD channels (40 GHz, 140 GHz and 402 GHz) and for three bandpass shapes. Computing the amount of bias on , ,…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
