Opened 7 days ago

Closed 4 days ago

#3272 closed help (fixed)

Error reading namelist JULES_OUTPUT_PROFILE

Reported by: mtodt Owned by: pmcguire
Component: JULES Keywords: jules output profile
Cc: Platform: JASMIN
UM Version:

Description

Hi

I am trying to run a suite of mine, which has been working for months, with some new output profiles, but JULES crashes with the following error message:

[FATAL ERROR] init_output: Error reading namelist JULES_OUTPUT_PROFILE (IOSTAT=-1 IOMSG=end-of-file during read, unit 1, file /work/scratch/mtodt/cylc-run/u-bj046/work/1/jules/./output.nml)

I prescribe two output profiles (nprofiles=2) in namelist jules_output and specify:

[namelist:jules_output_profile(1)]
file_period=0
nvars=6
output_main_run=.true.
output_period=86400
output_spinup=.false.
output_end='2012-12-31 21:00:00'
output_start='2000-01-01 00:00:00'
output_type=6*'M'
profile_name='daily'
var='surf_ht_flux_gb','smcl','ecan_gb','esoil_gb','et_stom_gb','fqw_gb'
var_name=''

[namelist:jules_output_profile(2)]
file_period=-2
nvars=4
output_main_run=.true.
output_period=10800
output_spinup=.false.
output_end='2012-12-31 21:00:00'
output_start='2000-01-01 00:00:00'
output_type='S','S','M','M'
profile_name='3hr'
var='tstar_gb','tl1','latent_heat','ftl_gb'
var_name=''

When I look at …/cylc-run/u-bj046/work/1/jules/./output.nml, however, it only picks up the first output profile despite listing nprofiles as 2. I've tried rose suite-run —new and deleting output.nml, but I get the same error. Is there anything that I'm overlooking? Thanks a lot for your help!

Cheers
Markus

Change History (2)

comment:1 Changed 7 days ago by mtodt

Oh, I forgot to mention that the suite name is u-bj046.

comment:2 Changed 4 days ago by mtodt

  • Resolution set to fixed
  • Status changed from new to closed

I found my mistake. I hadn't added the second output profile to

[file:output.nml]
source=namelist:jules_output namelist:jules_output_profile(1)

at the top of app/jules/rose-app.conf. I close this ticket now.

Cheers
Markus

Note: See TracTickets for help on using tickets.