Inquires on OZONE format

[tingting@ucar_edu]

Hi all,
I got a problem on running a case with prescribed ozone forcing, the end of cpl.log.XXXXXX is:

(seq_mct_drv) : Model initialization complete

the error statements in cesm.log.XXXXXX file are 'radiation ozone error'.

So, I am thinking this may be an inputdata issue. For my case, I am using the SPARC ozone, which is generated on pressure levels and is lacking PS.

The information of this netCDF data is:
...............
dimensions:
time = UNLIMITED ; // (2040 currently)
lev = 24 ;
lat = 37 ;
lon = 72 ;

variables:
float O3(time, lev, lat, lon) ;
O3:long_name = "O3" ;
O3:_FillValue = 9.96921e+36f ;
O3:standard_name = "mole_fraction_of_ozone_in_air" ;
O3:units = "mol/mol" ;
O3:cell_methods = "time:mean (interval: 1 months)" ;
float time(time) ;
time:axis = "T" ;
time:calendar = "noleap" ;
time:standard_name = "time" ;
time:units = "days since 1850-01-01 00:00" ;
time:long_name = "time" ;
time:bounds = "time_bnds" ;
time:_FillValue = 9.96920996838687e+36 ;
float lev(lev) ;
lev:units = "hPa" ;
lev:long_name = "Pressure" ;
lev:axis = "Z" ;
lev:positive = "down" ;
lev:standard_name = "air_pressure" ;
float lat(lat) ;
lat:units = "degrees_north" ;
lat:long_name = "Latitude" ;
lat:axis = "Y" ;
lat:standard_name = "latitude" ;
float lon(lon) ;
lon:units = "degrees_east" ;
lon:long_name = "Longitude" ;
lon:axis = "X" ;
lon:standard_name = "longitude" ;
int datesec(time) ;
datesec:units = "YYYYMM" ;
datesec:long_name = "time" ;
int date(time) ;
date:long_name = "date" ;
date:format = "YYYYMMDD" ;

Thanks for any help.
Tingting

 

[eaton]

The ozone field is interpolated to the model levels and is available for history output (done in the prescribed_ozone module).  It's not added to the history files by default, so you need to add the field 'ozone' to a fincl variable in the namelist.  That should allow you to check that the ozone interpolated to model levels looks reasonable. 

 

[tingting@ucar_edu]

Thanks for your replying.The problem has been fixed! tingting

 

[esjiayu_bin@163_com]

Hi Would you please tell me how you fixed your problem? I got the same error report in my simulation.