Ensemble Applications in OOPS


There is one ensemble application available in OOPS that allows to run three types of experiments: Ensemble Forecast, Ensemble HofX and Ensemble Data Assimilation. Their purpose is to allow users to run forecast and data assimilation applications on all the members of an ensemble at once.

MPI partition

MPI_WORLD (the communicator containing all the tasks requested for running an application) is split into several separate communicators; as many as there are members in the ensemble. Each ensemble member is then run on one of these MPI communicators. The members only know about their designated communicator until the end of the run and at the moment there is no communication between different ensemble members. To run the Ensemble Application to completion correctly, you need to allocate \(members * typical number of tasks for your application\) MPI tasks.

Templated Ensemble Application

There is only one EnsembleApplication to handle all three options in OOPS. It is templated on APP and will create an Ensemble<APP> that runs an ensemble of the APP application you passed. For example, oops::EnsembleApplication<HofX> will run the Ensemble Hofx application while oops::EnsembleApplication<Variational> will run an Ensemble of Data Assimilation.

How to run an Ensemble Application

Like all the other applications in OOPS, the Ensemble Application takes a yaml file as argument. The yaml file for this application differs from the typical yaml files in that it will be a list of yaml files, see the example below to run EnsHofX with five members.

  - "testinput/ens_hofx_1.yaml"
  - "testinput/ens_hofx_2.yaml"
  - "testinput/ens_hofx_3.yaml"
  - "testinput/ens_hofx_4.yaml"
  - "testinput/ens_hofx_5.yaml"

The first member of the ensemble will run HofX with the first file in the list, the second one will run HofX with the second file, … In order to run an Ensemble Hofx with five members, you need a total of six yaml files (the one passed to the EnsembleApplication, plus one for each member). In this case, each ens_hofx_{i}.yaml file contains the exact HofX yaml file for member{i}.

More about how to write yaml files for: