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

[Richard T. <tow...@as...>]

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