vlsr prior is too narrow
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating fit_map() and inspect how the ±10 km/s vlsr prior is defined and applied. Compare that assumption with the disc cases affected by the issue, then add coverage showing that fitting is no longer excluded by an overly narrow prior; the appropriate replacement range is not specified here.
Written by the indexing model from the issue text.
Description
I think the prior used by fit_map() for vlsr of +-10km/s is too narrow and incompatible with some discs.
- Dominant language
- Python
- Stars
- 23
- Forks
- 10
- Avg merge
- 28m
- Merged PRs (30d)
- 1
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.
More from PlanetFormationLab/eddy
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
PlanetFormationLab/eddy#36 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
PlanetFormationLab/eddy#39 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PlanetFormationLab/eddy#35 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PlanetFormationLab/eddy#34 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
PlanetFormationLab/eddy#32 ·
All issues in PlanetFormationLab/eddy
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100