Page 1 of 2

Issue with the given example

Posted: Fri Oct 21, 2016 1:44 am
by richakundu
hello
i am new to GYRE. I was just trying to work with the examples given on the bitbucket website. 1st example worked perfectly fine. In the subsequent examples i started getting problem. I am getting problem in the following part:

ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

The error shown on the screen is :

Fortran runtime error: Cannot match namelist object name ivp_solver_type

I was getting the same error in "outer_bound_type = 'ZERO' " as well but i just changed "outer_bound_type" to "outer_bound" and the error was gone. I tried the same thing with "ivp_solver_type" but still it was showing the same error.

PS: I am using GYRE 5.0
please help
Richa Kundu

Re: Issue with the given example

Posted: Fri Oct 21, 2016 6:31 am
by rhtownsend
richakundu wrote:hello
i am new to GYRE. I was just trying to work with the examples given on the bitbucket website. 1st example worked perfectly fine. In the subsequent examples i started getting problem. I am getting problem in the following part:

ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

The error shown on the screen is :

Fortran runtime error: Cannot match namelist object name ivp_solver_type

I was getting the same error in "outer_bound_type = 'ZERO' " as well but i just changed "outer_bound_type" to "outer_bound" and the error was gone. I tried the same thing with "ivp_solver_type" but still it was showing the same error.

PS: I am using GYRE 5.0
please help
Richa Kundu
Hi Richa --

Welcome to GYRE! It seems you've run into a known problem with the documentation -- I haven't finished updating it from v4.4 to 5.0. Can you let me know which specific examples have this problem, so I can add them to the list of docs needing updating?

For the moment, to work around your specific problem, use 'diff_scheme' instead of 'ivp_solver_type'.

Best wishes,

Rich

Re: Issue with the given example

Posted: Fri Oct 21, 2016 7:14 am
by richakundu
rhtownsend wrote:
richakundu wrote:hello
i am new to GYRE. I was just trying to work with the examples given on the bitbucket website. 1st example worked perfectly fine. In the subsequent examples i started getting problem. I am getting problem in the following part:

ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

The error shown on the screen is :

Fortran runtime error: Cannot match namelist object name ivp_solver_type

I was getting the same error in "outer_bound_type = 'ZERO' " as well but i just changed "outer_bound_type" to "outer_bound" and the error was gone. I tried the same thing with "ivp_solver_type" but still it was showing the same error.

PS: I am using GYRE 5.0
please help
Richa Kundu
Hi Richa --

Welcome to GYRE! It seems you've run into a known problem with the documentation -- I haven't finished updating it from v4.4 to 5.0. Can you let me know which specific examples have this problem, so I can add them to the list of docs needing updating?

For the moment, to work around your specific problem, use 'diff_scheme' instead of 'ivp_solver_type'.

Best wishes,

Rich

yeah sure
i used diff_scheme then i got the following error:
OpenMP Threads : 4
Input filename : gyre.in
ASSERT 'n_ot_p == 1' failed at line 110 <gyre_out_par:read_out_par>:
Input file should contain exactly one &ad_output and one &nad_output namelist

do i need to change something else as well?
I am sorry for the basic ques but I am just beginning to work with GYRE.

I had same issue in 2 codes. One is :

&model
model_type = 'EVOL' ! Use an evolutionary stellar model
file = 'rgb.mesa' ! File name of the evolutionary model
file_format = 'MESA' ! File format of the evolutionary model
/

&constants
/

&mode
l = 1 ! Harmonic degree
/

&osc
outer_bound_type = 'ZERO' ! Use a zero-pressure outer mechanical boundary condition
/

&num
ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

&scan
grid_type = 'INVERSE' ! Scan for modes using a uniform-in-period grid; best for g modes
freq_units = 'UHZ' ! Interpret freq_min and freq_max as having units of microHertz
freq_min = 39 ! Minimum frequency to scan from
freq_max = 42 ! Maximum frequency to scan to
n_freq = 200 ! Number of frequency points in scan
/

&shoot_grid
op_type = 'CREATE_CLONE' ! Clone the model grid
/

