[Mesa-users] history and profiles from more than one inlist

[Warrick Ball]

Hi,

You mentioned that you're working off the `20M_core_collapse` example, in 
which case you're possibly still using `inlist_massive_defaults` as well 
as your inlist.  If you have a look at that file (in `$MESA_DIR/star`), 
you'll see `&star_job` has the lines

     set_initial_age = .true.
     initial_age = 0 ! in years

     set_initial_model_number = .true.
     initial_model_number = 0

If you remove those (or change `.true.` to `.false.`), it should stop 
resetting the age and model number.

Cheers,
Warrick

------------
Warrick Ball
Postdoc, School of Physics and Astronomy
University of Birmingham, Edgbaston, Birmingham B15 2TT
W.H.Ball at bham.ac.uk
+44 (0)121 414 4552


On Tue, 7 Aug 2018, aldanag at campus.technion.ac.il wrote:

> 
> Yet there is still one problem- the age of the star still resets itself to 0 at the beginning of each history file. I can fix it in the analysis (by MATLAB) yet I wonder if there is a way telling MESA to
> start the second inlist from the point in time where the first inlist ended without setting the initial age to 0 after each inlist.
> 
> _______________________________________________________________________________________________________________________________________________________________________________________________________________
> From: Aldana Grichener
> Sent: Tuesday, August 7, 2018 7:03:36 PM
> To: Aaron Dotter; W.H.Ball at bham.ac.uk
> Cc: mesa-users
> Subject: Re: [Mesa-users] history and profiles from more than one inlist \A0
> 
> Thank you very much for both solutions, I tried them both and they worked perfectly.
> 
> 
> Aldana.
> 
> _______________________________________________________________________________________________________________________________________________________________________________________________________________
> From: Aaron Dotter <aaron.dotter at gmail.com>
> Sent: Tuesday, August 7, 2018 6:37:16 PM
> To: W.H.Ball at bham.ac.uk
> Cc: Aldana Grichener; mesa-users
> Subject: Re: [Mesa-users] history and profiles from more than one inlist \A0
> Hi Aldana,
> Another simple solution is to specify the name of the history file in each inlist (controls section), e.g.,\A0
> 
> star_history_name = 'history_h_burn.data'
> 
> in inlist_h_burn and similarly for the other inlists.\A0 Then, when you're done, you'll have three files corresponding to the three inlists.
> 
> You can do the same with profiles through
> 
> \A0 \A0 \A0 profiles_index_name = 'profiles_h_burn.index'
> 
> and\A0
> 
> \A0 \A0 \A0profile_data_prefix = 'profile_h_burn'
> 
> separately for each inlist.\A0
> 
> Aaron
> 
> 
> On Tue, Aug 7, 2018 at 11:32 AM Warrick Ball via Mesa-users <mesa-users at lists.mesastar.org> wrote:
>       Hi Aldana,
>
>       Can you not just move the files to a new folder between runs? e.g. after
>       running `inlist_h_burn`,
>
>       \A0 \A0 \A0mv LOGS/ LOGS_h_burn/
>
>       You can remake the LOGS directory if you want (`mkdir LOGS`) but this
>       isn't necessary: MESA remakes the directory on its own.
>
>       Cheers,
>       Warrick
>
>       ------------
>       Warrick Ball
>       Postdoc, School of Physics and Astronomy
>       University of Birmingham, Edgbaston, Birmingham B15 2TT
>       W.H.Ball at bham.ac.uk
>       +44 (0)121 414 4552
> 
>
>       On Tue, 7 Aug 2018, mesa-users at lists.mesastar.org wrote:
>
>       >
>       > Hello,
>       >
>       >
>       > I am using mesa-r9575 for evolving a massive star. I am working on a copy of the test-suite 20M_core_collapse, yet since I need to change some of the initial conditions I am creating the model
>       form the ZAMS
>       > phase running all the 3\A0inlists attached here via the header files.
>       >
>       > \A0
>       >
>       > My problem is that I need the profiles and history from the entire run, yet both profiles and history are reseted after MESA enters to each inlist, meaning that at the end of the run I can see
>       only the
>       > history and profiles from the point in time for which MESA entered the third inlist (inlist to_cc). I made sure during the run that MESA actually runs all 3 inlists.
>       >
>       >
>       > Does anyone know a way to save the data from the entire run?
>       >
>       >
>       > Thanks in advance.
>       >
>       >
>       > Aldana.
>       >
>       >
>       >
>       _______________________________________________
>       mesa-users at lists.mesastar.org
>       https://lists.mesastar.org/mailman/listinfo/mesa-users
> 
> 
>