You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _episodes/first_example_recipe.md
+99-76Lines changed: 99 additions & 76 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,11 +56,11 @@ Recipes are the instructions that you give to ESMValTool that tell it what you w
56
56
57
57
Note that the authors, publications and references are to be named in the config-references.yml
58
58
59
-
This information
59
+
This information ...
60
60
61
61
## How to run ESMValTool
62
62
63
-
Once you’ve set up your conda environment and installed ESMValTool (See episode #2) and set up your config-user.yml file to correctly match you local environment, (see episode #3), ESMValTool is invoked using a simple command:
63
+
Once you’ve set up your conda environment and installed ESMValTool (see episode #2 LINK) and set up your config-user.yml file to correctly match you local environment, (see episode #3 LINK), ESMValTool is invoked using a simple command:
> Use the command and investigate the sample recipe.
123
126
> ~~~
124
-
> vim recipe.yml
127
+
> vim recipe_example.yml
125
128
> ~~~
126
129
> {: .source}
127
130
>
128
-
> Please note the datasets, preprocessors, diagnostic sections.
131
+
132
+
Please note the following sections:
133
+
- documentation: lines 4-20
134
+
135
+
The documentation consists of the following information:
136
+
- description: a one line description of the recipe
137
+
- authors: a list of authors (linked to esmvaltool/config-references.yml)
138
+
- maintainer: a list of maintainers (linked to esmvaltool/config-references.yml)
139
+
- references: a list of references (linked to a bibtexfile in esmvaltool/references with the same name)
140
+
- projects: a list of projects (linked to esmvaltool/config-references.yml)
141
+
142
+
143
+
- datasets: lines 22-23
144
+
The dataset definition consists of a list of dictionaries with the information on the datasets.
145
+
[List of entries?]
146
+
147
+
148
+
- preprocessors: lines 25-28
149
+
The definition for different preprocessors or combinations.
150
+
[go into detail]
151
+
152
+
153
+
- diagnostic section: lines 30-42
154
+
The information of which diagnostic script to run with which variables.
155
+
[go into detail]
156
+
157
+
129
158
> What is the short_name of the variable being analysed?
130
159
> What is the diagnostic script being used?
131
160
> How many years of data are being analysed?
@@ -185,29 +214,23 @@ Please copy and paste the following recipe into your ESMValTool working area wit
185
214
{: .challenge}
186
215
187
216
188
-
> ## Common issues & tips
189
-
>
190
-
> ### Esmvaltool not found
191
-
> Can you run the command “esmvaltool -h”. If no, then it’s possible that the conda environment isn’t activated. Please return to the installation section, epside [2] LINK.
192
-
>
193
-
> ### ESMValTool can’t locate the data
194
-
> The error message is “esmvalcore._recipe_checks.RecipeError: Missing data”
195
-
> Which computing machine are you using? Does your user-config.yml file reflect your machine's settings? Is the dataset’s name in the correct order?
196
-
>
197
-
>
198
-
> ### Diagnostic path problems
199
-
> The directory path to your diagnostics code is set relative to the esmvaltool/diag_scripts subdirectory. Is the code placed in this subdirectory? Is it spelled correctly?
200
-
>
201
-
>
202
-
> ### FX files not found.
203
-
>
204
-
>
205
-
> ### The preprocessor works but the diagnostic fails:
206
-
> If your preprocessor works fine but your diagnostic script fails, congratulations! A failed diagnostic means that you won’t need to re-run the preprocessor. In your “run/main_log.txt” run output, you should see a line that reads: “To re-run this diagnostic script, run:”, followed by a line with a command that will allow you to re-run your diagnostic script only. Append this line with the “-i” option after the python script you call to re-run your diagnostic.
207
-
>
208
-
>
209
-
> ### Your recipe’s name/project/reference isn’t recognised by ESMValTool.
210
-
> Error message is “ValueError: Tag 'NAME' does not exist in section 'authors' of path/esmvaltool/config-references.yml”
211
-
> Most likely, you added your own name to the recipe in the description section, but didn’t add it to the esmvaltool/config-references.yml file, where the names are linked to an email address, institute, and ORCID Identity.
212
-
>
213
-
{: .callout}
217
+
## Common issues & tips
218
+
219
+
### Esmvaltool not found
220
+
Can you run the command “esmvaltool -h”. If no, then it’s possible that the conda environment isn’t activated. Please return to the installation section, epside [2] LINK.
221
+
222
+
### ESMValTool can’t locate the data
223
+
The error message is “esmvalcore._recipe_checks.RecipeError: Missing data”
224
+
Which computing machine are you using? Does your user-config.yml file reflect your machine's settings? Is the dataset’s name in the correct order?
225
+
226
+
### Diagnostic path problems
227
+
The directory path to your diagnostics code is set relative to the esmvaltool/diag_scripts subdirectory. Is the code placed in this subdirectory? Is it spelled correctly?
228
+
229
+
### FX files not found.
230
+
231
+
### The preprocessor works but the diagnostic fails:
232
+
If your preprocessor works fine but your diagnostic script fails, congratulations! A failed diagnostic means that you won’t need to re-run the preprocessor. In your “run/main_log.txt” run output, you should see a line that reads: “To re-run this diagnostic script, run:”, followed by a line with a command that will allow you to re-run your diagnostic script only. Append this line with the “-i” option after the python script you call to re-run your diagnostic.
233
+
234
+
### Your recipe’s name/project/reference isn’t recognised by ESMValTool.
235
+
Error message is “ValueError: Tag 'NAME' does not exist in section 'authors' of path/esmvaltool/config-references.yml”
236
+
Most likely, you added your own name to the recipe in the description section, but didn’t add it to the esmvaltool/config-references.yml file, where the names are linked to an email address, institute, and ORCID Identity.
0 commit comments