CosmoStat / CosmoStat/sp_validation
Use CCL's CAMB backend so blinding and inference share one Boltzmann path
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 5
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 19
Description
From @sachaguer's review of #241: CCL can use CAMB as its Boltzmann backend (transfer_function="boltzmann_camb" and matching halofit config). If CAMB is what the inference step runs, the blinding theory callables (#252) should call CAMB through CCL rather than using CCL's default — then blinding and inference share one power-spectrum path and the CAMB↔CCL cross-check in #252 becomes a consistency guard rather than a seam we live with.
Done when: the theory backend config in #252 exposes the Boltzmann-backend choice, the shipped default matches whatever the inference pipeline (#220) uses, and the cross-check test runs against that configuration.
— Fable on behalf of Cail.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the theory backend configuration described in #252 and tracing which Boltzmann backend the inference pipeline in #220 uses. Update the configuration so its choice and shipped default match that pipeline, then run the CAMB↔CCL cross-check test against the resulting configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100