Configuration and Running

Python API (preferred method)

Configuration

Before runnning the diagnostics, a python script must be prepared to specify parameters for running the diags.

  1. Create a Python script, ex: run_e3sm_diags.py. This script contains pairs of keys and values, as well as commands to run. At minimum, you must define values for the following:

  • reference_data_path [REQUIRED]: Path to the reference (obs) data. If there are multiple datasets in the path, use ref_name parameter to specify which dataset should be used.

  • results_dir [REQUIRED]: The name of the folder where all runs will be stored.

  • test_data_path [REQUIRED]: Path to the test (model) data.

  1. There are many other parameters that allow the user to customize regridding method, plotting backend, and much more. See available parameters for a description.

An example run_e3sm_diags.py script is shown below.

import os
from acme_diags.parameter.core_parameter import CoreParameter
from acme_diags.run import runner

param = CoreParameter()

param.reference_data_path = '/p/user_pub/e3sm/e3sm_diags_data/obs_for_e3sm_diags/climatology/'
param.test_data_path = '/p/user_pub/e3sm/e3sm_diags_data/test_model_data_for_acme_diags/climatology/'
param.test_name = '20161118.beta0.FC5COSP.ne30_ne30.edison'
param.seasons = ["ANN"]   #all seasons ["ANN","DJF", "MAM", "JJA", "SON"] will run,if comment out"

prefix = '/var/www/acme/acme-diags/zhang40/tests/'
param.results_dir = os.path.join(prefix, 'lat_lon_demo')
param.multiprocessing = True
param.num_workers = 32
#use below to run all core sets of diags:
#runner.sets_to_run = ['lat_lon','zonal_mean_xy', 'zonal_mean_2d', 'polar', 'cosp_histogram', 'meridional_mean_2d']
#use below to run lat_lon map only
runner.sets_to_run = ['lat_lon']
runner.run_diags([param])

To add your own diagnostics, create a cfg file like the one below, which we call mydiags.cfg. (Any available parameters can also serve as keys in the cfg file.)

[#]
# What sets to run this diagnostics on
sets = ['lat_lon']

# Diagnostics results are saved in a folder named after the case_id
case_id = "lat_lon_MERRA"

# variables, ref_name, and season are keywords for obs file searching
variables = ["T"]
ref_name = "MERRA"
seasons = ["ANN", "JJA"]

# Name of the observation that will appear on the output plot
reference_name = "MERRA Analysis 1979-2013 NASA"

# User-specified pressure levels
plevs = [200.0, 850.0]

# User-defined regions, the default region is "global" if region is empty
# Find default_regions.py in this repo for a list of all possible regions
regions = ["land", "ocean_TROPICS"]

If you have multiple diagnostics you want to run, create a cfg file with multiple entries:

[#]
# put all of the parameters for a diags run here

[#]
# another diags run

[#] is a special title can be used for multiple runs. When used as a title, you don’t need to create a new, unique title for that diagnostics run.

Running

If you don’t have your own diagnostic file (e.g. mydiags.cfg), simply run:

python run_e3sm_diags.py

to generate the standard set of E3SM diagnostics figures. If you do have your own own diagnostic file, specify it on the command line:

python run_e3sm_diags.py -d mydiags.cfg

View the results by opening index.html in the location specified.

See examples for model vs model, observation vs observation, and model vs observation runs.

e3sm_diags -p (older method)

Configuration

Before runnning the diagnostics, a python script must be prepared to specify parameters for running the diags.

  1. Create a Python script, ex: myparams.py. This script contains simply pairs of keys and values. At minimum, you must define values for the following:

  • reference_data_path: path to the reference (observational) data

  • test_data_path: path to the test (model output) data

  • test_name: name of the test (model output) file

  1. There are many other parameters that allow the user to customize regridding method, plotting backend, and much more. See available parameters for a description.

An example myparams.py script is shown below.

reference_data_path = '/p/user_pub/e3sm/e3sm_diags_data/obs_for_e3sm_diags/climatology/'
test_data_path = '/p/user_pub/e3sm/e3sm_diags_data/test_model_data_for_acme_diags/climatology/'

test_name = '20161118.beta0.FC5COSP.ne30_ne30.edison'

# a few optional parameters

results_dir = 'myresults'  # name of folder where all results will be stored

To add your own diagnostics, create a cfg file like the one below, which we call mydiags.cfg. (Any available parameters can also serve as keys in the cfg file.)

[#]
# What sets to run this diagnostics on
sets = ['lat_lon']

# Diagnostics results are saved in a folder named after the case_id
case_id = "lat_lon_MERRA"

# variables, ref_name, and season are keywords for obs file searching
variables = ["T"]
ref_name = "MERRA"
seasons = ["ANN", "JJA"]

# Name of the observation that will appear on the output plot
reference_name = "MERRA Analysis 1979-2013 NASA"

# User-specified pressure levels
plevs = [200.0, 850.0]

# User-defined regions, the default region is "global" if region is empty
# Find default_regions.py in this repo for a list of all possible regions
regions = ["land", "ocean_TROPICS"]

If you have multiple diagnostics you want to run, create a cfg file with multiple entries:

[#]
# put all of the parameters for a diags run here

[#]
# another diags run

[#] is a special title can be used for multiple runs. When used as a title, you don’t need to create a new, unique title for that diagnostics run.

Running

If you don’t have your own diagnostic file (e.g. mydiags.cfg), simply run:

e3sm_diags -p myparams.py

to generate the standard set of E3SM diagnostics figures. If you do have your own own diagnostic file, specify it on the command line:

e3sm_diags -p myparams.py -d mydiags.cfg

View the results by opening index.html in the location specified.