2 Copyright (C) 2008-2019 EDF R&D
4 This file is part of SALOME ADAO module.
6 This library is free software; you can redistribute it and/or
7 modify it under the terms of the GNU Lesser General Public
8 License as published by the Free Software Foundation; either
9 version 2.1 of the License, or (at your option) any later version.
11 This library is distributed in the hope that it will be useful,
12 but WITHOUT ANY WARRANTY; without even the implied warranty of
13 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
14 Lesser General Public License for more details.
16 You should have received a copy of the GNU Lesser General Public
17 License along with this library; if not, write to the Free Software
18 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
20 See http://www.salome-platform.org/ or email : webmaster.salome@opencascade.com
22 Author: Jean-Philippe Argaud, jean-philippe.argaud@edf.fr, EDF R&D
33 One ADAO case is defined by a set of data and of choices, packed together
34 through the user interface of the module. The data are physical
35 measurements that have technically to be available before or during the
36 case execution. The simulation code(s) and the data assimilation or
37 optimization method, and their parameters, has to be chosen, they define
38 the execution properties of the case.
41 One iteration occurs when using iterative optimizers (e.g. 3DVAR), and it
42 is entirely hidden in the main YACS OptimizerLoop Node named
43 "*compute_bloc*". Nevertheless, the user can watch the iterative process
44 through the "*YACS Container Log*" window, which is updated during the
45 process, and using "*Observers*" attached to calculation variables.
48 This is the object of study that will be represented by numerical
49 simulation and observed by measurements.
52 All the numerical relationships and equations characterizing the physical
56 Computational implementation of the set composed of the numerical
57 simulator and a particular set of all the input and control variables of
58 the simulator. These variables enable the digital simulator to be able to
59 numerically represent the system's behaviour.
61 observations or measurements
62 These are quantities that come from measuring instruments and
63 characterize the physical system to be studied. These quantities can vary
64 in space or time, can be punctual or integrated. They are themselves
65 characterized by their measurement nature, size, etc.
68 It is a transformation of the simulated state into a set of quantities
69 explicitly comparable to the observations.
72 These are particular input and control variables of the simulator, which
73 characterize the description of the system's behaviour at the border of
74 the simulation spatial domain.
77 These are specific simulator input and control variables that
78 characterize the description of the system's behavior at the initial edge
79 of the simulation time domain.
82 Keyword to indicate the covariance matrix of *a posteriori* analysis
85 APosterioriCorrelations
86 Keyword to indicate the correlation matrix of *a posteriori* analysis
90 Keyword to indicate the variances diagonal matrix of *a posteriori*
93 APosterioriStandardDeviations
94 Keyword to indicate the standard errors diagonal matrix of *a posteriori*
97 BMA (Background minus Analysis)
98 Difference between the background state and the optimal state estimation,
99 noted as :math:`\mathbf{x}^b - \mathbf{x}^a`.
101 OMA (Observation minus Analysis)
102 Difference between the observations and the result of the simulation based
103 on the optimal state estimation, the analysis, filtered to be compatible
104 with the observation, noted as :math:`\mathbf{y}^o -
105 \mathbf{H}\mathbf{x}^a`.
107 OMB (Observation minus Background)
108 Difference between the observations and the result of the simulation based
109 on the background state, filtered to be compatible with the observation,
110 noted as :math:`\mathbf{y}^o - \mathbf{H}\mathbf{x}^b`.
113 Keyword to indicate the Desroziers-Ivanov parameter measuring the
114 background part consistency of the data assimilation optimal state
115 estimation. Its value can be compared to 1, a "good" estimation leading to
116 a parameter "close" to 1.
119 Keyword to indicate the Desroziers-Ivanov parameter measuring the
120 observation part consistency of the data assimilation optimal state
121 estimation. Its value can be compared to 1, a "good" estimation leading to
122 a parameter "close" to 1.
124 MahalanobisConsistency
125 Keyword to indicate the Mahalanobis parameter measuring the consistency of
126 the data assimilation optimal state estimation. Its value can be compared
127 to 1, a "good" estimation leading to a parameter "close" to 1.
130 It is the optimal state estimated through a data assimilation or
131 optimization procedure.
134 It is a part (chosen to be modified) of the system state representation,
135 representation known *a priori* or initial one, which is not optimal, and
136 which is used as a rough estimate, or a "best estimate", before an
140 Difference between the observations and the result of the simulation based
141 on the background state, filtered to be compatible with the observation.
142 It is similar with OMB in static cases.
145 Keyword to indicate the minimization function, noted as :math:`J`.
148 Keyword to indicate the observation part of the minimization function,
149 noted as :math:`J^o`.
152 Keyword to indicate the background part of the minimization function,
153 noted as :math:`J^b`.
156 Keyword to indicate the current state used during an optimization