[Mesa-users] How to stop calculating the primary evolution details?

Tue May 12 06:48:53 EDT 2020

Hi Jelena,

you will only get a saved model if the code has a normal (as in, not solely
numerical) terminating condition. In this case you might want to evaluate
if the point where your simulation terminates is really meaningful to set
one star as a point mass. If it is, you can use the option
save_model_number in star job so that a model is saved before reaching this
termination point. However I would strongly advise you to setup a physical
terminating condition, you say that the model has finished burning, do you
mean it depleted central silicon or something like that? You should be able
to identify that stage automatically rather than having the code crash
instead.

On Tue, May 12, 2020 at 12:29 PM Jelena Petrović <jpetrovic at aob.rs> wrote:

> Hallo,
>
> The code stops because of too small timestep, since the primary finished
> all burning (please see below).
> There is no message that final model is saved.
>
> -------------------------------------------------------
> stopping because of problems dt < min_timestep_limit
>
> bin 5720474  49.066861  66.750227   9.022041  0.000E+00   2.104411
>     0          1 -6.505E-02   0.100000  3.708E+54 -2.215E+47 -1.387E+37
>   -13.449934  15.805531  21.139507   0.000000  0.000E+00 253.841225
> 21.139524 -8.069E-07 -2.163E+02  1.000E+99  0.000E+00 -1.270E+35
> 0.000E+00
>   9.2263E-02  33.261330   9.637786   0.000000 -1.494E+49 120.623422
> 29.672872 -6.752E-01  2.163E+01  0.000E+00  0.000E+00 -2.215E+47
>   0
>
>
> terminated evolution: cannot find acceptable model
>
> termination code: min_timestep_limit
>
> terminated evolution: cannot find acceptable model
>
> termination code: min_timestep_limit
> DATE: 2020-05-02
> TIME: 21:56:31ing because of problems dt < min_timestep_limit
>
> bin 5720474  49.066861  66.750227   9.022041  0.000E+00   2.104411
>     0          1 -6.505E-02   0.100000  3.708E+54 -2.215E+47 -1.387E+37
>   -13.449934  15.805531  21.139507   0.000000  0.000E+00 253.841225
> 21.139524 -8.069E-07 -2.163E+02  1.000E+99  0.000E+00 -1.270E+35
> 0.000E+00
>   9.2263E-02  33.261330   9.637786   0.000000 -1.494E+49 120.623422
> 29.672872 -6.752E-01  2.163E+01  0.000E+00  0.000E+00 -2.215E+47
>   0
>
>
> terminated evolution: cannot find acceptable model
>
> termination code: min_timestep_limit
>
> terminated evolution: cannot find acceptable model
>
> termination code: min_timestep_limit
> DATE: 2020-05-02
> TIME: 21:56:31
> -------------------------------------------------------
>
> Jelena
>
> On 12.05.2020 12:02, Rob Farmer wrote:
> > Please keep replies on the mailing list.
> >
> > That should be sufficient as long as the run terminates normally. How
> > are you stopping your run? Are you using an option in
> > http://mesa.sourceforge.net/controls_defaults.html#when_to_stop? or
> > modifying your run_star_extras/run_binary_extras to stop the run? or
> > ctrl-c the run? or does the model crash?
> >
> > The terminal output at the end of the run should include a line with
> > your chosen save_model_filename to show that it has saved a file. Does
> > the output state it has?
> >
> > Rob
> >
> > On Tue, 12 May 2020 at 11:43, Jelena Petrović <jpetrovic at aob.rs>
> > wrote:
> >
> >> Hallo Rob,
> >>
> >> I apologize for a basic question about saving models, but I have in
> >> inlist 2 this:
> >>
> >> save_model_when_terminate = .true.
> >> save_model_filename = '56+33-sec.mod'
> >>
> >> but I am not managing to find the saved model file after the run is
> >> finished..
> >> Do I need to add something more in inlist files?
> >>
> >> Many thanks,
> >> Jelena
> >>
> >> On 11.05.2020 14:18, Rob Farmer wrote:
> >>> Hi,
> >>>
> >>> A simple option would be to have the secondary write out a mod
> >> file at
> >>> the point where you stop.Then that mod file can then be loaded in
> >> a
> >>> single star run (copying over the inlists used for the secondary)
> >> or
> >>> if you still want the point particle secondary then have the
> >> inlist1
> >>> load that mod file (and set the secondary inlist appropriately).
> >> Thus
> >>> do what you tried but instead of using a photo use a saved mod
> >> file.
> >>>
> >>> Rob
> >>>
> >>> On Thu, 7 May 2020 at 22:18, Jelena Petrović <jpetrovic at aob.rs>
> >>> wrote:
> >>>
> >>>> Dear all,
> >>>>
> >>>> I have calculated evolution of a massive binary to the point that
> >>>> the
> >>>> primary finished carbon core burning and the secondary is still a
> >>>> main
> >>>> sequence star.
> >>>> I need to now stop calculating the primary evolution details and
> >>>> treat
> >>>> it further as a point star, but I am not managing to set this
> >>>> properly.
> >>>>
> >>>> If I try 'evolve both stars = .false', the evolution of the
> >>>> secondary is
> >>>> not calculated. If I swap inlist1 and inlist2 definitions in
> >>>> inlist_project, the code crashes immediately
> >>>> after I restart with ./re <x...>
> >>>>
> >>>> Is there a way to stop calculating the primary evolution details
> >> and
> >>>>
> >>>> follow further only the secondary evolution?
> >>>>
> >>>> Many thanks,
> >>>> Jelena
> >>>>
> >>>> -------------------------------
> >>>> Dr. Jelena Petrovic
> >>>> Associate Research Professor
> >>>> Astronomical Observatory
> >>>> Belgrade, Serbia
> >>>> -------------------------------
> >>>> _______________________________________________
> >>>> mesa-users at lists.mesastar.org
> >>>>
> >>>
> >>
> >
> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mesastar.org%2Fmailman%2Flistinfo%2Fmesa-users&data=02%7C01%7Cr.j.farmer%40uva.nl%7C19ae4579b79140b289d308d7f6599e4d%7Ca0f1cacd618c4403b94576fb3d6874e5%7C1%7C0%7C637248737091634429&sdata=%2F2R%2Fqnbk78RyVGHEuhaL2zJAdKJqh9CuMe51BkqheGM%3D&reserved=0
> _______________________________________________
> 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/20200512/db659472/attachment.htm>