Running Doubly-Periodic Experiment: Difference between revisions

Line 4:

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:

A doubly periodic code is run through GEOSgcm.x like full the model.

Until code are incorporated you will need to make a few modifications and recompile to properly run a doubly periodic experiment. Please see a member of the software infrastructure team for details. Once you have recompiled you will need to setup an experiment. The easiest way is to do a normal setup with gcm_setup and modify the appropriate rc files.

First in the fvcore_layout.rc file the size of the domain is specified in meters like so:

dx_const: 13000

Line 12:

Line 15:

==Example AGCM.rc==

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.

Most of the changes will be needed in the AGCM.rc file. 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.

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. For now the DP is only setup to run over ocean with no land so the OGCM_IM and OGCM_JM are 1. All the restarts can be bootstrapped, hence the dashes in front of every one.

<pre>

# Atmospheric Model Configuration Parameters

Line 160:

Line 163:

==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

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.

@@ Line 4: / Line 4: @@
 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:
+A doubly periodic code is run through GEOSgcm.x like full the model.
+Until code are incorporated you will need to make a few modifications and recompile to properly run a doubly periodic experiment. Please see a member of the software infrastructure team for details. Once you have recompiled you will need to setup an experiment. The easiest way is to do a normal setup with gcm_setup and modify the appropriate rc files.
+First in the fvcore_layout.rc file the size of the domain is specified in meters like so:
 dx_const: 13000
@@ Line 12: / Line 15: @@
 ==Example AGCM.rc==
-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.
+Most of the changes will be needed in the AGCM.rc file. 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.
+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. For now the DP is only setup to run over ocean with no land so the OGCM_IM and OGCM_JM are 1. All the restarts can be bootstrapped, hence the dashes in front of every one.
 <pre>
 # Atmospheric Model Configuration Parameters
@@ Line 160: / Line 163: @@
 ==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
+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.