firecrown
firecrown copied to clipboard
LSSTDESC
DESC Cosmology Likelihood Framework
The code in `TwoPoint.calcuate_pk` does not handle the two tracers it is given symmetrically; if the first is associated with a source that has a PT systematic, and the second...
This PR integrates the halo model for intrinsic alignments as a potential systematic for 3x2-point likelihoods. It adds a new ```WeakLensingSystematic``` class called ```HMAlignmentSystematic``` and the appropriate behaviour for when...
We don't have a consistent style for our docstrings. This was previously causing warnings in the sphinx auto doc and may be the underlying cause of #384. Acceptance Criteria *...
This is a more-or-less working prototype of a yaml-based likelihood specification, following the [discussion thread](https://github.com/LSSTDESC/firecrown/discussions/308#discussioncomment-7589995). Some features I think are nice: - Separation of model and data specification: specifying the...
For blinding (@arthurmloureiro) we need to be able to pass sacc objects to the likelihood creation entry point. At the moment, `load_likelihood` and `build_likelihood` expect a `NamedParameters` argument. This precludes...
Hi Firecrowd, It would be great to have a way for returning a dictionary of required parameters (keys and values) from a likelihood object. At the moment, I can return...
Right now the likelihoods in firecrown require a sacc object to compute anything. It would be nice to have a utility likelihood that takes in a list of ell (or...
We would like to make firecrown take higher precision settings for CCL; e.g., https://ccl.readthedocs.io/en/latest/source/notation_and_other_cosmological_conventions.html. How can those be passed smoothly to firecrown?
We need more examples showcasing factory functions that can be configure by sampling framework using `build_parameters`. For example, using different SACC files for the same likelihood configuration.