| 1 |
=========== |
| 2 |
DRS Schemes |
| 3 |
=========== |
| 4 |
|
| 5 |
In order to support multiple projects beyond CMIP5, DRSlib has been extended to support multiple DRS schemes. The ``--scheme`` switch to ``drs_tool`` will allow you to select form a set of configured schemes, currently: |
| 6 |
|
| 7 |
1. CMIP5 (default) |
| 8 |
2. SPECS |
| 9 |
3. CORDEX |
| 10 |
|
| 11 |
Each scheme has a different set of DRS components and component ordering. |
| 12 |
|
| 13 |
When operating on projects other than CMIP5 drslib is designed to |
| 14 |
perform less metadata checks. These functions are now performed by |
| 15 |
drslib's sister tool `ceda-cc`_. The ``ceda_cc`` tool will verify |
| 16 |
files meet a project's metadata requirements and output a JSON file |
| 17 |
which can be used by drslib to deduce certain metadata values that are |
| 18 |
not apparent from the files. This JSON file is passed to ``drs_tool`` |
| 19 |
using the `--json-drs` option. |
| 20 |
|
| 21 |
.. _`ceda-cc`: https://pypi.python.org/pypi/ceda-cc |