|
2 | 2 | title: "Running your first recipe" |
3 | 3 | teaching: 15 |
4 | 4 | exercises: 15 |
5 | | -compatibility: ESMValTool v2.12.0 |
| 5 | +compatibility: ESMValTool v2.13.0 |
6 | 6 |
|
7 | 7 | questions: |
8 | 8 | - "How to run a recipe?" |
@@ -45,14 +45,18 @@ or if you have the user configuration file in your current directory then |
45 | 45 | ``` |
46 | 46 | esmvaltool run --config_dir . examples/recipe_python.yml |
47 | 47 | ``` |
48 | | - |
49 | 48 | If everything is okay, you should see that ESMValTool is printing a lot of |
50 | 49 | output to the command line. The final message should be "Run was successful". |
51 | 50 | The exact output varies depending on your machine, but it should look something |
52 | | -like the example log output on terminal below. |
| 51 | +like the example log output below. |
| 52 | + |
| 53 | +``` |
53 | 54 |
|
54 | 55 | {% include example_output.txt %} |
55 | 56 |
|
| 57 | +``` |
| 58 | +{: .output} |
| 59 | + |
56 | 60 | > ## Pro tip: ESMValTool search paths |
57 | 61 | > |
58 | 62 | > You might wonder how ESMValTool was able find the recipe file, even though |
@@ -132,8 +136,9 @@ distinguished in the log messages: |
132 | 136 | > > following line in the output: |
133 | 137 | > > |
134 | 138 | > > ``` |
135 | | -> >INFO [3966381] These tasks will be executed: timeseries/script1, |
136 | | -> > timeseries/tas_amsterdam, timeseries/tas_global, map/tas, map/script1 |
| 139 | +> > 2025-11-26 09:59:39,409 UTC [3098040] INFO These tasks will be executed: timeseries/tas_global, map/tas, map/script1, |
| 140 | +> > timeseries/tas_amsterdam, timeseries/script1 |
| 141 | +> > |
137 | 142 | > > ``` |
138 | 143 | > > |
139 | 144 | > > So there are three tasks related to timeseries: global temperature, |
|
0 commit comments