[mesa-users] Writing GYRE output in extras_check_model

Robert Farmer rjfarmer at asu.edu
Mon Sep 19 14:13:06 EDT 2016


Hi
You might want to look at Alfred Gautchy's recent summer school material:
http://mesastar.org/teaching-materials/2016-mesa-summer-school/gautschy

Which dealt with calling gyre from mesa in a run_star_extras routine (in
this case during extras_finish_step)

Rob

On Mon, Sep 19, 2016 at 8:47 AM, Josiah Schwab <jwschwab at berkeley.edu>
wrote:

> Hi Earl,
>
> > I have a suite of routines that I use to post-process MESA and
> > GYRE/ADIPLS outputs. I am running into a problem where I am sometimes
> > getting pretty bizarre frequencies (e.g. all mixed modes on the main
> > sequence of a low-mass star; non-smooth frequency separations; etc). I
> > want to write an extras_check_model that checks for this condition and
> > backs up if it is encountered. The problem is, GYRE outputs are only
> > written after this point. So I am wondering: how can I write the GYRE
> > output during the extras_check_model step so that I can process it
> > with my external routines and determine whether or not I should
> > backup?
> >
> > Or maybe I am going about this problem all wrong. Advice appreciated.
>
> I haven't thought this through carefully or tried anything, but how
> about either calling GYRE yourself (i.e., call do_gyre_get_modes) in
> extras_check_model or if you need to write the file, look in
> star/public/star_lib.f90 and see if calling one of those routines (i.e.,
> star_write_gyre_data_to_file) in extra_check_model will get you what you
> need.
>
> Hope that helps,
> Josiah
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> 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/20160919/17848206/attachment.html>


More information about the Mesa-users mailing list