[Mesa-users] the certain mass range to use inlist_massive_defaults

[Warrick Ball]

Hi Ann,

I'm not sure I understand your question.  `inlist_massive_defaults` is 
only included when the user explicitly requests it.  For a survey of where 
it's used in the test suite (r10398), I opened a terminal and ran

$ cd $MESA_DIR/star/test_suite/
$ grep inlist_massive_defaults */inlist | awk --field-separator ':' '{print $1}' | uniq
20M_si_burn_qp_bcyclic/inlist
25M_z2m2_high_rotation/inlist
30M_big_net/inlist
30M_core_collapse_big_net/inlist
30M_logT_9.8_big_net/inlist
adjust_net/inlist
envelope_inflation/inlist
make_low_mass_with_uniform_composition/inlist

I went one step further and had a look at the `initial_mass` parameters in 
these runs.

$ grep inlist_massive_defaults */inlist | awk --field-separator ':' '{print $1}' | uniq | xargs -I{} sh -c "grep initial_mass {}*"
20M_si_burn_qp_bcyclic/inlist_si_burn_qp:      initial_mass = 20
25M_z2m2_high_rotation/inlist_25M_z2m2_high_rotation:         initial_mass = 25
30M_big_net/inlist_30M_big_net:      initial_mass = 30
30M_core_collapse_big_net/inlist_30M_big_net_core_collapse:      initial_mass = 30
30M_logT_9.8_big_net/inlist_30M_logT_9.8_big_net:      initial_mass = 30
adjust_net/inlist_adjust_net:      initial_mass = 15
envelope_inflation/inlist_envelope_inflation:      initial_mass = 30 ! in Msun units
make_low_mass_with_uniform_composition/inlist_low_uniform:! set "initial_mass" to the desired mass
make_low_mass_with_uniform_composition/inlist_low_uniform:         initial_mass = 6

This is just a quick survey.  It'd be better to go through interesting 
cases in detail so see if some controls from `inlist_massive_defaults` are 
being overridden.

I don't usually evolve massive stars myself, but I'd say if you're having 
a problem with a massive star that you think might be solved by using 
`inlist_massive_defaults`, rather isolate the control that fixes the 
problem for you, and be sure to understand *why* it fixes the problem. 
Put differently, don't use `inlist_massive_defaults` in a given mass range 
just because the test suite does.

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 Thu, 9 Aug 2018, d10631026 at gapps.fg.tp.edu.tw wrote:

> To Whom It May Concern:
> 
> Hello,
> 
> I wonder that what's the certain mass range to include inlist_massive_defaults in the module.
> 
> 
> Thanks in advance,
> 
> Ann
> 
> 
>