[Mesa-users] MESA error: STOP bad glist for get_glist_results

Tue May 28 16:43:53 EDT 2019

Hi Rob,

Thank you so much for your attitude to support (and for your patience!).
Now I understand your previous email, asking when it was crashing (not how
long it should be "if working"). The model crashes at the very beginning,
so it might well be within the first 5 steps as you mentioned.

As for the colors, I use add_bc and add_abs_mag. Attached also the rest of
files (I could have done it before, I was just not expecting a full
reproduction).

Again, so many thanks.

Cheers,
Iñigo

El mar., 28 may. 2019 a las 22:14, Rob Farmer (<r.j.farmer at uva.nl>)
escribió:

> hi,
> How are you adding the colors to your history columns file?
>
> Naming them individually or using add_bc or add_abs_mag or add all of them?
>
> I can debug the issue further if you provide everything needed to
> reproduce the problem, so your run_star_extras (as you use other_neu) ,
> history_columns.list. And it would make my life easier if you could provide
> a model from a few steps before the crash happens so i don't have to run
> several 1000 steps to find it.
>
> Rob
>
> On Tue, 28 May 2019 at 12:06, Iñigo Muñoz Elorza <imunozelorza at gmail.com>
> wrote:
>
>> Hi again,
>>
>> >How many steps would it work for? the default history_interval output is
>> every 5 steps, so if it only lasted 5 steps then the problem would be just
>> when we are doing the history output.
>>
>> Not sure if I'm interpreting something wrong here, but the model will run
>> for several 1000s steps (the same did the other models I was referring to
>> with the "vmag_tables_Adrian.dat" file).
>>
>> Cheers,
>> Iñigo
>>
>> El mar., 28 may. 2019 a las 20:25, Rob Farmer (<r.j.farmer at uva.nl>)
>> escribió:
>>
>>> Hi
>>> >But interestingly enough I could run several models with the
>>> vmag_tables_Adrian colors and the same version in the past. Why is it
>>> giving problems only now?
>>>
>>> How many steps would it work for? the default history_interval output is
>>> every 5 steps, so if it only lasted 5 steps then the problem would be just
>>> when we are doing the history output.
>>>
>>> Rob
>>>
>>>
>>> On Tue, 28 May 2019 at 10:57, Iñigo Muñoz Elorza <imunozelorza at gmail.com>
>>> wrote:
>>>
>>>> Hi Aaron, Rob
>>>>
>>>> Thanks for the quick answers. With Aaron's suggestion I found in the
>>>> star file that there was a problem with the colors module (thanks for the
>>>> confirmation Rob!), so now I'm running a model for 0.60 Msun but with the
>>>> default colors (removed the input to use the vmag_tables_Adrian.dat file,
>>>> which I attach).
>>>>
>>>> I also forgot to mention the MESA version, sorry, it's *r10398*. But
>>>> interestingly enough I could run several models with the vmag_tables_Adrian
>>>> colors and the same version in the past. Why is it giving problems only now?
>>>>
>>>> Many thanks!
>>>> Iñigo
>>>>
>>>>
>>>> El mar., 28 may. 2019 a las 19:43, Rob Farmer (<r.j.farmer at uva.nl>)
>>>> escribió:
>>>>
>>>>> hi
>>>>> >"STOP bad glist for get_glist_results"
>>>>>
>>>>> Is a problem in the colors module that you shouldn't hit. Can you send
>>>>> your "vmag_tables_Adrian.dat" file as well as your history_columns.list
>>>>> file. Also what version of mesa are you using?
>>>>>
>>>>> Thanks
>>>>> Rob
>>>>>
>>>>> On Tue, 28 May 2019 at 10:35, Aaron Dotter via Mesa-users <
>>>>> mesa-users at lists.mesastar.org> wrote:
>>>>>
>>>>>> Hi Iñigo,
>>>>>>
>>>>>> Try this:
>>>>>>
>>>>>> grep glist mesa/*/*/*
>>>>>>
>>>>>> Be patient and you'll see where the problem is.  From there, I bet
>>>>>> you can figure out what is the problem.
>>>>>>
>>>>>> Cheers,
>>>>>> Aaron
>>>>>>
>>>>>> On Tue, May 28, 2019 at 1:29 PM Iñigo Muñoz Elorza via Mesa-users <
>>>>>> mesa-users at lists.mesastar.org> wrote:
>>>>>>
>>>>>>> Hi MESA community,
>>>>>>>
>>>>>>> I want to calculate an interval of isochrones (and from there the
>>>>>>> luminosity functions) between 10 and 14 Gys for stars of low mass up to the
>>>>>>> RGB tip.
>>>>>>>
>>>>>>> For that I'm trying to compute model from 0.60 to 0.78 Msun with a
>>>>>>> 0.2 increment, but I'm encountering convergence problems for the lower
>>>>>>> masses 0.60-0.66 (didn't try the higher mass yet) because either I reach a
>>>>>>> too small time step (*"stopping because of problems dt <
>>>>>>> min_timestep_limit")* or mainly because after several attempts to
>>>>>>> converge reducing the log10(dt/yr) and log10(dt) it stops with the
>>>>>>> following message:
>>>>>>>
>>>>>>> *"STOP bad glist for get_glist_results"*
>>>>>>>
>>>>>>> Any ideas of 1) what is the possible cause and 2) how to overcome
>>>>>>> it? Any comment or hint would be really appreciated since I didn't find
>>>>>>> references to the *get_glist_results.*
>>>>>>>
>>>>>>> Attached the inlist with the star_job and controls inputs (for a
>>>>>>> 0.60 Msun star).
>>>>>>>
>>>>>>> Many thanks in advance for your help!
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Iñigo
>>>>>>> _______________________________________________
>>>>>>> mesa-users at lists.mesastar.org
>>>>>>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>>>>>>
>>>>>>> _______________________________________________
>>>>>> mesa-users at lists.mesastar.org
>>>>>> https://lists.mesastar.org/mailman/listinfo/mesa-users
>>>>>>
>>>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190528/92280fc9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: run_star_extras.f
Type: application/octet-stream
Size: 13643 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190528/92280fc9/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: history_columns.list
Type: application/octet-stream
Size: 37979 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20190528/92280fc9/attachment-0003.obj>