[mesa-users] discontinuity when restarting MESA

Jean-Claude Passy jcpassy at gmail.com
Tue Apr 7 10:09:28 EDT 2015


Hi Rich,

you were almost right. Turns out I had forgotten to specify the MLT and overshooting parameters in inlist_solar. Ugh…
I now get identical results down to the 8th digit, which is more than enough for me.

Cheers, and thanks again,

JC

On Apr 7, 2015, at 3:35 AM, Richard Townsend <townsend at astro.wisc.edu> wrote:

> That’s your problem! 
> 
> You need to modify inlist_solar to specify the same abundances as in inlist_astero_search_controls. Be careful with this — they specify abundances in different ways!
> 
> cheers,
> 
> Rich
> 
>> On Apr 6, 2015, at 8:37 PM, Jean-Claude Passy <jcpassy at gmail.com> wrote:
>> 
>> Yes, sorry Bill. I started with an astero run (inlist provided in my previous email), then restarted as a regular star run.
>> 
>> Cheers,
>> 
>> JC
>> 
>> On Apr 7, 2015, at 3:17 AM, Bill Paxton <paxton at kitp.ucsb.edu> wrote:
>> 
>>> Hi JC,
>>> 
>>> Please provide a bit more detail.  You mention using search_type = 'use_first_values', but you don't include inlist_astero_search_controls, so I don't know whether this is an astero run or a simple star run.  Which is it?   Or is it both -- starting as astero run and then restarting as simple star run?
>>> 
>>> -b
>>> 
>>> 
>>> 
>>> On Apr 6, 2015, at 6:07 PM, Jean-Claude Passy wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> I have been encountering a strange behavior when using MESA in restart mode.
>>>> I first ran the solar calibration model with a set of values and turn on search_type = ‘use_first_values’. The target is reached for model number 958, and gives the evolution represented by the blue line in the figures below (history.data file attached). 
>>>> 
>>>> Then I restart the runs at cycles 956 or 957 with the same inlist and let it evolve for one timestep only. I obtain the figures below, which show a significant increase in the two quantities I chose to plot (effective temperature and luminosity). I did that using *.mod files but I found the same behavior with the photos. 
>>>> 
>>>> I am a little bit perplexe since the combo (inlist + mod file) seems to contain all the information necessary to provide a correct restart, even the next timestep calculated by the first run. 
>>>> 
>>>> Before digging up more, I wanted to ask: has anyone already experienced this behavior and/or has an idea of what might be going on?
>>>> 
>>>> Cheers,
>>>> 
>>>> JC
>>>> 
>>>> PS: I am using Mesa r7503, OSX 10.9.5 with MESA SDK.
>>>> 
>>>> <1_history.data><inlist_solar><956.mod><957.mod><fig1.eps><fig2.eps>
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>>>> Develop your own process in accordance with the BPMN 2 standard
>>>> Learn Process modeling best practices with Bonita BPM through live exercises
>>>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>>>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
>>>> mesa-users mailing list
>>>> mesa-users at lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/mesa-users
>>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>> _______________________________________________
>> mesa-users mailing list
>> mesa-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mesa-users
> 





More information about the Mesa-users mailing list