Error in nicas_blk_compute_sampling_c1

I am trying to run fv3jedi_parameters.x using the bumpparameters_nicas_gfs_aero.yaml. I’ve added in the section for computing and writing out stddev, and it runs until starting to write out the nicas files. I get the error message:

!!! ABORT in nicas_blk_compute_sampling_c1 on task #0001: no valid level

I’m assuming that there is perhaps something missing from my yaml file. I’ve attached it here:

geometry:
nml_file_mpp: Data/fv3files/fmsmpp.nml
trc_file: Data/fv3files/field_table
akbk: Data/fv3files/akbk64.nc4

input.nml

layout: [2,2]
io_layout: [1,1]
npx: 97
npy: 97
npz: 64
ntiles: 6
fieldsets:
- fieldset: Data/fieldsets/dynamics.yaml
- fieldset: Data/fieldsets/aerosols_gfs.yaml
input variables: &aerovars [sulf,bc1,bc2,oc1,oc2,
dust1,dust2,dust3,dust4,dust5,
seas1,seas2,seas3,seas4,seas5]

date: ‘2016-07-01T00:00:00Z’
background:
filetype: gfs
datapath: Data/inputs/gfs_aero_c96/bkg/
filename_core: 20160701.000000.fv_core.res.nc
filename_trcr: 20160701.000000.fv_tracer.res.nc
filename_cplr: 20160701.000000.coupler.res
state variables: [sulf]
bump:
prefix: Data/bump/fv3jedi_bumpparameters_nicas_gfs_aero
verbosity: main
universe_rad: 2500.0e3
strategy: specific_univariate
new_nicas: 1
ntry: 10
nrep: 2
resol: 6.0
mpicom: 2

Forced length-scales

--------------------

write_cmat: 0
io_keys:

  • “sulf-sulf”
    io_values:
  • “fixed_2500km_1.5”
    new_vbal: 1
    vbal_block: [0,1,1,0,1,0]
    vbal_rad: 3000.0e3
    new_var: 1
    ne: 8
    var_filter: 1
    var_niter: 3
    var_rhflt: 2500.0e3
    ensemble:
    date: ‘2016-07-01T00:00:00Z’
    members:
  • filetype: gfs
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem001/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
  • filetype: gfs
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem002/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
  • filetype: gfs
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem003/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem004/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
  • filetype: gfs
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem005/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
  • filetype: gfs
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem006/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
  • filetype: gfs
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem007/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
  • filetype: gfs
    state variables: *aerovars
    datapath: Data/inputs/gfs_aero_c96/mem008/
    filename_trcr: fv_tracer.res.nc
    filename_cplr: coupler.res
    output:
  • parameter: stddev
    exp: stddev
    type: an
    filetype: gfs
    datapath: Data/bump_aero/
    filename_core: bumpparameters_nicas_gfs_aero.stddev.fv_core.res.nc
    filename_trcr: bumpparameters_nicas_gfs_aero.stddev.fv_tracer.res.nc
    filename_cplr: bumpparameters_nicas_gfs_aero.stddev.coupler.res
    date: ‘2016-07-01T00:00:00Z’
  • parameter: cor_rh
    exp: cor_rh
    type: an
    filetype: gfs
    datapath: Data/bump_aero/
    filename_core: bumpparameters_nicas_gfs_aero.cor_rh.fv_core.res.nc
    filename_trcr: bumpparameters_nicas_gfs_aero.cor_rh.fv_tracer.res.nc
    date: ‘2016-07-01T00:00:00Z’
  • parameter: cor_rv
    exp: cor_rv
    type: an
    filetype: gfs
    datapath: Data/bump_aero/
    filename_core: bumpparameters_nicas_gfs_aero.cor_rv.fv_core.res.nc
    filename_trcr: bumpparameters_nicas_gfs_aero.cor_rv.fv_tracer.res.nc
    date: ‘2016-07-01T00:00:00Z’

I’ve resolved this issue. But have encountered a new error that I have not seen before. During iterations - this error occurred.

!!! ABORT in stripack_trmesh on task #0009: N < 3
Traceback for instance 11 :

I was able to avoid the above ABORT by reducing the number of iterations in BUMP. I’m working on “load_var” in hyb-3dvar_gfs_aero.yaml. It would be helpful to see a complete yaml file that includes this.

1 Like