Skip to content

Commit f1aa106

Browse files
committed
add one challenge
1 parent 70f64f4 commit f1aa106

File tree

1 file changed

+21
-6
lines changed

1 file changed

+21
-6
lines changed

_episodes/03-configuration.md

Lines changed: 21 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,19 +14,18 @@ keypoints:
1414
- " ``output_dir`` is the destination directory."
1515
---
1616

17-
Contents:
18-
1917
Exercise: Copy the user config to your working area
2018
Exercise: Make site specific configuration information(ie the changes needed to you config-user.yml file before you can run)
2119

2220
## The configuration file
2321

2422
The ``config-user.yml`` configuration file contains all the global level information needed by ESMValTool to run.
25-
This is an [YAML file](https://yaml.org/spec/1.2/spec.html). An example configuration file can be found in the [root directory of the ESMValTool repository](https://github.com/ESMValGroup/ESMValTool/blob/master/config-user-example.yml).
26-
Let's download it in our working directory ``esmvaltool_tutorial`` that is made during the [Setup](https://esmvalgroup.github.io/tutorial/setup.html).
27-
Click on [this link](https://raw.githubusercontent.com/ESMValGroup/ESMValTool/master/config-user-example.yml) to see a raw version of the file, right-click and press save as, then you can rename it to ``config-user.yml`` and save it into the working directory ``esmvaltool_tutorial``.
23+
This is an [YAML file](https://yaml.org/spec/1.2/spec.html). An example configuration file can be found in the root directory of the ESMValTool repository: [config-user-example.yml](https://github.com/ESMValGroup/ESMValTool/blob/master/config-user-example.yml).
24+
25+
Let's download it to our working directory ``esmvaltool_tutorial`` that is made during the [Setup](https://esmvalgroup.github.io/tutorial/setup.html).
26+
To do that, click on [this link](https://raw.githubusercontent.com/ESMValGroup/ESMValTool/master/config-user-example.yml) to see a raw version of the file, right-click and press ``save as``, then you can rename it to ``config-user.yml`` and save it into the working directory ``esmvaltool_tutorial``.
2827

29-
Lets change our working directory to ``esmvaltool_tutorial``. Then, we run a text editor called Nano to open it:
28+
Now in a terminal, let's change our working directory to ``esmvaltool_tutorial``. Then, we run a text editor called Nano to open the configuration file:
3029

3130
~~~bash
3231
cd esmvaltool_tutorial
@@ -166,4 +165,20 @@ remove_preproc_dir: true
166165
profile_diagnostic: false
167166
~~~
168167

168+
> ## Make your own configuration file
169+
>
170+
> It is possible to have several configuration files with different purposes, for example: config-user_formalised_runs.yml, config-user_debugging.yml
171+
{: .callout}
172+
173+
> ## Set different preferences
174+
>
175+
> In the configuration file, which settings are useful to store preprocessed data?
176+
>
177+
>> ## Solution
178+
>>
179+
>> If the option ``save_intermediary_cubes`` is set to true in the config-user.yml file, then the intermediary cubes will also be saved in the folder ``preproc``. Also, if the option ``remove_preproc_dir`` is set to ``false``, then the ``preproc/`` directory contains all the preprocessed data and the metadata interface files.
180+
> {: .solution}
181+
{: .challenge}
182+
183+
169184
{% include links.md %}

0 commit comments

Comments
 (0)