&recon_grid
op_type = 'CREATE_CLONE' ! Clone the shooting grid
/

&output
summary_file = 'summary.txt' ! File name for summary file
summary_file_format = 'TXT' ! Format of summary file
summary_item_list = 'M_star,R_star,l,n_pg,omega,E_norm' ! Items to appear in summary file
mode_prefix = 'mode-' ! File-name prefix for mode files
mode_file_format = 'TXT' ! Format of mode files
mode_item_list = 'l,n_pg,omega,x,xi_r,xi_h' ! Items to appear in mode files
/


and the other is:

&model
model_type = 'EVOL' ! Obtain stellar structure from an evolutionary model
file = 'rgb.mesa' ! File name of the evolutionary model
file_format = 'MESA' ! File format of the evolutionary model
/

&constants
/

&mode
l = 0 ! Harmonic degree
tag = 'radial' ! Tag for namelist matching
/


&mode
l = 1 ! Harmonic degree
tag = 'non-radial' ! Tag for namelist matching
/


&mode
l = 2 ! Harmonic degree
tag = 'non-radial' ! Tag for namelist matching
/

&osc
outer_bound_type = 'ZERO' ! Use a zero-pressure outer mechanical boundary condition
tag_list = 'radial,non-radial' ! Comma-separated list of tags to match
/

&num
ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

&scan
grid_type = 'LINEAR' ! Scan for modes using a uniform-in-frequency grid; best for p modes
freq_units = 'UHZ' ! Interpret freq_min and freq_max as being in uHz
freq_min = 35 ! Minimum frequency to scan from
freq_max = 45 ! Maximum frequency to scan to
n_freq = 50 ! Number of frequency points in scan
tag_list = 'radial' ! Comma-separated list of tags to match
/

&scan
grid_type = 'INVERSE' ! Scan for modes using a uniform-in-period grid; best for g modes
freq_units = 'UHZ' ! Interpret freq_min and freq_max as being in uHz
freq_min = 35 ! Minimum frequency to scan from
freq_max = 45 ! Maximum frequency to scan to
n_freq = 1000 ! Number of frequency points in scan
tag_list = 'non-radial' ! Comma-separated list of tags to match
/

&shoot_grid
op_type = 'CREATE_CLONE'
/

&shoot_grid
op_type = 'RESAMP_DISPERSION'
alpha_osc = 5
alpha_exp = 1
/

&shoot_grid
op_type = 'RESAMP_CENTER'
n = 5
/

&recon_grid
op_type = 'CREATE_CLONE'
/

&output
summary_file = 'gyre_ad.txt'
summary_file_format = 'TXT'
summary_item_list = 'l,n_pg,n_p,n_g,omega'
/

thank you

Re: Issue with the given example

Posted: Sun Oct 23, 2016 12:25 pm
by richakundu
rhtownsend wrote:
richakundu wrote:hello
i am new to GYRE. I was just trying to work with the examples given on the bitbucket website. 1st example worked perfectly fine. In the subsequent examples i started getting problem. I am getting problem in the following part:

ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

The error shown on the screen is :

Fortran runtime error: Cannot match namelist object name ivp_solver_type

I was getting the same error in "outer_bound_type = 'ZERO' " as well but i just changed "outer_bound_type" to "outer_bound" and the error was gone. I tried the same thing with "ivp_solver_type" but still it was showing the same error.

PS: I am using GYRE 5.0
please help
Richa Kundu
Hi Richa --

Welcome to GYRE! It seems you've run into a known problem with the documentation -- I haven't finished updating it from v4.4 to 5.0. Can you let me know which specific examples have this problem, so I can add them to the list of docs needing updating?

For the moment, to work around your specific problem, use 'diff_scheme' instead of 'ivp_solver_type'.

Best wishes,

Rich



hello
its not solving the issue. Should i degrade the version?
thank you.

Re: Issue with the given example

