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 |
Revision as of 08:22, 9 July 2015
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. 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
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.
# 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
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