-
Notifications
You must be signed in to change notification settings - Fork 49
/
example_e3sm.cfg
169 lines (142 loc) · 7.14 KB
/
example_e3sm.cfg
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
## This file contains the most common config options that a user on an E3SM
## supported machine might want to customize. The values are mostly the same
## as in mpas_analysis/default.cfg, the default config file, which has nearly
## all of the available config options.
## Usage:
## 1. Copy this file to a new name for a specific run (say myrun.cfg).
##
## 2. Modify any config options you want to change in your new config file.
## At a minimum, you need to specify:
## * [runs]/mainRunName -- A name for the run to be included plot titles
## and legends
## * [input]/baseDirectory -- The directory for the simulation results
## to analyze
## * [input]/mpasMeshName -- The name of the MPAS ocean/sea ice mesh
## * [output]/baseDirectory -- The directory for the analysis results
##
## 3. run:
##
## $ mpas_analysis myrun.cfg
##
## This will read the configuration first from mpas_analysis/default.cfg
## and then replace that configuration with any changes from from myrun.cfg
##
## 4. If you want to run a subset of the analysis, you can either set
## [output]/generate in your config file or use the --generate flag on the
## command line. See the comments for [output]/generate below for more
## details on this option.
[runs]
## options related to the run to be analyzed and control runs to be
## compared against
# mainRunName is a name that identifies the simulation being analyzed.
mainRunName = runName
# config file for a control run to which this run will be compared. The
# analysis should have already been run to completion once with this config
# file, so that the relevant MPAS climatologies already exist and have been
# remapped to the comparison grid. Leave this option commented out if no
# control run is desired.
# controlRunConfigFile = /path/to/config/file
# config file for a main run on which the analysis was already run to
# completion. The relevant MPAS climatologies already exist and have been
# remapped to the comparison grid and time series have been extracted.
# Leave this option commented out if the analysis for the main run should be
# performed.
# mainRunConfigFile = /path/to/config/file
[input]
## options related to reading in the results to be analyzed
# directory containing model results
baseDirectory = /dir/for/model/output
# Note: an absolute path can be supplied for any of these subdirectories.
# A relative path is assumed to be relative to baseDirectory.
# In this example, results are assumed to be in <baseDirecory>/run
# subdirectory containing restart files
runSubdirectory = run
# subdirectory for ocean history files
oceanHistorySubdirectory = run
# subdirectory for sea ice history files
seaIceHistorySubdirectory = run
# names of namelist and streams files, either a path relative to baseDirectory
# or an absolute path.
oceanNamelistFileName = run/mpaso_in
oceanStreamsFileName = run/streams.ocean
seaIceNamelistFileName = run/mpassi_in
seaIceStreamsFileName = run/streams.seaice
# name of the ocean and sea-ice mesh (e.g. EC30to60E2r2, WC14to60E2r3,
# ECwISC30to60E2r1, SOwISC12to60E2r4, oQU240, etc.)
mpasMeshName = mesh
[output]
## options related to writing out plots, intermediate cached data sets, logs,
## etc.
# directory where analysis should be written
# NOTE: This directory path must be specific to each test case.
baseDirectory = /dir/for/analysis/output
# provide an absolute path to put HTML in an alternative location (e.g. a web
# portal). Uncomment the following and edit the "/dir/for/web/output"
# subdirectory to place your output in your own subdirectory on the web portal.
# htmlSubdirectory = ${web_portal:base_path}/${web_portal:username}/dir/for/web/output
htmlSubdirectory = html
# a list of analyses to generate. Valid names can be seen by running:
# mpas_analysis --list
# This command also lists tags for each analysis.
# Shortcuts exist to generate (or not generate) several types of analysis.
# These include:
# 'all' -- all analyses will be run
# 'all_publicObs' -- all analyses for which observations are available on the
# public server (the default)
# 'all_<tag>' -- all analysis with a particular tag will be run
# 'all_<component>' -- all analyses from a given component (either 'ocean'
# or 'seaIce') will be run
# 'only_<component>', 'only_<tag>' -- all analysis from this component or
# with this tag will be run, and all
# analysis for other components or
# without the tag will be skipped
# 'no_<task_name>' -- skip the given task
# 'no_<component>', 'no_<tag>' -- in analogy to 'all_*', skip all analysis
# tasks from the given component or with
# the given tag. Do
# mpas_analysis --list
# to list all task names and their tags
# an equivalent syntax can be used on the command line to override this
# option:
# mpas_analysis config.analysis --generate \
# only_ocean,no_timeSeries,timeSeriesSST
#
# Note: if an appropriate reference year isn't available for computing
# anomalies, include 'no_anomaly' in the generate list
generate = ['all_publicObs']
[climatology]
## options related to producing climatologies, typically to compare against
## observations and previous runs
# the year from which to compute anomalies if not the start year of the
# simulation. This might be useful if a long spin-up cycle is performed and
# only the anomaly over a later span of years is of interest.
# anomalyRefYear = 249
# the first year over which to average climatalogies
startYear = 11
# the last year over which to average climatalogies
endYear = 20
[timeSeries]
## options related to producing time series plots, often to compare against
## observations and previous runs
# the year from which to compute anomalies if not the start year of the
# simulation. This might be useful if a long spin-up cycle is performed and
# only the anomaly over a later span of years is of interest.
# anomalyRefYear = 249
# start and end years for timeseries analysis. Use endYear = end to indicate
# that the full range of the data should be used. If errorOnMissing = False,
# the start and end year will be clipped to the valid range. Otherwise, out
# of bounds values will lead to an error. In a "control" config file used in
# a "main vs. control" analysis run, the range of years must be valid and
# cannot include "end" because the original data may not be available.
startYear = 1
endYear = end
[index]
## options related to producing nino index.
# start and end years for El Nino 3.4 analysis. Use endYear = end to indicate
# that the full range of the data should be used. If errorOnMissing = False,
# the start and end year will be clipped to the valid range. Otherwise, out
# of bounds values will lead to an error. In a "control" config file used in
# a "main vs. control" analysis run, the range of years must be valid and
# cannot include "end" because the original data may not be available.
startYear = 1
endYear = end