UCSD-2019: Flowdown: Science to Measurement Requirements
From CMB-S4 wikiJump to navigationJump to search
Charge from SOC
- Define what simulations, and other forecasting tools, are still needed before CD-1, the schedule and plan for these simulations and other forecasting tools, and when any inputs are needed to achieve a complete connection between science and measurement for CD-1.
- Coordinate carefully with science and analysis working groups to understand the assumptions they are making and inputs they are using.
Additional tips for making this session maximally useful
- People listed below are being asked to prepare for this discussion by outlining, as well as they can, their response to the charge, and highlighting the questions they have about completing a response to the charge, and more generally, questions they have that will help them have a productive meeting in their Friday afternoon parallel session.
- List systematic effects and suggest plan for writing down appropriate requirements, or questions that may need communication with the Technical Council and coordination with them.
- Read the Science to Measurement Requirements chapter of the DSR in advance to know current state of our art, if you have not already.
- Overview of flowdown process: what it is and why we do it [Lawrence] File:Lawrence ucsd 2019.pdf
- REview of DSR and prompts for discussion [Knox] File:Science2Measurement Knox.key.pdf
- General discussion
- Flow down from low-ell BB [Bischoff and Wu] slides
- Flow down from light relics [Loverde and Reichardt]
- Flow down from galaxy clusters goal [Battaglia] File:S4 UCSD Cluster Flowdown.pdf
- Flow down from GRB goal [Vieira]
- We need requirements specified so people can build without consulting with each other constantly. Too many people for that consultation to be possible.
- "Good enough" is! "Better" costs more.
- science goals --> measurement reqs --> instrument reqs --> mission reqs, plus feasibility and cost loop back.
- Pryke: we've got foregrounds and we don't know what they are. How do we deal with this fundamental degree of uncertainty?
- Lawrence: I'm in complete agreement with that point. We have to make some allowances for the fact we don't know. One way we do that is to have a substantial margin on science requirements: a factor of two in some cases.
- Ed Wollack: It's not a new problem.
- Clem Pryke: but split bands for conservatism was not judged to be a valid argument. We needed to demonstrate it led to improvements, when we don't know what the foregrounds are like!
- Four science goals that drive design: r, light relics, clusters, GRBs. (Other science goals are not design drivers)
- Leads to two surveys: ultra-deep hybrid resolution and deep/wide high resolution
- Worked example of science to measurement flowdown for deep/wide survey. Science goals lead to sky coverage, beam size, map depth, observing cadence.
- Still need to think more about systematics (esp. beams), elevation minimum, margin for science targets.
- Frequency coverage is based on Colin Hill calculations that optimized several science goals... but none of these were actually "galaxy clusters". Is this good enough, or does it need to be revisited?
- Increasing sigma(Delta Neff) requirement from 0.03 to 0.033 makes measurement much easier. Can we do this (but maybe keep a goal of 0.03)?
- Do we need to connect measurement optimizations to cost models? Otherwise, we always want more angular resolution and deeper maps.
- Discussion of beam systematics and the need to simulate them:
- For Neff science goal, planet measurements will measure necessary beam parameters at high significance... so long as they don't vary frequently
- For r / delensing, beam systematics (like far sidelobes) will be important. Still have a problem of how much to believe physical optics models, ground models, etc.
- Example DESI CD-1 requirements document -- Only 19 pages, all flows down from BAO science goal. Sample variance pushes to large sky area, setting errors on D(z) and H(z). This is posted on the wiki (link??)
- Supposed to have draft baseline requirements document by end of 2020. Lots of work needed by June 2020!