Skip to content

Science IT Interface

Eric Guilyardi edited this page Jun 26, 2018 · 4 revisions

PMP driver

The first version of the Science / IT interface has been designed using the PMP as the external driver (see Fig. 2). Current ENSO Metrics package code per se is in the lib directory while the PMP driver is in scripts.

Brief description of ENSO science routines in lib:

  • EnsoCollectionsLib.py contains the definition of metric collections (i.e. which metrics, observations, variables) are needed.
  • EnsoMetricsLib.py contains the definition and computation of individual metrics
  • EnsoComputeMetricsLib.py is the place where the actual computation is done (called by the driver)
  • EnsoToolsLib.py and EnsoErrorsWarnings.py contain tools and error handling needed by the rest of the package

Some internal pre-processing is using CDAT/CDMS, but with a clear separation of the code using CDAT/CDMS (e.g EnsoUvcdatToolsLib.py) so that it can be replaced by another package if needed by the external driver.

ESmValTool driver

The next step is to adapt the interface in Fig.1 to the ESMValTool workflow. Initial analysis shows that this first requires relocating a part of the pre-processing in the driver and, second, removing the dependency to CVAT/CDMS.

PMP ENSO Metrics workflow

Clone this wiki locally