Remove hard-coding of ESMValTool developer configuration file #212
Description
Follows #294
CMEW uses a hard copied and updated ESMValTool developer configuration file (in app/configure_process/config_files/config-developer.yml) containing the following changes (compared with the default ESMValTool developer configuration file present in the ESMValTool v2.9.0 community environment):
25,26d24
< # custom:
< # cmor_path: ~/my/own/custom_tables
28a27,42
> custom:
> cmor_path: /home/h03/cdds/etc/mip_tables/GCModelDev/0.0.9
>
> ESMVal:
> cmor_strict: true
> input_dir:
> default: '/'
> BADC: '{activity}/{institute}/{dataset}/{exp}/{ensemble}/{mip}/{short_name}/{grid}/{version}'
> DKRZ: '{activity}/{institute}/{dataset}/{exp}/{ensemble}/{mip}/{short_name}/{grid}/{version}'
> ESGF: '{project}/{activity}/{institute}/{dataset}/{exp}/{ensemble}/{mip}/{short_name}/{grid}/{version}'
> ETHZ: '{exp}/{mip}/{short_name}/{dataset}/{ensemble}/{grid}/'
> SYNDA: '{activity}/{institute}/{dataset}/{exp}/{ensemble}/{mip}/{short_name}/{grid}/{version}'
> input_file: '{short_name}_{mip}_{dataset}_{exp}_{ensemble}_{grid}*.nc'
> output_file: '{project}_{dataset}_{mip}_{exp}_{ensemble}_{short_name}_{grid}'
> cmor_type: 'CMIP6'
> cmor_default_table_prefix: 'GCModelDev_'The cmor_path must be equal to the mip_table_dir in the request.json file.
Note also that the default developer config format has evolved since the above was copied.
Acceptance criteria (needs refined):
- Given definition for minimal metadata for a project (="CMEW")
- When
configure_reciperuns - Then that information is written to disk in a way that ESMValTool finds it as its configuration
Technical implementation:
- Add
create_developer_config_filetoconfigure_recipe.pythat writes what is needed for the developer config. - Create the developer config file in same directory as the user config file as defined by Get CMEW to work with new-style ESMValTool configuration files #324.