Runtime Error，

[q1165600785]

I used region-mom6 to generate the files required for running, and this error occurred

This is a time-related error. How can I solve it? Is there something wrong with the file I generated?

FATAL: time_interp_external 2: time 0 (00010101.000050 is before range of list 731230-731234(20030101.000000 - 20030105.000000),file=INPUT/forcing_obc_segment_001.nc,field=u_segment_001

FATAL: time_interp_external 2: time 0 (00010101.000050 is before range of list 731230-731234(20030101.000000 - 20030105.000000),file=INPUT/forcing_obc_segment_001.nc,field=u_segment_001

#0 0x5597d8a38c0c in __mpp_mod_MOD_mpp_error_basic
at ../src/mpp/include/mpp_util_mpi.inc:74
#1 0x5597d8cd6719 in __time_interp_external2_mod_MOD_time_interp_external_3d_r8
at ../src/time_interp/include/time_interp_external2.inc:178
#2 0x5597d856b6b7 in __mom_interp_infra_MOD_time_interp_extern_3d
at ../config_src/infra/FMS2/MOM_interp_infra.F90:240
#3 0x5597d856cd4e in __mom_interpolate_MOD_time_interp_external_3d
at ../src/framework/MOM_interpolate.F90:183
#4 0x5597d865377e in __mom_open_boundary_MOD_update_obc_segment_data
at ../src/core/MOM_open_boundary.F90:4069
#5 0x5597d83e8e9b in __mom_dynamics_split_rk2_MOD_step_mom_dyn_split_rk2
at ../src/core/MOM_dynamics_split_RK2.F90:533
#6 0x5597d8196046 in step_mom_dynamics
at ../src/core/MOM.F90:1257
#7 0x5597d8196046 in __mom_MOD_step_mom
at ../src/core/MOM.F90:922
#8 0x5597d83c1786 in mom6
at ../config_src/drivers/solo_driver/MOM_driver.F90:488
#9 0x5597d814de9e in main
at ../config_src/drivers/solo_driver/MOM_driver.F90:27
Abort(1) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

[q1165600785]

WARNING: categorize_axes: Failed to identify x- and y- axes in the axis list (nx_segment_002, ny_segment_002, time) of a variable being read from INPUT/forcing_obc_segment_002.nc

[q1165600785]

FATAL from PE 3: NetCDF: Index exceeds dimension bound: netcdf_read_data_4d: file:INPUT/forcing_obc_segment_001.nc- variable:u_segment_001

#0 0x55d06d323c0c in __mpp_mod_MOD_mpp_error_basic

[marshallward]

This looks like a possible bug in the OBC code. Or, at least, a problem with your OBC file which was undetected by the model.

Can you dump the netCDF metadata? ncdump -h. If it looks like a bug, then I will move this to Issues.

[q1165600785]

This is the output of ncdump -h ./INPUT/forcing_obc_segment_001.nc
netcdf forcing_obc_segment_001 {
dimensions:
time = UNLIMITED ; // (5 currently)
nz_segment_001_u = 50 ;
ny_segment_001 = 1 ;
nx_segment_001 = 121 ;
nz_segment_001_v = 50 ;
nz_segment_001_salt = 50 ;
nz_segment_001_temp = 50 ;
nz_salt_segment_001 = 50 ;
nz_temp_segment_001 = 50 ;
nz_u_segment_001 = 50 ;
nz_v_segment_001 = 50 ;
depth = 50 ;
variables:
double u_segment_001(time, nz_segment_001_u, ny_segment_001, nx_segment_001) ;
u_segment_001:_FillValue = 1.e+20 ;
u_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
double v_segment_001(time, nz_segment_001_v, ny_segment_001, nx_segment_001) ;
v_segment_001:_FillValue = 1.e+20 ;
v_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
double eta_segment_001(time, ny_segment_001, nx_segment_001) ;
eta_segment_001:_FillValue = 1.e+20 ;
eta_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
double salt_segment_001(time, nz_segment_001_salt, ny_segment_001, nx_segment_001) ;
salt_segment_001:_FillValue = 1.e+20 ;
salt_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
double temp_segment_001(time, nz_segment_001_temp, ny_segment_001, nx_segment_001) ;
temp_segment_001:_FillValue = 1.e+20 ;
temp_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
float dz_salt_segment_001(time, nz_salt_segment_001, ny_segment_001, nx_segment_001) ;
dz_salt_segment_001:_FillValue = 1.e+20f ;
dz_salt_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
float dz_temp_segment_001(time, nz_temp_segment_001, ny_segment_001, nx_segment_001) ;
dz_temp_segment_001:_FillValue = 1.e+20f ;
dz_temp_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
float dz_u_segment_001(time, nz_u_segment_001, ny_segment_001, nx_segment_001) ;
dz_u_segment_001:_FillValue = 1.e+20f ;
dz_u_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
float dz_v_segment_001(time, nz_v_segment_001, ny_segment_001, nx_segment_001) ;
dz_v_segment_001:_FillValue = 1.e+20f ;
dz_v_segment_001:coordinates = "lat_segment_001 lon_segment_001 nxp nyp" ;
float depth(depth) ;
depth:_FillValue = NaNf ;
double time(time) ;
time:_FillValue = NaN ;
time:calendar = "julian" ;
time:units = "days since 2003-01-01 00:00:00" ;
int64 nyp ;
int64 nxp(nx_segment_001) ;
double lon_segment_001(nx_segment_001) ;
lon_segment_001:_FillValue = NaN ;
lon_segment_001:standard_name = "geographic_longitude" ;
lon_segment_001:units = "degree_east" ;
double lat_segment_001(nx_segment_001) ;
lat_segment_001:_FillValue = NaN ;
lat_segment_001:standard_name = "geographic_latitude" ;
lat_segment_001:units = "degree_north" ;
int nz_segment_001_salt(nz_segment_001_salt) ;
int nz_segment_001_temp(nz_segment_001_temp) ;
int nz_segment_001_u(nz_segment_001_u) ;
int nz_segment_001_v(nz_segment_001_v) ;
int nx_segment_001(nx_segment_001) ;
int ny_segment_001(ny_segment_001) ;
}

[marshallward]

Sorry, I didn't read the error carefully enough. It looks like your time is set to zero but your interval is between 20030101 - 20030105. Did you want this to be fixed in time?

[q1165600785]

Yes, I hope this can be fixed in time.I don't know if this error is a problem with the file I generated or a problem with the mom6 program itself. Do I need to provide any other files?

[marshallward]

Have you looked at the time axis? It is set for the same times as your model run?

[marshallward]

I also see that units is set for days since 2003-01-01 00:00:00 but I don't know if the OBC reader uses that information.

[q1165600785]

import netCDF4  as nf 

def nf_read():
    path_obs=r'./mom6_run_directories/jbrangge3/INPUT/forcing_obc_segment_001.nc'
    ds = nf.Dataset(path_obs)   
    # print(ds)
    # variable_names = ds.variables.keys()  # 变量名，类似于该数据的属性
    # print(len(variable_names), variable_names)
    print(ds.variables['time'])
    print(ds.variables['time'][:])
    print(ds.variables['time'][0])
if  __name__ ==    '__main__':
    nf_read()

<class 'netCDF4.Variable'>
float64 time(time)
_FillValue: nan
calendar: julian
units: days since 2003-01-01 00:00:00
unlimited dimensions: time
current shape = (5,)
filling on
[0. 1. 2. 3. 4.]
0.0

Professor, I found the problem. The timeline was accidentally set wrong. I think this is the reason.
I checked the time axis as you requested, and it is indeed wrong. This is an error in the generated file, and has nothing to do with mom6. I think this is the reason. I really appreciate the professor's help.