BROOM: Blind Reconstruction Of signals from Observations in the Microwaves
BROOM is a Python package for blind component separation and Cosmic Microwave Background (CMB) data analysis.
📦 Installation
You can install the base package using:
pip install cmbroom
This installs the core functionality.
If you plan to use the few functions that depend on pymaster, you must install it separately (version >=2.4).
🔧 To include pymaster automatically:
You can install cmbroom along with its optional pymaster dependency by running:
pip install cmbroom[pymaster]
However, pymaster requires some additional system libraries to be installed before running the above command.
✅ On Ubuntu/Debian:
sudo apt update
sudo apt install build-essential python3-dev libfftw3-dev libcfitsio-dev libgsl-dev
✅ On macOS (using Homebrew):
brew install fftw cfitsio gsl
Documentation
A detailed introduction to the parameters and simulation pipeline is available in:
- tutorials/tutorial_satellite.ipynb
- configs/config_demo.yaml — Example configuration file
Component separation methods are covered in:
Power spectrum estimation is demonstrated in:
For partial-sky, ground-based experiment analysis, see:
🔗 Full online documentation:
👉 https://alecarones.github.io/broom/
References
Paper on broom package is in preparation.
If you use the following methodologies please cite the corresponding papers:
- ILC or NILC: Bennett et al., 2003, Delabrouille et al., 2009
- cMILC: Remazeilles et al., 2021, Carones et al., 2024
- MC-ILC or MC-NILC: Carones et al., 2023
- PILC: Fernández-Cobos et al., 2016
- cPILC: Adak, 2021
- GILC, GNILC, GPILC: Remazeilles et al., 2011, Planck Collaboration, 2016
- foreground diagnostic: Carones et al., 2024
- power spectrum computation: Gorski et al., 2005, Zonca et al., 2019, Alonso et al., 2019
📦 Dependencies
This package relies on several scientific Python libraries:
Metadata
Release files for cmbroom 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cmbroom-0.2.1.tar.gz | 1.0 MB | Without provenance | Details for cmbroom-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cmbroom-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for cmbroom-0.2.1-py3-none-any.whl |
Total release size: 2.0 MB
Release files / cmbroom-0.2.1.tar.gz
| Download URL | cmbroom-0.2.1.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e67932ccdbeb9f816fcfa4e72c8ac22f5d6d56ab2fdf8efc830f12384ef59b38
|
|
BLAKE2b-256 checksum How to use checksums |
38c8b9d24088a79746e23a8965daeac2715399e40f36e089bc32b79e551bb600
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.0
|
Release files / cmbroom-0.2.1-py3-none-any.whl
| Download URL | cmbroom-0.2.1-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d4b49ad403c3ca709a64814bb3a9fed09316d0fbf1ca4ed20c67481e7f6e3ec
|
|
BLAKE2b-256 checksum How to use checksums |
60cc6f159b25a171da769c4fce3adc42dad76e009599c2ed42050e6942b701b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.0
|
Security for cmbroom 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.