Running Doubly-Periodic Experiment: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
==Data files for doubly periodic experiment== | ==Data files for doubly periodic experiment== | ||
You will need an appropriate tile file named DPXXX.til where XXX is the resolution you are running. In addition since the OGCM_IM and OGCM_JM must be 1 you will need appropriately modified kpar.data, sst.data, and fraci.data files. | You will need an appropriate tile file named DPXXX.til where XXX is the resolution you are running. In addition since the OGCM_IM and OGCM_JM must be 1 you will need appropriately modified kpar.data, sst.data, and fraci.data files. | ||
==Overview== | |||
The doubly periodic capability in GEOS-5 allows one to run a simulation on an arbitrary Cartesian domain with periodicity in both dimensions. | |||
==Setup== | |||
A doubly periodic code is run through GEOSgcm.x like full the model. in the fvcore_layout.rc file the size of the domain is specified in meters like so: | |||
dx_const: 13000 | |||
dy_const: 13000 | |||
Thus for a given IM and JM you have a domain IMxJM grid on a Cartesian domain with size dx_const by dy_const. For now the domain and grid should be square, i.e. IM = JM. | |||
==Example AGCM.rc== | ==Example AGCM.rc== | ||
Below is snippets showing what needs to be changed in the AGCM.rc to perform a doubly periodic run. | Below is snippets showing what needs to be changed in the AGCM.rc to perform a doubly periodic run. Note the change in the grid name that alerts the model this is a doubly periodic setup. | ||
The most critical are the FIXED_LATS and FIXED_LONS keywords which tell where the cell is located. The CASE_ID, T0, and CASE_TRACERS values should be the values in the example below unless new cases get added in the future. | |||
<pre> | <pre> | ||
# Atmospheric Model Configuration Parameters | # Atmospheric Model Configuration Parameters | ||
Line 147: | Line 158: | ||
</pre> | </pre> | ||
==Other files== | |||
In addition you will need an appropriate tile file name DPXXX.til where XXX is the resolution as well as appropriate fraci.data, kpar.data, and sst.data files |