[mesa-users] Termination codes
Hannah Brinkman
brinkmanhe at gmail.com
Fri Sep 30 10:56:05 EDT 2016
My apologies if you receive this twice, but something went probably wrong
with the attachment. Here's a second try. Also, I realized it was the wrong
inlist_project file.
Thanks for your reply.
I've attached the inlist files for one of the binary systems that gives me
this error, maybe that helps.
Also, I am aware of the ways you can give the code your own termination
condition, my question was about the termination codes that come from MESA
itself. Is there a list of those?
With kind regards,
Hannah
2016-09-30 16:28 GMT+02:00 Choi, Jieun <jieun.choi at cfa.harvard.edu>:
> Hi Hannah,
>
> http://mesa.sourceforge.net/controls_defaults.html#when_to_stop lists the
> different options for terminating your run. You can, of course, set your
> own stopping criterion using run_star_extras.f.
>
> However, the case you've brought up --- STOP debug1: do_kap_for_cell ---
> is not like the other termination codes, such as the maximum number of
> models or max age reached, because this appears to be an actual problem.
>
> If I grep 'debug1' in mesa/star/private, I can see that the statement is
> being printed from opacities.f90.
>
> In the subroutine do_kap_for_cell, I see
>
> if (is_bad_num(s% opacity(k))) then
> !$omp critical (star_kap_get)
> call show_stuff
> stop 'debug1: do_kap_for_cell'
> !$omp end critical (star_kap_get)
> end if
>
> So the opacity in one or more of your cells is likely a NaN. Without more
> information on the models you're running, it's hard for me to tell what's
> going on. Maybe others will have better insights!
>
> There are so many of these STOP debug statements that it's hard to list
> them all. Try grepping 'stop' in star/private to see just how many there
> are!
>
> Cheers,
> Jieun
>
> On Fri, Sep 30, 2016 at 8:06 AM, Hannah Brinkman <brinkmanhe at gmail.com>
> wrote:
>
>> Dear all,
>>
>> for my master thesis, I am working with MESA to evolve binary systems.
>> Mostly, my simulations are ended because the maximum amount of models I've
>> allowed is reached, but sometimes I get another termination code. Is there
>> a list of these termination codes which explains what they mean?
>> Especially the following termination code confuses me:
>> STOP debug1: do_kap_for_cell
>> I hope someone can explain this to me.
>>
>> With kind regards,
>> Hannah
>>
>> ------------------------------------------------------------
>> ------------------
>>
>> _______________________________________________
>> mesa-users mailing list
>> mesa-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mesa-users
>>
>>
> On Fri, Sep 30, 2016 at 8:06 AM, Hannah Brinkman <brinkmanhe at gmail.com>
> wrote:
>
>> Dear all,
>>
>> for my master thesis, I am working with MESA to evolve binary systems.
>> Mostly, my simulations are ended because the maximum amount of models I've
>> allowed is reached, but sometimes I get another termination code. Is there
>> a list of these termination codes which explains what they mean?
>> Especially the following termination code confuses me:
>> STOP debug1: do_kap_for_cell
>> I hope someone can explain this to me.
>>
>> With kind regards,
>> Hannah
>>
>> ------------------------------------------------------------
>> ------------------
>>
>> _______________________________________________
>> mesa-users mailing list
>> mesa-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mesa-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160930/20dc4666/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inlist
Type: application/octet-stream
Size: 458 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160930/20dc4666/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inlist1_spec
Type: application/octet-stream
Size: 4870 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160930/20dc4666/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inlist2_spec
Type: application/octet-stream
Size: 5195 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160930/20dc4666/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inlist_project
Type: application/octet-stream
Size: 436 bytes
Desc: not available
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20160930/20dc4666/attachment-0003.obj>
More information about the Mesa-users
mailing list