Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[mbs-0021] SAT beams

Aperta
  • Qualcosa non va?
#74 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
data

Direzione di ricerca

Start with the issue's two beam-product options and inspect the listed products under /scratch/gpfs/SIMONSOBS/sat-iso/beams/planets/. Read the SO Wiki “Beams Metadata Version Log” and follow up on the broken strictly-SCR5 link. Done means deciding which granularity and normalization the simulations should use, then recording that decision in the project.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Context

We need to decide which SAT beam products to use in the map based simulations.

These are MEASUREMENTS, not simulations: the beams were measured on sky from radially binned planet maps (azimuthal symmetry of the beam assumed). The radial profile is obtained by fitting Bessel functions of the first kind to the beam core and a power-law wing to the tail, and the window functions come from numerical integration of the profiles (SO Wiki, "Beams Metadata Version Log").

Terminology

  • SAT: Small Aperture Telescope. SO has three (satp1, satp2, satp3); beam products exist for satp1 and satp3.
  • f090 / f150: frequency bands (~90 / ~150 GHz) of the SAT receivers.
  • ws (wafer slot): position on the focal plane, 7 per SAT telescope (ws0..ws6).
  • Beam radial profile: the measured beam brightness as a function of angle from the beam center (theta), assuming azimuthal symmetry.
  • Window function W(ell): transfer function of the beam in harmonic space, by which the underlying sky is multiplied when simulating the observed map.
  • solid angle (omega): integral of the beam over the sky, used to normalize.
  • ell: multipole number (0..1999 in these products).
  • SCR4 / SCR5: Site Cooldown Runs 4 and 5 (SAT-MF1 nomenclature), two successive observing campaigns of the SATs separated by cooldown/maintenance periods. Between them (around January 2025) the focal plane was reconfigured (detector retrofit / wafer swap): some wafers stayed, some were removed, some moved. SCR5 is the current configuration after the swap.
  • Covariance matrices: estimates of the uncertainty of the window function, propagated from the measurement uncertainties (statistical, and from the core-to-wing transition and Bessel scaling parameters).

Two options (differ in granularity of the maps)

  • Option 1 (per-frequency effective beams): 4 maps
    one per telescope and frequency band: satp1_f090, satp1_f150, satp3_f090, satp3_f150
  • Option 2 (per-wafer beams): 28 maps
    one per telescope, band and wafer slot: satp1/satp3 x f090/f150 x ws0..ws6

Products live on Tiger3 under /scratch/gpfs/SIMONSOBS/sat-iso/beams/planets/ :

Option 1: per-frequency effective beams -> 4 maps

Directories:

  • 20260521spline_effective_v4_paper_20260520_science/ (satp1)
  • 20260521spline_effective_v4_paper_20260520_science_satp3/ (satp3)

Files: one beam window function per telescope and band, in two formats:

  • satp1_science_v4_paper_f090.fits / .dat
  • satp1_science_v4_paper_f150.fits / .dat
  • satp3_science_v4_paper_f090.fits / .dat
  • satp3_science_v4_paper_f150.fits / .dat

Contents: the effective beam window function W(ell) for the full telescope and band, combining all 7 wafer slots. .dat: two columns, ell and window function (ell = 0..1999). .fits: healpy table with the 2000 window function values. Normalized to 1 at ell = 0. This is the beam to use when the simulation produces one map per telescope and band (4 maps).

Option 2: per-wafer beams -> 28 maps

Directory:

  • 20260602_bessel_analytic_cov/

Files: one npz per telescope, band and wafer slot: original_cov_fitted_peak_{telescope}{band}{ws}_bessel_analytic_cov.npz

Each npz contains:

  • theta, profile: radial angle (arcmin) and peak-normalized radial beam profile
  • Bl: window function, ell = 0..1999
  • omega, sigma_omega: solid angle and its 1-sigma error
  • analytic_cov_Bl: statistical ell-ell covariance matrix (bin = 1)
  • theta1_cov_Bl: covariance from the core-to-wing transition location uncertainty
  • lmax_cov_Bl: covariance from the Bessel scaling parameter uncertainty
  • sigma_wn_fn_diag: diagonal 1-sigma error on the window function (the three covariance terms added in quadrature)
  • fwhm: estimated FWHM (azimuthal symmetry assumed)

Window function to use: Bl^2 * (2*pi/omega)^2, normalized to 1 at ell = 0. This is the beam to use when the simulation produces one map per wafer slot (28 maps).

Other products in the same folder

  • 20260602_bessel_analytic_cov_effective_v4_paper_20260520_science: per-frequency effective beams with a different (not normalized to 1 at ell = 0) normalization; only the satp3 _norm0 variants are normalized
  • 20260521spline: per-wafer spline window functions (ell, wn_fn), not normalized to 1 at ell = 0, one wafer-slot file missing

Note from the wiki (Beams Metadata Version Log)

The 20260602 products combine beams measured during SCR4 and SCR5, so profiles are mixed between wafers that remained on the focal plane, those removed after SCR4, and those that moved. No large focal plane variation is seen in the profiles, but use with caution; a strictly-SCR5 product exists (the link in the wiki is broken, to follow up with the beam team). The metadata format is for analysis (post-processing of TODs) and may change.

Lingua principale
Jupyter Notebook
Stelle
6
Fork
3
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di simonsobs/map_based_simulations

Tutte le issue di simonsobs/map_based_simulations

Issue simili

Altre issue su Data Engineering

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.