Hi Gabi,
Thanks for the quick response. I have added in the required WACCM variables (hyam, hybm, PS, P0) but still get the same error.
Having checked again I can see that the variables listed above (plus lev, lat, lon, time, date and datesec) are read in to mozbc so I guess it's likely one of these variables causing the problem. I have compared the BC files I have previously successfully read in to the ones I'm trying to read in now. The only differences between the files are:
- The WACCM files I have successfully read in in the past have different time variable attributes ['days since 0001-01-01 00:00:00', 'calendar = gregorian'] (and are double type) compared with ['days since 2017-08-16 00:00:00', 'calendar = proleptic gregorian'] (and int64 type) in the new file. This also means that the first time value in the new file is 0.
- There are fewer levels in the new files (70 vs 88).
Would either of these differences cause problems with mozbc? I wondered if the time interpolation may break if the time values are used instead of date values. I did a diff --side-by-side on the successful and unsuccessful mozbc and can see it fails just before (or at) the time section of mozbc. I've pasted below in case this is helpful.
Thanks again for your help,
Ailish
checking wrf variable num_a03 checking wrf variable num_a03
len num_a2 = 6 len num_a2 = 6
len num_a1 = 6 len num_a1 = 6
len num_a3 = 6 len num_a3 = 6
len num_a2 = 6 len num_a2 = 6
len num_a1 = 6 len num_a1 = 6
len num_a3 = 6 len num_a3 = 6
checking wrf variable num_a04 checking wrf variable num_a04
len num_a2 = 6 len num_a2 = 6
len num_a1 = 6 len num_a1 = 6
len num_a3 = 6 len num_a3 = 6
len num_a2 = 6 len num_a2 = 6
len num_a1 = 6 len num_a1 = 6
len num_a3 = 6 len num_a3 = 6
NetCDF: Variable not found | finished init_mozart_lib
> dt_wrfbdy = 21600.00
> main; doing time 20170901 : 0
fail to process netCDF file... | get_moz_time_ndx; moz_dir,moz_fn = ./
moz0000.nc > get_moz_time_ndx; wrf_date,wrf_datesec,ntime_m = 2017090
> 89