This configuration was used to save TOD components (CMB, wn_1f_100mHz, wn_1f_30mHz, wn, fg) for the Madam mapmaker, and each combination should have been used individually:
obs_multitod.tod_wn_1f_100mHz = np.zeros_like(obs_multitod.tod)
obs_multitod.tod_wn_1f_30mHz = np.zeros_like(obs_multitod.tod)
obs_multitod.tod_wn = np.zeros_like(obs_multitod.tod)
obs_multitod.tod_fg = np.zeros_like(obs_multitod.tod)
In order to save memory the attribute obs_multitod.tod of the Class Observation was used to store CMB instead of using an additional field .tod_cmb, thus leaving .tod unused. In reality, Madam stored all the components in obs_multitod.tod, therefore when Madam produced maps (whether it was binning or destriping), the output showed an excess of power when referring to the case .tod, whereas a correct behaviour otherwise.
Issue is solved by correcting .tod with .tod_cmb. However, in this way, the obs.tod field is not used.
This configuration was used to save TOD components (
CMB,wn_1f_100mHz,wn_1f_30mHz,wn,fg) for the Madam mapmaker, and each combination should have been used individually:In order to save memory the attribute
obs_multitod.todof the ClassObservationwas used to store CMB instead of using an additional field.tod_cmb, thus leaving.todunused. In reality, Madam stored all the components inobs_multitod.tod, therefore when Madam produced maps (whether it was binning or destriping), the output showed an excess of power when referring to the case.tod, whereas a correct behaviour otherwise.Issue is solved by correcting
.todwith.tod_cmb. However, in this way, theobs.todfield is not used.