Changeset 4117 for branches/2013/dev_r3987_UKMO4_OBS/DOC
- Timestamp:
- 2013-10-23T22:32:11+02:00 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2013/dev_r3987_UKMO4_OBS/DOC/TexFiles/Chapters/Chap_OBS.tex
r4115 r4117 869 869 ! namoff Offline obs_oper namelist 870 870 !---------------------------------------------------------------------- 871 ! o ff_files specifies the files containing the model counterpart872 ! nn_o ff_idx specifies the time_counter index within the model file871 ! ooo_files specifies the files containing the model counterpart 872 ! nn_ooo_idx specifies the time_counter index within the model file 873 873 &namoff 874 o ff_files = "foo.nc"875 nn_o ff_idx = 2874 ooo_files = "foo.nc" 875 nn_ooo_idx = 2 876 876 / 877 877 \end{verbatim} … … 880 880 \subsubsection{Multiple fields per run} 881 881 882 Model field iteration is controlled via \textbf{nn\_o ff\_freq} which specifies882 Model field iteration is controlled via \textbf{nn\_ooo\_freq} which specifies 883 883 the number of model steps at which the next field gets read. For example, if 884 884 12 hourly fields are to be interpolated in a setup where 288 steps equals 24 hours. … … 890 890 ! namoff Offline obs_oper namelist 891 891 !---------------------------------------------------------------------- 892 ! o ff_files specifies the files containing the model counterpart893 ! nn_o ff_idx specifies the time_counter index within the model file894 ! nn_o ff_freq specifies number of time steps between read operations892 ! ooo_files specifies the files containing the model counterpart 893 ! nn_ooo_idx specifies the time_counter index within the model file 894 ! nn_ooo_freq specifies number of time steps between read operations 895 895 &namoff 896 o ff_files = "foo.nc" "foo.nc"897 nn_o ff_idx = 1 2898 nn_o ff_freq = 144896 ooo_files = "foo.nc" "foo.nc" 897 nn_ooo_idx = 1 2 898 nn_ooo_freq = 144 899 899 / 900 900 \end{verbatim} … … 1046 1046 \tiny 1047 1047 \begin{verbatim} 1048 o ff_files = "F.1.nc" "F.2.nc" "F.3.nc" "P.1.nc" "P.2.nc" "P.3.nc" "A.1.nc"1049 nn_o ff_idx = 1 1 1 1 1 1 11048 ooo_files = "F.1.nc" "F.2.nc" "F.3.nc" "P.1.nc" "P.2.nc" "P.3.nc" "A.1.nc" 1049 nn_ooo_idx = 1 1 1 1 1 1 1 1050 1050 \end{verbatim} 1051 1051 \end{alltt} … … 1060 1060 ! namoff Offline obs_oper namelist 1061 1061 !---------------------------------------------------------------------- 1062 ! o ff_files specifies the files containing the model counterpart1063 ! nn_o ff_idx specifies the time_counter index within the model file1064 ! nn_o ff_freq specifies number of time steps between read operations1062 ! ooo_files specifies the files containing the model counterpart 1063 ! nn_ooo_idx specifies the time_counter index within the model file 1064 ! nn_ooo_freq specifies number of time steps between read operations 1065 1065 &namoff 1066 o ff_files = "F.1.nc" "F.2.nc" "F.3.nc" "P.1.nc" "P.2.nc" "P.3.nc" "A.1.nc"1067 nn_o ff_idx = 1 1 1 1 1 1 11066 ooo_files = "F.1.nc" "F.2.nc" "F.3.nc" "P.1.nc" "P.2.nc" "P.3.nc" "A.1.nc" 1067 nn_ooo_idx = 1 1 1 1 1 1 1 1068 1068 / 1069 1069 !---------------------------------------------------------------------- … … 1122 1122 In certain cases it may be desirable to include both multiple model fields per 1123 1123 observation window with multiple match ups per observation. This can be achieved 1124 by specifying \textbf{nn\_o ff\_freq} as well as the class 4 settings. Care must1125 be taken in generating the o ff\_files list such that the files are arranged into1124 by specifying \textbf{nn\_ooo\_freq} as well as the class 4 settings. Care must 1125 be taken in generating the ooo\_files list such that the files are arranged into 1126 1126 consecutive blocks of single match ups. For example, 2 forecast fields 1127 1127 of 12 hourly data would result in 4 separate read operations but only 2 write … … 1131 1131 \tiny 1132 1132 \begin{verbatim} 1133 o ff_files = "F1.nc" "F1.nc" "F2.nc" "F2.nc"1133 ooo_files = "F1.nc" "F1.nc" "F2.nc" "F2.nc" 1134 1134 ... 1135 1135 cl4_fcst_idx = 1 2
Note: See TracChangeset
for help on using the changeset viewer.