This is an old revision of the document!
Calibrating a simulation model involves calculating a set of input-variable values for a historical time period which reproduces - using the simulator framework - the observed simulator outputs over that same period. To accomplish this a formal calibrator framework is created alongside the simulator framework within a model family (see How it's Organized).
[Perhaps give a trivial example where the simulator model is y = x + z. If the historical observed value for y is 6, then a calibration solution for (x,y) could be (3,3), (2,4) or (1,5)…and so on. For real-world models this is a non-trivial problem and requires a separate calibrator framework because:
]
[Explain the diagram below wrt the frameworks, relative to time, inputs and outputs.]
[Compare/contrast what we mean by calibration to other modelling paradigms: specification, estimate, calibration, etc. E.g. Choice model calibration.]
Note that the term calibration used in the whatIf? Platform / Design Approach context differs from specification and estimation of a statistical model. In particular, the use of data is different as in statistical modelling the data are used to estimate the parameters in the model using an appropriate statistical technique, while in the design approach, data which have not been measured, such as lifetimes of capital stocks, are estimated and then the data set is used to calibrate the model [clarify this with Bert] . The calibration is successful if the model reproduces the data, given a set of historical input variables, and this is considered a necessary but not sufficient condition for a valid model. [1]