[mesa-users] Binary capabilities on MESA

[Pablo Marchant]

Thanks for your quick and very informative answer :D

This gives me a clearer picture of how things work, so I can start digging
on the code, and ask again here if I get lost with something. I'll discuss
it in detail with Norbert when he comes back to Bonn next week, and I'll
keep you on the loop of course.

Additional hands working on development of this would certainly be great.
Guess Tassos is part of the mailing list, but I can also contact Selma. And
Jean-Claude, guess I'll see you around here then.

Cheers!

On Thu, Oct 4, 2012 at 7:08 PM, Bill Paxton <paxton at kitp.ucsb.edu> wrote:

> Hi,
>
> Also, take a look at star/binary_systems/tide_routines.inc -- I've haven't
> tested it, but I think it is close to being a working implementation in
> mesa of the spiba routine from Norbert et al.   We'll need to add code to
> the rlo routines to call the synch_spin_to_orbit routine from an
> "other_torque" routine.  The other_torque routine will need to get the
> arguments for synch_spin_to_orbit from the current state of the binary (see
> star/binary_systems/rlo_data.inc).
>
> -B
>
>
>
>
>
> On Oct 4, 2012, at 5:03 AM, Pablo Marchant wrote:
>
> > Hi! Last August at the MESA summer school we had a small session where
> we discussed the binary evolution capabilities of MESA. As far as I can
> remember, Bill Paxton said that the current implementation for binaries is
> more a "proof of concept" than a robust implementation (not his precise
> words but something on that line). In that sense, the current code has
> restrictions, as for instance only one star can be an accretor while the
> other one is set as the donor in a fixed way at the beggining of the
> simulation. Also, tidal torques are not implemented.
> >
> > Even though I'm not very experienced in FORTRAN, I've been skimming
> through the source code trying to understand where these things are done,
> but not to much avail. I've also been playing with the binary examples on
> the test suite (binary_rlo and binary_rlo_implicit, which have equal
> initial conditions but different implementations for mass transfer), but I
> have no idea if there's a simple way to output info on the binary system
> itself.
> >
> > So, going to the point ... I'm really interested on getting a robust
> implementation for binaries on MESA, so mostly I'd like to know more
> precisely what are the limitations of the current implementation and if
> it's part of the development roadmap to enhance this capability. In any
> case, I would not have problems on getting involved on actual development
> for this functionality.
> >
> > Cheers to all!
> >
> > --
> > Pablo Marchant Campos
> > M.Sc on Astrophysics, Universidad Católica de Chile
> > PhD student, Argelander-Institut für Astronomie
> >
> ------------------------------------------------------------------------------
> > Don't let slow site performance ruin your business. Deploy New Relic APM
> > Deploy New Relic app performance management and know exactly
> > what is happening inside your Ruby, Python, PHP, Java, and .NET app
> > Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> >
> http://p.sf.net/sfu/newrelic-dev2dev_______________________________________________
> > mesa-users mailing list
> > mesa-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mesa-users
>
>


-- 
Pablo Marchant Campos
M.Sc on Astrophysics, Universidad Católica de Chile
PhD student, Argelander-Institut für Astronomie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20121004/9a711420/attachment.html>