Interannual simulations

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
sriram
Posts: 3
Joined: Thu Oct 23, 2008 1:35 pm
Location: Indian Institute of Tropical Meteorology

Interannual simulations

#1 Unread post by sriram »

Hello,
I am running ROMS Agrif. I have completed 10 years spinup and then created all the forcing files with boundary files etc.. Now, when I am running the model for interannual simulations I am not getting the output files. I want to write the output on daily basis. Say, each day's output I want to write in a separate file. Instead, I am getting only one roms_avg.nc.

Please suggest me how to write the output files for the interannual simulations.

Regards and thanks in advance,
Sriram

hyy
Posts: 17
Joined: Wed Apr 22, 2009 6:01 pm
Location: National Institute for Environmental Studies

Re: Interannual simulations

#2 Unread post by hyy »

Hi Sriram,

Would you show us the contents (code) of input parameter file: "roms_inter.in" that you are using?
This file also control the number of timesteps between writing of output data.

Cheers,

Hiroshi (hyy)

sriram
Posts: 3
Joined: Thu Oct 23, 2008 1:35 pm
Location: Indian Institute of Tropical Meteorology

Re: Interannual simulations

#3 Unread post by sriram »

Hello Hiroshi,

Following is the roms_inter.in I am using for simulations. Hope this helps you to suggest me some thing that I am missing to write out the data.

Regards,
Sriram

--------------------------------------------------------------
title:
Indian Ocean Inter Run
time_stepping: NTIMES dt[sec] NDTFAST NINFO
NUMTIMES 450 60 1
S-coord: THETA_S, THETA_B, Hc (m)
6.0d0 0.0d0 10.0d0
grid: filename
ROMS_FILES/roms_grd.nc
forcing: filename
ROMS_FILES/roms_frc.nc
bulk_forcing: filename
ROMS_FILES/roms_blk.nc
climatology: filename
ROMS_FILES/roms_clm.nc
boundary: filename
ROMS_FILES/roms_bry.nc
initial: NRREC filename
1
ROMS_FILES/roms_ini.nc
restart: NRST, NRPFRST / filename
NUMTIMES -1
ROMS_FILES/roms_rst.nc
history: LDEFHIS, NWRT, NRPFHIS / filename
T NUMTIMES 0
ROMS_FILES/roms_his.nc
averages: NTSAVG, NAVG, NRPFAVG / filename
1 48 0
ROMS_FILES/roms_avg.nc

primary_history_fields: zeta UBAR VBAR U V wrtT(1:NT)
T F F F F 10*F
auxiliary_history_fields: rho Omega W Akv Akt Aks HBL Bostr
F F F F F F F F

primary_averages: zeta UBAR VBAR U V wrtT(1:NT)
T T T T T 10*T
auxiliary_averages: rho Omega W Akv Akt Aks HBL Bostr
F T T F T F T T


rho0:
1025.d0

lateral_visc: VISC2, VISC4 [m^2/sec for all]
0. 0.

tracer_diff2: TNU2(1:NT) [m^2/sec for all]
10*0.d0

bottom_drag: RDRG [m/s], RDRG2, Zob [m], Cdb_min, Cdb_max
0.0d-04 0.d-3 1.d-2 1.d-4 1.d-1

gamma2:
1.d0

sponge: X_SPONGE [m], V_SPONGE [m^2/sec]
100.e3 800.

nudg_cof: TauT_in, TauT_out, TauM_in, TauM_out [days for all]
1. 360. 10. 360.




diagnostics: ldefdia nwrtdia nrpfdia /filename
T 144 0
roms_diags.nc
diag_avg: ldefdia_avg ntsdia_avg nwrtdia_avg nprfdia_avg /filename
T 1 144 0
roms_diags_avg.nc

