[mesa-users] Reconstructing tracks for asterg-module fits

Richard Townsend townsend at astro.wisc.edu
Sun Jan 25 10:56:22 EST 2015

Aha — I’ve tweaked some parameters recently (esp. the metallicity), and it may be that target (Teff,L) no longer lies inside the main-sequence band. That would explain the mismatch.

I’m checking on this now, and will report back.



> On Jan 25, 2015, at 9:14 AM, Richard Townsend <townsend at astro.wisc.edu> wrote:
> Dear MESAnauts —
> I’m currently using the astero module to calculate stellar models with a certain Teff and luminosity. Although these quantities aren’t the usual free parameters we get to choose when calculating a stellar evolution track, the astero module (with the seismic frequency matching turned off) allows one to find the initial mass, age, etc which will produce an evolutionary track shooting right through the desired (Teff,L). It’s a really useful piece of functionality.
> However, I’ve run into an issue: if I take the initial mass found by the astero module, and then do an ordinary run (i.e., non-astero) using this value, then the resulting evolutionary track does *not* go through the desired point.
> My suspicion is that the calculations inside/outside astero are being run with different parameters; but I’m not able to track down what the issue is. I attach the relevant inlists — can anyone see what might be going wrong?
> One possibility: although step-based overshooting is turned on in the main inlist (inlist_project_…), it is turned off in inlist_astero_search_controls. However, from my reading of the source code, the astero module only changes the overshoot length for standard (rather than step) overshooting — so this should matter, right?
> Many thanks for any assistance,
> cheers,
> Rich
> <inlist_astero_search_controls><inlist_project_inside_astero><inlist_project_outside_astero>------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet_______________________________________________
> 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