RadApp: Difference between revisions

Line 33:

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.

'''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. (Somewhere I should provide an example HISTORY.rc to generate the needed datasets.)

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

=== Run the Module ===

Create a run directory and copy the files noted above into that space. Also copy the RadApp.x application from your build directory. Back in /discover/nobackup/pcolarco/demo_RadApp/run_RadApp I additionally provide an example run script ('''RadApp_run.j''') that you can use to drive the calculation. This is like the gcm_run.j you are used to from running GEOS-5. Note that you need to check paths for GEOSBIN and specify the usual PBS queueing stuff up top. When this runs you get a scratch sub-directory where everything is copied or linked and the output is stashed there until the run segment is complete, at which point it is moved to the local holding directory. If you additionally call the gcm_run.j script you can postprocess. You can also provide an archive script and move data to dirac.

@@ Line 33: / Line 33: @@
   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.
+'''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.  (Somewhere I should provide an example HISTORY.rc to generate the needed datasets.)
 '''HISTORY.rc''' specifies the output fields.  This should be variables specified in the radiation module.
+=== Run the Module ===
+Create a run directory and copy the files noted above into that space.  Also copy the RadApp.x application from your build directory.  Back in /discover/nobackup/pcolarco/demo_RadApp/run_RadApp I additionally provide an example run script ('''RadApp_run.j''') that you can use to drive the calculation.  This is like the gcm_run.j you are used to from running GEOS-5.  Note that you need to check paths for GEOSBIN and specify the usual PBS queueing stuff up top.  When this runs you get a scratch sub-directory where everything is copied or linked and the output is stashed there until the run segment is complete, at which point it is moved to the local holding directory.  If you additionally call the gcm_run.j script you can postprocess.  You can also provide an archive script and move data to dirac.