[Mesa-users] No correction using Kjeldsen

Warrick Ball W.H.Ball at bham.ac.uk
Wed Sep 15 20:11:02 UTC 2021


Hi Erica,

I just had a look at your original attachments to this thread:

     https://lists.mesastar.org/pipermail/mesa-users/2020-September/011847.html

As far as I can see, `inlist_astero_search_controls` does have `l0_n_obs(:) = 6` at line 616, and that (I think) should be

     l0_n_obs(:) = 1, 2, 3, 4, 5, 6

assuming that your observed radial modes are a complete sequence.

If this line *is* missing from your `&astero_search_controls` inlist, try adding it.

If that still doesn't work, send me any inlists that have changed since the post above and I'll see if I can reproduce the problem.

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 Wed, 15 Sep 2021, Erica Sawczynec wrote:

> Hi Warrick,
> 	Sorry to revive such an old thread, but I am having a similar problem as we discussed earlier. I’m not sure if I ever understood the advice you gave in this email because there was no parameter named l0_n_obs in my inlist. Did you mean nl0=6 should be nl0=1,2,3,4,5,6? I am noticing now that all of the r02 output parameters are NaNs—among some other things—and was wondering if this would fix that problem?
> Thanks!
> Erica
>
>> On Sep 3, 2020, at 5:36 AM, Warrick Ball <W.H.Ball at bham.ac.uk> wrote:
>>
>> Hi Erica,
>>
>> The problem is in this line of `&inlist_astero_search_controls`:
>>
>>    l0_n_obs(:) = 6
>>
>> This needs to be a range of values: 1 to 6 works.  You can either set each element of the array `l0_n_obs` on its own line or use
>>
>>    l0_n_obs(:) = 1, 2, 3, 4, 5, 6
>>
>> In principle, I think these values are meant to be the "observed" radial orders but, in practice, they only need to be correct relative to each other.
>>
>> Arrays in Fortran namelists can be confusing because they sometimes don't work like Fortran source would.  MESA's defaults can confuse things further because they're actually included as source and compiled, unlike the actual inlists.
>>
>> 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 Wed, 2 Sep 2020, Erica Sawczynec wrote:
>>
>>> Hi all, I am having some more difficulty using the Kjeldsen surface correction. It appears there is never any correction on the frequencies even
>>> though the correction factor is set to 1. I noticed there was another mailing list submission about this that was solved by using the mean
>>> delta_nu and putting a large error bar on it (link here).  I tried this solution as well, but I didn’t have any luck with the correction turning
>>> on.  Below I’ve attached my inlist, some information about my OS, graphs of the original frequencies and the corrected frequencies outputted in
>>> the simplex_results.data file (it appears there is only one dataset because the corrected and input frequencies are the same),  and a
>>> simplex_results.data file itself.  Any hints or comments are super appreciated!
>>> Thanks,
>>> Erica
>>> I am using MESA 12115 and MESASDK 20190830.
>>> Here is some information about my os:
>>> NAME="CentOS Linux"
>>> VERSION="7 (Core)"
>>> ID="centos"
>>> ID_LIKE="rhel fedora"
>>> VERSION_ID="7"
>>> PRETTY_NAME="CentOS Linux 7 (Core)”
>
>


More information about the Mesa-users mailing list