Page 1 of 1

"exactly one &<stage>_output namelist" error arises from walk-through in documentation

Posted: Fri Mar 14, 2025 12:10 pm
by mjoyce
Hi Rich,

I just assigned a student this walkthrough on the GYRE docs: https://gyre.readthedocs.io/en/latest/u ... rough.html

This results in the error

Code: Select all

ABORT at line 121 of /Users/calebeastlund/mesa-24.08.1/gyre/gyre/src/par/out_par_m.fypp
 assertion n_ot_p == 1 failed with message input file should contain exactly one &<stage>_output namelist"
regardless of what combination of the &nad_output, &ad_output,and &tides_output namelist sections we use. I can reproduce the error on my own system.

What's going on here? The namelist is exactly as on the GYRE walkthrough page:

&constants
/

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

&mode
l = 1 ! Harmonic degree
/

&mode
l = 2 ! Harmonic degree
/

&osc
outer_bound = 'VACUUM' ! Assume the density vanishes at the stellar surface
/

&rot
/

&num
diff_scheme = 'COLLOC_GL4' ! 4th-order collocation scheme for difference equations
/

&scan
grid_type = 'INVERSE' ! Scan grid uniform in inverse frequency
freq_min = 0.5 ! Minimum frequency to scan from
freq_max = 1.5 ! Maximum frequency to scan to
n_freq = 100 ! Number of frequency points in scan
/

&grid
w_osc = 10 ! Oscillatory region weight parameter
w_exp = 2 ! Exponential region weight parameter
w_ctr = 10 ! Central region weight parameter
/

&tides_output
/

&ad_output
summary_file = 'summary.h5' ! File name for summary file
summary_item_list = 'l,n_pg,freq,freq_units,E_norm' ! Items to appear in summary file
detail_template = 'detail.l%l.n%n.h5' ! File name template for detail files
detail_item_list = 'l,n_pg,omega,x,xi_r,
xi_h,c_1,As,V_2,Gamma_1' ! Items to appear in detail files
freq_units = 'CYC_PER_DAY' ! Units of freq output items
/

&nad_output
/

Thanks,

Re: "exactly one &<stage>_output namelist" error arises from walk-through in documentation

Posted: Fri Mar 14, 2025 2:16 pm
by rhtownsend
Hi Meridith --

I'm guessing this is being caused because there is a missing newline at the end of the file. The final line should be blank.

cheers,

Rich