Skip to content

Commit 0052710

Browse files
authored
Merge pull request #380 from ESMValGroup/update_cmorization_v2.13.0
Update cmorization episode for v2.13.0
2 parents effcf18 + 89146dd commit 0052710

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

_episodes/09-cmorization.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "CMORization: adding new datasets to ESMValTool"
33
teaching: 15
44
exercises: 45
5-
compatibility: ESMValTool v2.11.0
5+
compatibility: ESMValTool v2.13.0
66

77
questions:
88
- "CMORization: what is it and why do we need it?"
@@ -28,7 +28,7 @@ that follow the CMOR standards. Unfortunately, not all datasets follow these
2828
standards. In order to use such datasets in ESMValTool we first need to reformat
2929
the data. This process is called "CMORization".
3030

31-
More detailed informations can be found in the
31+
More detailed informations can be found in the
3232
[Documentation](https://docs.esmvaltool.org/en/latest/develop/dataset.html).
3333

3434
> ## What are the CMOR standards?
@@ -123,7 +123,7 @@ run the existing one. There is a specific command available in the ESMValTool to
123123
run the CMORizer scripts:
124124

125125
```bash
126-
esmvaltool data format --config_file <path to config-user.yml> <dataset-name>
126+
esmvaltool data format --config_dir <directory of config-user.yml> <dataset-name>
127127
```
128128

129129
The options `--start` and `--end` can be added to command above to restrict the
@@ -290,7 +290,8 @@ CMORized, ESMValTool will give a warning or error.
290290
Try to run the example recipe with
291291

292292
```bash
293-
esmvaltool run recipe_check_fluxcom.yml --config_file <path to config-user.yml> --log_level debug
293+
esmvaltool run recipe_check_fluxcom.yml --config_dir <directory of config-user.yml>
294+
--log_level debug
294295
```
295296

296297
If everything is okay, the recipe should run without problems.
@@ -413,7 +414,7 @@ You can try running the CMORizer at this point, and it should work without
413414
errors. However, it doesn't produce any output yet:
414415

415416
```bash
416-
esmvaltool data format --config_file <path to config-user.yml> FLUXCOM
417+
esmvaltool data format --config_dir <directory of config-user.yml> FLUXCOM
417418
```
418419

419420
### 1. Find the input data
@@ -643,7 +644,8 @@ rootpath:
643644
If we now run the test recipe on our newly 'CMORized' data,
644645

645646
```bash
646-
esmvaltool run recipe_check_fluxcom.yml --config_file <path to config-user.yml> --log_level debug
647+
esmvaltool run recipe_check_fluxcom.yml --config_dir <directory of config-user.yml>
648+
--log_level debug
647649
```
648650

649651
it should be able to find the correct file, but it does not succeed yet. The ESMValTool CMOR checker

0 commit comments

Comments
 (0)