Re: [mesa-users] A question about the pulsation package

[RICHARD H D T. <tow...@as...>]

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.

cheers,

Rich

> On Feb 23, 2017, at 4:04 AM, yan...@xa... 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
> mes...@li...
> https://lists.sourceforge.net/lists/listinfo/mesa-users