RadApp: Difference between revisions

Line 22:

=== What is Needed to Run the Module? ===

The RadApp tool utilizes much of the underlying GEOS-5 infrastructure to function. For example, you use the usual HISTORY structure to generate output files. Additionally, RadApp requires inputs. These inputs use EXTDATA. So we need to provide certain resource files and input data in order to actually run the calculation.

The RadApp tool utilizes much of the underlying GEOS-5 infrastructure to function, and you can think about it much the same terms as running the overall GEOS-5 system.. For example, you use the usual HISTORY structure to generate output files. Additionally, RadApp requires inputs. These inputs use EXTDATA. So we need to provide certain resource files and input data in order to actually run the calculation.

To get the resource files there is an example set saved on /discover/nobackup/pcolarco/demo_RadApp/run_RadApp. Copy these:

AGCM.rc

CAP.rc

Chem_Registry.rc

Chem_MieRegistry.rc

ExtData.rc

HISTORY.rc

cap_restart

'''cap_restart''' is the usual starting YYYYMMDD HHMMSS start time for running the calculator. '''CAP.rc''' is the usual resource file for cycling and setting the end date. '''Chem_Registry.rc''' and '''Chem_MieRegistry.rc''' are the usual controls for the chemistry and assigning the Mie tables to the GOCART aerosols.

'''AGCM.rc''' is a simplified form of the main resource file from GEOS-5. You can control the IM, JM, and KM for the model resolution you want to run the calculator on. NX and NY are additionally specified to control how the global grid is tiled. The product NX*NY should match the total number of CPUs the model is run on. Note also the specification of the XX_OPTICS tables for the GOCART-like aerosol species that points to the band files. The model can be run against the climatological aerosols (AERO_PROVIDER: PCHEM and uncomment the AEROCLIM lines) or against archived aerosol mixing ratios (e.g., inst3d_aer_v files; using AERO_PROVIDER: RADENV).

'''ExtData.rc''' points to the input files needed to drive the calculation. These are the needed input fields from atmosphere, surface, and aerosols. These should be generated from some earlier GEOS-5 run. Fields will be interpolated to the current time step.

'''HISTORY.rc''' specifies the output fields. This should be variables specified in the radiation module.

@@ Line 22: / Line 22: @@
 === What is Needed to Run the Module? ===
-The RadApp tool utilizes much of the underlying GEOS-5 infrastructure to function.  For example, you use the usual HISTORY structure to generate output files.  Additionally, RadApp requires inputs.  These inputs use EXTDATA.  So we need to provide certain resource files and input data in order to actually run the calculation.
+The RadApp tool utilizes much of the underlying GEOS-5 infrastructure to function, and you can think about it much the same terms as running the overall GEOS-5 system..  For example, you use the usual HISTORY structure to generate output files.  Additionally, RadApp requires inputs.  These inputs use EXTDATA.  So we need to provide certain resource files and input data in order to actually run the calculation.
+To get the resource files there is an example set saved on /discover/nobackup/pcolarco/demo_RadApp/run_RadApp.  Copy these:
+ AGCM.rc
+ CAP.rc
+ Chem_Registry.rc
+ Chem_MieRegistry.rc
+ ExtData.rc
+ HISTORY.rc
+ cap_restart
+'''cap_restart''' is the usual starting YYYYMMDD HHMMSS start time for running the calculator.  '''CAP.rc''' is the usual resource file for cycling and setting the end date.  '''Chem_Registry.rc''' and '''Chem_MieRegistry.rc''' are the usual controls for the chemistry and assigning the Mie tables to the GOCART aerosols.
+'''AGCM.rc''' is a simplified form of the main resource file from GEOS-5.  You can control the IM, JM, and KM for the model resolution you want to run the calculator on.  NX and NY are additionally specified to control how the global grid is tiled.  The product NX*NY should match the total number of CPUs the model is run on.  Note also the specification of the XX_OPTICS tables for the GOCART-like aerosol species that points to the band files.  The model can be run against the climatological aerosols (AERO_PROVIDER: PCHEM and uncomment the AEROCLIM lines) or against archived aerosol mixing ratios (e.g., inst3d_aer_v files; using AERO_PROVIDER: RADENV).
+'''ExtData.rc''' points to the input files needed to drive the calculation.  These are the needed input fields from atmosphere, surface, and aerosols.  These should be generated from some earlier GEOS-5 run.  Fields will be interpolated to the current time step.
+'''HISTORY.rc''' specifies the output fields.  This should be variables specified in the radiation module.