@@ -82,10 +82,12 @@ Let's dissect what's happening here.
8282> > 1 . The config file should be the one we edited in the previous episode,
8383> > something like ` /home/<username>/.esmvaltool/config-user.yml ` or
8484 ` ~/esmvaltool_tutorial/config-user.yml ` .
85- > > 1 . ESMValTool found the recipe in its installation directory, something like
85+ > > 1 . ESMValTool found the recipe in its installation directory,
86+ >> something like
8687> > ` /home/users/username/mambaforge/envs/esmvaltool/bin/esmvaltool/recipes/examples/ `
8788>> or if you are using a pre-installed module on a server, something like
88- `/apps/jasmin/community/esmvaltool/ESMValTool_<version> /esmvaltool/recipes/examples/recipe_python.yml`, where `<version> ` is the latest release.
89+ >> ` /apps/jasmin/community/esmvaltool/ESMValTool_<version>/esmvaltool/recipes/examples/recipe_python.yml ` ,
90+ >> where ` <version> ` is the latest release.
8991> > 1 . ESMValTool creates a time-stamped output directory for every run. In this
9092> > case, it should be something like ` recipe_python_YYYYMMDD_HHMMSS ` . This
9193> > folder is made inside the output directory specified in the previous
@@ -129,7 +131,8 @@ distinguished in the log messages:
129131> > following line in the output:
130132> >
131133> > ```
132- > >[18776] INFO These tasks will be executed: map/tas, timeseries/tas_global, timeseries/script1, map/script1, timeseries/tas_amsterdam
134+ > >[18776] INFO These tasks will be executed: map/tas, timeseries/tas_global,
135+ >>timeseries/script1, map/script1, timeseries/tas_amsterdam
133136> > ```
134137> >
135138> > So there are three tasks related to timeseries: global temperature,
0 commit comments