1. Pipeline tasks¶
1.1. Preparation¶
1.1.1. Data access¶
The ACT and SO map-makers provide sets of maps with mutually exclusive data; each set consists of completely independent TOD samples. This constitutes some splitting of the data. For historical reasons, we refer to each such set as an `array’. This terminology is derived from the fact that the TODs are primarily split by which detector array they originate from, though since 2015, ACTpol and its successors (including Advanced ACT and SO) use multi-chroic arrays, which means each hardware array will provide us multiple (almost always two) `array’ map sets even in the same season/year and region. We will now stop using quotes around `array’ under the understanding that it applies to some unit of splitting closely related to what is used in ACT.
Within ACT, these arrays typically come from some region or scan (though since 2016 there has primarily been just a wide scan each for day and night) for a particular season and particular frequency band (since the ACTpol PA3 array, one of two within a dichroic hardware array). For SO, under the current simulation design, there will be two array maps for each optics tube because of the dichroic hardware array in the tube.
We will also be combining with Planck, for which we define a Planck array as a particular frequency band, reprojected to the CAR pixelization and subtracted of sources (see planck_reproj).