[Mesa-users] Mass transfer rate used in run_star_extras.f

[Pablo Marchant]

Hi Thomas,

to access the data in the binary info pointer you need to define a
binary_info pointer, and then use the binary_ptr subroutine in the same way
that the star_ptr subroutine is used. Specifically, it looks like this

          type (star_info), pointer :: s
          type (binary_info), pointer :: b
          ierr = 0
          call star_ptr(id, s, ierr)
          if (ierr /= 0) return
          call binary_ptr(s% binary_id, b, ierr)
          if (ierr /= 0) return
         !now you can read b% mtransfer_rate

If you want a specific example, you can check the run_star_extras in the
double_bh test_case of the binary module.

Cheers!

On Mon, Sep 10, 2018 at 10:25 AM Gehrman, Thomas Charles <
thomas.gehrman at mnsu.edu> wrote:

> Hello all,
>
>
> I'm having trouble figuring out how to call the binary pointer for mass
> transfer in the run_star_extras. My equations I am implementing requires a
> torque on the mass gainer that is dependent on the amount of mass transfer
> overtime. I see other_binary_extras depend on the orbital Jdot or are
> related to tidal interaction to sync the spin and orbit, but I need it
> specifically for the mass gainer.
>
>
> I have attached my inlists, run_star_extras, and run_binary_extras. I have
> commented out the mass transfer variable I think I need for my equation in
> the run_star_extras.
>
>
> Thank you kindly,
>
>
> Thomas
>
>
> Thomas C. Gehrman Jr.
>
> M.S. Physics & Graduate Teaching Assistant
>
> Department of Physics and Astronomy
>
> Minnesota State University, Mankato
>
> Office: N144
>
>
>
> _______________________________________________
> mesa-users at lists.mesastar.org
> https://lists.mesastar.org/mailman/listinfo/mesa-users
>
>

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