296 |
\paragraph{Example configuration} ~ \\ |
\paragraph{Example configuration} ~ \\ |
297 |
% |
% |
298 |
The following block is taken from the \texttt{data.exf} file |
The following block is taken from the \texttt{data.exf} file |
299 |
of the veification experiment \texttt{global\_with\_exf/}. |
of the verification experiment \texttt{global\_with\_exf/}. |
300 |
It defines attributes for the heat flux variable \texttt{hflux}: |
It defines attributes for the heat flux variable \texttt{hflux}: |
301 |
|
|
302 |
\begin{verbatim} |
\begin{verbatim} |
317 |
Next record is 2592000 seconds (or 30 days) later. |
Next record is 2592000 seconds (or 30 days) later. |
318 |
Note that the first record read and used by the EXF package corresponds to the |
Note that the first record read and used by the EXF package corresponds to the |
319 |
value 'startDate1' set in data.cal. Therefore if you want to start the EXF |
value 'startDate1' set in data.cal. Therefore if you want to start the EXF |
320 |
forcing from later in the 'ncep_qnet.bin' file, it suffices to specify |
forcing from later in the 'ncep\_qnet.bin' file, it suffices to specify |
321 |
startDate1 in data.cal as a date later than 19920101 (for example, startDate1 |
startDate1 in data.cal as a date later than 19920101 (for example, startDate1 |
322 |
= 19940101, for starting January 1st, 1994). For this to work, |
= 19940101, for starting January 1st, 1994). For this to work, |
323 |
'ncep_qnet.bin' must have at least 2 years of data because in this |
'ncep\_qnet.bin' must have at least 2 years of data because in this |
324 |
configuration EXF will read 2 years into the file to find the 1994 starting |
configuration EXF will read 2 years into the file to find the 1994 starting |
325 |
value. |
value. |
326 |
Interpolation on-the-fly is used (in the present case trivially |
Interpolation on-the-fly is used (in the present case trivially |