simonsobs / simonsobs/SOOPERCOOL

Unifying simulation code

Open
#86 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
6
Forks
5
Avg merge
5d 22h
Merged PRs (30d)
2

Description

Currently the simulations used by soopercool are generated by many different scripts. We need to standardize the scripts/packages used for TF estimation sims, TF validation sims, CMB sims, FG sims, noise sims. This includes passing standardized theory CL files (including beams, where this simplifies things).

Currently, the status is:

  • TF estimation sims for ISO are bandlimited at ell_max=650 with width 50
  • A cleaned script for TF estimation sims has been added in #82
  • A cleaned script for CMB-only sims has been added in #82
  • CMB and FG sims can be produced by SOOPERSIMS in both map and alm format. The general TF validation script and the MC covariance script accept signal sims in both alm and map format.
  • Noise sims generator scripts are outdated. TF validation / MC covariance scripts only accept maps, no alms. This relates to #40

We should decide on standard simulation code, ensure compatibility with core code, and add documentation.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin by reviewing the cleaned TF-estimation and CMB-only scripts added in #82, then compare SOOPERSIMS with the TF validation and MC covariance scripts. Determine a standard simulation path covering TF estimation, TF validation, CMB, foreground, and noise sims, with compatible map, alm, and theory CL inputs; document the resulting approach and its core-code compatibility.

Written by the indexing model from the issue text.

Assessment

Domain
data, documentation
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.