Skip to content

Madam not working correctly when using in obs.tod #3

@nraffuzz

Description

@nraffuzz

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions