Analysis File Format
The user guide illustrates various use cases for EOS that mostly cover relatively simple phenomenological analyses, with a small number of observables, parameters, and statistical constraints. Typical analyses carried out with EOS, however, require a high degree of organisation, as discussed in the example on analysis organisation. To support this, EOS provides the means to store one or more analyses within an external text file, a so-called analysis file.
This is particularly beneficial when several analyses share common elements, such as:
the same named priors (e.g. a shared set of form-factor priors);
the same experimental and theoretical likelihoods (e.g. a common set of measurements and lattice-QCD constraints);
the same definitions of custom observables and parameters.
A typical case is a pair of analyses that use identical likelihoods and differ only in their statistical model — for instance, one inferring the CKM matrix element \(|V_{ub}|\) and another inferring the corresponding Wilson coefficients from the same set of measurements. Every analysis file is a YAML file that defines the individual steps of one or more Bayesian analyses. At the top level, the format recognizes the following YAML keys / sections.
The following keys are mandatory:
priorsA list of named priors. Each prior assigns a prior probability density to one or more parameters — for example a uniform or Gaussian density on a single parameter, or a (correlated) multivariate density taken from a built-in EOS constraint. Priors are referenced by name when assembling a posterior.
likelihoodsA list of named likelihoods. Each likelihood combines one or more contributions: experimental measurements and theoretical constraints from EOS’s built-in database, constraints specified inline within the file, or a likelihood imported from a
pyhfworkspace. Likelihoods are likewise referenced by name when assembling a posterior.posteriorsA list of named posteriors. Each posterior is built by combining one or more of the named priors and likelihoods defined above, optionally fixing parameters or setting global options. The posteriors are the objects on which the inference tasks — sampling, optimisation, and prediction — operate.
The following keys are optional:
metadataOptional bibliographic information about the analysis, such as a title, a unique identifier, and a list of authors with their affiliations and contact details. This information is purely descriptive and does not affect the inference.
observablesA list of custom observables defined for the scope of the analysis. Each entry introduces a new named observable from an expression, following the syntax for defining new observables, which can then be used like any built-in observable elsewhere in the file.
parametersA list of new parameters defined for the scope of the analysis. Each entry either introduces a genuinely new parameter or defines an alias for one or more existing parameters; the latter is useful to impose symmetries (e.g. lepton-flavour universality) by varying several parameters together.
signal_pdfsA list of custom signal PDFs. Each entry introduces a new truth-level signal PDF from two observables, its unnormalized density and its normalization, which can then be fitted in an unbinned likelihood.
predictionsA list of theory predictions. Each entry specifies a set of observables to be evaluated on the samples of a posterior, optionally at several kinematic configurations, and is used to propagate the inferred uncertainties to derived quantities.
figuresA list of figures to be produced from the results of the analysis. Each figure follows the dedicated figure description format and is rendered by the plotting tasks.
stepsA list of steps that make the analysis reproducible. Each step bundles one or more tasks (such as sampling or plotting) together with their arguments, and may declare dependencies on earlier steps, so that the whole analysis can be executed in a well-defined order.
masksA list of masks for filtering posterior samples. Each mask selects a subset of samples by combining one or more (pseudo-)observables, which is useful, for example, to isolate a single mode of a multi-modal posterior.
Each of these keys, and the entries it accepts, corresponds to a class in the
eos.analysis_file_description module. These classes, which document the meaning of every key,
are listed among the analysis file description classes in the Python API reference.
Note
For a complete, real-world example of an analysis file, see the Example section at the end of this page.
Priors
The priors key contains a list of named priors. Each prior has two mandatory keys:
name(mandatory) — The unique name of this prior.
descriptions(mandatory) — The ordered list of parameters described by this prior.
Each prior description is a key/value map whose type key selects the kind of prior; the same format is used in the Analysis constructor.
A univariate prior has a single description, while an uncorrelated multivariate prior has one description per parameter.
For example, the following code creates two named priors CKM (univariate) and FF-pi (multivariate but uncorrelated).
priors:
- name: CKM
descriptions:
- { 'parameter': 'CKM::abs(V_ub)', 'min': 3.0e-3, 'max': 4.0e-3, 'type': 'uniform' }
- name: FF-pi
descriptions:
- { 'parameter': 'B->pi::f_+(0)@BCL2008' , 'min': 0.21 , 'max': 0.32 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_+^1@BCL2008' , 'min': -2.96 , 'max': -0.60 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_+^2@BCL2008' , 'min': -3.98 , 'max': 4.38 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_+^3@BCL2008' , 'min': -18.30 , 'max': 9.27 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^1@BCL2008' , 'min': -0.10 , 'max': 1.35 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^2@BCL2008' , 'min': -2.08 , 'max': 4.65 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^3@BCL2008' , 'min': -4.73 , 'max': 9.07 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^4@BCL2008' , 'min': -60.00 , 'max': 38.00 , 'type': 'uniform' }
- { 'parameter': 'B->pi::f_T(0)@BCL2008' , 'min': 0.18 , 'max': 0.32 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_T^1@BCL2008' , 'min': -3.91 , 'max': -0.33 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_T^2@BCL2008' , 'min': -4.32 , 'max': 2.00 , 'type': 'uniform' }
- { 'parameter': 'B->pi::b_T^3@BCL2008' , 'min': -7.39 , 'max': 10.60 , 'type': 'uniform' }
A type: constraint description instead draws a (possibly correlated, multivariate) prior from a built-in EOS constraint, named by the constraint key.
The following example illustrates such a prior.
priors:
- name: FF-rho
descriptions:
- { 'type': 'constraint', 'constraint': 'B->rho::FormFactors[parametric,LCSR]@BSZ:2015A' }
Each prior description’s type key selects one of the following:
type |
description |
Python class |
|---|---|---|
|
Describes a (possibly correlated, multivariate) prior taken from a built-in EOS constraint. |
|
|
Describes a uniform (flat) prior on a single parameter. |
|
|
Describes a prior on a renormalization scale parameter. |
|
|
Describes a Gaussian prior on a single parameter. |
|
|
Describes a Poisson prior on a single parameter. |
|
|
Describes a uniform prior on variables \(y\), related to several parameters \(x\) by \(x = T y + s\). |
Likelihoods
The likelihoods key contains a list of named likelihoods. Each likelihood has two mandatory keys:
name(mandatory) — The unique name of this likelihood.
constraintsormanual_constraintsorpyhf(mandatory, unlesstype: 'unbinned'is given) — The ordered list of EOS objects that comprise this likelihood.
A likelihood may also carry an explicit type key. It is presently only required for type: 'unbinned'; otherwise the kind is inferred from which of constraints, manual_constraints, or pyhf is present.
The likelihoods can be of four types:
constraintsThe following example illustrates the organisation of a likelihood for a simple constraint. Each such constraint is described by aConstraintLikelihoodDescription.- name: EXP-pi constraints: - 'B^0->pi^-l^+nu::BR@HFLAV:2019A;form-factors=BCL2008-4'
manual_constraintsAdditional manually-specified constraints can also be added. The syntax needs to follow the syntax of the usualEOS constraints, as in the following example. Each entry is described by aManualConstraintDescription.- name: manual-TH-pi manual_constraints: "B->pi::form-factor-ratio": type: "Gaussian" observable: "B->pi::f_0(q2)/f_+(q2)" kinematics: {'q2': 0} options: {'form-factors': 'BSZ2015'} mean: 1 sigma-stat: {"hi": 0., "lo": 0.} sigma-sys: {"hi": 0.1, "lo": 0.1}
pyhfA likelihood can also be imported from a pyhf workspace, which provides a HistFactory statistical model. The import is described by aPyHFConstraintDescription.The
pyhfkey accepts a mandatoryfilekey, giving the path to the JSON file that specifies the workspace, and an optionalparameter_mapkey. In the simplest case only the workspace file is given:- name: EXP-pyhf pyhf: file: workspace_uncorr.jsonIf no
parameter_mapis given, each free parameter of the pyhf model is exposed as an EOS parameter namedpyhf::<name>. Such a parameter — for instancepyhf::mu— can then be constrained by a prior like any other EOS parameter:priors: - name: EXP-pyhf-params descriptions: - { 'parameter': 'pyhf::mu', 'min': -2, 'max': 6, 'type': 'uniform' }By providing a
parameter_map, a pyhf parameter is instead identified with an existing EOS observable or parameter, optionally fixing its kinematics and options. The pyhf likelihood then depends on EOS theory predictions and can be combined coherently with the other likelihoods and parameters of the analysis. For example, the following maps the pyhf parametermuonto the EOS observableB->pilnu::muevaluated over the givenq2range:- name: EXP-pyhf pyhf: file: workspace_corr.json parameter_map: mu: { 'name': 'B->pilnu::mu', 'kinematics': { 'q2_min': 1.0e-7, 'q2_max': 25.0 } }
type: 'unbinned'A likelihood can be an unbinned likelihood over individually observed events, rather than over binned or integrated observables. The truth-levelSignalPDFis convolved with a detector resolution and evaluated at each observed event; seeDetectorLevelPDF.Such a component is mutually exclusive with
constraints,manual_constraintsandpyhf. The observed events and the resolution live in aUnbinnedLikelihooddirectory, referenced by thedatakey; theoptionsapply to both the signal PDF and the resolution; as for constraints, the posterior’sglobal_optionssupersede them.- name: EXP-unbinned type: 'unbinned' pdf: 'B->Dlnu::P(q2,cos(theta_l))' options: { 'l': 'mu', 'q': 'd' } data: './data/observed-events'The data object declares the native sampling grid. The optional
axeskey crops it to a window, one entry per axis, whose bounds are moved outward onto the nearest enclosing nodes of the native grid; the node spacing is never changed, so the point count follows from the data object and the two cannot disagree. An axis omitted here keeps its full native range. Events outside the cropped axes do not enter the likelihood; their number is reported as a warning.axes: - { 'variable': 'q2', 'min': 1.0, 'max': 9.0 } - { 'variable': 'cos(theta_l)', 'min': -1.0, 'max': 1.0 }The optional
windowskey restricts the fit further to a union of non-overlapping boxes within the cropped axes, e.g. to exclude a region of the spectrum. Each box is a list of intervals, at most one per variable; a variable omitted from a box keeps its full cropped range. Only events within one of the boxes enter the likelihood, and the detector-level PDF is normalized over the union of the boxes rather than over the range of the truth-level PDF. Unlikeaxes, the boxes do not change the grid on which the convolution is computed.windows: - [ { 'variable': 'q2', 'min': 1.0, 'max': 6.0 } ] - [ { 'variable': 'q2', 'min': 7.0, 'max': 9.0 }, { 'variable': 'cos(theta_l)', 'min': -0.5, 'max': 0.5 } ]Because the underlying convolution uses a real discrete Fourier transform, every axis must end up with an even number of points; a crop that yields an odd count is rejected rather than silently adjusted. For a resolution supplied as numerical samples, the optional
tolerancekey (default1.0e-9) sets the tolerance used when checking that the samples’ declared offset grid matches the grid the fit requires. A resolution supplied as an expression (kind: expression) is sampled anew whenever the parameters change, and may therefore depend on them.For a resolution supplied as an expression, the optional
poleskey declares the poles of the truth-level amplitude, one entry per pole; all poles must lie in the same sampling variable. Each entry names the samplingvariablein which the pole lies, and the observables or parameters that provide the real and imaginary parts of the pole position,position_reandposition_im; the imaginary part must be negative. The optionalcoefficient_reandcoefficient_immust be given together; they provide the subtraction coefficient \(c\). If they are absent, \(c\) is extracted from the truth-level PDF on the grid points nearest to the pole, which must not straddle an edge of the phase space or another pole. The term \(\mathrm{Re}[c / (x - z_p)]\) is subtracted from the truth-level PDF before the numerical convolution, and convolved analytically instead. The resolution must be a linear combination of kernels with known Cauchy transforms, such asKernel::Gaussian, in the offset variable of each pole’s axis. ForKernel::CrystalBall, the analytic convolution is accurate to first order in the ratio of the pole’s width to the kernel’s width, and a warning is logged once that ratio exceeds 0.1; changing its tail parameters is costly, so they are best kept fixed. For several axes, the coefficients of these kernels may contain kernels in the other offset variables, such asKernel::Gaussian({m}, 0, 0.005) * Kernel::Gaussian({c}, 0, 0.02). Custom pole observables are declared in theobservablessection.poles: - { 'variable': 'q2', 'position_re': 'Example::Re_z_p', 'position_im': 'Example::Im_z_p' }
Posteriors
The posteriors key contains a list of named posteriors. Each posterior combines one or more of the named priors and likelihoods defined above into a single Bayesian posterior probability density — the object that the inference tasks, such as sampling, optimisation, and prediction, operate on. Each posterior has three mandatory keys and two optional keys:
name(mandatory) — The unique name of this posterior.
prior(mandatory) — The ordered list of named priors that are used as part of this posterior.
likelihood(mandatory) — The ordered list of named likelihoods that are used as part of this posterior.
global_options(optional) — A key/value map providing global options, i.e., options that apply to all observables used within this posterior.
fixed_parameters(optional) — A key/value map providing values for parameters that deviate from the default values.
The following example illustrates the organisation of a posterior.
posteriors:
- name: CKM-pi
global_options:
l: e
model: CKM
prior:
- CKM
- FF-pi
likelihood:
- TH-pi
- EXP-pi
The prior and likelihood keys refer to the named priors and likelihoods by their name; together, the chosen priors must constrain every parameter that the chosen likelihoods depend on.
The optional global_options apply to all observables evaluated within the posterior, and can be overridden by options given on an individual observable.
The optional fixed_parameters pins individual parameters to fixed values, removing them from the set of varied parameters in the inference.
A posterior is described by a PosteriorDescription.
Metadata
The optional metadata key provides bibliographic information about the analysis. It is purely descriptive and does not affect the inference. It accepts the following keys:
title(optional) — A human-readable title for the analysis.
id(optional) — A unique identifier for the analysis.
authors(optional) — A list of authors, each given by anameand, optionally, anaffiliationand an
The metadata is described by a MetadataDescription, and each author by a MetadataAuthorDescription.
Observables
New observables can be defined and used in the analysis description by following the syntax described in the corresponding section.
For example, the following code defines the ratio of two \(B \to \pi\) form-factors as a new observable.
observables:
'B->pi::f_+(q2)/f_0(q2)':
latex: '\frac{f_+}{f_0}'
unit: '1'
options: {}
expression:
'<<B->pi::f_+(q2)>> / <<B->pi::f_0(q2)>>'
Note that if you define a custom observable in an analysis file, and then plot some results from that analysis interactively, you need to ensure EOS knows about the new observable by loading in the same analysis file through eos.AnalysisFile("my_analysis.yaml").
Each entry is keyed by the qualified name of the new observable and accepts the keys latex (its LaTeX representation), unit, and expression (the expression that defines it), as well as an optional options map.
A custom observable is described by an ObservableComponent.
Parameters
New parameters can also be defined in the analysis description. This can be useful in two cases:
1. The new parameter(s) can be directly used in a custom observable and added to the analysis priors. The combination of new observables, parameters and manual constraints make
EOSextremely flexible. The syntax for a new parameter follows:parameters: 'prefix::name' : central: +1.0 min: +0.0 max: +2.0 unit: '1' latex: 'p_\mathrm{user}'2. New parameters can also be used as aliases for existing parameters. Varying the alias will then vary all the aliased parameters. This is particularly useful in analyses that assumes some symmetry amongst the parameters. E.g. for a fit to Wilson coefficients under the assumption of lepton flavor universality, we can use
parameters: 'ublnul::Re{cVL}' : alias_of: [ 'ubenue::Re{cVL}', 'ubmunumu::Re{cVL}', 'ubtaunutau::Re{cVL}' ] central: +1.0 min: +0.0 max: +2.0 unit: '1' latex: '\mathrm{Re}\, \mathcal{C}^{\bar{u}b\bar{\ell}\nu_\ell}_{V_L}'Note that if you define an alias in an analysis file, and then plot some results from that analysis interactively, you need to ensure
EOSknows about the aliases by loading in the same analysis file througheos.AnalysisFile("my_analysis.yaml").
Each entry is keyed by the qualified name of the new parameter and accepts the keys central, min, max, unit, and latex.
An optional alias_of key, holding a list of existing qualified names, instead makes the new parameter an alias for those parameters, so that varying it varies all of them together.
A custom parameter is described by a ParameterComponent.
Signal PDFs
New truth-level signal PDFs can be defined as the ratio of an observable that provides the unnormalized density and an observable that provides its normalization.
Either can be a custom observable from the observables section.
signal_pdfs:
- name: 'Example::P(x)'
numerator: 'Example::dGamma/dx'
variables: [ 'x' ]
normalization: 'Example::Gamma'
Each entry accepts the keys name, numerator, variables (the kinematic variables of the numerator, which become the sampling variables), and normalization.
The optional normalization_variables lists the kinematic variables of the normalization, and defaults to x_min and x_max for each sampling variable x.
The optional description and options keys provide a human-readable description and the options applied to both observables.
A custom signal PDF is described by a SignalPDFComponent.
Predictions
The last step of an analysis usually consists in the prediction of a set of observables based on previously obtained importance samples.
The recognized predictions keys are:
name(mandatory) The name of the set of predictions.
observables(mandatory) The list of observables that need to be predicted. This should contain valid existing or manually-specified observables.
global_options(optional) The global options that should be used in the evaluation of the observables.
fixed_parameters(optional) A dictionary of parameters and their values that will be fixed in the evaluation of the observables.
- The observables accept two keys:
name(mandatory) The qualified name of the observable. Options can be specified in the observable name following the syntax ofQualifiedName. A warning will be raised if the observable options override the global options defined above.kinematics(optional) The dictionary of kinematics specifications for the observables. For brevity, a list of kinematic specifications can be provided. In this case, one observable per specification will be created.
The following code provides a valid example of predictions.
predictions:
- name: BR
global_options:
model: CKM
observables:
- name: B_u->lnu::BR;l=e
- name: B_u->lnu::BR;l=mu
- name: B_u->lnu::BR;l=tau
- name: dBR
global_options:
l: e
q: d
model: CKM
form-factors: BCL2008
observables:
- name: B->pilnu::dBR/dq2
kinematics: [ { q2: 1.0 }, { q2: 2.0 }, { q2: 3.0 }, { q2: 4.0 }, { q2: 5.0 },
{ q2: 6.0 }, { q2: 7.0 }, { q2: 8.0 }, { q2: 9.0 }, { q2: 10.0 },
{ q2: 11.0 }, { q2: 12.0 }, { q2: 13.0 }, { q2: 14.0 }, { q2: 15.0 },
{ q2: 16.0 }, { q2: 17.0 }, { q2: 18.0 }, { q2: 19.0 }, { q2: 20.0 },
{ q2: 21.0 }, { q2: 22.0 }, { q2: 23.0 }, { q2: 24.0 }, { q2: 25.0 },
{ q2: 26.0 }, { q2: 27.0 } ]
A prediction is described by a PredictionDescription, and each of its observables by a PredictionObservableComponent.
Figures
The figures key contains a list of named figures to be produced from the results of the analysis. Each figure follows the dedicated figure description format and is created by the FigureFactory; the figure’s name determines the file name under which the rendered figure is stored.
Steps
The steps key contains a list of pre-defined tasks that allow an analysis to be fully reproduced. Each step has three mandatory keys, and two optional keys:
title(mandatory) — The title of this step.
id(mandatory) — The unique identifier of this step.
depends_on(optional) — A list of stepids that need to be executed prior to this step.
default_arguments(optional) — A dictionary of tasks and default arguments, for any of the tasks in this step.
tasks(mandatory) — The list of tasks that are part of this step.
The following example illustrates the description of two nested sampling steps, followed by drawing figures of the results.
steps:
- title: 'Sample from CKM-all posterior'
id: 'CKM-all.sample'
tasks:
- task: 'sample-nested'
arguments:
posterior: 'CKM-all'
bound: 'multi'
nlive: 100
dlogz: 9.0
maxiter: 4000
- title: 'Sample from WET-all posterior'
id: 'WET-all.sample'
tasks:
- task: 'sample-nested'
arguments:
posterior: 'WET-all'
bound: 'multi'
nlive: 100
dlogz: 9.0
maxiter: 4000
- title: 'Draw the corner figures'
id: 'CKM-all,WET-all.draw-figure'
depends_on: ['CKM-all.sample', 'WET-all.sample']
default_arguments:
draw-figure:
format: ['pdf', 'png']
tasks:
- task: 'draw-figure'
arguments:
figure_name: 'CKM-all-corner'
- task: 'draw-figure'
arguments:
figure_name: 'WET-all-corner'
The depends_on key orders the steps into a dependency graph, so that an analysis can be reproduced by executing its steps in a well-defined order, while default_arguments supplies arguments shared by a step’s tasks.
A step is described by a StepComponent, and each of its tasks by a TaskComponent.
Masks
In some analyses, the resulting posterior is multi-modal, and it is useful to be able to define within the analysis file a filter, or mask, that selects a subset of the posterior samples. The masks section allows to define a mask as a set of (pseudo-)observables, and filtering on any or all (pseudo-)observables being > 0.
The masks key contains a list of named masks. Each mask contains two mandatory keys and one optional key:
name(mandatory) — The unique name of this mask.
description(mandatory) — A list of expressions that define the mask.
logical_combination(optional) — The logical combination to take of the expressions in the mask. The options areandandor, defaults toand.
The description block contains a list of either existing EOS observable names, new observable names and valid expressions, or the name of a previously defined mask.
An example is shown below:
masks:
- name: fplus-arg-large
description:
- name: '0->pipi::Arg{f_+}(2)'
expression: '<<0->pipi::Arg{f_+}(q2)>>[q2=2] - 4.5'
- name: abs-b3-large
logical_combination: 'or'
description:
- name: 0->pipi::b3positive
expression: '[[0->pipi::b_(+,1)^3@KKRvD2024]] + 0.1'
- name: 0->pipi::b3negative
expression: '-[[0->pipi::b_(+,1)^4@KKRvD2024]] - 0.1'
- name: fplus-arg-large-or-abs-b3-large
logical_combination: 'or'
description:
- mask_name: fplus-arg-large
- mask_name: abs-b3-large
Each element of a mask’s description is selected, based on its keys, from the following concrete types:
YAML selector |
description |
Python class |
|---|---|---|
|
Describes a mask entry given by the name of an existing EOS observable. |
|
|
Describes a mask entry given by a new observable defined through an expression. |
|
|
Describes a mask entry that refers to another, previously defined mask. |
A mask is described by a MaskComponent.
Example
The following real-world example illustrates the analysis file format.
Example examples/b-to-u-l-nu.yaml
metadata:
title: 'Example analysis of B -> u l nu transitions'
id: 'b-to-u-l-nu'
authors:
- name: 'Alice Notarealperson'
affiliation: 'Department of Made-Up Physics, University of Nowhere'
email: 'alice@example.com'
- name: 'Bob McFakeface'
affiliation: 'Institute for Fictional Studies, Imaginary Institute of Technology'
email: 'bob@example.com'
parameters:
'ublnul::Re{cVL}' :
alias_of: [ 'ubenue::Re{cVL}', 'ubmunumu::Re{cVL}', 'ubtaunutau::Re{cVL}' ]
central: 1.0
min: -2.0
max: 2.0
unit: '1'
latex: '\mathrm{Re}\, \mathcal{C}^{\bar{u}b\bar{\nu}_\ell\ell}_{V_L}'
'ublnul::Re{cVR}' :
alias_of: [ 'ubenue::Re{cVR}', 'ubmunumu::Re{cVR}', 'ubtaunutau::Re{cVR}' ]
central: 0.0
min: -2.0
max: 2.0
unit: '1'
latex: '\mathrm{Re}\, \mathcal{C}^{\bar{u}b\bar{\nu}_\ell\ell}_{V_R}'
likelihoods:
- name: TH-pi
constraints:
- 'B->pi::form-factors[f_+,f_0,f_T]@LMvD:2021A;form-factors=BCL2008-4'
- 'B->pi::f_++f_0+f_T@FNAL+MILC:2015C;form-factors=BCL2008-4'
- 'B->pi::f_++f_0@RBC+UKQCD:2015A;form-factors=BCL2008-4'
- name: EXP-pi
constraints:
- 'B^0->pi^-l^+nu::BR@HFLAV:2019A;form-factors=BCL2008-4'
- name: EXP-leptonic
constraints:
- 'B^+->tau^+nu::BR@Belle:2014A;form-factors=BCL2008-4'
priors:
- name: CKM
descriptions:
- { 'parameter': 'CKM::abs(V_ub)', 'min': 3.0e-3, 'max': 4.5e-3, 'type': 'uniform' }
- name: WET
descriptions:
- { 'parameter': 'ublnul::Re{cVL}', 'min': 0.5, 'max': 1.5, 'type': 'uniform' }
- { 'parameter': 'ublnul::Re{cVR}', 'min': -0.5, 'max': 0.5, 'type': 'uniform' }
- name: DC-Bu
descriptions:
- { 'parameter': 'decay-constant::B_u', 'central': 0.1894, 'sigma': 0.0014, 'type': 'gaussian' }
- name: FF-pi
descriptions:
- { 'parameter': 'B->pi::f_+(0)@BCL2008', 'min': 0.21, 'max': 0.32, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_+^1@BCL2008' , 'min': -2.96, 'max': -0.60, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_+^2@BCL2008' , 'min': -3.98, 'max': 4.38, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_+^3@BCL2008' , 'min': -18.30, 'max': 9.27, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^1@BCL2008' , 'min': -0.10, 'max': 1.35, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^2@BCL2008' , 'min': -2.08, 'max': 4.65, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^3@BCL2008' , 'min': -4.73, 'max': 9.07, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_0^4@BCL2008' , 'min': -60.00, 'max': 38.00, 'type': 'uniform' }
- { 'parameter': 'B->pi::f_T(0)@BCL2008', 'min': 0.18, 'max': 0.32, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_T^1@BCL2008' , 'min': -3.91, 'max': -0.33, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_T^2@BCL2008' , 'min': -4.32, 'max': 2.00, 'type': 'uniform' }
- { 'parameter': 'B->pi::b_T^3@BCL2008' , 'min': -7.39, 'max': 10.60, 'type': 'uniform' }
posteriors:
- name: CKM-all
global_options:
model: CKM
prior:
- CKM
- DC-Bu
- FF-pi
likelihood:
- TH-pi
- EXP-pi
- EXP-leptonic
- name: WET-all
global_options:
model: WET
fixed_parameters:
CKM::abs(V_ub): 3.67e-3
prior:
- WET
- DC-Bu
- FF-pi
likelihood:
- TH-pi
- EXP-pi
- EXP-leptonic
observables:
"B->pilnu::R_pi_e":
latex: "R_{\\pi}"
unit: '1'
options: {}
expression: "<<B->pilnu::BR;l=tau>>[q2_min=>q2_tau_min] / <<B->pilnu::BR;l=e>>[q2_min=>q2_e_min]"
predictions:
- name: leptonic-BR-CKM
global_options:
model: CKM
observables:
- name: B_u->lnu::BR;l=e
- name: B_u->lnu::BR;l=mu
- name: B_u->lnu::BR;l=tau
- name: leptonic-BR-WET
global_options:
model: WET
observables:
- name: B_u->lnu::BR;l=e
- name: B_u->lnu::BR;l=mu
- name: B_u->lnu::BR;l=tau
- name: pi-dBR-CKM
global_options:
model: CKM
form-factors: BCL2008
observables:
- name: B->pilnu::dBR/dq2
kinematics:
[ { q2: 0.05 }, { q2: 1.0 }, { q2: 2.0 }, { q2: 3.0 }, { q2: 3.5 }, { q2: 4.0 }, { q2: 4.5 }, { q2: 5.0 }, { q2: 5.5 }, { q2: 6.0 }, { q2: 6.5 }, { q2: 7.0 }, { q2: 7.25 }, { q2: 7.5 }, { q2: 7.75 }, { q2: 8.0 }, { q2: 8.25 }, { q2: 8.5 }, { q2: 8.75 }, { q2: 9.0 }, { q2: 9.25 }, { q2: 9.5 }, { q2: 9.75 }, { q2: 10.0 }, { q2: 10.25 }, { q2: 10.5 }, { q2: 10.75 }, { q2: 11.0 }, { q2: 11.25 }, { q2: 11.5 }, { q2: 11.75 }, { q2: 12.0 }, { q2: 13.0 }, { q2: 14.0 }, { q2: 15.0 }, { q2: 16.0 }, { q2: 17.0 }, { q2: 18.0 }, { q2: 19.0 }, { q2: 20.0 }, { q2: 21.0 }, { q2: 22.0 }, { q2: 23.0 }, { q2: 24.0 }, { q2: 25.0 }, { q2: 26.0 }, { q2: 27.0 } ]
- name : R_pi
global_options:
model: WET
observables:
- name: B->pilnu::R_pi_e
kinematics:
q2_e_min: 1.0e-7
q2_tau_min: 3.3
q2_max: 25.0
figures:
- name: CKM-all-corner
type: 'corner'
contents:
- path: 'data/CKM-all/samples'
label: 'CKM-all'
- name: WET-all-corner
type: 'corner'
contents:
- path: 'data/WET-all/samples'
label: 'WET-all'
variables: [ 'ublnul::Re{cVL}', 'ublnul::Re{cVR}' ]
steps:
- title: 'Sample from CKM-all posterior'
id: 'CKM-all.sample'
tasks:
- task: 'sample-nested'
arguments:
posterior: 'CKM-all'
bound: 'multi'
nlive: 100
dlogz: 9.0
maxiter: 4000
- title: 'Sample from WET-all posterior'
id: 'WET-all.sample'
tasks:
- task: 'sample-nested'
arguments:
posterior: 'WET-all'
bound: 'multi'
nlive: 100
dlogz: 9.0
maxiter: 4000
- title: 'Draw the corner figures'
id: 'CKM-all,WET-all.draw-figure'
depends_on: ['CKM-all.sample', 'WET-all.sample']
default_arguments:
draw-figure:
format: ['pdf', 'png']
tasks:
- task: 'draw-figure'
arguments:
figure_name: 'CKM-all-corner'
- task: 'draw-figure'
arguments:
figure_name: 'WET-all-corner'
- title: 'Find mode of CKM-all posterior'
id: 'CKM-all.find-mode'
depends_on: ['CKM-all.sample']
tasks:
- task: 'find-mode'
arguments:
posterior: 'CKM-all'
optimizations: 100
importance_samples: True