[Mesa-users] mass transfer reset to zero when resuming a run using a saved model

[Pablo Marchant]

I don't think mass loss rate is stored in saved models (you can directly
open your saved models to see this). If you're reading the value in
extras_binary_finish_step you already have one step completed, and the mdot
of the star will have been set by the step, not from the loading of the
model. So for the moment, as there is no simple save model functionality in
the binary module, you'll have to rely on this. You can automate it via
fortran though, just by saving a file on the termination of your run that
includes b% mtransfer_rate and b% mtransfer_rate_old, and reading that file
on reload.

Cheers

On Tue, Feb 23, 2021 at 11:35 AM O Toloza <odette.toloza at gmail.com> wrote:

> Hi Pablo,
>
> thanks a lot for the help. It does work.
>
> I just give to it the value N which I read from the history.data
> (lg_mtransfer_rate),
>
> b% mtransfer_rate_old = N
> b% mtransfer_rate = N*1.01
>
> However it seems that b% s_donor% mstar_dot is stored, because I can
> retrieve it within extras_binary_finish_step, but not within
> extras_binary_startup.
>
> I am trying,
>
> b% mtransfer_rate_old =  b% s_donor% mstar_dot_old
> b% mtransfer_rate =  b% s_donor% mstar_dot
>
> Is there a way to know what are the parameters contained in a model?
>
>
> Cheers,
> Odette.
>
>
>
> On Tue, 23 Feb 2021 at 08:20, Pablo Marchant <pamarca at gmail.com> wrote:
>
>> Hi Odette,
>>
>> the value that is missing in the run with the loaded model is the mass
>> transfer rate stored in binary info, b% mtransfer_rate. In your run_binary
>> extras you should have access to the extras_binary_startup subroutine. Can
>> you try setting the value of b% mtransfer_rate (and b% mtransfer_rate_old)
>> in there?
>>
>> Cheers
>>
>> On Mon, Feb 22, 2021 at 11:07 PM O Toloza via Mesa-users <
>> mesa-users at lists.mesastar.org> wrote:
>>
>>> Hi mesa users,
>>>
>>> I hope you are all doing well. I am trying to run binary when there is
>>> mass transfer.
>>>
>>> I am stopping the simulation until the mass transfer reaches a certain
>>> threshold,
>>> and saving a model (save_model_when_terminate = .true.). And I would
>>> like to
>>> resume changing a few functions/parameters.
>>>
>>> However when resuming and loading the model the mass transfer (b%
>>> mtransfer_rate)
>>> is set to zero instead of the last value recorded on the run.
>>>
>>> I have tried a few things.
>>>
>>> 1. starting_mdot which is only valid for roche_lobe scheme, but I am
>>> using "Ritter".
>>> And in an attempt of providing an initial mass transfer, I tried number
>>> 2 below.
>>>
>>> 2. mass_change where I give the last value of mass_transfer recorded in
>>> the run. But
>>> it does not solve it.
>>>
>>> 3. ./re photo, however here I am not able to save the last photo of the
>>> binary run, just
>>> the star (save_photo_when_terminate in inlist 1), and if I resume from
>>> the last photo
>>> in save for the star I get:
>>>
>>>   STOP error in binary_photo_read
>>>
>>> Any feedback/input/suggestion is very appreciated.
>>>
>>> Cheers,
>>> Odette.
>>>
>>>
>>> --
>>> *Odette*
>>> _______________________________________________
>>> 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
>>
>
>
> --
> *Odette*
>


-- 
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/20210223/fa7ec81f/attachment.htm>