@@ -329,7 +329,8 @@ shortly. The last three arguments will not be considered in this script but
329329can be used in other cases. ``cfg_user`` corresponds to the user configuration
330330file, ``start_date`` to the start of the period to format, and ``end_date`` to
331331the end of the period to format. When you type the command ``esmvaltool data format``
332- in the terminal, ESMValTool will call this function with the settings found in your configuration files.
332+ in the terminal, ESMValTool will call this function with the settings found in
333+ your configuration files.
333334
334335The ESMValTool CMORizer also needs a dataset configuration file. Create a file
335336called `~/ESMValTool/esmvaltool/cmorizers/data/cmor_config/FLUXCOM.yml`
@@ -402,7 +403,8 @@ and the output should contain something like this:
402403
403404~~~
404405... in_dir: '/home/peter/data/RAWOBS/Tier3/FLUXCOM'
405- ... cfg: '{'attributes': {'project_id': 'OBS6', 'comment': ''}, 'cmor_table': <esmvalcore.cmor.table.CMIP6Info object at 0x7fbd0a0f6bf0>}'
406+ ... cfg: '{'attributes': {'project_id': 'OBS6', 'comment': ''},
407+ ' cmor_table ' : <esmvalcore.cmor.table.CMIP6Info object at 0x7fbd0a0f6bf0>}'
406408~~~
407409{: .output}
408410
@@ -782,7 +784,8 @@ Once everything works as expected, there's a couple of things that we can still
782784
783785
784786- **Fill the dataset information list**. The file
785- [datasets.yml](https://github.com/ESMValGroup/ESMValTool/blob/main/esmvaltool/cmorizers/data/datasets.yml)
787+ [datasets.yml](https://github.com/ESMValGroup/ESMValTool/blob/main/esmvaltool/
788+ cmorizers/data/datasets.yml)
786789 contains the ESMValTool "tier", the data source, the last access time and
787790 download instructions for all supported datasets in ESMValTool. You can
788791 simply reuse the information written in the header of the CMORizer.
0 commit comments