astrofrog / astrofrog/sedfitter

Difference in fitting results compared to fortran sedfitter

Open
#62 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
21
Forks
23
PR merge metrics
No merged PRs in 30d

Description

In a test fit of Kurucz model atmospheres to a large (150,000) catalog of combined UKIDSS/2MASS and GLIMPSE point sources in a chunk of the Galactic midplane, I find ~10% more badly fit sources using the python sedfitter than previously with the fortran sedfitter. Best of my knowledge* all fitting parameters are the same (extinction law is your old ex_law_gl.par file, cpd=2, minimum datapoints = 4).

*Am I correct that the format/units of old extinction law files, including lots of extraneous columns, are still appropriate for the python sedfitter?

Contributor guide

No contributing guide indexed for this repository

Research direction

Compare the Python sedfitter with the Fortran sedfitter using the stated settings: the old ex_law_gl.par extinction law, cpd=2, and a minimum of four datapoints. First verify whether the old extinction-law format and units, including its extra columns, are accepted, then identify why the Python fit produces about 10% more badly fit sources.

Written by the indexing model from the issue text.

Assessment

Tech stack
fortran, python
Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.