[mesa-users] Store history.data in the end of several inlists

Kevin Moore klmoore at soe.ucsc.edu
Wed Feb 25 19:53:20 EST 2015

Hi Héctor,

You don’t need to do this through extras_finish_step(). You can just specify the name of a different history file for each inlist with the star_history_name parameter (look in mesa/star/defaults/controls.defaults for more output options). MESA defaults to writing to ‘history.data’ so if you don’t specify a different one for each inlist, they will overwrite each other.


On Feb 25, 2015, at 4:40 PM, Héctor MR <HEM52 at pitt.edu> wrote:

>   Hi all,
>   I am using several inlists for a project. How can I tell MESA in the function extras_finish_step (run_extras) to store a history. data in the end of every inlist, when I reach the termination_code? Right now, it is only saving the information corresponding to the last one, therefore I am not recording the history.data of the previous inlists.
>   Thanks!
>   --
>   Héctor
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the 
> conversation now. http://goparallel.sourceforge.net/_______________________________________________
> 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