FGONG and gyre_nad

Bug/problem reports for any of the GYRE executables (gyre_ad, gyre_nad, etc)

FGONG and gyre_nad

Postby pieterd » Wed Feb 05, 2014 11:35 am

Hi Rich,

I'm trying to run gyre_nad on an FGONG file, but I get

Code: Select all
Root Solving
       l    n_pg     n_p     n_g                 Re(omega)                 Im(omega)                       chi  n_iter        n
 ABORT at line 794 <gyre_coeffs_evol:tau_thm_1>:
 tau_thm is undefined
STOP Program aborted


after the adiabatic calculations went fine. I'm not familiar with the source code at all, but I see in the "gyre_fgong_file.f90" that when the base coefficients are initialized, the information on the opacity and opacity derivatives is not loaded:

Code: Select all

call ec%init(G, M_star, R_star, L_star, r, m, p, rho, T, &
                 N2, Gamma_1, nabla_ad, delta, SPREAD(0._WP, DIM=1, NCOPIES=n), &
                 deriv_type, add_center)



Could this be the reason? In the official FGONG file format description, all the columns you require should be there (nabla=6, kappa=8, kappa_rho=18, kappa_T=17, Omega_rot=16, epsilon=9, epsilon_rho=20, epsilon_T=19 (Fortran indexing)).

I can of course translate the FGONG file to an HDF5 file if this is really the issue, but I just thought you might know.

Cheers,
Pieter
pieterd
 
Posts: 9
Joined: Mon Apr 08, 2013 2:09 am

Re: FGONG and gyre_nad

Postby rhtownsend » Wed Feb 05, 2014 12:21 pm

Hi Pieter --

The routines in GYRE to read FGONG files are based off the description here:

http://www.astro.up.pt/corot/ntools/doc ... _Files.pdf

Do you have a more-recent description of the FGONG format, which I could use to update the code?

cheers,

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

Re: FGONG and gyre_nad

Postby pieterd » Thu Feb 06, 2014 2:54 am

Hi Rich,

ah sorry, I was looking at the OSC format for my column description...

Only columns 37 to 40 are unused, but 37 and 38 are unofficially reserved for nabla and nablarad, that leaves only 39 and 40 for the other variables... that's a no go..

I will just stick to the GSM format then.

I don't know in how far you want to catch stupid user errors; but perhaps raising an error when running gyre_nad with impossible file formats can give some comprehensive output? Working with different codes, I sometimes forget that information is lost in file conversions.

Cheers & thanks,
Pieter
pieterd
 
Posts: 9
Joined: Mon Apr 08, 2013 2:09 am


Return to Bug reports

Who is online

Users browsing this forum: No registered users and 1 guest

cron