Posted: Sun Oct 23, 2016 12:35 pm
by rhtownsend
richakundu wrote:
rhtownsend wrote:
richakundu wrote:hello
i am new to GYRE. I was just trying to work with the examples given on the bitbucket website. 1st example worked perfectly fine. In the subsequent examples i started getting problem. I am getting problem in the following part:

ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

The error shown on the screen is :

Fortran runtime error: Cannot match namelist object name ivp_solver_type

I was getting the same error in "outer_bound_type = 'ZERO' " as well but i just changed "outer_bound_type" to "outer_bound" and the error was gone. I tried the same thing with "ivp_solver_type" but still it was showing the same error.

PS: I am using GYRE 5.0
please help
Richa Kundu
Hi Richa --

Welcome to GYRE! It seems you've run into a known problem with the documentation -- I haven't finished updating it from v4.4 to 5.0. Can you let me know which specific examples have this problem, so I can add them to the list of docs needing updating?

For the moment, to work around your specific problem, use 'diff_scheme' instead of 'ivp_solver_type'.

Best wishes,

Rich



hello
its not solving the issue. Should i degrade the version?
thank you.
Please could you tell me what error message you're encountering?

Also, you might want to study the inlist found here

https://bitbucket.org/rhdtownsend/gyre/ ... ing%20GYRE

...to get an idea of what sort of structure a 5.0 inlist should have.

cheers,

Rich

Re: Issue with the given example

Posted: Sun Oct 23, 2016 9:48 pm
by richakundu
richakundu wrote:
rhtownsend wrote:
richakundu wrote:hello
i am new to GYRE. I was just trying to work with the examples given on the bitbucket website. 1st example worked perfectly fine. In the subsequent examples i started getting problem. I am getting problem in the following part:

ivp_solver_type = 'MAGNUS_GL4' ! 4th-order Magnus solver for initial-value integrations
/

The error shown on the screen is :

Fortran runtime error: Cannot match namelist object name ivp_solver_type

I was getting the same error in "outer_bound_type = 'ZERO' " as well but i just changed "outer_bound_type" to "outer_bound" and the error was gone. I tried the same thing with "ivp_solver_type" but still it was showing the same error.

PS: I am using GYRE 5.0
please help
Richa Kundu
Hi Richa --

Welcome to GYRE! It seems you've run into a known problem with the documentation -- I haven't finished updating it from v4.4 to 5.0. Can you let me know which specific examples have this problem, so I can add them to the list of docs needing updating?

For the moment, to work around your specific problem, use 'diff_scheme' instead of 'ivp_solver_type'.

Best wishes,

Rich



hello
its not solving the issue. Should i degrade the version?
thank you.


yeah sure
i used diff_scheme then i got the following error:

OpenMP Threads : 4
Input filename : gyre.in
ASSERT 'n_ot_p == 1' failed at line 110 <gyre_out_par:read_out_par>:
Input file should contain exactly one &ad_output and one &nad_output namelist

thank you
Richa

Re: Issue with the given example

Posted: Tue Oct 25, 2016 8:17 am
by rhtownsend
Hi Richa --

Your problems are coming from the fact that you're using a GYRE 4.x namelist file, but running GYRE 5.0. Please see the link I sent you for an example of the namelist file structure you should be using.

cheers,

Rich

Re: Issue with the given example

Posted: Thu Nov 03, 2016 11:41 am
by richakundu
hello rich
thanx for your help. finally i was able to execute the example. the issue was with the output and grid namelist. its not accepting the namelist options of earlier version.
thank you
Richa

Re: Issue with the given example

Posted: Fri Nov 04, 2016 2:59 pm
by rhtownsend
Hi Richa --

I'm glad you got it working in the end -- thanks for letting us know!

cheers,

Rich

Re: Issue with the given example

Posted: Wed Feb 15, 2017 1:13 am
by richakundu
hello rich
i am again having an issue with new version. I want my output frequencies in per day unit.
I tried t add
freq_units='PER_DAY'
in the summery file but its not accepting this unit. If i give
freq_units='HZ'
the program runs perfectly fine but omega that i get is still dimensionless frequency.
plz help...
Richa Kundu