Instrument Configuration Options

[smsimon]

1) It would be convenient to have a hardware input file in YAML that can be shared between TOAST an s4cmb, so that we can just import an experiment (SO for example). 2) We're also wondering if the following are implemented/easily implemented into the instrument setup

• square focal plane vs. hex focal plane layout
• dichroic detectors 3) Is there room for a hierarchy of detector info (wafer, physical location, electrical info) versus just detector index? For example, a bolometer class with these attributes.

[JulienPeloton]

1. agree. If you can provide me with a typical YAML file from TOAST, I will implement a routine to read/save hardware file in s4cmb.

2. I would say

   • A priori no problem to implement a different geometry for the focal plane.
   • It is slightly challenging but doable. The idea if I understand correctly would be to have 4 bolometers at each current pixel location, with 2 frequency bands total. From the point of view of the initialisation, that means doubling all instrument parameters (defining 2 beam sizes, 2 instrument noise levels, and so on). From the point of view of processing the data, that means processing 2 kinds of detectors. From the point of view of running the code, that means twice more detectors to process than currently.

3. Yes there is one. In the class FocalPlane, you have a routine make_focal_plane which defines the hierarchy and physical locations:

## Initialise
self.crate_id, self.dfmux_id = [], []
self.squid_id, self.bolo_id = [], []
self.bolo_index_in_squid, self.bolo_index_in_fp = [], []
self.bolo_xcoord, self.bolo_ycoord, self.bolo_polangle = [], [], []

It is very basic and can be expanded (we can add electrical info for example which could be useful to have later on when we simulate crosstalk, or any other idea). Note that what I call currently Crate would correspond to a wafer (sorry, this is probably not the right thing to do...).

[JulienPeloton]

Concerning 2. : we should also coordinate to create input file containing location of bolometers and useful information to be read by codes rather than on-the-fly generation. (PB used to use hardware map, but others have similar things).

[JulienPeloton]

Idea: configuration file should contain beam parameters.

[JulienPeloton]

Concerning dichroic detector, here is a first attempt. The change still lives in a separate branch in s4cmb (origin/dichroic), so make sure you switch to that branch if you want to use it. As it is still experimental (and messy!) do not hesitate to report here any issue or concern.