[mesa-users] A question about the pulsation package

yangtaozhi at xao.ac.cn yangtaozhi at xao.ac.cn
Tue Feb 28 00:14:55 EST 2017

Hi Rich,

Thanks for your help. As your suggestions, I set the first_*, min_* and max_* parameters in the file gyre.in and the range of frequencies shown on screen is indeed in the search bounds.
However, I also add the follow parameters:
search_type = ‘simplex'
vary_FeH = .true.
vary_Y = .true.
vary_mass = .true.
 in the file inlist_astero_search_controls, It seems remain unchanged as before, it still just match the finnal model's frequency,
I really don't konw how to do with it. Can you give me any help?


Date: 2017-02-24 23:25
To: yangtaozhi at xao.ac.cn
CC: mesa-users
Subject: Re: [mesa-users] A question about the pulsation package
Hi Taozhi —
The way the pulsation_gyre is currently set up, it doesn’t perform any optimization on the mass, metallicity etc — it just assumes that these parameters are sufficient to get a good match (at some point during the star’s evolution) to the frequencies specified in the inlist_astero_search_controls file. If you alter these frequencies (but don’t otherwise modify the inlist), then it’s unsurprising that you’re not able to get a good match.
To fix this, you need to set some parameters in inlist_astero_search_controls. To allow mass and abundances to vary:
search_type = ‘simplex'
vary_FeH = .true.
vary_Y = .true.
vary_mass = .true.
Also, look at the first_*, min_* and max_* parameters to set the search bounds.
> On Feb 23, 2017, at 4:04 AM, yangtaozhi at xao.ac.cn wrote:
> Hi everyone,
> I want to use the package 'pulsation_gyre' to calculate the frequency of every model, and match a certain frequency, but when I have a try, I find that it always match the final model's frequency when it terminate, for example, in the package /star/test_suit/pulse_gyre, firstly, I have a try to the initial test, it is OK and it can match the frequency (n=0, l=4, frequency=378d0) which is set in the file /src/run_star_extras.f, and it terminate. when I change the frequency to another value (it maybe the previous model's frequency), it will show the bad match for the expected frequency.
> I don't know why is it?  Can anyone give me some help, How can I set the parameter?
> Thanks in advance.
> Taozhi
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot_______________________________________________
> mesa-users mailing list
> mesa-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mesa-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20170228/36db7eb3/attachment.html>

More information about the Mesa-users mailing list