-
Notifications
You must be signed in to change notification settings - Fork 22
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
support for binary star modelling #68
Comments
…evelop#68, now on gully laptop
This is very exciting! I have been monitoring the progress over at https://github.com/gully/Starfish/tree/mix_model_omega2 (and #CS19 in general), and it seems as though you all have made significant progress in implementing a binary model. As you mentioned, the primary changes would need to be in the |
Hi all, a little follow-up: We successfully wrote and compiled the double-lined spectroscopic binary code at the Cool Stars 19 Hack Day. It was exciting. Our approach was a bit simplistic- lots of copying, pasting, and tweaking existing lines of code to hack a second spectrum component. A more elegant approach would have been to abstract-away some of the At the Hack Day wrap-up/demo we showed the first 20 samples of a 40-walker The sampling actually halted shortly after the 20 samples, so that should be looked into... The next steps would be to demo the code on either some real spectroscopic binary data, or synthetic data constructed for the purpose of recovering "known" or "injected" stellar parameters to convince ourselves that the machinery works. It could be fun to add a fake binary to an existing real data spectrum, for example. Ian's point about training the spectral emulator should also be considered for real-world applications. Simultaneously modeling an A-star and an M-star would be infeasible. Near-equal mass binaries should be fine, I suppose. Another approach would be to train isolated islands of parameter space and alter the code to emulate the two spectral components from these isolated ranges. Needless to say this isolated islands approach would require some thinking about the implementation that I have not done. |
Support for binary modeling has largely been superseded by this new package that supports radial velocity variations from multiple components. The only reason I can see for adding support for binaries in Starfish would be if you had only one epoch available, since much of the value from PSOAP comes from access to multiple epochs. https://github.com/iancze/PSOAP Unless someone objects I propose to close this issue. |
I don't know about closing this just yet. While the GP framework in PSOAP is certainly complementary to Starfish, it is purely data driven, meaning it never touches physical models of the star, which are necessary for determining Teff, log g, etc... Certainly aspects of PSOAP could be borrowed to use in Starfish, but I would be in favor of leaving this issue open for now. |
Currently the code can model single stars with starspots @gully (with a single temp. and fill factor). We (@tofflemire, @gully and @EdGillen) want to extend that to do full modelling of intrinsic (e.g. logg, Teff) and extrinsic (e.g. vsini) model parameters. This would describe double-lined binary stars.
The main changes would be to
update_theta
.The text was updated successfully, but these errors were encountered: