Post subject: Error while processing Climatology multi-file

[limaolin]

Hi everyone,I have run the south china sea in coawst model,there are some mistakes, thanks for help

CHECK_MULTIFILE - Error while processing Climatology multi-files:
data does not include initialization time = 56228 00:00:00

***** **:**:** ***** **:**:** Projects_My/scs_1/3D_BC/6_days/scs_1_clm.nc

But I check the time of the files:
the time of ini file is 56228
the time of bdy and clm files are 56228 to 56231
the time of frc file is 56228 to 56231

[kate]

Can you just change the first time in the climatology file to 56227.99? That might do the trick.

[limaolin]

I used the m file(roms_master_climatology.m) from the coawst model, the date sets as follows:

T1=datenum(2012,10,27,0,0,0); %start date
%number of days to create clm for
numdays=3;
dayFrequency=1;

I did not know how to set them.

But I used those m files to creat ini clm bdy files and run correctly in Sandy example. I did the same way in south china sea example, there were mistakes, why?

[jcwarner]

the error says
CHECK_MULTIFILE - Error while processing Climatology multi-files:
data does not include initialization time = 56228 00:00:00

***** **:**:** ***** **:**:** Projects_My/scs_1/3D_BC/6_days/scs_1_clm.nc

so the model is reading your netcdf file and coming up with:
***** **:**:** ***** **:**:** Projects_My/scs_1/3D_BC/6_days/scs_1_clm.nc

which means that it can not accurately figure out what the time is. this can be due to many issues, such as the time computed in an incorrect date format. I suggest you do an ncdump of the time stamps in the file
Projects_My/scs_1/3D_BC/6_days/scs_1_clm.nc
and see what the values are for temp_time or salt_time or whatever the time varaibles are.

-j

[limaolin]

thanks for reply, I did the "ncdump scs_1_clm.nc -c", the result as follows

netcdf scs_1_clm {
dimensions:
xpsi = 321 ;
xrho = 322 ;
xu = 321 ;
xv = 322 ;
epsi = 321 ;
erho = 322 ;
eu = 322 ;
ev = 321 ;
s_rho = 16 ;
ocean_time = UNLIMITED ; // (6 currently)
zeta_time = 6 ;
v2d_time = 6 ;
v3d_time = 6 ;
salt_time = 6 ;
temp_time = 6 ;
one = 1 ;
variables:
double ocean_time(ocean_time) ;
ocean_time:long_name = "wind field time" ;
ocean_time:units = "days" ;
ocean_time:field = "wave_time, scalar, series" ;
double zeta_time(zeta_time) ;
zeta_time:long_name = "zeta_time" ;
zeta_time:units = "days" ;
zeta_time:field = "zeta_time, scalar, series" ;
double v2d_time(v2d_time) ;
v2d_time:long_name = "v2d_time" ;
v2d_time:units = "days" ;
v2d_time:field = "v2d_time, scalar, series" ;
double v3d_time(v3d_time) ;
v3d_time:long_name = "v3d_time" ;
v3d_time:units = "days" ;
v3d_time:field = "v3d_time, scalar, series" ;
double salt_time(salt_time) ;
salt_time:long_name = "salt_time" ;
salt_time:units = "days" ;
salt_time:field = "salt_time, scalar, series" ;
double temp_time(temp_time) ;
temp_time:long_name = "temp_time" ;
temp_time:units = "days" ;
temp_time:field = "temp_time, scalar, series" ;
float lon_rho(erho, xrho) ;
lon_rho:long_name = "lon_rho" ;
lon_rho:units = "degrees" ;
lon_rho:FillValue_ = 100000. ;
lon_rho:missing_value = 100000. ;
lon_rho:field = "xp, scalar, series" ;
float lat_rho(erho, xrho) ;
lat_rho:long_name = "lon_rho" ;
lat_rho:units = "degrees" ;
lat_rho:FillValue_ = 100000. ;
lat_rho:missing_value = 100000. ;
lat_rho:field = "yp, scalar, series" ;
double zeta(zeta_time, erho, xrho) ;
zeta:long_name = "zeta" ;
zeta:units = "meter" ;
zeta:field = "zeta, scalar, series" ;
float salt(salt_time, s_rho, erho, xrho) ;
salt:long_name = "salt" ;
salt:units = "psu" ;
salt:field = "salt, scalar, series" ;
float temp(temp_time, s_rho, erho, xrho) ;
temp:long_name = "temp" ;
temp:units = "C" ;
temp:field = "temp, scalar, series" ;
float u(v3d_time, s_rho, eu, xu) ;
u:long_name = "velx" ;
u:units = "meter second-1" ;
u:field = "velx, scalar, series" ;
float v(v3d_time, s_rho, ev, xv) ;
v:long_name = "vely" ;
v:units = "meter second-1" ;
v:field = "vely, scalar, series" ;
float ubar(v2d_time, eu, xu) ;
ubar:long_name = "mean velx" ;
ubar:units = "meter second-1" ;
ubar:field = "mean velx, scalar, series" ;
float vbar(v2d_time, ev, xv) ;
vbar:long_name = "mean vely" ;
vbar:units = "meter second-1" ;
vbar:field = "mean vely, scalar, series" ;

// global attributes:
:history = "Created by updatclim on 17-Nov-2015 07:21:31" ;
:type = "climate forcing file from http://hycom.coaps.fsu.edu:8080/thredds ... b_analysis" ;
data:

ocean_time = 4858099200, 4858185600, 4858272000, 4858358400, 4858444800,
4858531200 ;

zeta_time = 56228, 56229, 56230, 56231, 56232, 56233 ;

v2d_time = 56228, 56229, 56230, 56231, 56232, 56233 ;

v3d_time = 56228, 56229, 56230, 56231, 56232, 56233 ;

salt_time = 56228, 56229, 56230, 56231, 56232, 56233 ;

temp_time = 56228, 56229, 56230, 56231, 56232, 56233 ;
}