diagnostics_bio: ldefdiabio nwrtdiabio nrpfdiabio /filename
T 20 0
roms_diagsbio.nc
diagbio_avg: ldefdiabio_avg ntsdiabio_avg nwrtdiabio_avg nprfdiabio_avg /filename
T 1 20 0
roms_diagsbio_avg.nc

sediments: input file
sediment.in
sediment_history_fields: bed_thick bed_poros bed_fra(sand,silt)
T F T T

bbl_history_fields: Abed Hripple Lripple Zbnot Zbapp Bostrw
T F F T F T

floats: LDEFFLT, NFLT, NRPFFLT / inpname, hisname
T 6 0
floats.in
floats.nc
float_fields: Grdvar Temp Salt Rho Vel
F F F F F

stations: LDEFSTA, NSTA, NRPFSTA / inpname, hisname
T 400 0
stations.in
stations.nc
station_fields: Grdvar Temp Salt Rho Vel
T T T T T

psource: Nsrc Isrc Jsrc Dsrc Qbar [m3/s] Lsrc Tsrc
2
3 54 1 200. T T 5. 0.
3 40 0 200. T T 5. 0.

hyy
Posts: 17
Joined: Wed Apr 22, 2009 6:01 pm
Location: National Institute for Environmental Studies

Re: Interannual simulations

#4 Unread post by hyy »

Hi Sriram, Thanks for uploading the code (input parameter file) you are using.

For example, why not changing the value of "NWRT" from 'NUMTIMES' to '48', which is same as the value of "NAVG", as follows?;

BEFORE (Your Original Code):
..........
restart: NRST, NRPFRST / filename
NUMTIMES -1
ROMS_FILES/roms_rst.nc
history: LDEFHIS, NWRT, NRPFHIS / filename
T NUMTIMES 0
ROMS_FILES/roms_his.nc
averages: NTSAVG, NAVG, NRPFAVG / filename
1 48 0
ROMS_FILES/roms_avg.nc
...........

AFTER (Suggested Code):
..........
restart: NRST, NRPFRST / filename
NUMTIMES -1
ROMS_FILES/roms_rst.nc
history: LDEFHIS, NWRT, NRPFHIS / filename
T 48 0
ROMS_FILES/roms_his.nc
averages: NTSAVG, NAVG, NRPFAVG / filename
1 48 0
ROMS_FILES/roms_avg.nc
...........

"NWRT" is the number of timesteps between writing of outputs into history file.

Cheers, Hiroshi

sriram
Posts: 3
Joined: Thu Oct 23, 2008 1:35 pm
Location: Indian Institute of Tropical Meteorology

Re: Interannual simulations

#5 Unread post by sriram »

Dear Hiroshi,

Thanks for the suggestion. That is fine, but I would like to write daily averages and each day's data into a separate file. Can you pl. suggest me as to how I can write that way?

Thanks again and Regards,
Sriram

hyy
Posts: 17
Joined: Wed Apr 22, 2009 6:01 pm
Location: National Institute for Environmental Studies

Re: Interannual simulations

#6 Unread post by hyy »

Hi Sriram,

> I would like to write daily averages

You can write down daily averages onto averages file: ".._avg_.." by
setting "NAVG" appropriately. "NAVG" defines the number of timesteps
between writing of time-averaged data into averages file.

To write down daily averages, you can derive "NAVG" using
"dt[sec]":timestep [sec] for 3D equations; that is,...

NAVG = 24 * 3600 / dt[sec]

In your input parameter file, setting "NAVG" as '192' (= 24 * 3600 /
450), you can get daily averages in averages file.

> and each day's data into a separate file.

As you have already known, filename of output files are managed by csh
script: "run_roms_inter.csh". In default, this script manages 'every
monthly' outputs (e.g., Y1996M2 (February 1996) etc.). If you want to
derive 'every daily' outputs as a separate file, you have to modify
this script. For me, I am afraid that I do not know about it; csh
script which manages 'every daily' outputs, so far. I am sorry about
it.

Cheers, Hiroshi

Post Reply