Running Doubly-Periodic Experiment: Difference between revisions
No edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| 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. | The doubly periodic capability in GEOS-5 allows one to run a simulation on an arbitrary Cartesian domain with periodicity in both dimensions. | ||
==Setup== | ==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 | dx_const: 13000 | ||
| Line 12: | Line 15: | ||
==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. 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> | <pre> | ||
# Atmospheric Model Configuration Parameters | # Atmospheric Model Configuration Parameters | ||
| Line 159: | Line 162: | ||
</pre> | </pre> | ||
==Example fvcore_layout.rc== | |||
<pre> | |||
ntiles: 1 | |||
grid_type: 4 | |||
dx_const: 7000. | |||
dy_const: 7000. | |||
test_case: 14 | |||
ADIABATIC: .false. | |||
hydrostatic: .false. | |||
nord: 0 | |||
d2_bg: 0.0075 | |||
d4_bg: 0.0 | |||
dddmp: 0.2 | |||
kd3: 0.0 | |||
fill_dp: .true. | |||
n_sponge: 0 | |||
d2_bg_k1: 0.2 | |||
d2_bg_k2: 0.2 | |||
ksplit: 4 | |||
nsplit: 15 | |||
msplit: 3 | |||
hord_mt: 10 | |||
hord_vt: 10 | |||
hord_tm: 10 | |||
hord_dp: 13 | |||
hord_tr: 13 | |||
kord_tm: -9 | |||
kord_mt: 9 | |||
kord_wz: 9 | |||
kord_tr: 9 | |||
remap_t: .false | |||
consv_te: .true. | |||
fv_debug: .false. | |||
FV_OFF: .false. | |||
inline_q: .false. | |||
z_tracer: .true. | |||
</pre> | |||
==Other files== | ==Other files== | ||
In addition | In addition to the changes to the AGCM.rc and fvcore_layout.rc files the doubly periodic case requires new boundary conditions. | ||
The files that need to be replaced are as follows: | |||
The normal tile file will need to be replaced and should have the name DPXXX.til. | |||
The doubly periodic case has one ocean point so you will need a fraci.data, kpar.data, and sst.data files that have the appropriate point extracted. | |||
Finally you will need dummy topography files for the topography and the gwd and turb variances since we are only simulating over ocean. A file that consists of one record of the appropriate IMxIM filled with zeros will suffice. The topography files can all be pointed to this file. | |||
Latest revision as of 14:44, 15 January 2016
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.
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. 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 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
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. 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.
# Atmospheric Model Configuration Parameters
# ------------------------------------------
NX: 12
NY: 12
AGCM_IM: 360
AGCM_JM: 360
AGCM_LM: 72
AGCM_GRIDNAME: PE360x360-DP
FIXED_LATS: 18.0
FIXED_LONS: 0.0
DYCORE: FV3
COLDSTART: 1
T0: 280.0
CASE_ID: 2
CASE_TRACERS: 1234
SOLAR_LOAD_BALANCE: 0
SOLAR_DT: 1800
IRRAD_DT: 1800
SOLARAvrg: 0
IRRADAvrg: 0
# Ocean Model Configuration Parameters
# ------------------------------------
OGCM_IM: 1
OGCM_JM: 1
OGCM_LM: 34
OGCM_GRIDNAME: PE1x1-DE
ANA_GRIDNAME: PE360x360-DP
# Required AGCM Model Restart Files
# ---------------------------------
DYN_INTERNAL_RESTART_FILE: -fvcore_internal_rst
DYN_INTERNAL_RESTART_TYPE: pbinary
DYN_INTERNAL_CHECKPOINT_FILE: fvcore_internal_checkpoint
DYN_INTERNAL_CHECKPOINT_TYPE: pbinary
DYN_INTERNAL_HEADER: 1
LAKE_INTERNAL_RESTART_FILE: -lake_internal_rst
LAKE_INTERNAL_RESTART_TYPE: binary
LAKE_INTERNAL_CHECKPOINT_FILE: lake_internal_checkpoint
LAKE_INTERNAL_CHECKPOINT_TYPE: binary
LANDICE_INTERNAL_RESTART_FILE: -landice_internal_rst
LANDICE_INTERNAL_RESTART_TYPE: binary
LANDICE_INTERNAL_CHECKPOINT_FILE: landice_internal_checkpoint
LANDICE_INTERNAL_CHECKPOINT_TYPE: binary
CATCH_INTERNAL_RESTART_FILE: -catch_internal_rst
CATCH_INTERNAL_RESTART_TYPE: binary
CATCH_INTERNAL_CHECKPOINT_FILE: catch_internal_checkpoint
CATCH_INTERNAL_CHECKPOINT_TYPE: binary
MOIST_INTERNAL_RESTART_FILE: +moist_internal_rst
MOIST_INTERNAL_RESTART_TYPE: pbinary
MOIST_INTERNAL_CHECKPOINT_FILE: moist_internal_checkpoint
MOIST_INTERNAL_CHECKPOINT_TYPE: pbinary
# Boot-Strapable AGCM Model Restart Files
# ---------------------------------------
MOIST_IMPORT_RESTART_FILE: -moist_import_rst
MOIST_IMPORT_RESTART_TYPE: pbinary
MOIST_IMPORT_CHECKPOINT_FILE: moist_import_checkpoint
MOIST_IMPORT_CHECKPOINT_TYPE: pbinary
SURFACE_IMPORT_RESTART_FILE: -surf_import_rst
SURFACE_IMPORT_RESTART_TYPE: binary
SURFACE_IMPORT_CHECKPOINT_FILE: surf_import_checkpoint
SURFACE_IMPORT_CHECKPOINT_TYPE: binary
SOLAR_INTERNAL_RESTART_FILE: -solar_internal_rst
SOLAR_INTERNAL_RESTART_TYPE: pbinary
SOLAR_INTERNAL_CHECKPOINT_FILE: solar_internal_checkpoint
SOLAR_INTERNAL_CHECKPOINT_TYPE: pbinary
IRRAD_INTERNAL_RESTART_FILE: -irrad_internal_rst
IRRAD_INTERNAL_RESTART_TYPE: pbinary
IRRAD_INTERNAL_CHECKPOINT_FILE: irrad_internal_checkpoint
IRRAD_INTERNAL_CHECKPOINT_TYPE: pbinary
TURBULENCE_INTERNAL_RESTART_FILE: -turb_internal_rst
TURBULENCE_INTERNAL_RESTART_TYPE: pbinary
TURBULENCE_INTERNAL_CHECKPOINT_FILE: turb_internal_checkpoint
TURBULENCE_INTERNAL_CHECKPOINT_TYPE: pbinary
TURBULENCE_IMPORT_RESTART_FILE: -turb_import_rst
TURBULENCE_IMPORT_RESTART_TYPE: pbinary
TURBULENCE_IMPORT_CHECKPOINT_FILE: turb_import_checkpoint
TURBULENCE_IMPORT_CHECKPOINT_TYPE: pbinary
PCHEM_INTERNAL_RESTART_FILE: -pchem_internal_rst
PCHEM_INTERNAL_RESTART_TYPE: pbinary
PCHEM_INTERNAL_CHECKPOINT_FILE: pchem_internal_checkpoint
PCHEM_INTERNAL_CHECKPOINT_TYPE: pbinary
# Chemistry/AEROSOL Model Restart Files
# -------------------------------------
GOCART_INTERNAL_RESTART_FILE: -gocart_internal_rst
GOCART_INTERNAL_RESTART_TYPE: pbinary
GOCART_INTERNAL_CHECKPOINT_FILE: gocart_internal_checkpoint
GOCART_INTERNAL_CHECKPOINT_TYPE: pbinary
#CARMA_INTERNAL_RESTART_FILE: carma_internal_rst
#CARMA_INTERNAL_RESTART_TYPE: pbinary
#CARMA_INTERNAL_CHECKPOINT_FILE: carma_internal_checkpoint
#CARMA_INTERNAL_CHECKPOINT_TYPE: pbinary
#STRATCHEM_INTERNAL_RESTART_FILE: stratchem_internal_rst
#STRATCHEM_INTERNAL_RESTART_TYPE: pbinary
#STRATCHEM_INTERNAL_CHECKPOINT_FILE: stratchem_internal_checkpoint
#STRATCHEM_INTERNAL_CHECKPOINT_TYPE: pbinary
#GMICHEM_INTERNAL_RESTART_FILE: gmichem_internal_rst
#GMICHEM_INTERNAL_RESTART_TYPE: pbinary
#GMICHEM_INTERNAL_CHECKPOINT_FILE: gmichem_internal_checkpoint
#GMICHEM_INTERNAL_CHECKPOINT_TYPE: pbinary
#MAM_INTERNAL_RESTART_FILE: mam_internal_rst
#MAM_INTERNAL_RESTART_TYPE: pbinary
#MAM_INTERNAL_CHECKPOINT_FILE: mam_internal_checkpoint
#MAM_INTERNAL_CHECKPOINT_TYPE: pbinary
# OCEAN Model Restart Files
# -------------------------
SALTWATER_INTERNAL_RESTART_FILE: +saltwater_internal_rst
SALTWATER_INTERNAL_RESTART_TYPE: pbinary
SALTWATER_INTERNAL_CHECKPOINT_FILE: saltwater_internal_checkpoint
SALTWATER_INTERNAL_CHECKPOINT_TYPE: pbinary
SALTWATER_IMPORT_RESTART_FILE: -saltwater_import_rst
SALTWATER_IMPORT_RESTART_TYPE: pbinary
SALTWATER_IMPORT_CHECKPOINT_FILE: saltwater_import_checkpoint
SALTWATER_IMPORT_CHECKPOINT_TYPE: pbinary
Example fvcore_layout.rc
ntiles: 1
grid_type: 4
dx_const: 7000.
dy_const: 7000.
test_case: 14
ADIABATIC: .false.
hydrostatic: .false.
nord: 0
d2_bg: 0.0075
d4_bg: 0.0
dddmp: 0.2
kd3: 0.0
fill_dp: .true.
n_sponge: 0
d2_bg_k1: 0.2
d2_bg_k2: 0.2
ksplit: 4
nsplit: 15
msplit: 3
hord_mt: 10
hord_vt: 10
hord_tm: 10
hord_dp: 13
hord_tr: 13
kord_tm: -9
kord_mt: 9
kord_wz: 9
kord_tr: 9
remap_t: .false
consv_te: .true.
fv_debug: .false.
FV_OFF: .false.
inline_q: .false.
z_tracer: .true.
Other files
In addition to the changes to the AGCM.rc and fvcore_layout.rc files the doubly periodic case requires new boundary conditions. The files that need to be replaced are as follows: The normal tile file will need to be replaced and should have the name DPXXX.til.
The doubly periodic case has one ocean point so you will need a fraci.data, kpar.data, and sst.data files that have the appropriate point extracted.
Finally you will need dummy topography files for the topography and the gwd and turb variances since we are only simulating over ocean. A file that consists of one record of the appropriate IMxIM filled with zeros will suffice. The topography files can all be pointed to this file.