Re: [mesa-users] Limiting the mass transfer

[Pablo M. <pa...@gm...>]

Hi Odette, this is straightforward.

In you src/run_binary_extras you can use this

       integer function extras_binary_check_model(binary_id)
          type (binary_info), pointer :: b
          integer, intent(in) :: binary_id
          integer :: ierr
          call binary_ptr(binary_id, b, ierr)
          if (ierr /= 0) then ! failure in  binary_ptr
             return
          end if

          !check if mass transfer rate reached maximun, assume merger if it
happens
          extras_binary_check_model = keep_going
          if(abs(b% mtransfer_rate) >= b% max_implicit_abs_mdot*Msun/secyer)
then
             extras_binary_finish_step = terminate
             write(*,*) "TERMINATING: Reached maximum mass transfer rate"
          end if
       end function extras_binary_check_model

and in you inlist you choose the value of max_implicit_abs_mdot. I usually
prefer doing it using max_implicit_abs_mdot instead of directly writing the
limit, because at the onset of unstable MT the code might not be able to
converge to a solution and get stuck.

On Fri, May 19, 2017 at 4:48 AM, Odette Toloza <ode...@gm...>
wrote:

> Hi Mesa users,
>
> I was wondering if I can implement a limit to the mass  transfer as a
> stopping condition, when I evolve a binary?
>
> Cheers,
> Odette.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> mesa-users mailing list
> mes...@li...
> 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