[mesa-users] Pulse test-suite g-mode order failure

Момчил Молнар momchil.molnar at gmail.com
Fri Jul 19 06:49:49 EDT 2013


I am using a 0.8 solar mass ZAMS model with 0.8 initial X, initial z=0.02.

Best,
Momchil

Sent from my iPad

On 19.07.2013, at 09:18, Dennis Stello <stello at physics.usyd.edu.au> wrote:

> Hi Momchil,
> 
> What kind of star are you trying to model?
> 
> Cheers
> Dennis/
> 
> -- 
> DENNIS STELLO | Senior Lecturer
> School of Physics A28 | Faculty of Science
> 
> THE UNIVERSITY OF SYDNEY
> Rm225, K90 | The University of Sydney | NSW | 2006
> T +61 2 9036 5108  | F +61 2 9351 7726
> E stello at physics.usyd.edu.au  | W http://www.physics.usyd.edu.au/~stello/
> 
> 
> On Thu, 18 Jul 2013, Momchil Molnar wrote:
> 
>> Hi,
>> 
>> I am a newbie in the MESA users community and I have the following problem,
>> while using the pulse test_suite  scenario:
>> 
>> When looking for g-modes with periods around 3-4 days (i.e. 2-3 microHz),
>> the output gives me back modes with really awkward order numeration - the
>> modes don't have the right numeration at all.
>> 
>> How should I configure the nu1, nu2 and the iscan parameters in
>> run_star_extras.f?
>> 
>> Now I am using:
>> 
>>        nu1 = 0.2
>>        nu2 = 0.4
>>        iscan = 200
>>        l = 2
>> 
>> 
>> I attach and piece from the output:
>>    2     -34        0.2114468337    0.6345298399E-03
>>      2      90        0.2126794888    0.5346764147E+28
>>      2      91        0.2149748764    0.5108900070E+18
>>      2     -33        0.2172143771    0.4735642070E-03
>>      2      92        0.2172774254    0.5830447338E+18
>>      2      93        0.2195892113    0.5765449514E+18
>>      2      94        0.2218860481    0.5476002471E+18
>>      2     -32        0.2232938498    0.4387064286E-03
>>      2      95        0.2241797933    0.4532089974E+18
>>      2      96        0.2264905432    0.3492776321E+18
>>      2      97        0.2287961221    0.4320581225E+18
>>      2     -33        0.2297057383    0.3317271872E-03
>>      2      98        0.2311085274    0.4760731828E+18
>>      2      99        0.2334318768    0.4197194630E+18
>>      2     100        0.2357646475    0.4446131381E+18
>>      2     -30        0.2364670542    0.2825893379E-03
>>      2     -32        0.2435970690    0.2305376775E-03
>>      2     -33        0.2511157027    0.1942925337E-03
>>      2     -33        0.2590444899    0.1363465687E-03
>>      2     -31        0.2674127522    0.1224663362E-03
>>      2     -31        0.2762559873    0.1013855347E-03
>> 
>> I hope, somebody has resolved this problem before :)
>> 
>> Looking forward to hearing your suggestions,
>> Momchil Molnar
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> mesa-users mailing list
> mesa-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mesa-users




More information about the Mesa-users mailing list