[rtopper]

ocean_time = 4858099200, 4858185600, 4858272000, 4858358400, 4858444800,
4858531200 ;

This is clearly the problem. Check if the calculation of ocean_time is different from zeta_time/v2d_time/etc, because these other time variables seem to be what you want.

[limaolin]

I used the same m file to create clm ini and bdy files in the Sandy example, the ocean_time in clm file is the same. So ,I thought it's not the answer for my problem.

[jcwarner]

these m files may have been updated at some time. to solve the problem, it would simply be to load the ocean_time into maltab using ot=ncread(file,'ocean_time'); use ocean_time=ocean_time/3600/24 ( I think), then ncwrite(file,'ocean_time',ocean_time) and we can move on. these issues happen a lot because people use different methods to reference time.

[smchen]

As what rtopper said, ocean_time is usually equal to other time frames. This is the magic number: 4858099200/56228=86400. Do you use seconds instead of days for ocean_time?

[rtopper]

It seems you are using COAWST. Which means you are likely using roms_master_climatology_coawst_mw.m to create clm, bdy, and ini files.

In this matlab script the clm file is created first with all its time variables. In updatclim_coawst_mw.m you should see:

Code: Select all

tempid=netcdf.inqVarID(RN,'ocean_time');
netcdf.putVar(RN,tempid,tg2(tid1));
tempid=netcdf.inqVarID(RN,'zeta_time');
netcdf.putVar(RN,tempid,tg2(tid1));
tempid=netcdf.inqVarID(RN,'v2d_time');
netcdf.putVar(RN,tempid,tg2(tid1));
tempid=netcdf.inqVarID(RN,'v3d_time');
netcdf.putVar(RN,tempid,tg2(tid1));
tempid=netcdf.inqVarID(RN,'salt_time');
netcdf.putVar(RN,tempid,tg2(tid1));
tempid=netcdf.inqVarID(RN,'temp_time');
netcdf.putVar(RN,tempid,tg2(tid1));
netcdf.close(RN);

This means that all time variables are defined in the same way and should contain the same values.

The bdy and ini file are created after the clm file and take the ocean_time variable from the clm file. It is therefore expected that ocean_time is the same in clm, ini, and bdy files.

If you don't want to use John's solution to your problem. Update your COAWST installation to the most recent version and use the matlab files from it.

[limaolin]

thanks all, I have solved the problems with your help.