The GYRE Forums

Hi Rich et al., Quick question: is it possible to hand GYRE, or build within GYRE, initial conditions that have a non-monotonic rotation profile (e.g. a measured surface rotation rate than exceeds an internal subsurface rotation rate)? My assumption is no (and how would one produce that in MESA, an...

I would advise against modifying any code -- post-processing is the right way to go.

cheers,

Rich

Hi Rich, I returned to this problem because I find this behaviour in other calculations. Again I found Deltag values quite lower than expected. So I write the N on the MESA file and proceed to compute "by hand" the intergral to obtain the value of the asimptotic period spacing with the Tassoul form...

OK, thanks for checking that out!

But I still think this behavior is physical -- see, e.g., Miglio et al. (2008, MNRAS, 386, 1487), especially their Fig. 4.

cheers,

Rich

Hi Francisco -- At first, I thought there may be an issue with your input file -- but that looks fine. On further consideration, I think the result you are finding for the period spaceings looks correct. Your model star shows a period spacing with regular dips -- this is the symptom of mixed modes, ...

Hi Francisco --

Welcome to the forum! As a first suggestion, can you post the namelist input file you use for GYRE?

cheers,

Rich

yup that worked, thanks! I do note that eta is listed as a valid output option at https://gyre.readthedocs.io/en/stable/ref-guide/output-files/summary-files.html#only-n without warning that this is a nad parameter only, but perhaps a more informed user/real asteroseismologist would recognize that t...

Thanks. It appears the crash arises from requesting 'eta' as one of the adiabatic summary-file items -- for adiabatic calculations, this quantity (the Stellingwerf normalized growth rate) is undefined. So, as a workaround, remove 'eta' from the summary_item_list in &ad_output. I'll also be working o...

Hi Meridith --

The input file you sent me still has a number of template fields -- e.g., <<freq_min>>. Can you send an example with these filled in (pref. the crashing example).

cheers,

Rich

Hi Warrick --

This is in fact a design choice; although GYRE currently only works with a single stellar model at a time, the output code can support multiple models. Hence, I decided it made more sense to have {M,R,L} be arrays.

cheers,

Rich