cannot output lag_p or eul_p

Bug/problem reports for any of the GYRE executables (gyre_ad, gyre_nad, etc)
Post Reply
jingluan
Posts: 10
Joined: Thu Jan 19, 2017 1:30 pm

cannot output lag_p or eul_p

Post by jingluan » Mon Feb 20, 2017 4:39 pm

Hi,

I am using gyre 5.0. As I include the lag_p or eul_p in the output list for mode file for &ad_output:

mode_item_list = 'l,n_pg,omega,x,xi_r,xi_h,eul_p'

Gyre reports error below:

item:eul_p
ABORT at line 456 <gyre_output:write_mode:write_mode_evol_>:
Invalid item
STOP Program aborted

How could I ask gyre to ouput pressure perturbations please? Many thanks :-)

Sincerely,
Jing

User avatar
rhtownsend
Site Admin
Posts: 397
Joined: Sun Mar 31, 2013 4:22 pm

Re: cannot output lag_p or eul_p

Post by rhtownsend » Mon Feb 20, 2017 4:40 pm

jingluan wrote:Hi,

I am using gyre 5.0. As I include the lag_p or eul_p in the output list for mode file for &ad_output:

mode_item_list = 'l,n_pg,omega,x,xi_r,xi_h,eul_p'

Gyre reports error below:

item:eul_p
ABORT at line 456 <gyre_output:write_mode:write_mode_evol_>:
Invalid item
STOP Program aborted

How could I ask gyre to ouput pressure perturbations please? Many thanks :-)

Sincerely,
Jing
Hi Jing --

It should be 'lag_P' and 'eul_P'.

cheers,

Rich

jingluan
Posts: 10
Joined: Thu Jan 19, 2017 1:30 pm

Re: cannot output lag_p or eul_p

Post by jingluan » Mon Feb 20, 2017 4:46 pm

Hi Rich,

Thank you for your quick reply. I observe that in the description for the output file (the link below), it appears small p there.

https://bitbucket.org/rhdtownsend/gyre/ ... es%20(4.4)

Thank you :-)

Sincerely,
Jing

User avatar
rhtownsend
Site Admin
Posts: 397
Joined: Sun Mar 31, 2013 4:22 pm

Re: cannot output lag_p or eul_p

Post by rhtownsend » Mon Feb 20, 2017 4:48 pm

jingluan wrote:Hi Rich,

Thank you for your quick reply. I observe that in the description for the output file (the link below), it appears small p there.

https://bitbucket.org/rhdtownsend/gyre/ ... es%20(4.4)

Thank you :-)

Sincerely,
Jing
That's because the link you give is to the documentation for version 4.4! I'm in the process of re-writing the 5.0 documentation, which is a time-consuming process; that's why it's taking so long for 5.0 to be officially released.

cheers,

Rich

Post Reply