Skip to content

Commit 89146dd

Browse files
committed
fix line length
1 parent 3cfef8e commit 89146dd

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

_episodes/09-cmorization.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -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?
@@ -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_dir <directory of 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.
@@ -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_dir <directory of 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)