Skip to content

Commit

Permalink
fixing Foreground.yaml
Browse files Browse the repository at this point in the history
  • Loading branch information
sgiardie committed Sep 19, 2024
1 parent 78b1a5e commit b3a346c
Showing 1 changed file with 11 additions and 14 deletions.
25 changes: 11 additions & 14 deletions mflike/Foreground.yaml
Original file line number Diff line number Diff line change
@@ -1,13 +1,10 @@
requested_cls: [ "tt", "te", "ee" ]
requested_cls: ["tt", "te", "ee"]
lmin: 2
lmax: 6001
# ells set automatically from above if not set directly
ells:
experiments: [ "LAT_93", "LAT_145", "LAT_225" ]
bandint_freqs: [ 93.0, 145.0, 225.0 ]

# path to data
data_folder:
experiments: ["LAT_93", "LAT_145", "LAT_225"]
bandint_freqs: [93.0, 145.0, 225.0]

# Parameters to build a top-hat band:
# - nsteps sets the number of frequencies used in the band integration
Expand Down Expand Up @@ -37,18 +34,18 @@ top_hat_band:
# or be read from a file (either from external file with name "rootname" or from sacc)
# - if Gaussian_beam = False/empty and beam_from_file = False/empty, it will be read from the sacc file (currently not working)
# - if Gaussian_beam = False/empty and beam_from_file is specified, it will be read from this file
# the file has to be saved in the same path as the data
# indicate only the name, without the yaml extension and the rest of the path
# the file name has to be its absolute path without the yaml extension
# it has to be a yaml with keys = experiments and items = array((freqs, ells))
# i.e. numpy arrays of beam profiles for each frequency in the passband of that array
# - If we want to compute Gaussian beams, fill the Gaussian_beam entry with dictionaries
# containing the parametrization for FWHM for each experiment/array in T and pol
# - If bandpass shifts are != 0, you have to fill the Bandpass_shifted_beams key
# with the name of the file containing the dictionary with beam profiles for different values
# of Delta nu. As before, the file should be a yaml, the filename should not contain the ".yaml"
# extension and should be in the same path as the data. The dictionary should contain a key for
# each experiment/array, and for each of these keys there should be a "nu_0", "alpha" and "beams"
# keys. The "beams" item would be a dictionary {"nu_0 + Delta nu": b_ell, "nu_0 + 2Delta nu": b'_ell,...}
# - If bandpass shifts are != 0 and you want to propagate them to the beams, you have to fill
# the Bandpass_shifted_beams key with the name of the file containing the dictionary
# with beam profiles for different values of Delta nu. As before, the file should be a yaml,
# and you should provide its absolute path without the ".yaml" extension.
# The dictionary should contain a key for each experiment/array, and for each of these keys
# there should be a "nu_0", "alpha" and "beams" keys. The "beams" item would be a
# dictionary {"nu_0 + Delta nu": b_ell, "nu_0 + 2Delta nu": b'_ell,...}
# default is the beam_profile to be a null dict and chromatic beam not
# taken into account
beam_profile:
Expand Down

0 comments on commit b3a346c

Please sign in to comment.