Campuses:
This is an old revision of the document!
Send e-mail to:
probedatachallenge+subscribe@umn.edu
The subject and body of the e-mail can be empty. Within minutes you will receive an automated e-mail response asking you to click on a radio button to subscribe. The group's managers will then receive a notification and will add you.
Important: if you don't receive the first automated response please contact Julian (jdborrill@lbl.gov) or Lloyd (lknox@ucdavis.edu). While not common, this is a failure we have seen with some e-mail addresses.
These data challenges are in support of the study of the imager option for a Probe-class CMB mission. We will use it as a check on analytic forecasts, and to further optimize the baseline design.
We are at the very beginning stages of defining this data challenge. Nothing written here should be understood as finalized. Please feel free to contribute to the definition of the data challenge.
Following the model used in CMB-S4, we will define Data Challenge X.Y as the application of Mission Model X to Sky Model Y. We anticipate the first iteration (DC_0.0) to be available in mid-July. This will primarily be a test case for the construction and analysis processes, with more detailed and representative models to follow.
Links to the details of specific mission and sky models are provided below.
Data will be made available at NERSC at /project/projectdirs/cmbp
To obtain a NERSC account please go to http://crd.lbl.gov/cmb to sign-up, using repository mp107 and PI Borrill.
A mission model includes an Instrument Model and an Observation Model
A basic instrument model will include specification of each frequency band:
An advanced instrument model will also include:
An observation model defines the scanning strategy
and any polarization modulation
Given an observation and an advanced instrument model, we will use the TOAST tools to generate simulated hit and noise maps.
A sky model comprises four elements: