LAT Multifrequency Likelihood
An external likelihood using cobaya.
Installing the code
The easiest way to install and to use mflike likelihood is via pip
pip install mflike
If you want to dig into the code, you’d better clone this repository to some location
git clone https://github.com/simonsobs/LAT_MFLike.git /where/to/clone
Then you can install the mflike likelihood and its dependencies via
pip install -e /where/to/clone
The -e option allow the developer to make changes within the mflike directory without having to reinstall at every changes. If you plan to just use the likelihood and do not develop it, you can remove the -e option.
Installing LAT likelihood data
Preliminary simulated data can be found at NERSC. You can download them by yourself but you can also use the cobaya-install binary and let it do the installation job. For instance, if you do the next command
cobaya-install /where/to/clone/examples/mflike_example.yaml -p /where/to/put/packages
data and code such as CAMB will be downloaded and installed within the /where/to/put/packages directory. For more details, you can have a look to cobaya documentation.
Running/testing the code
You can test the mflike likelihood by doing
cobaya-run /where/to/clone/examples/mflike_example.yaml -p /where/to/put/packages
which should run a MCMC sampler for the simulation n°44 (i.e. data_sacc_00044.fits in the mflike_example.yaml file) using the combination of TT, TE and EE spectra (i.e. polarizations: ['TT', 'TE', 'ET', 'EE']). The results will be stored in the chains/mcmc directory.
Simulation releases
v0.8 release has spectra produced with high accuracy camb parameters up to ell = 9000, the foreground components are integrated in frequency using top-hat bandpasses, stored in the sacc files
v0.7.1 is a bugfix release of v0.7 release where the mono-frequency and dirac bandpasses have been correctly set with the sacc files
v0.7 release includes the ACT like foregrounds. Simulation parameters are also stored within sacc metadata and the associated dict file can be viewed here.
v0.6 release make use of CMB map based simulations (see https://github.com/simonsobs/map_based_simulations/blob/master/201911_lensed_cmb/README.md). Only temperature foregrounds were considered.
Releases prior to v0.6 version were development simulations and should not be used for simulation analysis.
Contributors
Metadata
Release files for mflike 1.0.2
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 |
|---|---|---|---|---|
| mflike-1.0.2.tar.gz | 1.2 MB | Without provenance | Details for mflike-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mflike-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for mflike-1.0.2-py3-none-any.whl |
Total release size: 2.3 MB
Release files / mflike-1.0.2.tar.gz
| Download URL | mflike-1.0.2.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
770a3ebe4f2228457574f7b207fe31bea5ed93db737a514dfd9f8e29504dd33a
|
|
BLAKE2b-256 checksum How to use checksums |
b47fc14623b78acf69c2abe29ea2fae9020617549c06c66f8c8850303ac82154
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / mflike-1.0.2-py3-none-any.whl
| Download URL | mflike-1.0.2-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
06b0e09dbf337ea87dfb2447727250d31edad41f894e21a27c208f1de0d21000
|
|
BLAKE2b-256 checksum How to use checksums |
4d05cbc498ac49f85ba53573bff04300df7f46a1ad3c80dc9e613bf09f0d0a76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for mflike 1.0.2
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.