CosmoStat / CosmoStat/sp_validation
Add calibrated single-column e1/e2 fields to release catalogue
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 5
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 19
Description
Keep the existing raw/uncalibrated columns unchanged, and add ready-to-use single-column e1/e2 with m-bias and PSF-leakage corrections already applied, for non-expert external users (galaxy-galaxy lensing, replication). Additive, so strictly-uncalibrated shapes remain available.
Context: Paris meeting notes
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 locating the release catalogue generation and the existing raw/uncalibrated shape columns. Determine how m-bias and PSF-leakage corrections are represented in the project before adding the calibrated single-column e1/e2 fields. Done means external users can consume corrected e1/e2 values while the existing strictly uncalibrated columns remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100