Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

isochrone fitting #26

Closed
10 of 12 tasks
joshspeagle opened this issue Dec 18, 2018 · 3 comments
Closed
10 of 12 tasks

isochrone fitting #26

joshspeagle opened this issue Dec 18, 2018 · 3 comments
Assignees
Labels
enhancement New feature or request models Related to underlying stellar/dust models validation Validating performance

Comments

@joshspeagle
Copy link
Owner

joshspeagle commented Dec 18, 2018

Add in functionality to deal with MAP isochrone fitting for observed data. This will focus on generating isochrones as a function of age and metallicity and comparing them to observed objects. The goal here will be to do this by implicitly marginalizing out per-star variables, which include:

  • mass
  • binarity
  • distance
  • Av
  • Rv

Which are listed in roughly the order of importance. To start, we will focus on marginalizing over the first two (primary and secondary mass, i.e. mini and smf) assuming a co-eval and co-spatial cluster. The latter become more relevant when we want to start modeling co-eval populations that have since been disrupted, and so can be in different locations on the sky (inspired by @smeingast and Joao Alves).

One big challenge to this is outlier modeling, which essentially take two flavors. The first is cluster-based outliers which we can't model well and need to exclude relative to a given isochrone. The second is field stars, which can take on a much broader distribution and is the result of contamination. These are also listed in order of importance:

  • field stars
  • blue stragglers
  • blue horizontal branch stars
  • white dwarfs

Finally, there will need to systematics included in the isochrone models. These have two regimes:

  • low masses (M <~ 0.5 after corrections)
  • high masses (M >~ 20)
  • post-MS (EEP >~450)

Both of the above issues will be dealt with based on conversations with (primarily) @aarondotter.

Once we have this working on a population level, I will try to expand this to include hierarchical inference so we can also extract individual stellar results. This might involve building a similar suite of functions to MINESweeper, or might just involve basic hacks over other posteriors (from BruteForce) or the SEDMaker-type objects I'm already using.

@joshspeagle joshspeagle added enhancement New feature or request models Related to underlying stellar/dust models labels Dec 18, 2018
@joshspeagle joshspeagle self-assigned this Dec 18, 2018
@joshspeagle joshspeagle added the validation Validating performance label Dec 18, 2018
@joshspeagle
Copy link
Owner Author

After having other things pop up delaying this forever, Initial results look really promising! I ended up using a simpler outlier model and the code is still hacky, but this appears to have worked.

As an example, here's the best-fit isochrone for M67, marginalized over mass and binarity:

image

@smeingast
Copy link

smeingast commented Jul 25, 2019 via email

@joshspeagle
Copy link
Owner Author

Sounds reasonable to me! I currently don't have the built-in capabilities to allow for different distances and/or extinctions to each star at the moment, but if you think that's not really an issue (i.e. these can all be converted to absolute magnitudes fairly confidently), then I'm happy to give this a spin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request models Related to underlying stellar/dust models validation Validating performance
Projects
None yet
Development

No branches or pull requests

2 participants