# Difference between revisions of "Reference design simulation tool"

Jump to navigationJump to search

October, 2019 - Data management group

# Background

This page documents a simulation tool based on the reference design that allows users to explore how various design choices affect CMB-S4 maps. We use limited scope time domain simulations to build an archive of signal, noise and systematic maps that can be combined with appropriate weights to account for

• observing efficiency
• survey length
• detector counts and sensitivity
• telescope siting
• levels of systematics

## Specifications

• Which resolutions to support?
• Specify the reference design. What are the parameters to vary?

## Schedule

1. Focalplane geometry 11/15/2019
2. Instrument noise model 11/08/2019
3. Observing schedules chosen by 11/15/2019
4. All inputs for TOD simulation in place by 11/15/2019
5. Simulated component maps ready by 12/01/2019
6. Simulation tool written, tested and delivered to the collaboration by 12/15/2019

# Instrument model

## Reference SAT

Describe frequencies and detector counts on the smallest independent unit (tube?).

### Focalplane

Choose some representative geometry (hexagon?) for the independent unit.

### Noise

What site and elevation-dependent noise model to use?

## Reference LAT

Describe frequencies and detector counts on the smallest independent unit (tube?).

### Focalplane

Choose some representative geometry (hexagon?) for the independent unit.

### Noise

What site and elevation-dependent noise model to use?

# Scan strategy

The simulation requires specifying a scan strategy for each telescope and site considered.

## Pole SAT

We use the Pole deep scan strategy from Deep_SAT_from_the_Pole. The boresight scans over RA = [20..60] deg and Dec = [-55..-50] deg in 0.25-degree elevation steps, 30 minutes per step. The 21 steps take 10h 50min to complete with 1min gap between each step. Here is an example 10-day hit map using a dummy 35-degree hexagonal focalplane with 217 pixels:

For simplicity, we schedule exactly one complete scan for each calendar day.

## Pole LAT

The Pole LAT scan strategy is designed to cover the SAT patch. We enlarge the target patch to account for the considerable difference in focal plane sizes. The boresight sweeps over RA = [10..70] deg and Dec = [-65..-40] deg in 0.25-degree elevation steps, 5 minutes per step. The 101 steps take 10h 5min to complete with a 1min gap between each step. Here is an example 10-day hit map using a fake focalplane with 19 pixels:

## Chile SAT

The Chile SAT strategy is based on Deeper_SAT_from_Chile_II. We have circled the Celestial sphere above Atacama with 10x20-degree (RA x Dec) tiles to form an almost continuous chain of low foreground tiles. The tiles are divided into three tiers, each tier having absolute priority over lower tiers when ever they can be targeted. This way the schedule targets two deep patches (North and South) as much as the scheduling constraints allow and embeds them in a wedding cake fashion in a shallower environment. The scheduler considers observing elevations in range of 45-60 degrees with a preference for higher elevations. For the 10-day example we have disabled Sun and Moon avoidance with the understanding that full season observations will lead to similar hit map even with the avoidance enabled.

## Chile LAT

The Chile LAT strategy is based on Modulated_scan_high_cadence_LAT, the experimental scan strategy that modulates the scan rate based on telescope Azimuth. We observe at 40-degree elevation, sweeping at Az = [20..160] degrees or Az = [200..340] degrees. The telescope scan rate is lowest at Az=90 and Az=270 degrees and 2.75 times higher at the start of the turnaround. This allows for a near uniform 65% sky coverage while maintaining daily cadence across the observable sky. As with Chile SAT, we have disabled the Sun and Moon avoidance for the 10-day representative period.

# Data reduction

Data reduction must be linear. Each component will be processed separately.

# Input archive

We'll use NERSC to host the input maps.

# Software

Where do the scripts, parameter files and code go?