Page History

...

These changes will then flow on to simulation installation and subsequently submission to the workflow.

User input

Currently any parameters that are to be included in the realisation (perturbed or not) are included in the additional options yaml file, while the perturbation values are given in the source uncertanities yaml file.

We intend to merge these files.

The nominal values and perturbation settings for each of these parameters will have to be given in the additional parameters source uncertainties yaml (as passed to gcmt2srf), with each parameter and its nominal value forming a key:value pair, and that pair itself being a value in a list where the component of the workflow it belongs to is the key of the list.The realisation-uncertainty file will remain as it is.

Each parameter that is given in the CMT solutions csv file will be at the top level, while each additional parameter will be nested inside the relevant process.

Each parameter will have at least two associated pieces of information, being the nominal value (mean) of the parameter, and the distribution. If the distribution requires any random variables, these must also be given.

An example is available below:

mw:
    distribution: uniform
    halfrange: 0.05
hf:
    sdrop: 
        mean: 50
        halfrange: 5
        distribution: uniform
    rvfac: 
        mean: 0.8
        std_dev: 0.01
        distribution: normal
    rvfac_shallow:
        mean: 0.7
        distribution: none
bb:
    fmin: 
        mean: 0.2
        distribution: uniform_relative
        scalefactor: 0.05

Internal changes

In order to simplify the implementation of this, we have chosen to have every parameter added to the slurm script and passed as an argument to the simulation script, which will then discard any parameters it does not recognize.

...

The parameters for each component are as follows: