[Mesa-users] YNT: Evolution of binaries, problem

[Gökhan Yücel]

Thanks for replying Josiah. 

I have tried the parameter you suggested but MESA still stucks on same point. I even had tried several values from 1d-7 to 1d-10. I don't think my error is related with mass transfer but a systematic error. Because when MESA hits the point where it stuck first time, I could be able to catch an error on terminal as follows;


       retry log10(dt/yr), log10(dt), retry_factor     1   618        1.497106        8.996218        0.500000
       retry log10(dt/yr), log10(dt), retry_factor     1   618        1.497106        8.996218        0.500000
       retry log10(dt/yr), log10(dt), retry_factor     2   618        1.196076        8.695188        0.500000
hydro_newton_step failed to accept
       retry log10(dt/yr), log10(dt), retry_factor     2   618        1.196076        8.695188        0.500000
 have reached retry limit so now backup
 have reached retry limit so now backup

I guess there is a problem while doing iterations.

Could something be faulty with my MESA system files? I use MESA version r10398. I attached the files in "src" directory. 

Gökhan 
________________________________________
Kimden: Josiah Schwab via Mesa-users [mesa-users at lists.mesastar.org] adına Mesa-users [mesa-users-bounces at lists.mesastar.org]
Gönderildi: 21 Mart 2019 Perşembe 04:11
Kime: mesa-users at lists.mesastar.org
Konu: Re: [Mesa-users] Evolution of binaries, problem

Hi Gökhan,

> I have a weird problem about evolution of the binaries. I have been
> trying to see the evolution of a resolved binary system that consists
> of two main-sequence stars. I would like to see what will happen on
> this system after mass transfer. But MESA stuck in a time and
> producing new models for that time over and over. I attached the
> "age-model number" diagram. What could cause this problem?

When the MESA timestep gets small, it is important to think a little
about what is happening physically (i.e. when is MESA getting stuck).
That helps in thinking through what might be going wrong.

In your history files (or on the terminal), you can see that the
timestep starts falling when star 1 starts to fill its Roche lobe for
the first time.  So for some reason mass transfer is having trouble
getting started.

> Also, I attached the inlist files.

Thank you for attaching everything to reproduce your problem.

That showed you were using

   mdot_scheme = "roche_lobe"

and if you search the docs about that scheme, you will see that there
are a couple of options that control how that scheme gets started.

You will find that it has an initial guess for mdot for the first
overflowing step.  By default that is 1d-12.  I know the mass transfer
rate here is going to be several orders of magnitude higher than that.
So I tried upping the guess a bit to

  starting_mdot = 1d-10

and then mass transfer started up smoothly.

Josiah
_______________________________________________
mesa-users at lists.mesastar.org
https://lists.mesastar.org/mailman/listinfo/mesa-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: run_binary_extras.f
Type: text/x-fortran
Size: 5350 bytes
Desc: run_binary_extras.f
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190321/59d23910/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: run_star_extras.f
Type: text/x-fortran
Size: 1309 bytes
Desc: run_star_extras.f
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190321/59d23910/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: binary_run.f
Type: text/x-fortran
Size: 132 bytes
Desc: binary_run.f
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190321/59d23910/attachment-0002.bin>