Lmfit
Lmfit
3 Getting Help 13
i
7 Modeling Data and Curve Fitting 61
7.1 Motivation and simple example: Fit data to Gaussian profile . . . . . . . . . . . . . . . . . . . . . . 61
7.2 The Model class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.3 The ModelResult class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.4 Composite Models : adding (or multiplying) Models . . . . . . . . . . . . . . . . . . . . . . . . . . 92
ii
13.1 Fit with Data in a pandas DataFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
13.2 Using an ExpressionModel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
13.3 Fit Using Inequality Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
13.4 Fit Using differential_evolution Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
13.5 Fit Using Bounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
13.6 Fit with Algebraic Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
13.7 Fit Specifying Different Reduce Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
13.8 Building a lmfit model with SymPy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
13.9 Fit Multiple Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
13.10 Fit using the Model interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
13.11 Fit Specifying a Function to Compute the Jacobian . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
13.12 Outlier detection via leave-one-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
13.13 Emcee and the Model Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
13.14 Complex Resonator Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
13.15 Model Selection using lmfit and emcee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
13.16 Calculate Confidence Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
13.17 Fit Two Dimensional Peaks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
13.18 Global minimization using the brute method (a.k.a. grid search) . . . . . . . . . . . . . . . . . . . 233
Index 315
iii
iv
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
Lmfit provides a high-level interface to non-linear optimization and curve fitting problems for Python. It builds on
and extends many of the optimization methods of scipy.optimize. Initially inspired by (and named for) extending the
Levenberg-Marquardt method from scipy.optimize.leastsq, lmfit now provides a number of useful enhancements to
optimization and data fitting problems, including:
• Using Parameter objects instead of plain floats as variables. A Parameter has a value that can be varied during
the fit or kept at a fixed value. It can have upper and/or lower bounds. A Parameter can even have a value that is
constrained by an algebraic expression of other Parameter values. As a Python object, a Parameter can also have
attributes such as a standard error, after a fit that can estimate uncertainties.
• Ease of changing fitting algorithms. Once a fitting model is set up, one can change the fitting algorithm used to
find the optimal solution without changing the objective function.
• Improved estimation of confidence intervals. While scipy.optimize.leastsq will automatically calculate uncer-
tainties and correlations from the covariance matrix, the accuracy of these estimates is sometimes questionable.
To help address this, lmfit has functions to explicitly explore parameter space and determine confidence levels
even for the most difficult cases. Additionally, lmfit will use the numdifftools package (if installed) to estimate
parameter uncertainties and correlations for algorithms that do not natively support this in SciPy.
• Improved curve-fitting with the Model class. This extends the capabilities of scipy.optimize.curve_fit, allowing
you to turn a function that models your data into a Python class that helps you parametrize and fit data with that
model.
• Many built-in models for common lineshapes are included and ready to use.
The lmfit package is Free software, using an Open Source license. The software and this document are works in
progress. If you are interested in participating in this effort please use the lmfit GitHub repository.
CONTENTS 1
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
2 CONTENTS
CHAPTER
ONE
The lmfit package provides simple tools to help you build complex fitting models for non-linear least-squares problems
and apply these models to real data. This section gives an overview of the concepts and describes how to set up and
perform simple fits. Some basic knowledge of Python, NumPy, and modeling data are assumed – this is not a tutorial
on why or how to perform a minimization or fit data, but is rather aimed at explaining how to use lmfit to do these
things.
In order to do a non-linear least-squares fit of a model to data or for any other optimization problem, the main task
is to write an objective function that takes the values of the fitting variables and calculates either a scalar value to be
minimized or an array of values that are to be minimized, typically in the least-squares sense. For many data fitting
processes, the latter approach is used, and the objective function should return an array of (data-model), perhaps
scaled by some weighting factor such as the inverse of the uncertainty in the data. For such a problem, the chi-square
(𝜒2 ) statistic is often defined as:
𝑁
∑︁ [𝑦 meas − 𝑦 model (v)]2
𝑖 𝑖
𝜒2 =
𝑖
𝜖2𝑖
where 𝑦𝑖meas is the set of measured data, 𝑦𝑖model (v) is the model calculation, v is the set of variables in the model to be
optimized in the fit, and 𝜖𝑖 is the estimated uncertainty in the data, respectively.
In a traditional non-linear fit, one writes an objective function that takes the variable values and calculates the residual
array 𝑦𝑖meas − 𝑦𝑖model (v), or the residual array scaled by the data uncertainties, [𝑦𝑖meas − 𝑦𝑖model (v)]/𝜖𝑖 , or some other
weighting factor.
As a simple concrete example, one might want to model data with a decaying sine wave, and so write an objective
function like this:
3
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
Though it is wonderful to be able to use Python for such optimization problems, and the SciPy library is robust and
easy to use, the approach here is not terribly different from how one would do the same fit in C or Fortran. There are
several practical challenges to using this approach, including:
a) The user has to keep track of the order of the variables, and their meaning – variables[0] is the amplitude,
variables[2] is the frequency, and so on, although there is no intrinsic meaning to this order.
b) If the user wants to fix a particular variable (not vary it in the fit), the residual function has to be altered to
have fewer variables, and have the corresponding constant value passed in some other way. While reasonable
for simple cases, this quickly becomes a significant work for more complex models, and greatly complicates
modeling for people not intimately familiar with the details of the fitting code.
c) There is no simple, robust way to put bounds on values for the variables, or enforce mathematical relationships
between the variables. While some optimization methods in SciPy do provide bounds, they require bounds to
be set for all variables with separate arrays that are in the same arbitrary order as variable values. Again, this is
acceptable for small or one-off cases, but becomes painful if the fitting model needs to change.
d) In some cases, constraints can be placed on Parameter values, but this is a pretty opaque and complex process.
While these shortcomings can be worked around with some work, they are all essentially due to the use of arrays or
lists to hold the variables. This closely matches the implementation of the underlying Fortran code, but does not fit
very well with Python’s rich selection of objects and data structures. The key concept in lmfit is to define and use
Parameter objects instead of plain floating point numbers as the variables for the fit. Using Parameter objects (or
the closely related Parameters – a dictionary of Parameter objects), allows one to do the following:
a) forget about the order of variables and refer to Parameters by meaningful names.
b) place bounds on Parameters as attributes, without worrying about preserving the order of arrays for variables
and boundaries, and without relying on the solver to support bounds itself.
c) fix Parameters, without having to rewrite the objective function.
d) place algebraic constraints on Parameters.
To illustrate the value of this approach, we can rewrite the above example for the decaying sine wave as:
params = Parameters()
params.add('amp', value=10)
params.add('decay', value=0.007)
params.add('phase', value=0.2)
params.add('frequency', value=3.0)
At first look, we simply replaced a list of values with a dictionary, so that we can access Parameters by name. Just by
itself, this is better as it allows separation of the objective function from the code using it.
Note that creation of Parameters here could also be done as:
New in version 1.2.0.
where keyword/value pairs set Parameter names and their initial values.
Either when using create_param() or Parameters, the resulting params object is an instance of Parameters,
which acts like a dictionary, with keys being the Parameter name and values being individual Parameter objects.
These Parameter objects hold the value and several other attributes that control how a Parameter acts. For example,
Parameters can be fixed or bounded; setting attributes to control this behavior can be done during definition, as with:
params = Parameters()
params.add('amp', value=10, vary=False)
params.add('decay', value=0.007, min=0.0)
params.add('phase', value=0.2)
params.add('frequency', value=3.0, max=10)
Here vary=False will prevent the value from changing in the fit, and min=0.0 will set a lower bound on that param-
eter’s value. The same thing can be accomplished by providing a dictionary of attribute values to create_params():
New in version 1.2.0.
Parameter attributes can also be modified after they have been created:
params['amp'].vary = False
params['decay'].min = 0.10
5
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
Importantly, our objective function remains unchanged. This means the objective function can simply express the
parametrized phenomenon to be calculated, accessing Parameter values by name and separating the choice of param-
eters to be varied in the fit.
The params object can be copied and modified to make many user-level changes to the model and fitting process. Of
course, most of the information about how your data is modeled goes into the objective function, but the approach here
allows some external control; that is, control by the user performing the fit, instead of by the author of the objective
function.
Finally, in addition to the Parameters approach to fitting data, lmfit allows switching optimization methods without
changing the objective function, provides tools for generating fitting reports, and provides a better determination of
Parameters confidence levels.
TWO
2.1 Prerequisites
Lmfit works with Python versions 3.7 and higher. Version 0.9.15 is the final version to support Python 2.7.
Lmfit requires the following Python packages, with versions given:
• NumPy version 1.19 or higher.
• SciPy version 1.6 or higher.
• asteval version 0.9.28 or higher.
• uncertainties version 3.1.4 or higher.
All of these are readily available on PyPI, and are installed automatically if installing with pip install lmfit.
In order to run the test suite, the pytest, pytest-cov, and flaky packages are required. Some functionality requires
the emcee (version 3+), corner, pandas, Jupyter, matplotlib, dill, or numdifftools packages. These are not installed
automatically, but we highly recommend each of them.
For building the documentation and generating the examples gallery, matplotlib, emcee (version 3+), corner, Sphinx,
sphinx-gallery, jupyter_sphinx, ipykernel, Pillow, and SymPy are required. For generating the PDF documentation, the
Python packages sphinxcontrib-svg2pdfconverter and cairosvg are also required, as well as the LaTex package Latexmk
(which is included by default in some LaTex distributions).
Please refer to setup.cfg under options.extras_require for a list of all dependencies that are needed if you want
to participate in the development of lmfit. You can install all these dependencies automatically by doing pip install
lmfit[all], or select only a subset (e.g., dev`, doc, or test).
Please note: the “original” python setup.py install is deprecated, but we will provide a shim setup.py file for
as long as Python and/or setuptools allow the use of this legacy command.
2.2 Downloads
The latest stable version of lmfit is 1.2.0 and is available from PyPI. Check the Release Notes for a list of changes
compared to earlier releases.
7
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
2.3 Installation
For Anaconda Python, lmfit is not an official package, but several Anaconda channels provide it, allowing installation
with (for example):
To get the latest development version from the lmfit GitHub repository, use:
python -m build
pip install ".[all]'
to generate the wheel and install lmfit with all its dependencies.
We welcome all contributions to lmfit! If you cloned the repository for this purpose, please read CONTRIBUTING.md
for more detailed instructions.
2.5 Testing
A battery of tests scripts that can be run with the pytest testing framework is distributed with lmfit in the tests folder.
These are automatically run as part of the development process. For any release or any master branch from the git
repository, running pytest should run all of these tests to completion without errors or failures.
Many of the examples in this documentation are distributed with lmfit in the examples folder, and should also run for
you. Some of these examples assume that matplotlib has been installed and is working correctly.
2.6 Acknowledgements
Matthew Newville wrote the original version and maintains the project.
Renee Otten wrote the brute force method, implemented the basin-hopping
and AMPGO global solvers, implemented uncertainty calculations for scalar
minimizers and has greatly improved the code, testing, and documentation
and overall project.
Antonino Ingargiola wrote much of the high level Model code and has
provided many bug fixes and improvements.
Daniel B. Allan wrote much of the original version of the high level Model
code, and many improvements to the testing and documentation.
Austen Fox fixed many of the built-in model functions and improved the
testing and documentation of these.
The method used for placing bounds on parameters was derived from the
clear description in the MINUIT documentation, and adapted from
J. J. Helmus's Python implementation in leastsqbounds.py.
The original AMPGO code came from Andrea Gavana and was adopted for
lmfit.
which references the original work of: J. Wolberg, Data Analysis Using the
Method of Least Squares, 2006, Springer.
Additional patches, bug fixes, and suggestions have come from Faustin
Carter, Christoph Deil, Francois Boulogne, Thomas Caswell, Colin Brosseau,
nmearl, Gustavo Pasquevich, Clemens Prescher, LiCode, Ben Gamari, Yoav
Roam, Alexander Stark, Alexandre Beelen, Andrey Aristov, Nicholas Zobrist,
Ethan Welty, Julius Zimmermann, Mark Dean, Arun Persaud, Ray Osborn, @lneuhaus,
Marcel Stimberg, Yoshiera Huang, Leon Foks, Sebastian Weigand, Florian LB,
Michael Hudson-Doyle, Ruben Verweij, @jedzill4, @spalato, Jens Hedegaard Nielsen,
(continues on next page)
2.6. Acknowledgements 9
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
The lmfit code obviously depends on, and owes a very large debt to the code
in scipy.optimize. Several discussions on the SciPy-user and lmfit mailing
lists have also led to improvements in this code.
BSD-3
3. Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Some code has been taken from the scipy library whose licence is below.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
Some code has been taken from the AMPGO library of Andrea Gavana, which was
released under a MIT license.
THREE
GETTING HELP
If you have questions, comments, or suggestions for LMFIT, please use the mailing list. This provides an on-line
conversation that is both archived well and can be searched easily with standard web searches. If you find a bug in the
code or documentation, use GitHub Issues to submit a report. If you have an idea for how to solve the problem and are
familiar with Python and GitHub, submitting a GitHub Pull Request would be greatly appreciated.
If you are unsure whether to use the mailing list or the Issue tracker, please start a conversation on the mailing list.
That is, the problem you’re having may or may not be due to a bug. If it is due to a bug, creating an Issue from the
conversation is easy. If it is not a bug, the problem will be discussed and then the Issue will be closed. While one can
search through closed Issues on GitHub, these are not so easily searched, and the conversation is not easily useful to
others later. Starting the conversation on the mailing list with “How do I do this?” or “Why didn’t this work?” instead
of “This should work and doesn’t” is generally preferred, and will better help others with similar questions. Of course,
there is not always an obvious way to decide if something is a Question or an Issue, and we will try our best to engage
in all discussions.
13
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
FOUR
4.1 What’s the best way to ask for help or submit a bug report?
4.2 Why did my script break when upgrading from lmfit 0.8.3 to 0.9.0?
then you need to install the ipywidgets package, try: pip install ipywidgets.
The fitting routines accept data arrays that are one-dimensional and double precision. So you need to convert the data
and model (or the value returned by the objective function) to be one-dimensional. A simple way to do this is to use
numpy.ndarray.flatten, for example:
15
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
As above, the fitting routines accept data arrays that are one-dimensional and double precision. So you need to convert
the sets of data and models (or the value returned by the objective function) to be one-dimensional. A simple way to
do this is to use numpy.concatenate. As an example, here is a residual function to simultaneously fit two lines to two
different arrays. As a bonus, the two lines share the ‘offset’ parameter:
import numpy as np
As with working with multi-dimensional data, you need to convert your data and model (or the value returned by the
objective function) to be double precision, floating point numbers. The simplest approach is to use numpy.ndarray.view,
perhaps like:
import numpy as np
Alternately, you can use the lmfit.Model class to wrap a fit function that returns a complex vector. It will automatically
apply the above prescription when calculating the residual. The benefit to this method is that you also get access to the
plot routines from the ModelResult class, which are also complex-aware.
See https://dx.doi.org/10.5281/zenodo.11813
The solvers used by lmfit use NaN (see https://en.wikipedia.org/wiki/NaN) values as signals that the calculation cannot
continue. If any value in the residual array (typically (data-model)*weight) is NaN, then calculations of chi-square
or comparisons with other residual arrays to try find a better fit will also give NaN and fail. There is no sensible way
for lmfit or any of the optimization routines to know how to handle such NaN values. They indicate that numerical
calculations are not sensible and must stop.
This means that if your objective function (if using minimize) or model function (if using Model) generates a NaN,
the fit will stop immediately. If your objective or model function generates a NaN, you really must handle that.
4.8.1 nan_policy
If you are using lmfit.Model and the NaN values come from your data array and are meant to indicate missing values,
or if you using lmfit.minimize() with the same basic intention, then it might be possible to get a successful fit in
spite of the NaN values. To do this, you can add a nan_policy='omit' argument to lmfit.minimize(), or when
creating a lmfit.Model, or when running lmfit.Model.fit().
In order for this to be effective, the number of NaN values cannot ever change during the fit. If the NaN values come
from the data and not the calculated model, that should be the case.
If you are seeing errors due to NaN values, you will need to figure out where they are coming from and eliminate them.
It is sometimes difficult to tell what causes NaN values. Keep in mind that all values should be assumed to be either
scalar values or numpy arrays of double precision real numbers when fitting. Some of the most likely causes of NaNs
are:
• taking sqrt(x) or log(x) where x is negative.
• doing x**y where x is negative. Since y is real, there will be a fractional component, and a negative number to
a fractional exponent is not a real number.
• doing x/y where both x and y are 0.
If you use these very common constructs in your objective or model function, you should take some caution for what
values you are passing these functions and operators. Many special functions have similar limitations and should also
be viewed with some suspicion if NaNs are being generated.
A related problem is the generation of Inf (Infinity in floating point), which generally comes from exp(x) where x has
values greater than 700 or so, so that the resulting value is greater than 1.e308. Inf is only slightly better than NaN.
It will completely ruin the ability to do the fit. However, unlike NaN, it is also usually clear how to handle Inf, as
you probably won’t ever have values greater than 1.e308 and can therefore (usually) safely clip the argument passed to
exp() to be smaller than about 700.
In order for a Parameter to be optimized in a fit, changing its value must have an impact on the fit residual (data-model
when curve fitting, for example). If a fit has not changed one or more of the Parameters, it means that changing those
Parameters did not change the fit residual.
Normally (that is, unless you specifically provide a function for calculating the derivatives, in which case you probably
would not be asking this question ;)), the fitting process begins by making a very small change to each Parameter value
to determine which way and how large of a change to make for the parameter: This is the derivative or Jacobian (change
in residual per change in parameter value). By default, the change made for each variable Parameter is to multiply its
value by (1.0+1.0e-8) or so (unless the value is below about 1.e-15, in which case it adds 1.0e-8). If that small change
does not change the residual, then the value of the Parameter will not be updated.
Parameter values that are “way off” are a common reason for Parameters being stuck at initial values. As an example,
imagine fitting peak-like data with and x range of 0 to 10, peak centered at 6, and a width of 1 or 2 or so, as in the
example at doc_model_gaussian.py. A Gaussian function with an initial value of for the peak center at 5 and an initial
width or 5 will almost certainly find a good fit. An initial value of the peak center of -50 will end up being stuck with a
“bad fit” because a small change in Parameters will still lead the modeled Gaussian to have no intensity over the actual
range of the data. You should make sure that initial values for Parameters are reasonable enough to actually effect the
fit. As it turns out in the example linked to above, changing the center value to any value between about 0 and 10 (that
is, the data range) will result to a good fit.
Another common cause for Parameters being stuck at initial values is when the initial value is at a boundary value. For
this case, too, a small change in the initial value for the Parameter will still leave the value at the boundary value and
not show any real change in the residual.
If you’re using bounds, make sure the initial values for the Parameters are not at the boundary values.
Finally, one reason for a Parameter to not change is that they are actually used as discrete values. This is discussed
below in Can Parameters be used for Array Indices or Discrete Values?.
In order for Parameter uncertainties to be estimated, each variable Parameter must actually change the fit, and cannot
be stuck at an initial value or at a boundary value. See Why are Parameter values sometimes stuck at initial values? for
why values may not change from their initial values.
The short answer is “No”: variables in all of the fitting methods used in lmfit (and all of those available in scipy.
optimize) are treated as continuous values, and represented as double precision floating point values. As an important
example, you cannot have a variable that is somehow constrained to be an integer.
Still, it is a rather common question of how to fit data to a model that includes a breakpoint, perhaps
{︃
𝑐 for 𝑥 < 𝑥0
𝑓 (𝑥; 𝑥0 , 𝑎, 𝑏, 𝑐) =
𝑎 + 𝑏𝑥2 for 𝑥 > 𝑥0
That you implement with a model function and use to fit data like this:
import numpy as np
import lmfit
x0 = 19
b = 0.02
a = 2.0
xdat = np.linspace(0, 100, 101)
ydat = a + b * xdat**2
ydat[np.where(xdat < x0)] = a + b * x0**2
ydat += np.random.normal(scale=0.1, size=xdat.size)
mod = lmfit.Model(quad_off)
pars = mod.make_params(x0=22, a=1, b=1, c=1)
[[Model]]
Model(quad_off)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 14
# data points = 101
# variables = 4
chi-square = 3.19745850
reduced chi-square = 0.03296349
Akaike info crit = -340.729188
Bayesian info crit = -330.268706
R-squared = 0.99999099
[[Variables]]
x0: 22.0000000 +/- 1.7288e-05 (0.00%) (init = 22)
a: 1.99533131 +/- 0.03754894 (1.88%) (init = 1)
b: 0.02000201 +/- 7.3258e-06 (0.04%) (init = 1)
c: 9.32421159 +/- 0.03870840 (0.42%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(a, b) = -0.8368
C(x0, a) = +0.1871
C(x0, b) = -0.1508
This will not result in a very good fit, as the value for x0 cannot be found by making a small change in its value.
Specifically, model[np.where(x < x0)] will give the same result for x0=22 and x0=22.001, and so that value is
not changed during the fit.
There are a couple ways around this problem. First, you may be able to make the fit depend on x0 in a way that is not
just discrete. That depends on your model function. A second option is to treat the break not as a hard break but as a
more gentle transition with a sigmoidal function, such as an error function. Like the break-point, these will go from 0
to 1, but more gently and with some finite value leaking into neighboring points. The amount of leakage or width of
the step can also be adjusted.
A simple modification of the above to use an error function would look like this and give better fit results:
import numpy as np
from scipy.special import erf
import lmfit
x0 = 19
b = 0.02
a = 2.0
xdat = np.linspace(0, 100, 101)
ydat = a + b * xdat**2
ydat[np.where(xdat < x0)] = a + b * x0**2
ydat += np.random.normal(scale=0.1, size=xdat.size)
mod = lmfit.Model(quad_off)
pars = mod.make_params(x0=22, a=1, b=1, c=1)
[[Model]]
Model(quad_off)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 56
# data points = 101
# variables = 4
chi-square = 1.01206740
reduced chi-square = 0.01043368
Akaike info crit = -456.915660
Bayesian info crit = -446.455178
R-squared = 0.99999715
[[Variables]]
x0: 19.4038028 +/- 0.34484695 (1.78%) (init = 22)
a: 1.96097115 +/- 0.02047153 (1.04%) (init = 1)
b: 0.02000347 +/- 4.0388e-06 (0.02%) (init = 1)
c: 9.24175811 +/- 0.02313785 (0.25%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
(continues on next page)
The natural width of the error function is about 2 x units, but you can adjust this, shortening it with erf((x-x0)*2)
to give a sharper transition for example.
FIVE
This chapter describes the Parameter object, which is a key concept of lmfit.
A Parameter is the quantity to be optimized in all minimization problems, replacing the plain floating point number
used in the optimization routines from scipy.optimize. A Parameter has a value that can either be varied in the
fit or held at a fixed value, and can have lower and/or upper bounds placed on the value. It can even have a value that
is constrained by an algebraic expression of other Parameter values. Since Parameter objects live outside the core
optimization routines, they can be used in all optimization routines from scipy.optimize. By using Parameter
objects instead of plain variables, the objective function does not have to be modified to reflect every change of what
is varied in the fit, or whether bounds can be applied. This simplifies the writing of models, allowing general models
that describe the phenomenon and gives the user more flexibility in using and testing variations of that model.
Whereas a Parameter expands on an individual floating point variable, the optimization methods actually still need
an ordered group of floating point variables. In the scipy.optimize routines this is required to be a one-dimensional
numpy.ndarray. In lmfit, this one-dimensional array is replaced by a Parameters object, which works as an ordered
dictionary of Parameter objects with a few additional features and methods. That is, while the concept of a Parameter
is central to lmfit, one normally creates and interacts with a Parameters instance that contains many Parameter ob-
jects. For example, the objective functions you write for lmfit will take an instance of Parameters as its first argument.
A table of parameter values, bounds, and other attributes can be printed using Parameters.pretty_print().
23
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
• vary (bool, optional) – Whether the Parameter is varied during a fit (default is True).
• min (float, optional) – Lower bound for value (default is -numpy.inf, no lower
bound).
• max (float, optional) – Upper bound for value (default is numpy.inf, no upper bound).
• expr (str, optional) – Mathematical expression used to constrain the value during the
fit (default is None).
• brute_step (float, optional) – Step size for grid points in the brute method (default
is None).
• user_data (optional) – User-definable extra attribute used for a Parameter (default is
None).
stderr
The estimated standard error for the best-fit value.
Type
float
correl
A dictionary of the correlation with the other fitted Parameters of the form:
Type
dict
See Bounds Implementation for details on the math used to implement the bounds with min and max.
The expr attribute can contain a mathematical expression that will be used to compute the value for the Parameter
at each step in the fit. See Using Mathematical Constraints for more details and examples of this feature.
set(value=None, vary=None, min=None, max=None, expr=None, brute_step=None, is_init_value=True)
Set or update Parameter attributes.
Parameters
• value (float, optional) – Numerical Parameter value.
• vary (bool, optional) – Whether the Parameter is varied during a fit.
• min (float, optional) – Lower bound for value. To remove a lower bound you must
use -numpy.inf.
• max (float, optional) – Upper bound for value. To remove an upper bound you must
use numpy.inf.
• expr (str, optional) – Mathematical expression used to constrain the value during the
fit. To remove a constraint you must supply an empty string.
• brute_step (float, optional) – Step size for grid points in the brute method. To
remove the step size you must use 0.
• is_init_value (bool, optional) – Whether to set value as init_value, when setting
value.
Notes
Each argument to set() has a default value of None, which will leave the current value for the attribute
unchanged. Thus, to lift a lower or upper bound, passing in None will not work. Instead, you must set these
to -numpy.inf or numpy.inf, as with:
Explicitly setting a value or setting vary=True will also clear the expression.
Finally, to clear the brute_step size, pass 0, not None:
class Parameters(usersyms=None)
A dictionary of Parameter objects.
It should contain all Parameter objects that are required to specify a fit model. All minimization and Model fitting
routines in lmfit will use exactly one Parameters object, typically given as the first argument to the objective
function.
All keys of a Parameters() instance must be strings and valid Python symbol names, so that the name must match
[a-z_][a-z0-9_]* and cannot be a Python reserved word.
All values of a Parameters() instance must be Parameter objects.
A Parameters() instance includes an asteval Interpreter used for evaluation of constrained Parameters.
Parameters() support copying and pickling, and have methods to convert to and from serializations using json
strings.
Parameters
usersyms (dict, optional) – Dictionary of symbols to add to the asteval.Interpreter
(default is None).
add(name, value=None, vary=True, min=-inf, max=inf, expr=None, brute_step=None)
Add a Parameter.
Parameters
• name (str or Parameter) – If name refers to a Parameter object it will be added directly
to the Parameters instance, otherwise a new Parameter object with name string is created
before adding it. In both cases, name must match [a-z_][a-z0-9_]* and cannot be a
Python reserved word.
• value (float, optional) – Numerical Parameter value, typically the initial value.
• vary (bool, optional) – Whether the Parameter is varied during a fit (default is True).
• min (float, optional) – Lower bound for value (default is -numpy.inf, no lower
bound).
• max (float, optional) – Upper bound for value (default is numpy.inf, no upper
bound).
• expr (str, optional) – Mathematical expression used to constrain the value during the
fit (default is None).
• brute_step (float, optional) – Step size for grid points in the brute method (default
is None).
Examples
add_many(*parlist)
Add many parameters, using a sequence of tuples.
Parameters
*parlist (sequence of tuple or Parameter) – A sequence of tuples, or a sequence of
Parameter instances. If it is a sequence of tuples, then each tuple must contain at least
a name. The order in each tuple must be (name, value, vary, min, max, expr,
brute_step).
Examples
• colwidth (int, optional) – Column width for all columns specified in columns (de-
fault is 8).
• precision (int, optional) – Number of digits to be printed after floating point (default
is 4).
• fmt ({'g', 'e', 'f'}, optional) – Single-character numeric formatter. Valid values are:
‘g’ floating point and exponential (default), ‘e’ exponential, or ‘f’ floating point.
• columns (list of str, optional) – List of Parameter attribute names to print (default is
to show all attributes).
valuesdict()
Return an ordered dictionary of parameter values.
Returns
A dictionary of name:value pairs for each Parameter.
Return type
dict
dumps(**kws)
Represent Parameters as a JSON string.
Parameters
**kws (optional) – Keyword arguments that are passed to json.dumps.
Returns
JSON string representation of Parameters.
Return type
str
See also:
dump, loads, load, json.dumps
dump(fp, **kws)
Write JSON representation of Parameters to a file-like object.
Parameters
• fp (file-like object) – An open and .write()-supporting file-like object.
• **kws (optional) – Keyword arguments that are passed to dumps.
Returns
Return value from fp.write(): the number of characters written.
Return type
int
See also:
dumps, load, json.dump
eval(expr)
Evaluate a statement using the asteval Interpreter.
Parameters
expr (str) – An expression containing parameter names and other symbols recognizable by
the asteval Interpreter.
Returns
The result of evaluating the expression.
Return type
float
loads(s, **kws)
Load Parameters from a JSON string.
Parameters
**kws (optional) – Keyword arguments that are passed to json.loads.
Returns
Updated Parameters from the JSON string.
Return type
Parameters
Notes
Current Parameters will be cleared before loading the data from the JSON string.
See also:
dump, dumps, load, json.loads
load(fp, **kws)
Load JSON representation of Parameters from a file-like object.
Parameters
• fp (file-like object) – An open and .read()-supporting file-like object.
• **kws (optional) – Keyword arguments that are passed to loads.
Returns
Updated Parameters loaded from fp.
Return type
Parameters
See also:
dump, loads, json.load
Warning: Saving Parameters with user-added functions to the _asteval interpreter using :meth::dump and
dumps() may not be easily recovered with the load() and loads(). See Saving and Loading Models for fur-
ther discussion.
The create_params() function is probably the easiest method for making Parameters objects, as it allows defining
Parameter names by keyword with values either being the numerical initial value for the Parameter or being a dictionary
with keyword/value pairs for value as well as other Parameter attribute such as min, max, expr, and so forth.
create_params(**kws)
Create lmfit.Parameters instance and set initial values and attributes.
Parameters
**kws – keywords are parameter names, value are dictionaries of Parameter values and attributes.
Return type
Parameters instance
Notes
Examples
A basic example making use of Parameters and the minimize() function (discussed in the next chapter) might look
like this:
# <examples/doc_parameters_basic.py>
import numpy as np
# ... or use
params = create_params(amp=dict(value=10, min=0),
decay=0.1,
omega=3,
shift=dict(value=0, min=-np.pi/2, max=np.pi/2))
Here, the objective function explicitly unpacks each Parameter value. This can be simplified using the Parameters
valuesdict() method, which would make the objective function fcn2min above look like:
SIX
As shown in the previous chapter, a simple fit can be performed with the minimize() function. For more sophisticated
modeling, the Minimizer class can be used to gain a bit more control, especially when using complicated constraints
or comparing results from related fits.
The minimize() function is a wrapper around Minimizer for running an optimization problem. It takes an objective
function (the function that calculates the array to be minimized), a Parameters object, and several optional arguments.
See Writing a Fitting Function for details on writing the objective function.
minimize(fcn, params, method='leastsq', args=None, kws=None, iter_cb=None, scale_covar=True,
nan_policy='raise', reduce_fcn=None, calc_covar=True, max_nfev=None, **fit_kws)
Perform the minimization of the objective function.
The minimize function takes an objective function to be minimized, a dictionary (Parameters ; Parameters)
containing the model parameters, and several optional arguments including the fitting method.
Parameters
• fcn (callable) – Objective function to be minimized. When method is ‘leastsq’ or
‘least_squares’, the objective function should return an array of residuals (difference be-
tween model and data) to be minimized in a least-squares sense. With the scalar methods the
objective function can either return the residuals array or a single scalar value. The function
must have the signature:
31
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
– ’powell’: Powell
– ’cg’: Conjugate-Gradient
– ’newton’: Newton-CG
– ’cobyla’: Cobyla
– ’bfgs’: BFGS
– ’tnc’: Truncated Newton
– ’trust-ncg’: Newton-CG trust-region
– ’trust-exact’: nearly exact trust-region
– ’trust-krylov’: Newton GLTR trust-region
– ’trust-constr’: trust-region for constrained optimization
– ’dogleg’: Dog-leg trust-region
– ’slsqp’: Sequential Linear Squares Programming
– ’emcee’: Maximum likelihood via Monte-Carlo Markov Chain
– ’shgo’: Simplicial Homology Global Optimization
– ’dual_annealing’: Dual Annealing optimization
In most cases, these methods wrap and use the method of the same name from scipy.optimize,
or use scipy.optimize.minimize with the same method argument. Thus ‘leastsq’
will use scipy.optimize.leastsq, while ‘powell’ will use scipy.optimize.minimizer(. . . ,
method=’powell’)
For more details on the fitting methods please refer to the SciPy docs.
• args (tuple, optional) – Positional arguments to pass to fcn.
• kws (dict, optional) – Keyword arguments to pass to fcn.
• iter_cb (callable, optional) – Function to be called at each fit iteration. This function
should have the signature:
where params will have the current parameter values, iter the iteration number, resid the
current residual array, and *args and **kws as passed to the objective function.
• scale_covar (bool, optional) – Whether to automatically scale the covariance matrix
(default is True).
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – Specifies action if fcn (or
a Jacobian) returns NaN values. One of:
– ’raise’ : a ValueError is raised
– ’propagate’ : the values returned from userfcn are un-altered
– ’omit’ : non-finite values are filtered
• reduce_fcn (str or callable, optional) – Function to convert a residual array to a
scalar value for the scalar minimizers. See Notes in Minimizer.
• calc_covar (bool, optional) – Whether to calculate the covariance matrix (default is
True) for solvers other than ‘leastsq’ and ‘least_squares’. Requires the numdifftools package
to be installed.
Notes
The objective function should return the value to be minimized. For the Levenberg-Marquardt algorithm from
leastsq(), this returned value must be an array, with a length greater than or equal to the number of fitting variables
in the model. For the other methods, the return value can either be a scalar or an array. If an array is returned,
the sum-of- squares of the array will be sent to the underlying fitting method, effectively doing a least-squares
optimization of the return values.
A common use for args and kws would be to pass in other data needed to calculate the residual, including such
things as the data array, dependent variable, uncertainties in the data, and other data structures for the model
calculation.
On output, params will be unchanged. The best-fit values and, where appropriate, estimated uncertainties and
correlations, will all be contained in the returned MinimizerResult. See MinimizerResult – the optimization
result for further details.
This function is simply a wrapper around Minimizer and is equivalent to:
An important component of a fit is writing a function to be minimized – the objective function. Since this function will
be called by other routines, there are fairly stringent requirements for its call signature and return value. In principle,
your function can be any Python callable, but it must look like this:
func(params, *args, **kws):
Calculate objective residual to be minimized from parameters.
Parameters
• params (Parameters) – Parameters.
• args – Positional arguments. Must match args argument to minimize().
• kws – Keyword arguments. Must match kws argument to minimize().
Returns
Residual array (generally data-model) to be minimized in the least-squares sense.
Return type
numpy.ndarray. The length of this array cannot change between calls.
A common use for the positional and keyword arguments would be to pass in other data needed to calculate the residual,
including things as the data array, dependent variable, uncertainties in the data, and other data structures for the model
calculation.
The objective function should return the value to be minimized. For the Levenberg-Marquardt algorithm from
leastsq(), this returned value must be an array, with a length greater than or equal to the number of fitting vari-
ables in the model. For the other methods, the return value can either be a scalar or an array. If an array is returned, the
sum of squares of the array will be sent to the underlying fitting method, effectively doing a least-squares optimization
of the return values.
Since the function will be passed in a dictionary of Parameters, it is advisable to unpack these to get numerical values
at the top of the function. A simple way to do this is with Parameters.valuesdict(), as shown below:
if data is None:
return model
if eps is None:
return model - data
return (model-data) / eps
In this example, x is a positional (required) argument, while the data array is actually optional (so that the function
returns the model calculation if the data is neglected). Also note that the model calculation will divide x by the value
of the period Parameter. It might be wise to ensure this parameter cannot be 0. It would be possible to use bounds on
the Parameter to do this:
is also a reasonable approach. Similarly, one could place bounds on the decay parameter to take values only between
-pi/2 and pi/2.
By default, the Levenberg-Marquardt algorithm is used for fitting. While often criticized, including the fact it finds
a local minimum, this approach has some distinct advantages. These include being fast, and well-behaved for most
curve-fitting needs, and making it easy to estimate uncertainties for and correlations between pairs of fit variables, as
discussed in MinimizerResult – the optimization result.
Alternative algorithms can also be used by providing the method keyword to the minimize() function or Minimizer.
minimize() class as listed in the Table of Supported Fitting Methods. If you have the numdifftools package installed,
lmfit will try to estimate the covariance matrix and determine parameter uncertainties and correlations if calc_covar
is True (default).
Table of Supported Fitting Methods:
Note: The objective function for the Levenberg-Marquardt method must return an array, with more elements than
variables. All other methods can return either a scalar value or an array. The Monte-Carlo Markov Chain or emcee
method has two different operating methods when the objective function returns a scalar value. See the documentation
for emcee.
Warning: Much of this documentation assumes that the Levenberg-Marquardt (leastsq) method is used. Many
of the fit statistics and estimates for uncertainties in parameters discussed in MinimizerResult – the optimization
result are done only unconditionally for this (and the least_squares) method. Lmfit versions newer than 0.9.11
provide the capability to use numdifftools to estimate the covariance matrix and calculate parameter uncertainties
and correlations for other methods as well.
result.params.pretty_print()
with results being a MinimizerResult object. Note that the method pretty_print() accepts several arguments
for customizing the output (e.g., column width, numeric format, etcetera).
class MinimizerResult(**kws)
The results of a minimization.
Minimization results include data such as status and error messages, fit statistics, and the updated (i.e., best-fit)
parameters themselves in the params attribute.
The list of (possible) MinimizerResult attributes is given below:
params
The best-fit parameters resulting from the fit.
Type
Parameters
status
Termination status of the optimizer. Its value depends on the underlying solver. Refer to message for details.
Type
int
var_names
Ordered list of variable parameter names used in optimization, and useful for understanding the values in
init_vals and covar.
Type
list
covar
Covariance matrix from minimization, with rows and columns corresponding to var_names.
Type
numpy.ndarray
init_vals
List of initial values for variable parameters using var_names.
Type
list
init_values
Dictionary of initial values for variable parameters.
Type
dict
nfev
Number of function evaluations.
Type
int
success
True if the fit succeeded, otherwise False.
Type
bool
errorbars
True if uncertainties were estimated, otherwise False.
Type
bool
message
Message about fit success.
Type
str
call_kws
Keyword arguments sent to underlying solver.
Type
dict
ier
Integer error value from scipy.optimize.leastsq (‘leastsq’ method only).
Type
int
lmdif_message
Message from scipy.optimize.leastsq (‘leastsq’ method only).
Type
str
nvarys
Number of variables in fit: 𝑁varys .
Type
int
ndata
Number of data points: 𝑁 .
Type
int
nfree
Degrees of freedom in fit: 𝑁 − 𝑁varys .
Type
int
residual
Residual array Residi . Return value of the objective function when using the best-fit values of the param-
eters.
Type
numpy.ndarray
chisqr
∑︀𝑁
Chi-square: 𝜒2 = 𝑖 [Resid𝑖 ]2 .
Type
float
redchi
Reduced chi-square: 𝜒2𝜈 = 𝜒2 /(𝑁 − 𝑁varys ).
Type
float
aic
Akaike Information Criterion statistic: 𝑁 ln(𝜒2 /𝑁 ) + 2𝑁varys .
Type
float
bic
Bayesian Information Criterion statistic: 𝑁 ln(𝜒2 /𝑁 ) + ln(𝑁 )𝑁varys .
Type
float
flatchain
A flatchain view of the sampling chain from the emcee method.
Type
pandas.DataFrame
show_candidates()
pretty_print() representation of candidates from the brute fitting method.
Table of Fit Results: These values, including the standard Goodness-of-Fit statistics, are all attributes of
the MinimizerResult object returned by minimize() or Minimizer.minimize().
Note that the calculation of chi-square and reduced chi-square assume that the returned residual function is scaled
properly to the uncertainties in the data. For these statistics to be meaningful, the person writing the function to be
minimized must scale them properly.
After a fit using the leastsq() or least_squares() method has completed successfully, standard errors for the fitted
variables and correlations between pairs of fitted variables are automatically calculated from the covariance matrix. For
other methods, the calc_covar parameter (default is True) in the Minimizer class determines whether or not to use
the numdifftools package to estimate the covariance matrix. The standard error (estimated 1𝜎 error-bar) goes into
the stderr attribute of the Parameter. The correlations with all other variables will be put into the correl attribute
of the Parameter – a dictionary with keys for all other Parameters and values of the corresponding correlation.
In some cases, it may not be possible to estimate the errors and correlations. For example, if a variable actually has no
practical effect on the fit, it will likely cause the covariance matrix to be singular, making standard errors impossible to
estimate. Placing bounds on varied Parameters makes it more likely that errors cannot be estimated, as being near the
maximum or minimum value makes the covariance matrix singular. In these cases, the errorbars attribute of the fit
result (Minimizer object) will be False.
The MinimizerResult includes the traditional chi-square and reduced chi-square statistics:
𝑁
∑︁
𝜒2 = 𝑟𝑖2
𝑖
𝜒2𝜈 2
= 𝜒 /(𝑁 − 𝑁varys )
where 𝑟 is the residual array returned by the objective function (likely to be (data-model)/uncertainty for data
modeling usages), 𝑁 is the number of data points (ndata), and 𝑁varys is number of variable parameters.
Also included are the Akaike Information Criterion, and Bayesian Information Criterion statistics, held in the aic and
bic attributes, respectively. These give slightly different measures of the relative quality for a fit, trying to balance
quality of fit with the number of variable parameters used in the fit. These are calculated as:
aic = 𝑁 ln(𝜒2 /𝑁 ) + 2𝑁varys
bic = 𝑁 ln(𝜒2 /𝑁 ) + ln(𝑁 )𝑁varys
When comparing fits with different numbers of varying parameters, one typically selects the model with lowest reduced
chi-square, Akaike information criterion, and/or Bayesian information criterion. Generally, the Bayesian information
criterion is considered the most conservative of these statistics.
As mentioned above, when a fit is complete the uncertainties for fitted Parameters as well as the correlations between
pairs of Parameters are usually calculated. This happens automatically either when using the default leastsq()
method, the least_squares() method, or for most other fitting methods if the highly-recommended numdifftools
package is available. The estimated standard error (the 1𝜎 uncertainty) for each variable Parameter will be contained in
the stderr, while the correl attribute for each Parameter will contain a dictionary of the correlation with each other
variable Parameter.
These estimates of the uncertainties are done by inverting the Hessian matrix which represents the second derivative
of fit quality for each variable parameter. There are situations for which the uncertainties cannot be estimated, which
generally indicates that this matrix cannot be inverted because one of the fit is not actually sensitive to one of the
variables. This can happen if a Parameter is stuck at an upper or lower bound, if the variable is simply not used by the
fit, or if the value for the variable is such that it has no real influence on the fit.
In principle, the scale of the uncertainties in the Parameters is closely tied to the goodness-of-fit statistics chi-square and
reduced chi-square (chisqr and redchi). The standard errors or 1𝜎 uncertainties are those that increase chi-square by
1. Since a “good fit” should have redchi of around 1, this requires that the data uncertainties (and to some extent the
sampling of the N data points) is correct. Unfortunately, it is often not the case that one has high-quality estimates of the
data uncertainties (getting the data is hard enough!). Because of this common situation, the uncertainties reported and
held in stderr are not those that increase chi-square by 1, but those that increase chi-square by reduced chi-square. This
is equivalent to rescaling the uncertainty in the data such that reduced chi-square would be 1. To be clear, this rescaling
is done by default because if reduced chi-square is far from 1, this rescaling often makes the reported uncertainties
sensible, and if reduced chi-square is near 1 it does little harm. If you have good scaling of the data uncertainty and
believe the scale of the residual array is correct, this automatic rescaling can be turned off using scale_covar=False.
Note that the simple (and fast!) approach to estimating uncertainties and correlations by inverting the second derivative
matrix assumes that the components of the residual array (if, indeed, an array is used) are distributed around 0 with a
normal (Gaussian distribution), and that a map of probability distributions for pairs would be elliptical – the size of the
of ellipse gives the uncertainty itself and the eccentricity of the ellipse gives the correlation. This simple approach to
assessing uncertainties ignores outliers, highly asymmetric uncertainties, or complex correlations between Parameters.
In fact, it is not too hard to come up with problems where such effects are important. Our experience is that the
automated results are usually the right scale and quite reasonable as initial estimates, but a more thorough exploration of
the Parameter space using the tools described in Minimizer.emcee() - calculating the posterior probability distribution
of parameters and An advanced example for evaluating confidence intervals can give a more complete understanding
of the distributions and relations between Parameters.
# <examples/doc_fitting_withreport.py>
from numpy import exp, linspace, pi, random, sign, sin
random.seed(0)
x = linspace(0.0, 250., 1001)
noise = random.normal(scale=0.7215, size=x.size)
data = residual(p_true, x) + noise
print(fit_report(out))
# <end examples/doc_fitting_withreport.py>
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 83
# data points = 1001
# variables = 4
chi-square = 498.811759
reduced chi-square = 0.50031270
Akaike info crit = -689.222517
Bayesian info crit = -669.587497
[[Variables]]
amp: 13.9121959 +/- 0.14120321 (1.01%) (init = 13)
period: 5.48507038 +/- 0.02666520 (0.49%) (init = 2)
shift: 0.16203673 +/- 0.01405662 (8.67%) (init = 0)
decay: 0.03264539 +/- 3.8015e-04 (1.16%) (init = 0.02)
[[Correlations]] (unreported correlations are < 0.100)
C(period, shift) = +0.7974
C(amp, decay) = +0.5816
C(amp, shift) = -0.2966
C(amp, period) = -0.2432
C(shift, decay) = -0.1819
C(period, decay) = -0.1496
To be clear, you can get at all of these values from the fit result out and out.params. For example, a crude printout
of the best fit variables and standard errors could be done as
print('-------------------------------')
print('Parameter Value Stderr')
for name, param in out.params.items():
print(f'{name:7s} {param.value:11.5f} {param.stderr:11.5f}')
-------------------------------
Parameter Value Stderr
amp 13.91220 0.14120
period 5.48507 0.02667
shift 0.16204 0.01406
decay 0.03265 0.00038
An iteration callback function is a function to be called at each iteration, just after the objective function is called. The
iteration callback allows user-supplied code to be run at each iteration, and can be used to abort a fit.
iter_cb(params, iter, resid, *args, **kws):
User-supplied function to be run at each iteration.
Parameters
• params (Parameters) – Parameters.
• iter (int) – Iteration number.
• resid (numpy.ndarray) – Residual array.
• args – Positional arguments. Must match args argument to minimize()
For full control of the fitting process, you will want to create a Minimizer object.
class Minimizer(userfcn, params, fcn_args=None, fcn_kws=None, iter_cb=None, scale_covar=True,
nan_policy='raise', reduce_fcn=None, calc_covar=True, max_nfev=None, **kws)
A general minimizer for curve fitting and optimization.
Parameters
• userfcn (callable) – Objective function that returns the residual (difference between
model and data) to be minimized in a least-squares sense. This function must have the sig-
nature:
where params will have the current parameter values, iter the iteration number, resid the
current residual array, and *fcn_args and **fcn_kws are passed to the objective function.
• scale_covar (bool, optional) – Whether to automatically scale the covariance matrix
(default is True).
• nan_policy ({'raise', 'propagate', 'omit}, optional) – Specifies action if userfcn
(or a Jacobian) returns NaN values. One of:
– ’raise’ : a ValueError is raised (default)
– ’propagate’ : the values returned from userfcn are un-altered
– ’omit’ : non-finite values are filtered
• reduce_fcn (str or callable, optional) – Function to convert a residual array to a
scalar value for the scalar minimizers. Optional values are (where r is the residual array):
– None : sum-of-squares of residual (default)
= (r*r).sum()
Notes
The objective function should return the value to be minimized. For the Levenberg-Marquardt algorithm from
leastsq() or least_squares(), this returned value must be an array, with a length greater than or equal to
the number of fitting variables in the model. For the other methods, the return value can either be a scalar or
an array. If an array is returned, the sum-of-squares of the array will be sent to the underlying fitting method,
effectively doing a least-squares optimization of the return values. If the objective function returns non-finite
values then a ValueError will be raised because the underlying solvers cannot deal with them.
A common use for the fcn_args and fcn_kws would be to pass in other data needed to calculate the residual,
including such things as the data array, dependent variable, uncertainties in the data, and other data structures
for the model calculation.
The Minimizer object has a few public methods:
Minimizer.minimize(method='leastsq', params=None, **kws)
Perform the minimization.
Parameters
• method (str, optional) – Name of the fitting method to use. Valid values are:
– ’leastsq’: Levenberg-Marquardt (default)
– ’least_squares’: Least-Squares minimization, using Trust Region Reflective method
– ’differential_evolution’: differential evolution
– ’brute’: brute force method
– ’basinhopping’: basinhopping
– ’ampgo’: Adaptive Memory Programming for Global Optimization
– ’nelder’: Nelder-Mead
– ’lbfgsb’: L-BFGS-B
– ’powell’: Powell
– ’cg’: Conjugate-Gradient
– ’newton’: Newton-CG
– ’cobyla’: Cobyla
– ’bfgs’: BFGS
– ’tnc’: Truncated Newton
– ’trust-ncg’: Newton-CG trust-region
– ’trust-exact’: nearly exact trust-region
– ’trust-krylov’: Newton GLTR trust-region
– ’trust-constr’: trust-region for constrained optimization
– ’dogleg’: Dog-leg trust-region
– ’slsqp’: Sequential Linear Squares Programming
– ’emcee’: Maximum likelihood via Monte-Carlo Markov Chain
– ’shgo’: Simplicial Homology Global Optimization
– ’dual_annealing’: Dual Annealing optimization
In most cases, these methods wrap and use the method with the same name
from scipy.optimize, or use scipy.optimize.minimize with the same method ar-
gument. Thus ‘leastsq’ will use scipy.optimize.leastsq, while ‘powell’ will use
scipy.optimize.minimizer(. . . , method=’powell’).
For more details on the fitting methods please refer to the SciPy documentation.
• params (Parameters, optional) – Parameters of the model to use as starting values.
• **kws (optional) – Additional arguments are passed to the underlying minimization
method.
Returns
Object containing the optimized parameters and several goodness-of-fit statistics.
Return type
MinimizerResult
Changed in version 0.9.0: Return value changed to MinimizerResult.
Minimizer.leastsq(params=None, max_nfev=None, **kws)
Use Levenberg-Marquardt minimization to perform a fit.
It assumes that the input Parameters have been initialized, and a function to minimize has been properly set up.
When possible, this calculates the estimated uncertainties and variable correlations from the covariance matrix.
This method calls scipy.optimize.leastsq and, by default, numerical derivatives are used.
Parameters
• params (Parameters, optional) – Parameters to use as starting point.
• max_nfev (int or None, optional) – Maximum number of function evaluations. De-
faults to 2000*(nvars+1), where nvars is the number of variable parameters.
• **kws (dict, optional) – Minimizer options to pass to scipy.optimize.leastsq.
Returns
Object containing the optimized parameters and several goodness-of-fit statistics.
Return type
MinimizerResult
Changed in version 0.9.0: Return value changed to MinimizerResult.
Parameters
• method (str, optional) – Name of the fitting method to use. One of:
– ’Nelder-Mead’ (default)
– ’L-BFGS-B’
– ’Powell’
– ’CG’
– ’Newton-CG’
– ’COBYLA’
– ’BFGS’
– ’TNC’
– ’trust-ncg’
– ’trust-exact’
– ’trust-krylov’
– ’trust-constr’
– ’dogleg’
– ’SLSQP’
– ’differential_evolution’
• params (Parameters, optional) – Parameters to use as starting point.
• max_nfev (int or None, optional) – Maximum number of function evaluations. De-
faults to 2000*(nvars+1), where nvars is the number of variable parameters.
• **kws (dict, optional) – Minimizer options pass to scipy.optimize.minimize.
Returns
Object containing the optimized parameters and several goodness-of-fit statistics.
Return type
MinimizerResult
Notes
If the objective function returns a NumPy array instead of the expected scalar, the sum-of-squares of the array
will be used.
Note that bounds and constraints can be set on Parameters for any of these methods, so are not supported sepa-
rately for those designed to use bounds. However, if you use the differential_evolution method you must
specify finite (min, max) for each varying Parameter.
Minimizer.prepare_fit(params=None)
Prepare parameters for fitting.
Prepares and initializes model and Parameters for subsequent fitting. This routine prepares the conversion of
Parameters into fit variables, organizes parameter bounds, and parses, “compiles” and checks constrain ex-
pressions. The method also creates and returns a new instance of a MinimizerResult object that contains the
copy of the Parameters that will actually be varied in the fit.
Parameters
params (Parameters, optional) – Contains the Parameters for the model; if None, then the
Parameters used to initialize the Minimizer object are used.
Return type
MinimizerResult
Notes
This method is called directly by the fitting methods, and it is generally not necessary to call this function ex-
plicitly.
Changed in version 0.9.0: Return value changed to MinimizerResult.
Minimizer.brute(params=None, Ns=20, keep=50, workers=1, max_nfev=None)
Use the brute method to find the global minimum of a function.
The following parameters are passed to scipy.optimize.brute and cannot be changed:
It assumes that the input Parameters have been initialized, and a function to minimize has been properly set up.
Parameters
• params (Parameters, optional) – Contains the Parameters for the model. If None, then
the Parameters used to initialize the Minimizer object are used.
• Ns (int, optional) – Number of grid points along the axes, if not otherwise specified (see
Notes).
• keep (int, optional) – Number of best candidates from the brute force method that are
stored in the candidates attribute. If ‘all’, then all grid points from scipy.optimize.brute
are stored as candidates.
• workers (int or map-like callable, optional) – For parallel evaluation of the grid
(see scipy.optimize.brute for more details).
• max_nfev (int or None, optional) – Maximum number of function evaluations (de-
fault is None). Defaults to 200000*(nvarys+1).
Returns
Object containing the parameters from the brute force method. The return values (x0, fval,
grid, Jout) from scipy.optimize.brute are stored as brute_<parname> attributes. The Min-
imizerResult also contains the :attr:candidates attribute and show_candidates() method.
The candidates attribute contains the parameters and chisqr from the brute force method
as a namedtuple, ('Candidate', ['params', 'score']) sorted on the (lowest) chisqr
value. To access the values for a particular candidate one can use result.candidate[#].
params or result.candidate[#].score, where a lower # represents a better candidate. The
show_candidates() method uses the pretty_print() method to show a specific candidate-#
or all candidates when no number is specified.
Return type
MinimizerResult
New in version 0.9.6.
Notes
The brute() method evaluates the function at each point of a multidimensional grid of points. The grid
points are generated from the parameter ranges using Ns and (optional) brute_step. The implementation in
scipy.optimize.brute requires finite bounds and the range is specified as a two-tuple (min, max) or slice-object
(min, max, brute_step). A slice-object is used directly, whereas a two-tuple is converted to a slice object
that interpolates Ns points from min to max, inclusive.
In addition, the brute() method in lmfit, handles three other scenarios given below with their respective slice-
object:
• lower bound (min) and brute_step are specified:
range = (min, min + Ns * brute_step, brute_step).
• upper bound (max) and brute_step are specified:
range = (max - Ns * brute_step, max, brute_step).
Returns
Object containing the parameters from the ampgo method, with fit parameters, statistics and such.
The return values (x0, fval, eval, msg, tunnel) are stored as ampgo_<parname> attributes.
Return type
MinimizerResult
New in version 0.9.10.
Notes
SHGO stands for “simplicial homology global optimization” and calls scipy.optimize.shgo using its default ar-
guments.
Parameters
• params (Parameters, optional) – Contains the Parameters for the model. If None, then
the Parameters used to initialize the Minimizer object are used.
• max_nfev (int or None, optional) – Maximum number of function evaluations. De-
faults to 200000*(nvars+1), where nvars is the number of variable parameters.
• **kws (dict, optional) – Minimizer options to pass to the SHGO algorithm.
Returns
Object containing the parameters from the SHGO method. The return values specific to
scipy.optimize.shgo (x, xl, fun, funl, nfev, nit, nlfev, nlhev, and nljev) are stored as
shgo_<parname> attributes.
Return type
MinimizerResult
New in version 0.9.14.
Minimizer.dual_annealing(params=None, max_nfev=None, **kws)
Use the dual_annealing algorithm to find the global minimum.
This method calls scipy.optimize.dual_annealing using its default arguments.
Parameters
• params (Parameters, optional) – Contains the Parameters for the model. If None, then
the Parameters used to initialize the Minimizer object are used.
• max_nfev (int or None, optional) – Maximum number of function evaluations. De-
faults to 200000*(nvars+1), where nvars is the number of variables.
• **kws (dict, optional) – Minimizer options to pass to the dual_annealing algorithm.
Returns
Object containing the parameters from the dual_annealing method. The return values specific to
scipy.optimize.dual_annealing (x, fun, nfev, nhev, njev, and nit) are stored as da_<parname>
attributes.
Return type
MinimizerResult
New in version 0.9.14.
Minimizer.emcee(params=None, steps=1000, nwalkers=100, burn=0, thin=1, ntemps=1, pos=None,
reuse_sampler=False, workers=1, float_behavior='posterior', is_weighted=True, seed=None,
progress=True, run_mcmc_kwargs={})
Bayesian sampling of the posterior distribution.
The method uses the emcee Markov Chain Monte Carlo package and assumes that the prior is Uniform. You
need to have emcee version 3 or newer installed to use this method.
Parameters
• params (Parameters, optional) – Parameters to use as starting point. If this is not spec-
ified then the Parameters used to initialize the Minimizer object are used.
• steps (int, optional) – How many samples you would like to draw from the posterior
distribution for each of the walkers?
• nwalkers (int, optional) – Should be set so 𝑛𝑤𝑎𝑙𝑘𝑒𝑟𝑠 >> 𝑛𝑣𝑎𝑟𝑦𝑠, where nvarys
are the number of parameters being varied during the fit. ‘Walkers are the members of the
ensemble. They are almost like separate Metropolis-Hastings chains but, of course, the pro-
posal distribution for a given walker depends on the positions of all the other walkers in the
ensemble.’ - from the emcee webpage.
• burn (int, optional) – Discard this many samples from the start of the sampling regime.
• thin (int, optional) – Only accept 1 in every thin samples.
• ntemps (int, deprecated) – ntemps has no effect.
• pos (numpy.ndarray, optional) – Specify the initial positions for the sampler, an ndar-
ray of shape (nwalkers, nvarys). You can also initialise using a previous chain of the
same nwalkers and nvarys. Note that nvarys may be one larger than you expect it to be if
your userfcn returns an array and is_weighted=False.
• reuse_sampler (bool, optional) – Set to True if you have already run emcee with the
Minimizer instance and want to continue to draw from its sampler (and so retain the chain
history). If False, a new sampler is created. The keywords nwalkers, pos, and params will
be ignored when this is set, as they will be set by the existing sampler. Important: the
Parameters used to create the sampler must not change in-between calls to emcee. Alteration
of Parameters would include changed min, max, vary and expr attributes. This may happen,
for example, if you use an altered Parameters object and call the minimize method in-between
calls to emcee.
• workers (Pool-like or int, optional) – For parallelization of sampling. It can be
any Pool-like object with a map method that follows the same calling sequence as the built-in
map function. If int is given as the argument, then a multiprocessing-based pool is spawned
internally with the corresponding number of parallel processes. ‘mpi4py’-based paralleliza-
tion and ‘joblib’-based parallelization pools can also be used here. Note: because of multi-
processing overhead it may only be worth parallelising if the objective function is expensive
to calculate, or if there are a large number of objective evaluations per step (nwalkers *
nvarys).
• float_behavior (str, optional) – Meaning of float (scalar) output of objective func-
tion. Use ‘posterior’ if it returns a log-posterior probability or ‘chi2’ if it returns 𝜒2 . See
Notes for further details.
• is_weighted (bool, optional) – Has your objective function been weighted by mea-
surement uncertainties? If is_weighted=True then your objective function is assumed
to return residuals that have been divided by the true measurement uncertainty (data -
model) / sigma. If is_weighted=False then the objective function is assumed to return
unweighted residuals, data - model. In this case emcee will employ a positive measure-
ment uncertainty during the sampling. This measurement uncertainty will be present in the
output params and output chain with the name __lnsigma. A side effect of this is that you
cannot use this parameter name yourself. Important: this parameter only has any effect if
your objective function returns an array. If your objective function returns a float, then this
parameter is ignored. See Notes for more details.
• seed (int or numpy.random.RandomState, optional) – If seed is an int, a new
numpy.random.RandomState instance is used, seeded with seed. If seed is already a
numpy.random.RandomState instance, then that numpy.random.RandomState instance is
used. Specify seed for repeatable minimizations.
• progress (bool, optional) – Print a progress bar to the console while running.
• run_mcmc_kwargs (dict, optional) – Additional (optional) keyword arguments that are
passed to emcee.EnsembleSampler.run_mcmc.
Returns
MinimizerResult object containing updated params, statistics, etc. The updated params rep-
resent the median of the samples, while the uncertainties are half the difference of the 15.87
and 84.13 percentiles. The MinimizerResult contains a few additional attributes: chain contain
the samples and has shape ((steps - burn) // thin, nwalkers, nvarys). flatchain is
a pandas.DataFrame of the flattened chain, that can be accessed with result.flatchain[parname].
lnprob contains the log probability for each sample in chain. The sample with the highest prob-
ability corresponds to the maximum likelihood estimate. acor is an array containing the auto-
correlation time for each parameter if the auto-correlation time can be computed from the chain.
Finally, acceptance_fraction (an array of the fraction of steps accepted for each walker).
Return type
MinimizerResult
Notes
This method samples the posterior distribution of the parameters using Markov Chain Monte Carlo. It calcu-
lates the log-posterior probability of the model parameters, F, given the data, D, ln 𝑝(𝐹𝑡𝑟𝑢𝑒 |𝐷). This ‘posterior
probability’ is given by:
where ln 𝑝(𝐷|𝐹𝑡𝑟𝑢𝑒 ) is the ‘log-likelihood’ and ln 𝑝(𝐹𝑡𝑟𝑢𝑒 ) is the ‘log-prior’. The default log-prior encodes
prior information known about the model that the log-prior probability is -numpy.inf (impossible) if any of
the parameters is outside its limits, and is zero if all the parameters are inside their bounds (uniform prior). The
log-likelihood function is1 :
1 ∑︁ (𝑔𝑛 (𝐹𝑡𝑟𝑢𝑒 ) − 𝐷𝑛 )2
[︂ ]︂
2
ln 𝑝(𝐷|𝐹𝑡𝑟𝑢𝑒 ) = − + ln(2𝜋𝑠 𝑛 )
2 𝑛 𝑠2𝑛
The first term represents the residual (𝑔 being the generative model, 𝐷𝑛 the data and 𝑠𝑛 the measurement uncer-
tainty). This gives 𝜒2 when summed over all data points. The objective function may also return the log-posterior
probability, ln 𝑝(𝐹𝑡𝑟𝑢𝑒 |𝐷). Since the default log-prior term is zero, the objective function can also just return
the log-likelihood, unless you wish to create a non-uniform prior.
If the objective function returns a float value, this is assumed by default to be the log-posterior proba-
bility, (float_behavior default is ‘posterior’). If your objective function returns 𝜒2 , then you should use
float_behavior='chi2' instead.
By default objective functions may return an ndarray of (possibly weighted) residuals. In this case, use
is_weighted to select whether these are correctly weighted by measurement uncertainty. Note that this ignores the
second term above, so that to calculate a correct log-posterior probability value your objective function should
return a float value. With is_weighted=False the data uncertainty, s_n, will be treated as a nuisance pa-
rameter to be marginalized out. This uses strictly positive uncertainty (homoscedasticity) for each data point,
𝑠𝑛 = exp(__lnsigma). __lnsigma will be present in MinimizerResult.params, as well as Minimizer.chain and
nvarys will be increased by one.
1 https://emcee.readthedocs.io
References
Minimizer.emcee() can be used to obtain the posterior probability distribution of parameters, given a set of ex-
perimental data. Note that this method does not actually perform a fit at all. Instead, it explores parameter space to
determine the probability distributions for the parameters, but without an explicit goal of attempting to refine the so-
lution. It should not be used for fitting, but it is a useful method to to more thoroughly explore the parameter space
around the solution after a fit has been done and thereby get an improved understanding of the probability distribution
for the parameters. It may be able to refine your estimate of the most likely values for a set of parameters, but it will
not iteratively find a good solution to the minimization problem. To use this method effectively, you should first use
another minimization method and then use this method to explore the parameter space around thosee best-fit values.
To illustrate this, we’ll use an example problem of fitting data to function of a double exponential decay, including a
modest amount of Gaussian noise to the data. Note that this example is the same problem used in An advanced example
for evaluating confidence intervals for evaluating confidence intervals in the parameters, which is a similar goal to the
one here.
import lmfit
p = lmfit.Parameters()
p.add_many(('a1', 4.), ('a2', 4.), ('t1', 3.), ('t2', 3., True))
def residual(p):
v = p.valuesdict()
return v['a1'] * np.exp(-x / v['t1']) + v['a2'] * np.exp(-(x - 0.1) / v['t2']) - y
Solving with minimize() gives the Maximum Likelihood solution. Note that we use the robust Nelder-Mead method
here. The default Levenberg-Marquardt method seems to have difficulty with exponential decays, though it can refine
the solution if starting near the solution:
[[Variables]]
a1: 2.98623689 +/- 0.15010519 (5.03%) (init = 4)
a2: -4.33525597 +/- 0.11765821 (2.71%) (init = 4)
t1: 1.30993186 +/- 0.13449653 (10.27%) (init = 3)
t2: 11.8240752 +/- 0.47172598 (3.99%) (init = 3)
[[Correlations]] (unreported correlations are < 0.500)
C(a2, t2) = +0.9876
C(a2, t1) = -0.9278
(continues on next page)
and plotting the fit using the Maximum Likelihood solution gives the graph below:
plt.plot(x, y, 'o')
plt.plot(x, residual(mi.params) + y, label='best fit')
plt.legend()
plt.show()
Note that the fit here (for which the numdifftools package is installed) does estimate and report uncertainties in the
parameters and correlations for the parameters, and reports the correlation of parameters a2 and t2 to be very high.
As we’ll see, these estimates are pretty good, but when faced with such high correlation, it can be helpful to get the full
probability distribution for the parameters. MCMC methods are very good for this.
Furthermore, we wish to deal with the data uncertainty. This is called marginalisation of a nuisance parameter. emcee
requires a function that returns the log-posterior probability. The log-posterior probability is a sum of the log-prior
probability and log-likelihood functions. The log-prior probability is assumed to be zero if all the parameters are within
their bounds and -np.inf if any of the parameters are outside their bounds.
If the objective function returns an array of unweighted residuals (i.e., data-model) as is the case here, you can
use is_weighted=False as an argument for emcee. In that case, emcee will automatically add/use the __lnsigma
parameter to estimate the true uncertainty in the data. To place boundaries on this parameter one can do:
Now we have to set up the minimizer and do the sampling (again, just to be clear, this is not doing a fit):
As mentioned in the Notes for Minimizer.emcee(), the is_weighted argument will be ignored if your objective
function returns a float instead of an array. For the documentation we set progress=False; the default is to print a
progress bar to the Terminal if the tqdm package is installed.
The success of the method (i.e., whether or not the sampling went well) can be assessed by checking the integrated
autocorrelation time and/or the acceptance fraction of the walkers. For this specific example the autocorrelation time
could not be estimated because the “chain is too short”. Instead, we plot the acceptance fraction per walker and its
mean value suggests that the sampling worked as intended (as a rule of thumb the value should be between 0.2 and
0.5).
plt.plot(res.acceptance_fraction, 'o')
plt.xlabel('walker')
plt.ylabel('acceptance fraction')
plt.show()
With the results from emcee, we can visualize the posterior distributions for the parameters using the corner package:
import corner
The values reported in the MinimizerResult are the medians of the probability distributions and a 1 𝜎 quantile,
estimated as half the difference between the 15.8 and 84.2 percentiles. Printing these values:
You can see that this recovered the right uncertainty level on the data. Note that these values agree pretty well with the
results, uncertainties and correlations found by the fit and using numdifftools to estimate the covariance matrix. That
is, even though the parameters a2, t1, and t2 are all highly correlated and do not display perfectly Gaussian probability
distributions, the probability distributions found by explicitly sampling the parameter space are not so far from elliptical
as to make the simple (and much faster) estimates from inverting the covariance matrix completely invalid.
As mentioned above, the result from emcee reports the median values, which are not necessarily the same as the
Maximum Likelihood Estimate. To obtain the values for the Maximum Likelihood Estimation (MLE) we find the
location in the chain with the highest probability:
highest_prob = np.argmax(res.lnprob)
hp_loc = np.unravel_index(highest_prob, res.lnprob.shape)
mle_soln = res.chain[hp_loc]
for i, par in enumerate(p):
p[par].value = mle_soln[i]
Here the difference between MLE and median value are seen to be below 0.5%, and well within the estimated 1-𝜎
uncertainty.
Finally, we can use the samples from emcee to work out the 1- and 2-𝜎 error estimates.
And we see that the initial estimates for the 1-𝜎 standard error using numdifftools was not too bad. We’ll return
to this example problem in An advanced example for evaluating confidence intervals and use a different method to
calculate the 1- and 2-𝜎 error bars.
SEVEN
A common use of least-squares minimization is curve fitting, where one has a parametrized model function meant
to explain some phenomena and wants to adjust the numerical values for the model so that it most closely matches
some data. With scipy, such problems are typically solved with scipy.optimize.curve_fit, which is a wrapper around
scipy.optimize.leastsq. Since lmfit’s minimize() is also a high-level wrapper around scipy.optimize.leastsq it can be
used for curve-fitting problems. While it offers many benefits over scipy.optimize.leastsq, using minimize() for many
curve-fitting problems still requires more effort than using scipy.optimize.curve_fit.
The Model class in lmfit provides a simple and flexible approach to curve-fitting problems. Like
scipy.optimize.curve_fit, a Model uses a model function – a function that is meant to calculate a model for some phe-
nomenon – and then uses that to best match an array of supplied data. Beyond that similarity, its interface is rather
different from scipy.optimize.curve_fit, for example in that it uses Parameters, but also offers several other important
advantages.
In addition to allowing you to turn any model function into a curve-fitting method, lmfit also provides canonical defi-
nitions for many known lineshapes such as Gaussian or Lorentzian peaks and Exponential decays that are widely used
in many scientific domains. These are available in the models module that will be discussed in more detail in the next
chapter (Built-in Fitting Models in the models module). We mention it here as you may want to consult that list before
writing your own model. For now, we focus on turning Python functions into high-level fitting models with the Model
class, and using these to fit data.
Let’s start with a simple and common example of fitting data to a Gaussian peak. As we will see, there is a built-in
GaussianModel class that can help do this, but here we’ll build our own. We start with a simple definition of the
model function:
We want to use this function to fit to data 𝑦(𝑥) represented by the arrays y and x. With scipy.optimize.curve_fit, this
would be:
61
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
That is, we create data, make an initial guess of the model values, and run scipy.optimize.curve_fit with the model func-
tion, data arrays, and initial guesses. The results returned are the optimal values for the parameters and the covariance
matrix. It’s simple and useful, but it misses the benefits of lmfit.
With lmfit, we create a Model that wraps the gaussian model function, which automatically generates the appropriate
residual function, and determines the corresponding parameter names from the function signature itself:
gmodel = Model(gaussian)
print(f'parameter names: {gmodel.param_names}')
print(f'independent variables: {gmodel.independent_vars}')
As you can see, the Model gmodel determined the names of the parameters and the independent variables. By default,
the first argument of the function is taken as the independent variable, held in independent_vars, and the rest of
the functions positional arguments (and, in certain cases, keyword arguments – see below) are used for Parameter
names. Thus, for the gaussian function above, the independent variable is x, and the parameters are named amp,
cen, and wid, and – all taken directly from the signature of the model function. As we will see below, you can modify
the default assignment of independent variable / arguments and specify yourself what the independent variable is and
which function arguments should be identified as parameter names.
Parameters are not created when the model is created. The model knows what the parameters should be named,
but nothing about the scale and range of your data. To help you create Parameters for a Model, each model has a
make_params() method that will generate parameters with the expected names. You will have to do this, or make
Parameters some other way (say, with create_params()), and assign initial values for all Parameters. You can also
assign other attributes when doing this:
params = gmodel.make_params()
This creates the Parameters but does not automatically give them initial values since it has no idea what the scale
should be. If left unspecified, the initial values will be -Inf, which will generally fail to give useful results. You can
set initial values for parameters with keyword arguments to make_params():
or assign them (and other parameter properties) after the Parameters class has been created.
A Model has several methods associated with it. For example, one can use the eval() method to evaluate the model or
the fit() method to fit data to this model with a Parameter object. Both of these methods can take explicit keyword
arguments for the parameter values. For example, one could use eval() to calculate the predicted function:
or with:
Admittedly, this a slightly long-winded way to calculate a Gaussian function, given that you could have called your
gaussian function directly. But now that the model is set up, we can use its fit() method to fit this model to data,
as with:
or with:
Putting everything together, included in the examples folder with the source code, is:
# <examples/doc_model_gaussian.py>
import matplotlib.pyplot as plt
from numpy import exp, loadtxt, pi, sqrt
data = loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
gmodel = Model(gaussian)
result = gmodel.fit(y, x=x, amp=5, cen=5, wid=1)
print(result.fit_report())
plt.plot(x, y, 'o')
plt.plot(x, result.init_fit, '--', label='initial fit')
plt.plot(x, result.best_fit, '-', label='best fit')
plt.legend()
plt.show()
# <end examples/doc_model_gaussian.py>
which is pretty compact and to the point. The returned result will be a ModelResult object. As we will see below,
this has many components, including a fit_report() method, which will show:
[[Model]]
Model(gaussian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 33
# data points = 101
# variables = 3
chi-square = 3.40883599
reduced chi-square = 0.03478404
Akaike info crit = -336.263713
Bayesian info crit = -328.418352
(continues on next page)
As the script shows, the result will also have init_fit for the fit with the initial parameter values and a best_fit for
the fit with the best fit parameter values. These can be used to generate the following plot:
which shows the data in blue dots, the best fit as a solid green line, and the initial fit as a dashed orange line.
Note that the model fitting was really performed with:
gmodel = Model(gaussian)
result = gmodel.fit(y, params, x=x, amp=5, cen=5, wid=1)
These lines clearly express that we want to turn the gaussian function into a fitting model, and then fit the 𝑦(𝑥) data
to this model, starting with values of 5 for amp, 5 for cen and 1 for wid. In addition, all the other features of lmfit are
included: Parameters can have bounds and constraints and the result is a rich object that can be reused to explore the
model fit in detail.
The Model class provides a general way to wrap a pre-defined function as a fitting model.
class Model(func, independent_vars=None, param_names=None, nan_policy='raise', prefix='', name=None,
**kws)
Create a model from a user-supplied model function.
The model function will normally take an independent variable (generally, the first argument) and a series of
arguments that are meant to be parameters for the model. It will return an array of data to model some data as
for a curve-fitting problem.
Parameters
• func (callable) – Function to be wrapped.
• independent_vars (list of str, optional) – Arguments to func that are independent vari-
ables (default is None).
• param_names (list of str, optional) – Names of arguments to func that are to be made
into parameters (default is None).
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• prefix (str, optional) – Prefix used for the model.
• name (str, optional) – Name for the model. When None (default) the name is the same
as the model function (func).
• **kws (dict, optional) – Additional keyword arguments to pass to model function.
Notes
1. Parameter names are inferred from the function arguments, and a residual function is automatically con-
structed.
2. The model function must return an array that will be the same size as the data being modeled.
3. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
Examples
The model function will normally take an independent variable (generally, the first argument) and a series of
arguments that are meant to be parameters for the model. Thus, a simple peak using a Gaussian defined as:
this will automatically discover the names of the independent variables and parameters:
Model.eval(params=None, **kwargs)
Evaluate the model with supplied parameters and keyword arguments.
Parameters
• params (Parameters, optional) – Parameters to use in Model.
• **kwargs (optional) – Additional keyword arguments to pass to model function.
Returns
Value of model given the parameters and other arguments.
Return type
numpy.ndarray, float, int or complex
Notes
1. if params is None, the values for all parameters are expected to be provided as keyword arguments.
2. If params is given, and a keyword argument for a parameter value is also given, the keyword argument will
be used in place of the value in the value in params.
3. all non-parameter arguments for the model function, including all the independent variables will need to
be passed in using keyword arguments.
4. The return types are generally numpy.ndarray, but may depends on the model function and input independent
variables. That is, return values may be Python float, int, or complex values.
Model.fit(data, params=None, weights=None, method='leastsq', iter_cb=None, scale_covar=True,
verbose=False, fit_kws=None, nan_policy=None, calc_covar=True, max_nfev=None, **kwargs)
Fit the model to the data using the supplied Parameters.
Parameters
• data (array_like) – Array of data to be fit.
• params (Parameters, optional) – Parameters to use in fit (default is None).
• weights (array_like, optional) – Weights to use for the calculation of the fit residual
[i.e., weights*(data-fit)]. Default is None; must have the same size as data.
• method (str, optional) – Name of fitting method to use (default is ‘leastsq’).
• iter_cb (callable, optional) – Callback function to call at each iteration (default is
None).
• scale_covar (bool, optional) – Whether to automatically scale the covariance matrix
when calculating uncertainties (default is True).
• verbose (bool, optional) – Whether to print a message when a new parameter is added
because of a hint (default is True).
• fit_kws (dict, optional) – Options to pass to the minimizer being used.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – What to do when encoun-
tering NaNs when fitting Model.
• calc_covar (bool, optional) – Whether to calculate the covariance matrix (default is
True) for solvers other than ‘leastsq’ and ‘least_squares’. Requires the numdifftools pack-
age to be installed.
• max_nfev (int or None, optional) – Maximum number of function evaluations (de-
fault is None). The default value depends on the fitting method.
• **kwargs (optional) – Arguments to pass to the model function, possibly overriding pa-
rameters.
Return type
ModelResult
Notes
1. if params is None, the values for all parameters are expected to be provided as keyword arguments. Mixing
params and keyword arguments is deprecated (see Model.eval).
2. all non-parameter arguments for the model function, including all the independent variables will need to
be passed in using keyword arguments.
3. Parameters are copied on input, so that the original Parameter objects are unchanged, and the updated values
are in the returned ModelResult.
Examples
Take t to be the independent variable and data to be the curve we will fit. Use keyword arguments to set initial
guesses:
Model.guess(data, x, **kws)
Guess starting values for the parameters of a Model.
This is not implemented for all models, but is available for many of the built-in models.
Parameters
• data (array_like) – Array of data (i.e., y-values) to use to guess parameter values.
• x (array_like) – Array of values for the independent variable (i.e., x-values).
• **kws (optional) – Additional keyword arguments, passed to model function.
Returns
Initial, guessed values for the parameters of a Model.
Return type
Parameters
Raises
NotImplementedError – If the guess method is not implemented for a Model.
Notes
Should be implemented for each model subclass to run self.make_params(), update starting values and return a
Parameters object.
Changed in version 1.0.3: Argument x is now explicitly required to estimate starting values.
Model.make_params(verbose=False, **kwargs)
Create a Parameters object for a Model.
Parameters
• verbose (bool, optional) – Whether to print out messages (default is False).
• **kwargs (optional) –
Parameter names and initial values or dictionaries of
values and attributes.
Returns
params – Parameters object for the Model.
Return type
Parameters
Notes
1. Parameter values can be numbers (floats or ints) to set the parameter value, or dictionaries with any of the
following keywords: value, vary, min, max, expr, brute_step, is_init_value to set those parameter
attributes.
2. This method will also apply any default values or parameter hints that may have been defined for the model.
Example
Model.set_param_hint(name, **kwargs)
Set hints to use when creating parameters with make_params().
The given hint can include optional bounds and constraints (value, vary, min, max, expr), which will be
used by Model.make_params() when building default parameters.
While this can be used to set initial values, Model.make_params or the function create_params should be pre-
ferred for creating parameters with initial values.
The intended use here is to control how a Model should create parameters, such as setting bounds that are required
by the mathematics of the model (for example, that a peak width cannot be negative), or to define common
constrained parameters.
Parameters
• name (str) – Parameter name, can include the models prefix or not.
• **kwargs (optional) – Arbitrary keyword arguments, needs to be a Parameter attribute.
Can be any of the following:
– value
[float, optional] Numerical Parameter value.
– vary
[bool, optional] Whether the Parameter is varied during a fit (default is True).
– min
[float, optional] Lower bound for value (default is -numpy.inf, no lower bound).
– max
[float, optional] Upper bound for value (default is numpy.inf, no upper bound).
– expr
[str, optional] Mathematical expression used to constrain the value during the fit.
Example
func
The model function used to calculate the model.
independent_vars
List of strings for names of the independent variables.
nan_policy
Describes what to do for NaNs that indicate missing values in the data. The choices are:
• 'raise': Raise a ValueError (default)
• 'propagate': Do not check for NaNs or missing values. The fit will try to ignore them.
• 'omit': Remove NaNs or missing observations in data. If pandas is installed, pandas.isnull() is used,
otherwise numpy.isnan() is used.
name
Name of the model, used only in the string representation of the model. By default this will be taken from the
model function.
opts
Extra keyword arguments to pass to model function. Normally this will be determined internally and should not
be changed.
param_hints
Dictionary of parameter hints. See Using parameter hints.
param_names
List of strings of parameter names.
prefix
Prefix used for name-mangling of parameter names. The default is ''. If a particular Model has arguments
amplitude, center, and sigma, these would become the parameter names. Using a prefix of 'g1_' would
convert these parameter names to g1_amplitude, g1_center, and g1_sigma. This can be essential to avoid
name collision in composite models.
The Model created from the supplied function func will create a Parameters object, and names are inferred from the
function` arguments, and a residual function is automatically constructed.
By default, the independent variable is taken as the first argument to the function. You can, of course, explicitly set this,
and will need to do so if the independent variable is not first in the list, or if there is actually more than one independent
variable.
If not specified, Parameters are constructed from all positional arguments and all keyword arguments that have a default
value that is numerical, except the independent variable, of course. Importantly, the Parameters can be modified after
creation. In fact, you will have to do this because none of the parameters have valid initial values. In addition, one can
place bounds and constraints on Parameters, or fix their values.
As we saw for the Gaussian example above, creating a Model from a function is fairly easy. Let’s try another one:
import numpy as np
from lmfit import Model
decay_model = Model(decay)
print(f'independent variables: {decay_model.independent_vars}')
params = decay_model.make_params()
print('\nParameters:')
for pname, par in params.items():
print(pname, par)
Parameters:
(continues on next page)
Here, t is assumed to be the independent variable because it is the first argument to the function. The other function
arguments are used to create parameters for the model.
If you want tau to be the independent variable in the above example, you can say so:
params = decay_model.make_params()
print('\nParameters:')
for pname, par in params.items():
print(pname, par)
Parameters:
t <Parameter 't', value=-inf, bounds=[-inf:inf]>
N <Parameter 'N', value=-inf, bounds=[-inf:inf]>
You can also supply multiple values for multi-dimensional functions with multiple independent variables. In fact, the
meaning of independent variable here is simple, and based on how it treats arguments of the function you are modeling:
independent variable
A function argument that is not a parameter or otherwise part of the model, and that will be required to be
explicitly provided as a keyword argument for each fit with Model.fit() or evaluation with Model.eval().
Note that independent variables are not required to be arrays, or even floating point numbers.
If the model function had keyword parameters, these would be turned into Parameters if the supplied default value was
a valid number (but not None, True, or False).
mod = Model(decay2)
params = mod.make_params()
print('Parameters:')
for pname, par in params.items():
print(pname, par)
Parameters:
tau <Parameter 'tau', value=-inf, bounds=[-inf:inf]>
N <Parameter 'N', value=10, bounds=[-inf:inf]>
Here, even though N is a keyword argument to the function, it is turned into a parameter, with the default numerical
value as its initial value. By default, it is permitted to be varied in the fit – the 10 is taken as an initial value, not a fixed
value. On the other hand, the check_positive keyword argument, was not converted to a parameter because it has a
boolean default value. In some sense, check_positive becomes like an independent variable to the model. However,
because it has a default value it is not required to be given for each model evaluation or fit, as independent variables
are.
As we will see in the next chapter when combining models, it is sometimes necessary to decorate the parameter names in
the model, but still have them be correctly used in the underlying model function. This would be necessary, for example,
if two parameters in a composite model (see Composite Models : adding (or multiplying) Models or examples in the
next chapter) would have the same name. To avoid this, we can add a prefix to the Model which will automatically
do this mapping for us.
Parameters:
f1_amplitude <Parameter 'f1_amplitude', value=1, bounds=[-inf:inf]>
f1_center <Parameter 'f1_center', value=0, bounds=[-inf:inf]>
f1_sigma <Parameter 'f1_sigma', value=1, bounds=[-inf:inf]>
You would refer to these parameters as f1_amplitude and so forth, and the model will know to map these to the
amplitude argument of myfunc.
As mentioned above, creating a model does not automatically create the corresponding Parameters. These can be
created with either the create_params() function, or the Model.make_params() method of the corresponding
instance of Model.
When creating Parameters, each parameter is created with invalid initial value of -Inf if it is not set explicitly. That is
to say, parameter values must be initialized in order for the model to evaluate a finite result or used in a fit. There are
a few different ways to do this:
1. You can supply initial values in the definition of the model function.
2. You can initialize the parameters when creating parameters with Model.make_params().
3. You can create a Parameters object with Parameters or create_params().
4. You can supply initial values for the parameters when calling Model.eval() or Model.fit() methods.
Generally, using the Model.make_params() method is recommended. The methods described above can be mixed,
allowing you to overwrite initial values at any point in the process of defining and using the model.
To supply initial values for parameters in the definition of the model function, you can simply supply a default value:
instead of using:
This has the advantage of working at the function level – all parameters with keywords can be treated as options. It
also means that some default initial value will always be available for the parameter.
When creating parameters with Model.make_params() you can specify initial values. To do this, use keyword ar-
guments for the parameter names. You can either set initial values as numbers (floats or ints) or as dictionaries with
keywords of (value, vary, min, max, expr, brute_step, and is_init_value) to specify these parameter attributes.
mod = Model(myfunc)
You can also create your own Parameters directly using create_params(). This is independent of using the Model
class, but is essentially equivalent to Model.make_params() except with less checking of errors for model prefixes
and so on.
mod = Model(myfunc)
Because less error checking is done, Model.make_params() should probably be preferred when using Models.
Finally, you can explicitly supply initial values when using a model. That is, as with Model.make_params(), you can
include values as keyword arguments to either the Model.eval() or Model.fit() methods:
These approaches to initialization provide many opportunities for setting initial values for parameters. The methods
can be combined, so that you can set parameter hints but then change the initial value explicitly with Model.fit().
After a model has been created, but prior to creating parameters with Model.make_params(), you can define param-
eter hints for that model. This allows you to set other parameter attributes for bounds, whether it is varied in the fit, or
set a default constraint expression for a parameter. You can also set the initial value, but that is not really the intention
of the method, which is to really to let you say that about the idealized Model, for example that some values may not
make sense for some parameters, or that some parameters might be a small change from another parameter and so be
fixed or constrained by default.
To set a parameter hint, you can use Model.set_param_hint(), as with:
mod = Model(myfunc)
mod.set_param_hint('bounded_parameter', min=0, max=1.0)
pars = mod.make_params()
Parameter hints are discussed in more detail in section Using parameter hints.
Parameter hints are stored in a model’s param_hints attribute, which is simply a nested dictionary:
print('Parameter hints:')
for pname, par in mod.param_hints.items():
print(pname, par)
Parameter hints:
bounded_parameter {'min': 0, 'max': 1.0}
You can change this dictionary directly or use the Model.set_param_hint() method. Either way, these parameter
hints are used by Model.make_params() when making parameters.
Parameter hints also allow you to create new parameters. This can be useful to make derived parameters with constraint
expressions. For example to get the full-width at half maximum of a Gaussian model, one could use a parameter hint
of:
mod = Model(gaussian)
mod.set_param_hint('wid', min=0)
mod.set_param_hint('fwhm', expr='2.3548*wid')
params = mod.make_params(amp={'value': 10, 'min':0.1, 'max':2000},
cen=5.5, wid=1.25)
params.pretty_print()
With that definition, the value (and uncertainty) of the fwhm parameter will be reported in the output of any fit done
with that model.
7.2.9 Data Types for data and independent data with Model
The model as defined by your model function will use the independent variable(s) you specify to best match the data
you provide. The model is meant to be an abstract representation for data, but when you do a fit with Model.fit(),
you really need to pass in values for the data to be modeled and the independent data used to calculate that data.
The mathematical solvers used by lmfit all work exclusively with 1-dimensional numpy arrays of datatype (dtype)
float64. The value of the calculation (model-data)*weights using the calculation of your model function, and
the data and weights you pass in will be coerced to an 1-dimensional ndarray with dtype float64 when it is passed to
the solver.
If the data you pass to Model.fit() is not an ndarray of dtype float64 but is instead a tuples of numbers, a list of
numbers, or a pandas.Series, it will be coerced into an ndarray. If your data is a list, tuple, or Series of complex
numbers, it will be coerced to an ndarray with dtype complex128.
If your data is a numpy array of dtype float32, it will not be coerced to float64, as we assume this was an intentional
choice. That may make all of the calculations done in your model function be in single-precision which may make fits
less sensitive, but the values will be converted to float64 before being sent to the solver, so the fit should work.
The independent data for models using Model are meant to be truly independent, and not not required to be strictly
numerical or objects that are easily converted to arrays of numbers. That is, independent data for a model could be a
dictionary, an instance of a user-defined class, or other type of structured data. You can use independent data any way
you want in your model function.
But, as with almost all the examples given here, independent data is often also a 1-dimensonal array of values, say
x, and a simple view of the fit would be to plot the data as y as a function of x. Again, this is not required, but it is
very common. Because of this very common usage, if your independent data is a tuple or list of numbers or pandas.
Series, it will be coerced to be an ndarray of dtype float64. But as with the primary data, if your independent data
is an ndarray of some different dtype (float32, uint16, etc), it will not be coerced to float64, as we assume this
was intentional.
Note: Data and independent data that are tuples or lists of numbers, or panda.Series will be coerced to an ndarray
of dtype float64 before passing to the model function. Data with other dtypes (or independent data of other object
types such as dicts) will not be coerced to float64.
# <examples/doc_model_savemodel.py>
import numpy as np
sinemodel = Model(mysine)
pars = sinemodel.make_params(amp=1, freq=0.25, shift=0)
save_model(sinemodel, 'sinemodel.sav')
# <end examples/doc_model_savemodel.py>
# <examples/doc_model_loadmodel.py>
import os
import sys
if not os.path.exists('sinemodel.sav'):
os.system(f"{sys.executable} doc_model_savemodel.py")
data = np.loadtxt('sinedata.dat')
x = data[:, 0]
y = data[:, 1]
plt.plot(x, y, 'o')
plt.plot(x, result.best_fit, '-')
plt.show()
# <end examples/doc_model_loadmodel.py>
A ModelResult (which had been called ModelFit prior to version 0.9) is the object returned by Model.fit(). It
is a subclass of Minimizer, and so contains many of the fit results. Of course, it knows the Model and the set of
Parameters used in the fit, and it has methods to evaluate the model, to fit the data (or re-fit the data with changes to
the parameters, or fit with different or modified data) and to print out a report for that fit.
While a Model encapsulates your model function, it is fairly abstract and does not contain the parameters or data used
in a particular fit. A ModelResult does contain parameters and data as well as methods to alter and re-do fits. Thus the
Model is the idealized model while the ModelResult is the messier, more complex (but perhaps more useful) object
that represents a fit with a set of parameters to data with a model.
A ModelResult has several attributes holding values for fit results, and several methods for working with fits. These
include statistics inherited from Minimizer useful for comparing different models, including chisqr, redchi, aic,
and bic.
class ModelResult(model, params, data=None, weights=None, method='leastsq', fcn_args=None,
fcn_kws=None, iter_cb=None, scale_covar=True, nan_policy='raise', calc_covar=True,
max_nfev=None, **fit_kws)
Result from the Model fit.
This has many attributes and methods for viewing and working with the results of a fit using Model. It inherits
from Minimizer, so that it can be used to modify and re-run the fit for the Model.
Parameters
• model (Model) – Model to use.
• params (Parameters) – Parameters with initial values for model.
• data (array_like, optional) – Data to be modeled.
• weights (array_like, optional) – Weights to multiply (data-model) for fit residual.
• method (str, optional) – Name of minimization method to use (default is ‘leastsq’).
• fcn_args (sequence, optional) – Positional arguments to send to model function.
• fcn_dict (dict, optional) – Keyword arguments to send to model function.
• iter_cb (callable, optional) – Function to call on each iteration of fit.
• scale_covar (bool, optional) – Whether to scale covariance matrix for uncertainty
evaluation.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – What to do when encoun-
tering NaNs when fitting Model.
• calc_covar (bool, optional) – Whether to calculate the covariance matrix (default is
True) for solvers other than ‘leastsq’ and ‘least_squares’. Requires the numdifftools pack-
age to be installed.
• max_nfev (int or None, optional) – Maximum number of function evaluations (de-
fault is None). The default value depends on the fitting method.
• **fit_kws (optional) – Keyword arguments to send to minimization routine.
ModelResult.eval(params=None, **kwargs)
Evaluate model function.
Parameters
• params (Parameters, optional) – Parameters to use.
• **kwargs (optional) – Options to send to Model.eval().
Returns
Array or value for the evaluated model.
Return type
numpy.ndarray, float, int, or complex
ModelResult.eval_components(params=None, **kwargs)
Evaluate each component of a composite model function.
Parameters
• params (Parameters, optional) – Parameters, defaults to ModelResult.params.
• **kwargs (optional) – Keyword arguments to pass to model function.
Returns
Keys are prefixes of component models, and values are the estimated model value for each com-
ponent of the model.
Return type
dict
ModelResult.fit(data=None, params=None, weights=None, method=None, nan_policy=None, **kwargs)
Re-perform fit for a Model, given data and params.
Parameters
• data (array_like, optional) – Data to be modeled.
• params (Parameters, optional) – Parameters with initial values for model.
• weights (array_like, optional) – Weights to multiply (data-model) for fit residual.
• method (str, optional) – Name of minimization method to use (default is ‘leastsq’).
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – What to do when encoun-
tering NaNs when fitting Model.
• **kwargs (optional) – Keyword arguments to send to minimization routine.
ModelResult.fit_report(modelpars=None, show_correl=True, min_correl=0.1, sort_pars=False,
correl_mode='list')
Return a printable fit report.
The report contains fit statistics and best-fit values with uncertainties and correlations.
Parameters
• modelpars (Parameters, optional) – Known Model Parameters.
• show_correl (bool, optional) – Whether to show list of sorted correlations (default is
True).
Notes
model, method, ndata, nvarys, nfree, chisqr, redchi, aic, bic, rsquared, nfev, max_nfev,
aborted, errorbars, success, message, lmdif_message, ier, nan_policy, scale_covar,
calc_covar, ci_out, col_deriv, flatchain, call_kws, var_names, user_options, kws,
init_values, best_values, and params.
where ‘params’ is a list of parameter “states”: tuples with entries of (name, value, vary, expr, min,
max, brute_step, stderr, correl, init_value, user_data).
3. The result will include only plain Python objects, and so should be easily serializable with JSON or similar
tools.
ModelResult.conf_interval(**kwargs)
Calculate the confidence intervals for the variable parameters.
Confidence intervals are calculated using the confidence.conf_interval() function and keyword arguments
(**kwargs) are passed to that function. The result is stored in the ci_out attribute so that it can be accessed
without recalculating them.
ModelResult.ci_report(with_offset=True, ndigits=5, **kwargs)
Return a formatted text report of the confidence intervals.
Parameters
• with_offset (bool, optional) – Whether to subtract best value from all other values
(default is True).
• ndigits (int, optional) – Number of significant digits to show (default is 5).
• **kwargs (optional) – Keyword arguments that are passed to the conf_interval function.
Returns
Text of formatted report on confidence intervals.
Return type
str
ModelResult.eval_uncertainty(params=None, sigma=1, **kwargs)
Evaluate the uncertainty of the model function.
This can be used to give confidence bands for the model from the uncertainties in the best-fit parameters.
Parameters
• params (Parameters, optional) – Parameters, defaults to ModelResult.params.
• sigma (float, optional) – Confidence level, i.e. how many sigma (default is 1).
• **kwargs (optional) – Values of options, independent variables, etcetera.
Returns
Uncertainty at each value of the model.
Return type
numpy.ndarray
Notes
Examples
ModelResult.plot_fit
Plot the fit results using matplotlib.
ModelResult.plot_residuals
Plot the fit residuals using matplotlib.
Notes
ModelResult.plot_residuals
Plot the fit residuals using matplotlib.
ModelResult.plot
Plot the fit results and residuals using matplotlib.
Notes
For details about plot format strings and keyword arguments see documentation of matplotlib.axes.Axes.plot.
If yerr is specified or if the fit model included weights, then matplotlib.axes.Axes.errorbar is used to plot the
data. If yerr is not specified and the fit includes weights, yerr set to 1/self.weights.
If model returns complex data, yerr is treated the same way that weights are in this case.
If ax is None then matplotlib.pyplot.gca(**ax_kws) is called.
ModelResult.plot_residuals(ax=None, datafmt='o', yerr=None, data_kws=None, fit_kws=None,
ax_kws=None, parse_complex='abs', title=None)
Plot the fit residuals using matplotlib, if available.
If yerr is supplied or if the model included weights, errorbars will also be plotted.
Parameters
• ax (matplotlib.axes.Axes, optional) – The axes to plot on. The default in None,
which means use the current pyplot axis or create one if there is none.
• datafmt (str, optional) – Matplotlib format string for data points.
• yerr (numpy.ndarray, optional) – Array of uncertainties for data array.
• data_kws (dict, optional) – Keyword arguments passed to the plot function for data
points.
• fit_kws (dict, optional) – Keyword arguments passed to the plot function for fitted
curve.
• ax_kws (dict, optional) – Keyword arguments for a new axis, if a new one is created.
• parse_complex ({'abs', 'real', 'imag', 'angle'}, optional) – How to reduce com-
plex data for plotting. Options are one of: ‘abs’ (default), ‘real’, ‘imag’, or ‘angle’, which
correspond to the NumPy functions with the same name.
• title (str, optional) – Matplotlib format string for figure title.
Return type
matplotlib.axes.Axes
See also:
ModelResult.plot_fit
Plot the fit results using matplotlib.
ModelResult.plot
Plot the fit results and residuals using matplotlib.
Notes
For details about plot format strings and keyword arguments see documentation of matplotlib.axes.Axes.plot.
If yerr is specified or if the fit model included weights, then matplotlib.axes.Axes.errorbar is used to plot the
data. If yerr is not specified and the fit includes weights, yerr set to 1/self.weights.
If model returns complex data, yerr is treated the same way that weights are in this case.
If ax is None then matplotlib.pyplot.gca(**ax_kws) is called.
aic
Floating point best-fit Akaike Information Criterion statistic (see MinimizerResult – the optimization result).
best_fit
numpy.ndarray result of model function, evaluated at provided independent variables and with best-fit parameters.
best_values
Dictionary with parameter names as keys, and best-fit values as values.
bic
Floating point best-fit Bayesian Information Criterion statistic (see MinimizerResult – the optimization result).
chisqr
Floating point best-fit chi-square statistic (see MinimizerResult – the optimization result).
ci_out
Confidence interval data (see Calculation of confidence intervals) or None if the confidence intervals have not
been calculated.
covar
numpy.ndarray (square) covariance matrix returned from fit.
data
numpy.ndarray of data to compare to model.
dely
numpy.ndarray of estimated uncertainties in the y values of the model from ModelResult.
eval_uncertainty() (see Calculating uncertainties in the model function).
dely_comps
a dictionary of estimated uncertainties in the y values of the model components, from ModelResult.
eval_uncertainty() (see Calculating uncertainties in the model function).
errorbars
Boolean for whether error bars were estimated by fit.
ier
Integer returned code from scipy.optimize.leastsq.
init_fit
numpy.ndarray result of model function, evaluated at provided independent variables and with initial parameters.
init_params
Initial parameters.
init_values
Dictionary with parameter names as keys, and initial values as values.
iter_cb
Optional callable function, to be called at each fit iteration. This must take take arguments of (params, iter,
resid, *args, **kws), where params will have the current parameter values, iter the iteration, resid the
current residual array, and *args and **kws as passed to the objective function. See Using a Iteration Callback
Function.
jacfcn
Optional callable function, to be called to calculate Jacobian array.
lmdif_message
String message returned from scipy.optimize.leastsq.
message
String message returned from minimize().
method
String naming fitting method for minimize().
call_kws
Dict of keyword arguments actually send to underlying solver with minimize().
model
Instance of Model used for model.
ndata
Integer number of data points.
nfev
Integer number of function evaluations used for fit.
nfree
Integer number of free parameters in fit.
nvarys
Integer number of independent, freely varying variables in fit.
params
Parameters used in fit; will contain the best-fit values.
redchi
Floating point reduced chi-square statistic (see MinimizerResult – the optimization result).
residual
numpy.ndarray for residual.
rsquared
Floating point 𝑅2 statisic, defined for data 𝑦 and best-fit model 𝑓 as
(𝑦𝑖 − 𝑓𝑖 )2
∑︀
2
𝑅 = 1 − ∑︀𝑖
¯)2
𝑖 (𝑦𝑖 − 𝑦
scale_covar
Boolean flag for whether to automatically scale covariance matrix.
success
Boolean value of whether fit succeeded.
weights
numpy.ndarray (or None) of weighting values to be used in fit. If not None, it will be used as a multiplicative
factor of the residual array, so that weights*(data - fit) is minimized in the least-squares sense.
We return to the first example above and ask not only for the uncertainties in the fitted parameters but for the range of val-
ues that those uncertainties mean for the model function itself. We can use the ModelResult.eval_uncertainty()
method of the model result object to evaluate the uncertainty in the model with a specified level for 𝜎.
That is, adding:
dely = result.eval_uncertainty(sigma=3)
plt.fill_between(x, result.best_fit-dely, result.best_fit+dely, color="#ABABAB",
label='3-$\sigma$ uncertainty band')
to the example fit to the Gaussian at the beginning of this chapter will give 3-𝜎 bands for the best-fit Gaussian, and
produce the figure below.
component. The uncertainty of the full model will be held in result.dely, and the uncertainties for each component
will be held in the dictionary result.dely_comps, with keys that are the component prefixes.
An example script shows how the uncertainties in components of a composite model can be calculated and used:
# <examples/doc_model_uncertainty2.py>
import matplotlib.pyplot as plt
import numpy as np
dat = np.loadtxt('NIST_Gauss2.dat')
x = dat[:, 1]
y = dat[:, 0]
model = (GaussianModel(prefix='g1_') +
GaussianModel(prefix='g2_') +
ExponentialModel(prefix='bkg_'))
comps = result.eval_components(x=x)
dely = result.eval_uncertainty(sigma=3)
plt.show()
# <end examples/doc_model_uncertainty2.py>
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='bkg_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 55
# data points = 250
# variables = 8
chi-square = 1247.52821
reduced chi-square = 5.15507524
Akaike info crit = 417.864631
Bayesian info crit = 446.036318
R-squared = 0.99648654
[[Variables]]
g1_amplitude: 4257.77399 +/- 42.3838008 (1.00%) (init = 3000)
g1_center: 107.030957 +/- 0.15006868 (0.14%) (init = 100)
g1_sigma: 16.6725789 +/- 0.16048222 (0.96%) (init = 10)
g2_amplitude: 2493.41715 +/- 36.1696228 (1.45%) (init = 3000)
g2_center: 153.270104 +/- 0.19466723 (0.13%) (init = 150)
g2_sigma: 13.8069453 +/- 0.18680099 (1.35%) (init = 10)
(continues on next page)
# <examples/doc_model_savemodelresult.py>
import numpy as np
data = np.loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
gmodel = GaussianModel()
result = gmodel.fit(y, x=x, amplitude=5, center=5, sigma=1)
save_modelresult(result, 'gauss_modelresult.sav')
print(result.fit_report())
# <end examples/doc_model_savemodelresult.py>
# <examples/doc_model_loadmodelresult.py>
import os
import sys
if not os.path.exists('gauss_modelresult.sav'):
os.system(f"{sys.executable} doc_model_savemodelresult.py")
data = np.loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
result = load_modelresult('gauss_modelresult.sav')
print(result.fit_report())
plt.plot(x, y, 'o')
plt.plot(x, result.best_fit, '-')
plt.show()
# <end examples/doc_model_loadmodelresult.py>
One of the more interesting features of the Model class is that Models can be added together or combined with basic
algebraic operations (add, subtract, multiply, and divide) to give a composite model. The composite model will have
parameters from each of the component models, with all parameters being available to influence the whole model. This
ability to combine models will become even more useful in the next chapter, when pre-built subclasses of Model are
discussed. For now, we’ll consider a simple example, and build a model of a Gaussian plus a line, as to model a peak
with a background. For such a simple problem, we could just build a model that included both components:
mod = Model(gaussian_plus_line)
But we already had a function for a gaussian function, and maybe we’ll discover that a linear background isn’t sufficient
which would mean the model function would have to be changed.
Instead, lmfit allows models to be combined into a CompositeModel. As an alternative to including a linear back-
ground in our model function, we could define a linear function:
This model has parameters for both component models, and can be used as:
# <examples/doc_model_two_components.py>
import matplotlib.pyplot as plt
from numpy import exp, loadtxt, pi, sqrt
data = loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1] + 0.25*x - 1.0
plt.plot(x, y, 'o')
plt.plot(x, result.init_fit, '--', label='initial fit')
plt.plot(x, result.best_fit, '-', label='best fit')
plt.legend()
plt.show()
# <end examples/doc_model_two_components.py>
[[Model]]
(Model(gaussian) + Model(line))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 55
# data points = 101
(continues on next page)
On the left, data is shown in blue dots, the total fit is shown in solid green line, and the initial fit is shown as a orange
dashed line. The figure on the right shows again the data in blue dots, the Gaussian component as a orange dashed line
and the linear component as a green dashed line. It is created using the following code:
comps = result.eval_components()
plt.plot(x, y, 'o')
plt.plot(x, comps['gaussian'], '--', label='Gaussian component')
plt.plot(x, comps['line'], '--', label='Line component')
The components were generated after the fit using the ModelResult.eval_components() method of the result,
which returns a dictionary of the components, using keys of the model name (or prefix if that is set). This will
use the parameter values in result.params and the independent variables (x) used during the fit. Note that while the
ModelResult held in result does store the best parameters and the best estimate of the model in result.best_fit,
In this example, the argument names for the model functions do not overlap. If they had, the prefix argument to
Model would have allowed us to identify which parameter went with which component model. As we will see in the
next chapter, using composite models with the built-in models provides a simple way to build up complex models.
class CompositeModel(left, right, op[, **kws ])
Combine two models (left and right) with binary operator (op).
Normally, one does not have to explicitly create a CompositeModel, but can use normal Python operators +, -,
*, and / to combine components as in:
Parameters
• left (Model) – Left-hand model.
• right (Model) – Right-hand model.
• op (callable binary operator) – Operator to combine left and right models.
• **kws (optional) – Additional keywords are passed to Model when creating this new
model.
Notes
will create a CompositeModel. Here, left will be Model(fcn1), op will be operator.add(), and right will
be another CompositeModel that has a left attribute of Model(fcn2), an op of operator.mul(), and a right of
Model(fcn3).
To use a binary operator other than +, -, *, or / you can explicitly create a CompositeModel with the appropriate
binary operator. For example, to convolve two models, you could define a simple convolution function, perhaps as:
import numpy as np
which extends the data in both directions so that the convolving kernel function gives a valid result over the data range.
Because this function takes two array arguments and returns an array, it can be used as the binary operator. A full script
using this technique is here:
# <examples/doc_model_composite.py>
import matplotlib.pyplot as plt
import numpy as np
# create parameters for model. Note that 'mid' and 'center' will be highly
# correlated. Since 'mid' is used as an integer index, it will be very
# hard to fit, so we fix its value
pars = mod.make_params(amplitude=dict(value=1, min=0),
center=3.5,
sigma=dict(value=1.5, min=0),
mid=dict(value=4, vary=False))
print(result.fit_report())
# generate components
comps = result.eval_components(x=x)
# plot results
fig, axes = plt.subplots(1, 2, figsize=(12.8, 4.8))
axes[0].plot(x, y, 'bo')
axes[0].plot(x, result.init_fit, 'k--', label='initial fit')
axes[0].plot(x, result.best_fit, 'r-', label='best fit')
axes[0].legend()
axes[1].plot(x, y, 'bo')
axes[1].plot(x, 10*comps['jump'], 'k--', label='Jump component')
axes[1].plot(x, 10*comps['gaussian'], 'r-', label='Gaussian component')
axes[1].legend()
plt.show()
# <end examples/doc_model_composite.py>
[[Model]]
(Model(jump) <function convolve at 0x130d64dc0> Model(gaussian))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 33
# data points = 201
# variables = 3
chi-square = 24.7562335
reduced chi-square = 0.12503148
Akaike info crit = -414.939746
Bayesian info crit = -405.029832
R-squared = 0.99632577
[[Variables]]
mid: 4 (fixed)
amplitude: 0.62508458 +/- 0.00189732 (0.30%) (init = 1)
center: 5.50853669 +/- 0.00973231 (0.18%) (init = 3.5)
sigma: 0.59576097 +/- 0.01348579 (2.26%) (init = 1.5)
[[Correlations]] (unreported correlations are < 0.100)
C(amplitude, center) = +0.3292
C(amplitude, sigma) = +0.2680
Using composite models with built-in or custom operators allows you to build complex models from testable sub-
components.
EIGHT
Lmfit provides several built-in fitting models in the models module. These pre-defined models each subclass from the
Model class of the previous chapter and wrap relatively well-known functional forms, such as Gaussian, Lorentzian,
and Exponential that are used in a wide range of scientific domains. In fact, all the models are based on simple, plain
Python functions defined in the lineshapes module. In addition to wrapping a function into a Model, these models
also provide a guess() method that is intended to give a reasonable set of starting values from a data array that closely
approximates the data to be fit.
As shown in the previous chapter, a key feature of the Model class is that models can easily be combined to give a com-
posite CompositeModel. Thus, while some of the models listed here may seem pretty trivial (notably, ConstantModel
and LinearModel), the main point of having these is to be able to use them in composite models. For example, a
Lorentzian plus a linear background might be represented as:
peak = LorentzianModel()
background = LinearModel()
model = peak + background
Almost all the models listed below are one-dimensional, with an independent variable named x. Many of these models
represent a function with a distinct peak, and so share common features. To maintain uniformity, common parameter
names are used whenever possible. Thus, most models have a parameter called amplitude that represents the overall
intensity (or area of) a peak or function and a sigma parameter that gives a characteristic width.
After a list of built-in models, a few examples of their use are given.
There are many peak-like models available. These include GaussianModel, LorentzianModel, VoigtModel,
PseudoVoigtModel, and some less commonly used variations. Most of these models are unit-normalized and share
the same parameter names so that you can easily switch between models and interpret the results. The amplitude
parameter is the multiplicative factor for the unit-normalized peak lineshape, and so will represent the strength of that
peak or the area under that curve. The center parameter will be the centroid x value. The sigma parameter is the
characteristic width of the peak, with many functions using (𝑥 − 𝜇)/𝜎 where 𝜇 is the centroid value. Most of these
peak functions will have two additional parameters derived from and constrained by the other parameters. The first of
these is fwhm which will hold the estimated “Full Width at Half Max” for the peak, which is often easier to compare
between different models than sigma. The second of these is height which will contain the maximum value of the
peak, typically the value at 𝑥 = 𝜇. Finally, each of these models has a guess() method that uses data to make a fairly
crude but usually sufficient guess for the value of amplitude, center, and sigma, and sets a lower bound of 0 on the
value of sigma.
99
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
8.1.1 GaussianModel
𝐴 2 2
𝑓 (𝑥; 𝐴, 𝜇, 𝜎) = √ 𝑒[−(𝑥−𝜇) /2𝜎 ]
𝜎 2𝜋
where√the parameter amplitude corresponds to 𝐴, center to 𝜇, and sigma to 𝜎. The full width at half maximum
is 2𝜎 2 ln 2, approximately 2.3548𝜎.
For more information, see: https://en.wikipedia.org/wiki/Normal_distribution
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.2 LorentzianModel
𝐴 [︀ 𝜎 ]︀
𝑓 (𝑥; 𝐴, 𝜇, 𝜎) = 2 2
𝜋 (𝑥 − 𝜇) + 𝜎
where the parameter amplitude corresponds to 𝐴, center to 𝜇, and sigma to 𝜎. The full width at half maximum
is 2𝜎.
For more information, see: https://en.wikipedia.org/wiki/Cauchy_distribution
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.3 SplitLorentzianModel
2𝐴 [︀ 𝜎2 𝜎𝑟2 ]︀
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, 𝜎𝑟 ) = 2 2
* 𝐻(𝜇 − 𝑥) + 2 2
* 𝐻(𝑥 − 𝜇)
𝜋(𝜎 + 𝜎𝑟 ) (𝑥 − 𝜇) + 𝜎 (𝑥 − 𝜇) + 𝜎𝑟
where the parameter amplitude corresponds to 𝐴, center to 𝜇, sigma to 𝜎, sigma_l to 𝜎𝑙 , and 𝐻(𝑥) is a Heaviside
step function:
The full width at half maximum is 𝜎𝑙 + 𝜎𝑟 . Just as with the Lorentzian model, integral of this function from -.inf
to +.inf equals to amplitude.
For more information, see: https://en.wikipedia.org/wiki/Cauchy_distribution
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.4 VoigtModel
𝐴Re[𝑤(𝑧)]
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, 𝛾) = √
𝜎 2𝜋
where
𝑥 − 𝜇 + 𝑖𝛾
𝑧 = √
𝜎 2
2
𝑤(𝑧) = 𝑒−𝑧 erfc(−𝑖𝑧)
and erfc() is the complementary error function. As above, amplitude corresponds to 𝐴, center to 𝜇, and sigma
to 𝜎. The parameter gamma corresponds to 𝛾. If gamma is kept at the default value (constrained to sigma), the
full width at half maximum is approximately 3.6013𝜎.
For more information, see: https://en.wikipedia.org/wiki/Voigt_profile
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.5 PseudoVoigtModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.6 MoffatModel
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.7 Pearson4Model
⃒ Γ(𝑚+𝑖 𝜈 ) ⃒2
⃒ ⃒
⃒ 2 ⃒ ]︂−𝑚
⃒ Γ(𝑚) ⃒ [︂ (𝑥 − 𝜇)2
(︂ (︂ )︂)︂
𝑥−𝜇
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, 𝑚, 𝜈) = 𝐴 1 + exp −𝜈 arctan
𝜎𝛽(𝑚 − 12 , 12 ) 𝜎2 𝜎
where 𝛽 is the beta function (see scipy.special.beta). The guess() function always gives a starting value of 1.5
for expon, and 0 for skew.
For more information, see: https://en.wikipedia.org/wiki/Pearson_distribution#The_Pearson_type_IV_
distribution
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.8 Pearson7Model
𝐴 [︀ (𝑥 − 𝜇)2 ]︀−𝑚
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, 𝑚) = 1 +
𝜎𝛽(𝑚 − 21 , 12 ) 𝜎2
where 𝛽 is the beta function (see scipy.special.beta). The guess() function always gives a starting value for
exponent of 1.5. In addition, parameters fwhm and height are included as constraints to report full width at half
maximum and maximum peak height, respectively.
For more information, see: https://en.wikipedia.org/wiki/Pearson_distribution#The_Pearson_type_VII_
distribution
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.9 StudentsTModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.10 BreitWignerModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.11 LognormalModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.12 DampedOscillatorModel
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.13 DampedHarmonicOscillatorModel
𝐴𝜎 [︁ 1 1 ]︁
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, 𝛾) = −
𝜋[1 − exp(−𝑥/𝛾)] (𝑥 − 𝜇)2 + 𝜎 2 (𝑥 + 𝜇)2 + 𝜎 2
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.14 ExponentialGaussianModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.15 SkewedGaussianModel
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.16 SkewedVoigtModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.17 ThermalDistributionModel
1
𝑓 (𝑥; 𝐴, 𝑥0 , 𝑘𝑡, form = ′ maxwell′ ) =
𝐴 exp( 𝑥−𝑥
𝑘𝑡 )
0
1
𝑓 (𝑥; 𝐴, 𝑥0 , 𝑘𝑡, form = ′ fermi′ ) = 𝑥−𝑥0 ]
𝐴 exp( 𝑘𝑡 ) + 1
Notes
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.1.18 DoniachModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
These models correspond to polynomials of some degree. Of course, lmfit is a very inefficient way to do linear re-
gression (see numpy.polyfit or scipy.stats.linregress), but these models may be useful as one of many components of a
composite model. The SplineModel below corresponds to a cubic spline.
8.2.1 ConstantModel
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.2.2 LinearModel
𝑓 (𝑥; 𝑚, 𝑏) = 𝑚𝑥 + 𝑏
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.2.3 QuadraticModel
𝑓 (𝑥; 𝑎, 𝑏, 𝑐) = 𝑎𝑥2 + 𝑏𝑥 + 𝑐
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.2.4 PolynomialModel
with parameters c0, c1, . . . , c7. The supplied degree will specify how many of these are actual variable parame-
ters. This uses numpy.polyval for its calculation of the polynomial.
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.2.5 SplinelModel
Notes
1. There must be at least 4 knot points, and not more than 300.
2. nan_policy sets what to do when a NaN or missing value is seen in
the data. Should be one of:
8.3.1 SineModel
𝑓 (𝑥; 𝐴, 𝜑, 𝑓 ) = 𝐴 sin(𝑓 𝑥 + 𝜑)
where the parameter amplitude corresponds to 𝐴, frequency to 𝑓 , and shift to 𝜑. All are constrained to be non-
negative, and shift additionally to be smaller than 2𝜋.
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.4.1 StepModel
where 𝛼 = (𝑥 − 𝜇)/𝜎.
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.4.2 RectangleModel
The function starts with a value 0 and transitions to a value of 𝐴, taking the value 𝐴/2 at 𝜇1 , with 𝜎1 setting the
characteristic width. The function then transitions again to the value 𝐴/2 at 𝜇2 , with 𝜎2 setting the characteristic
width. The functional forms are defined as:
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, form = ′ linear′ ) = 𝐴{min [1, max (−1, 𝛼1 )] + min [1, max (−1, 𝛼2 )]}/2
′ ′
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, form = arctan ) = 𝐴[arctan (𝛼1 ) + arctan (𝛼2 )]/𝜋
′ ′
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, form = erf ) = 𝐴 [erf(𝛼1 ) + erf(𝛼2 )] /2
[︂ ]︂
1 1
𝑓 (𝑥; 𝐴, 𝜇, 𝜎, form = ′ logistic′ ) =𝐴 1− −
1 + 𝑒𝛼1 1 + 𝑒𝛼 2
where 𝛼1 = (𝑥 − 𝜇1 )/𝜎1 and 𝛼2 = −(𝑥 − 𝜇2 )/𝜎2 .
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.5.1 ExponentialModel
𝑓 (𝑥; 𝐴, 𝜏 ) = 𝐴𝑒−𝑥/𝜏
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.5.2 PowerLawModel
𝑓 (𝑥; 𝐴, 𝑘) = 𝐴𝑥𝑘
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
8.6.1 Gaussian2dModel
𝐴 2 2
𝑔(𝑥; 𝐴, 𝜇, 𝜎) = √ 𝑒[−(𝑥−𝜇) /2𝜎 ] .
𝜎 2𝜋
Parameters
• independent_vars (list of str, optional) – Arguments to the model function that are
independent variables default is [‘x’, ‘y’]).
• prefix (str, optional) – String to prepend to parameter names, needed to add two Mod-
els that have parameter names in common.
• nan_policy ({'raise', 'propagate', 'omit'}, optional) – How to handle NaN and
missing values in data. See Notes below.
• **kwargs (optional) – Keyword arguments to pass to Model.
Notes
1. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
As shown in the previous chapter (Modeling Data and Curve Fitting), it is fairly straightforward to build fitting models
from parametrized Python functions. The number of model classes listed so far in the present chapter should make it
clear that this process is not too difficult. Still, it is sometimes desirable to build models from a user-supplied function.
This may be especially true if model-building is built-in to some larger library or application for fitting in which the
user may not be able to easily build and use a new model from Python code.
The ExpressionModel allows a model to be built from a user-supplied expression. This uses the asteval module also
used for mathematical constraints as discussed in Using Mathematical Constraints.
8.7.1 ExpressionModel
Notes
1. each instance of ExpressionModel will create and use its own version of an asteval interpreter.
2. prefix is not supported for ExpressionModel.
3. nan_policy sets what to do when a NaN or missing value is seen in the data. Should be one of:
• ‘raise’ : raise a ValueError (default)
• ‘propagate’ : do nothing
• ‘omit’ : drop missing data
Since the point of this model is that an arbitrary expression will be supplied, the determination of what are the parameter
names for the model happens when the model is created. To do this, the expression is parsed, and all symbol names are
found. Names that are already known (there are over 500 function and value names in the asteval namespace, including
most Python built-ins, more than 200 functions inherited from NumPy, and more than 20 common lineshapes defined
in the lineshapes module) are not converted to parameters. Unrecognized names are expected to be names of either
parameters or independent variables. If independent_vars is the default value of None, and if the expression contains
a variable named x, that will be used as the independent variable. Otherwise, independent_vars must be given.
For example, if one creates an ExpressionModel as:
The name exp will be recognized as the exponent function, so the model will be interpreted to have parameters named
off, amp, x0 and phase. In addition, x will be assumed to be the sole independent variable. In general, there is no
obvious way to set default parameter values or parameter hints for bounds, so this will have to be handled explicitly.
To evaluate this model, you might do the following:
While many custom models can be built with a single line expression (especially since the names of the lineshapes
like gaussian, lorentzian and so on, as well as many NumPy functions, are available), more complex models will
inevitably require multiple line functions. You can include such Python code with the init_script argument. The
text of this script is evaluated when the model is initialized (and before the actual expression is parsed), so that you can
define functions to be used in your expression.
As a probably unphysical example, to make a model that is the derivative of a Gaussian function times the logarithm
of a Lorentzian function you may could to define this in a script:
script = """
def mycurve(x, amp, cen, sig):
loren = lorentzian(x, amplitude=amp, center=cen, sigma=sig)
gauss = gaussian(x, amplitude=amp, center=cen, sigma=sig)
return log(loren) * gradient(gauss) / gradient(x)
"""
As above, this will interpret the parameter names to be height, mid, and wid, and build a model that can be used to
fit data.
8.8 Example 1: Fit Peak data to Gaussian, Lorentzian, and Voigt pro-
files
Here, we will fit data to three similar lineshapes, in order to decide which might be the better model. We will start with
a Gaussian profile, as in the previous chapter, but use the built-in GaussianModel instead of writing one ourselves.
This is a slightly different version from the one in previous example in that the parameter names are different, and have
built-in default values. We will simply use:
data = loadtxt('test_peak.dat')
x = data[:, 0]
y = data[:, 1]
mod = GaussianModel()
print(out.fit_report(min_correl=0.25))
[[Model]]
Model(gaussian)
[[Fit Statistics]]
(continues on next page)
We see a few interesting differences from the results of the previous chapter. First, the parameter names are longer.
Second, there are fwhm and height parameters, to give the full-width-at-half-maximum and maximum peak height,
respectively. And third, the automated initial guesses are pretty good. A plot of the fit:
shows a decent match to the data – the fit worked with no explicit setting of initial parameter values. Looking more
closely, the fit is not perfect, especially in the tails of the peak, suggesting that a different peak shape, with longer
tails, should be used. Perhaps a Lorentzian would be better? To do this, we simply replace GaussianModel with
LorentzianModel to get a LorentzianModel:
8.8. Example 1: Fit Peak data to Gaussian, Lorentzian, and Voigt profiles 123
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
mod = LorentzianModel()
with the rest of the script as above. Perhaps predictably, the first thing we try gives results that are worse by comparing
the fit statistics:
[[Model]]
Model(lorentzian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 25
# data points = 401
# variables = 3
chi-square = 53.7535387
reduced chi-square = 0.13505914
Akaike info crit = -799.830322
Bayesian info crit = -787.848438
R-squared = 0.98289441
[[Variables]]
amplitude: 38.9726380 +/- 0.31386754 (0.81%) (init = 54.52798)
center: 9.24439393 +/- 0.00927645 (0.10%) (init = 9.25)
sigma: 1.15483177 +/- 0.01315708 (1.14%) (init = 1.35)
fwhm: 2.30966354 +/- 0.02631416 (1.14%) == '2.0000000*sigma'
height: 10.7421504 +/- 0.08634317 (0.80%) == '0.3183099*amplitude/max(1e-15,␣
˓→sigma)'
and also by visual inspection of the fit to the data (figure below).
The tails are now too big, and the value for 𝜒2 almost doubled. A Voigt model does a better job. Using VoigtModel,
this is as simple as using:
mod = VoigtModel()
[[Model]]
Model(voigt)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 25
# data points = 401
# variables = 3
chi-square = 14.5448627
reduced chi-square = 0.03654488
Akaike info crit = -1324.00615
Bayesian info crit = -1312.02427
R-squared = 0.99537150
[[Variables]]
amplitude: 35.7553799 +/- 0.13861559 (0.39%) (init = 65.43358)
center: 9.24411179 +/- 0.00505496 (0.05%) (init = 9.25)
sigma: 0.73015485 +/- 0.00368473 (0.50%) (init = 0.8775)
gamma: 0.73015485 +/- 0.00368473 (0.50%) == 'sigma'
fwhm: 2.62949983 +/- 0.01326979 (0.50%) == '1.0692*gamma+sqrt(0.
˓→8664*gamma**2+5.545083*sigma**2)'
8.8. Example 1: Fit Peak data to Gaussian, Lorentzian, and Voigt profiles 125
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
which has a much better value for 𝜒2 and the other goodness-of-fit measures, and an obviously better match to the data
as seen in the figure below (left).
Fit to peak with Voigt model (left) and Voigt model with gamma varying independently of sigma (right).
Can we do better? The Voigt function has a 𝛾 parameter (gamma) that can be distinct from sigma. The default behavior
used above constrains gamma to have exactly the same value as sigma. If we allow these to vary separately, does the fit
improve? To do this, we have to change the gamma parameter from a constrained expression and give it a starting value
using something like:
mod = VoigtModel()
pars = mod.guess(y, x=x)
pars['gamma'].set(value=0.7, vary=True, expr='')
which gives:
[[Model]]
Model(voigt)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 26
# data points = 401
# variables = 4
chi-square = 10.9301767
reduced chi-square = 0.02753193
Akaike info crit = -1436.57602
Bayesian info crit = -1420.60017
R-squared = 0.99652177
[[Variables]]
amplitude: 34.1914716 +/- 0.17946974 (0.52%) (init = 65.43358)
center: 9.24374846 +/- 0.00441904 (0.05%) (init = 9.25)
sigma: 0.89518951 +/- 0.01415479 (1.58%) (init = 0.8775)
(continues on next page)
Here, we repeat the point made at the end of the last chapter that instances of Model class can be added together to
make a composite model. By using the large number of built-in models available, it is therefore very simple to build
models that contain multiple peaks and various backgrounds. An example of a simple fit to a noisy step function plus
a constant:
# <examples/doc_builtinmodels_stepmodel.py>
import matplotlib.pyplot as plt
import numpy as np
8.9. Example 2: Fit data to a Composite Model with pre-defined models 127
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
print(out.fit_report())
plt.plot(x, y)
plt.plot(x, out.init_fit, '--', label='initial fit')
plt.plot(x, out.best_fit, '-', label='best fit')
plt.legend()
plt.show()
# <end examples/doc_builtinmodels_stepmodel.py>
After constructing step-like data, we first create a StepModel telling it to use the erf form (see details above), and a
ConstantModel. We set initial values, in one case using the data and guess() method for the initial step function
parameters, and make_params() arguments for the linear component. After making a composite model, we run fit()
and report the results, which gives:
[[Model]]
(Model(step, prefix='step_', form='erf') + Model(linear, prefix='line_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 55
# data points = 201
# variables = 5
chi-square = 593.709621
reduced chi-square = 3.02913072
Akaike info crit = 227.700173
Bayesian info crit = 244.216697
R-squared = 0.99897798
[[Variables]]
line_slope: 1.87162383 +/- 0.09318592 (4.98%) (init = 0)
line_intercept: 12.0964588 +/- 0.27606017 (2.28%) (init = 11.58574)
step_amplitude: 112.858576 +/- 0.65391731 (0.58%) (init = 134.7378)
step_center: 3.13494787 +/- 0.00516602 (0.16%) (init = 2.5)
step_sigma: 0.67393440 +/- 0.01091158 (1.62%) (init = 1.428571)
[[Correlations]] (unreported correlations are < 0.100)
C(line_slope, step_amplitude) = -0.8791
C(step_amplitude, step_sigma) = +0.5643
C(line_slope, step_sigma) = -0.4569
C(line_intercept, step_center) = +0.4269
C(line_slope, line_intercept) = -0.3093
C(line_slope, step_center) = -0.2338
C(line_intercept, step_sigma) = -0.1372
C(line_intercept, step_amplitude) = -0.1173
C(step_amplitude, step_center) = +0.1095
with a plot of
As shown above, many of the models have similar parameter names. For composite models, this could lead to a problem
of having parameters for different parts of the model having the same name. To overcome this, each Model can have a
prefix attribute (normally set to a blank string) that will be put at the beginning of each parameter name. To illustrate,
we fit one of the classic datasets from the NIST StRD suite involving a decaying exponential and two Gaussians.
# <examples/doc_builtinmodels_nistgauss.py>
import matplotlib.pyplot as plt
import numpy as np
dat = np.loadtxt('NIST_Gauss2.dat')
x = dat[:, 1]
y = dat[:, 0]
exp_mod = ExponentialModel(prefix='exp_')
pars = exp_mod.guess(y, x=x)
gauss1 = GaussianModel(prefix='g1_')
pars.update(gauss1.make_params(center=dict(value=105, min=75, max=125),
sigma=dict(value=15, min=0),
amplitude=dict(value=2000, min=0)))
gauss2 = GaussianModel(prefix='g2_')
(continues on next page)
print(out.fit_report(correl_mode='table'))
comps = out.eval_components(x=x)
axes[1].plot(x, y)
axes[1].plot(x, comps['g1_'], '--', label='Gaussian component 1')
axes[1].plot(x, comps['g2_'], '--', label='Gaussian component 2')
axes[1].plot(x, comps['exp_'], '--', label='Exponential component')
axes[1].legend()
plt.show()
# <end examples/doc_builtinmodels_nistgauss.py>
where we give a separate prefix to each model (they all have an amplitude parameter). The prefix values are attached
transparently to the models.
Note that the calls to make_param() used the bare name, without the prefix. We could have used the prefixes, but
because we used the individual model gauss1 and gauss2, there was no need.
Note also in the example here that we explicitly set bounds on many of the parameter values.
The fit results printed out are:
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='exp_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 46
# data points = 250
# variables = 8
chi-square = 1247.52821
reduced chi-square = 5.15507524
Akaike info crit = 417.864631
Bayesian info crit = 446.036318
R-squared = 0.99648654
[[Variables]]
exp_amplitude: 99.0183278 +/- 0.53748593 (0.54%) (init = 162.2102)
exp_decay: 90.9508853 +/- 1.10310778 (1.21%) (init = 93.24905)
(continues on next page)
We get a very good fit to this problem (described at the NIST site as of average difficulty, but the tests there are generally
deliberately challenging) by applying reasonable initial guesses and putting modest but explicit bounds on the parameter
values. The overall fit is shown on the left, with its individual components displayed on the right:
One final point on setting initial values. From looking at the data itself, we can see the two Gaussian peaks are rea-
sonably well separated but do overlap. Furthermore, we can tell that the initial guess for the decaying exponential
component was poorly estimated because we used the full data range. We can simplify the initial parameter values by
using this, and by defining an index_of() function to limit the data range. That is, with:
exp_mod.guess(y[:ix1], x=x[:ix1])
gauss1.guess(y[ix1:ix2], x=x[ix1:ix2])
gauss2.guess(y[ix2:ix3], x=x[ix2:ix3])
The fit converges to the same answer, giving to identical values (to the precision printed out in the report), but in fewer
steps, and without any bounds on parameters at all:
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='exp_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 37
# data points = 250
# variables = 8
chi-square = 1247.52821
reduced chi-square = 5.15507524
Akaike info crit = 417.864631
Bayesian info crit = 446.036318
R-squared = 0.99648654
[[Variables]]
exp_amplitude: 99.0183265 +/- 0.53748764 (0.54%) (init = 94.53724)
exp_decay: 90.9508884 +/- 1.10310753 (1.21%) (init = 111.1985)
g1_amplitude: 4257.77384 +/- 42.3839276 (1.00%) (init = 3189.648)
g1_center: 107.030957 +/- 0.15006934 (0.14%) (init = 106.5)
g1_sigma: 16.6725783 +/- 0.16048220 (0.96%) (init = 14.5)
g1_fwhm: 39.2609209 +/- 0.37790669 (0.96%) == '2.3548200*g1_sigma'
g1_height: 101.880228 +/- 0.59216965 (0.58%) == '0.3989423*g1_amplitude/max(1e-
˓→15, g1_sigma)'
This script is in the file doc_builtinmodels_nistgauss2.py in the examples folder, and the figure above shows an
improved initial estimate of the data.
In the example above, the two peaks might represent the interesting part of the data, and the exponential decay could
be viewed a “background” which might be due to other physical effects or part of some response of the instrumentation
used to make the measurement. That is, the background might be well-understood to be modeled as an exponential
decay, as in the example above and so easily included in the full analysis. As the results above show, there is some – but
not huge – correlation of the parameters between the peak amplitudes and the decay of the exponential function. That
means that it is helpful to include all of those components in a single fit, as the uncertainties in the peak amplitudes
(which would be interpreted as “line strength” or “area”) will reflect some of the uncertainty in how well we modeled
the background.
Sometimes a background is more complex or at least has a less obvious functional form. In these cases, it can be
useful to use a spline to model part of the curve. Just for completeness, a spline is a piecewise continuous polynomial
function (typically made of cubic polynomials) that has a series of x values known as “knots” at which the highest order
derivative is allowed to be discontinuous. By adding more knots, the spline function has more flexibility to follow a
particular function.
As an example (see the example file “doc_builtinmodels_splinemodel.py”), we start with data with a single peak and
import numpy as np
import matplotlib.pyplot as plt
from lmfit.models import SplineModel, GaussianModel
data = np.loadtxt('test_splinepeak.dat')
x = data[:, 0]
y = data[:, 1]
plt.plot(x, y, label='data')
plt.legend()
plt.show()
There is definitely a peak there, so we could start with building a model for a Gaussian peak, say with:
model = GaussianModel(prefix='peak_')
params = model.make_params(amplitude=8, center=16, sigma=1)
To account for that changing background, we’ll use a spline, but need to know where to put the “knots”. Picking points
away from the peak makes sense – we don’t want to fit the peak – but we want it to have some flexibility near the peak.
Let’s try spacing knot points at x=1, 3, ..., 13, then skip over the peak at around x=16 and then pick up knots
points at x=19, 21, 23, 25.
Note that we used bkg.guess() to guess the initial values of the spline parameters and then update the params
Parameters object with these 11 parameters to account for the spline. These will be very close to the y values at the
knot x values. The precise definition of the spline knot parameters is not “the y-values through which the resulting
spline curve goes”, but these values are pretty good estimates for the resulting spline values. You’ll see below that these
initial values are close.
With a spline background defined, we can create a composite model, and run a fit.
params['peak_amplitude'].min = 0
params['peak_center'].min = 10
params['peak_center'].max = 20
You’ll see that we first set some “sanity bounds” on the peak parameters to prevent the peak from going completely
wrong. This really is not necessary in this case, but it is often a reasonable thing to do - the general advice for this is to
be generous in the bounds, not overly restrictive.
This fit will print out a report of
[[Model]]
(Model(gaussian, prefix='peak_') + Model(spline_model, prefix='bkg_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 92
# data points = 501
# variables = 14
chi-square = 52.6611549
reduced chi-square = 0.10813379
Akaike info crit = -1100.61674
Bayesian info crit = -1041.58425
R-squared = 0.94690612
[[Variables]]
peak_amplitude: 12.2231135 +/- 0.29554108 (2.42%) (init = 8)
peak_center: 16.4280869 +/- 0.01091051 (0.07%) (init = 16)
peak_sigma: 0.72096400 +/- 0.01336667 (1.85%) (init = 1)
peak_fwhm: 1.69774046 +/- 0.03147610 (1.85%) == '2.3548200*peak_sigma'
peak_height: 6.76360674 +/- 0.09854044 (1.46%) == '0.3989423*peak_amplitude/
˓→max(1e-15, peak_sigma)'
from this we can make a few observations. First, the correlation between the “spline” parameters” and the “peak
parameters” is noticeable, but not extremely high – that’s good, and the estimated uncertainties do account for this
correlation. The spline components are correlated with each other (especially with the N-1 and N+1 spline parameter).
Second, we can see that the initial values for the background spline parameters are pretty good.
We can plot the results and fit components with
comps = out.eval_components()
plt.plot(x, out.best_fit, label='best fit')
plt.plot(x, comps['bkg_'], label='background')
plt.plot(x, comps['peak_'], label='peak')
plt.legend()
You might be interested in trying to assess what impact the select of the knots has on the resulting peak intensity. For
example, you might try some of the following set of knot values:
and re-run the fit with these different sets of knot points. The results are shown in the table below.
Table of Peak amplitudes with varying spline points
Adding more spline points, especially near the peak center around x=16.4, can impact the measurement of the ampli-
tude but the uncertainty increases dramatically enough to mostly cover the same range of values. This is a interesting
case of adding more parameters to a fit and having the uncertainties in the fitted parameters getting worse. The interested
reader is encouraged to explore the fit reports and plot these different case.
Finally, the basic case above used 11 spline points to fit the baseline. In fact, it would be reasonable to ask whether that
is enough parameters to fit the full spectra. By imposing that there is also a Gaussian peak nearby makes the spline fit
only the background, but without the Gaussian, the spline could fit the full curve. By way of example, we’ll just try
increasing the number of spline points to fit this data
plt.legend()
plt.show()
By itself, 10 knots does not give a very good fit, but 25 knots or more does give a very good fit to the peak. This should
give some confidence that the fit with 11 parameters for the background spline is acceptable, but also give some reason
to be careful in selecting the number of spline points to use.
NINE
The lmfit confidence module allows you to explicitly calculate confidence intervals for variable parameters. For most
models, it is not necessary since the estimation of the standard error from the estimated covariance matrix is normally
quite good.
But for some models, the sum of two exponentials for example, the approximation begins to fail. For this case, lmfit
has the function conf_interval() to calculate confidence intervals directly. This is substantially slower than using
the errors estimated from the covariance matrix, but the results are more robust.
The F-test is used to compare our null model, which is the best fit we have found, with an alternate model, where one
of the parameters is fixed to a specific value. The value is changed until the difference between 𝜒20 and 𝜒2𝑓 can’t be
explained by the loss of a degree of freedom within a certain confidence.
(︃ )︃
𝜒2𝑓 𝑁 −𝑃
𝐹 (𝑃𝑓 𝑖𝑥 , 𝑁 − 𝑃 ) = 2 −1
𝜒0 𝑃𝑓 𝑖𝑥
N is the number of data points and P the number of parameters of the null model. 𝑃𝑓 𝑖𝑥 is the number of fixed parameters
(or to be more clear, the difference of number of parameters between our null model and the alternate model).
Adding a log-likelihood method is under consideration.
import numpy as np
import lmfit
def residual(p):
return 1/(p['a']*x) + p['b'] - y
141
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
before we can generate the confidence intervals, we have to run a fit, so that the automated estimate of the standard
errors can be used as a starting point:
print(lmfit.fit_report(result.params))
[[Variables]]
a: 0.09943896 +/- 1.9322e-04 (0.19%) (init = 0.1)
b: 1.98476942 +/- 0.01222678 (0.62%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(a, b) = +0.6008
ci = lmfit.conf_interval(mini, result)
lmfit.printfuncs.report_ci(ci)
This shows the best-fit values for the parameters in the _BEST_ column, and parameter values that are at the varying
confidence levels given by steps in 𝜎. As we can see, the estimated error is almost the same, and the uncertainties are
well behaved: Going from 1-𝜎 (68% confidence) to 3-𝜎 (99.7% confidence) uncertainties is fairly linear. It can also
be seen that the errors are fairly symmetric around the best fit value. For this problem, it is not necessary to calculate
confidence intervals, and the estimates of the uncertainties from the covariance matrix are sufficient.
Sometimes the estimation of the standard errors from the covariance matrix fails, especially if values are near given
bounds. Hence, to find the confidence intervals in these cases, it is necessary to set the errors by hand. Note that the
standard error is only used to find an upper limit for each value, hence the exact value is not important.
To set the step-size to 10% of the initial value we loop through all parameters and set it manually:
for p in result.params:
result.params[p].stderr = abs(result.params[p].value * 0.1)
The estimated values for the 1 − 𝜎 standard error calculated by default for each fit include the effects of correlation
between pairs of variables, but assumes the uncertainties are symmetric. While it doesn’t exactly say what the values
of the 𝑛 − 𝜎 uncertainties would be, the implication is that the 𝑛 − 𝜎 error is simply 𝑛2 𝜎.
The conf_interval() function described above improves on these automatically (and quickly) calculated uncer-
tainies by explicitly finding 𝑛 − 𝜎 confidence levels in both directions – it does not assume that the uncertainties are
symmetric. This function also takes into account the correlations between pairs of variables, but it does not convey this
information very well.
For even further exploration of the confidence levels of parameter values, it can be useful to calculate maps of 𝜒2 values
for pairs of variables around their best fit values and visualize these as contour plots. Typically, pairs of variables will
have elliptical contours of constant 𝑛 − 𝜎 level, with highly-correlated pairs of variables having high ratios of major
and minor axes.
The conf_interval2d() can calculate 2-d arrays or maps of either probability or 𝛿𝜒2 = 𝜒2 − 𝜒2best for any pair
of variables. Visualizing these can help better understand the nature of the uncertainties and correlations between
parameters. To illustrate this, we’ll start with an example fit to data that we deliberately add components not accounted
for in the model, and with slightly non-Gaussian noise – a constructed but “real-world” example:
# <examples/doc_confidence_chi2_maps.py>
import matplotlib.pyplot as plt
import numpy as np
sigma_levels = [1, 2, 3]
rng = np.random.default_rng(seed=102)
#########################
# set up data -- deliberately adding imperfections and
# a small amount of non-Gaussian noise
npts = 501
x = np.linspace(1, 100, num=npts)
noise = rng.normal(scale=0.3, size=npts) + 0.2*rng.f(3, 9, size=npts)
y = (gaussian(x, amplitude=83, center=47., sigma=5.)
+ 0.02*x + 4 + 0.25*np.cos((x-20)/8.0) + noise)
#########################
# run conf_intervale, print report
sigma_levels = [1, 2, 3]
ci = conf_interval(out, out, sigmas=sigma_levels)
[[Model]]
(Model(gaussian) + Model(linear))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 31
# data points = 501
# variables = 5
chi-square = 103.861381
reduced chi-square = 0.20939794
Akaike info crit = -778.348033
Bayesian info crit = -757.265003
R-squared = 0.93782756
[[Variables]]
amplitude: 78.8171374 +/- 1.21910939 (1.55%) (init = 100)
center: 47.0751649 +/- 0.07576660 (0.16%) (init = 50)
sigma: 4.93298753 +/- 0.07984021 (1.62%) (init = 5)
slope: 0.01839006 +/- 7.1957e-04 (3.91%) (init = 0)
intercept: 4.39234411 +/- 0.04420227 (1.01%) (init = 0)
fwhm: 11.6162977 +/- 0.18800933 (1.62%) == '2.3548200*sigma'
height: 6.37412722 +/- 0.08603873 (1.35%) == '0.3989423*amplitude/max(1e-15,␣
˓→sigma)'
## Confidence Report:
99.73% 95.45% 68.27% _BEST_ 68.27% 95.45% 99.73%
amplitude: -3.62610 -2.41983 -1.21237 78.81714 +1.22111 +2.45479 +3.70515
center : -0.22849 -0.15214 -0.07584 47.07516 +0.07587 +0.15225 +0.22873
sigma : -0.23335 -0.15640 -0.07870 4.93299 +0.08000 +0.16158 +0.24509
slope : -0.00217 -0.00144 -0.00072 0.01839 +0.00072 +0.00144 +0.00217
intercept: -0.13326 -0.08860 -0.04423 4.39234 +0.04421 +0.08854 +0.13312
The reports show that we obtained a pretty good fit, and that the automated estimates of the uncertainties are actually
pretty good – agreeing to the second decimal place. But we also see that some of the uncertainties do become noticeably
asymmetric at high 𝑛 − 𝜎 levels.
We’ll plot this data and fit, and then further explore these uncertainties using conf_interval2d():
#########################
# plot initial fit
colors = ('#2030b0', '#b02030', '#207070')
fig, axes = plt.subplots(2, 3, figsize=(15, 9.5))
aix, aiy = 0, 0
nsamples = 30
for pairs in (('sigma', 'amplitude'), ('intercept', 'amplitude'),
('slope', 'intercept'), ('slope', 'center'), ('sigma', 'center')):
xpar, ypar = pairs
print("Generating chi-square map for ", pairs)
c_x, c_y, dchi2_mat = conf_interval2d(out, out, xpar, ypar,
nsamples, nsamples,
nsigma=3.5, chi2_out=True)
# sigma matrix: sigma increases chi_square
# from chi_square_best
# to chi_square + sigma**2 * reduced_chi_square
# so: sigma = sqrt(dchi2 / reduced_chi_square)
sigma_mat = np.sqrt(abs(dchi2_mat)/out.redchi)
aix += 1
if aix == 2:
aix = 0
aiy += 1
ax = axes[aix, aiy]
cix = ci[xpar]
ciy = ci[ypar]
nc = len(sigma_levels)
for i in sigma_levels:
# dotted line: scaled stderr
ax.plot((xv-i*xs, xv+i*xs, xv+i*xs, xv-i*xs, xv-i*xs),
(yv-i*ys, yv-i*ys, yv+i*ys, yv+i*ys, yv-i*ys),
linestyle='dotted', color=colors[i-1])
ax.set_xlabel(xpar)
ax.set_ylabel(ypar)
ax.grid(True, color='#d0d0d0')
plt.show()
# <end examples/doc_confidence_chi2_maps.py>
Here we made contours for the 𝑛 − 𝜎 levels from the 2-D array of 𝜒2 by noting that the 𝑛 − 𝜎 level will have 𝜒2
increased by 𝑛2 𝜒2𝜈 where 𝜒2𝜈 is reduced chi-square.
The dotted boxes show both the scaled values of the standard errors from the initial fit, and the dashed boxes show the
confidence levels from conf_interval(). You can see that the notion of increasing 𝜒2 by 𝜒2𝜈 works very well, and
that there is a small asymmetry in the uncertainties for the amplitude and sigma parameters.
Now we look at a problem where calculating the error from approximated covariance can lead to misleading result –
the same double exponential problem shown in Minimizer.emcee() - calculating the posterior probability distribution
of parameters. In fact such a problem is particularly hard for the Levenberg-Marquardt method, so we first estimate
the results using the slower but robust Nelder-Mead method. We can then compare the uncertainties computed (if the
numdifftools package is installed) with those estimated using Levenberg-Marquardt around the previously found
solution. We can also compare to the results of using emcee.
# <examples/doc_confidence_advanced.py>
import matplotlib.pyplot as plt
import numpy as np
import lmfit
def residual(p):
return p['a1']*np.exp(-x/p['t1']) + p['a2']*np.exp(-(x-0.1)/p['t2']) - y
# create Minimizer
mini = lmfit.Minimizer(residual, p, nan_policy='propagate')
lmfit.report_fit(out2.params, min_correl=0.5)
[[Variables]]
a1: 2.98622095 +/- 0.14867027 (4.98%) (init = 2.986237)
a2: -4.33526363 +/- 0.11527574 (2.66%) (init = -4.335256)
t1: 1.30994276 +/- 0.13121215 (10.02%) (init = 1.309932)
t2: 11.8240337 +/- 0.46316956 (3.92%) (init = 11.82408)
[[Correlations]] (unreported correlations are < 0.500)
C(a2, t2) = +0.9871
C(a2, t1) = -0.9246
C(t1, t2) = -0.8805
C(a1, t1) = -0.5988
Again we called conf_interval(), this time with tracing and only for 1- and 2-𝜎. Comparing these two different
estimates, we see that the estimate for a1 is reasonably well approximated from the covariance matrix, but the estimates
for a2 and especially for t1, and t2 are very asymmetric and that going from 1 𝜎 (68% confidence) to 2 𝜎 (95%
confidence) is not very predictable.
Plots of the confidence region are shown in the figures below for a1 and t2 (left), and a2 and t2 (right):
Neither of these plots is very much like an ellipse, which is implicitly assumed by the approach using the covariance
matrix. The plots actually look quite a bit like those found with MCMC and shown in the “corner plot” in Mini-
mizer.emcee() - calculating the posterior probability distribution of parameters. In fact, comparing the confidence
interval results here with the results for the 1- and 2-𝜎 error estimated with emcee, we can see that the agreement is
pretty good and that the asymmetry in the parameter distributions are reflected well in the asymmetry of the uncertain-
ties.
The trace returned as the optional second argument from conf_interval() contains a dictionary for each variable pa-
rameter. The values are dictionaries with arrays of values for each variable, and an array of corresponding probabilities
for the corresponding cumulative variables. This can be used to show the dependence between two parameters:
plt.show()
As an alternative/complement to the confidence intervals, the Minimizer.emcee() method uses Markov Chain Monte
Carlo to sample the posterior probability distribution. These distributions demonstrate the range of solutions that the
data supports and we refer to Minimizer.emcee() - calculating the posterior probability distribution of parameters where
this methodology was used on the same problem.
Credible intervals (the Bayesian equivalent of the frequentist confidence interval) can be obtained with this method.
MCMC can be used for model selection, to determine outliers, to marginalize over nuisance parameters, etcetera. For
example, you may have fractionally underestimated the uncertainties on a dataset. MCMC can be used to estimate the
true level of uncertainty on each data point. A tutorial on the possibilities offered by MCMC can be found at1 .
Notes
The values for sigma are taken as the number of standard deviations for a normal distribution and converted to
probabilities. That is, the default sigma=[1, 2, 3] will use probabilities of 0.6827, 0.9545, and 0.9973. If
any of the sigma values is less than 1, that will be interpreted as a probability. That is, a value of 1 and 0.6827
will give the same results, within precision.
Examples
Now with quantiles for the sigmas and using the trace.
This makes it possible to plot the dependence between free and fixed parameters.
conf_interval2d(minimizer, result, x_name, y_name, nx=10, ny=10, limits=None, prob_func=None, nsigma=5,
chi2_out=False)
Calculate confidence regions for two fixed parameters.
The method itself is explained in conf_interval: here we are fixing two parameters.
Parameters
• minimizer (Minimizer) – The minimizer to use, holding objective function.
• result (MinimizerResult) – The result of running minimize().
• x_name (str) – The name of the parameter which will be the x direction.
• y_name (str) – The name of the parameter which will be the y direction.
• nx (int, optional) – Number of points in the x direction (default is 10).
• ny (int, optional) – Number of points in the y direction (default is 10).
• limits (tuple, optional) – Should have the form ((x_upper, x_lower),
(y_upper, y_lower)). If not given, the default is nsigma*stderr in each direction.
• prob_func (None or callable, deprecated) – Starting with version 1.2, this argu-
ment is unused and has no effect.
• nsigma (float or int, optional) – Multiplier of stderr for limits (default is 5).
• chi2_out (bool) – Whether to return chi-square at each coordinate instead of probability.
Returns
• x (numpy.ndarray) – X-coordinates (same shape as nx).
• y (numpy.ndarray) – Y-coordinates (same shape as ny).
• grid (numpy.ndarray) – 2-D array (with shape (nx, ny)) containing the calculated proba-
bilities or chi-square.
See also:
conf_interval
Examples
TEN
BOUNDS IMPLEMENTATION
This section describes the implementation of Parameter bounds. The MINPACK-1 implementation used in
scipy.optimize.leastsq for the Levenberg-Marquardt algorithm does not explicitly support bounds on parameters, and
expects to be able to fully explore the available range of values for any Parameter. Simply placing hard constraints
(that is, resetting the value when it exceeds the desired bounds) prevents the algorithm from determining the partial
derivatives, and leads to unstable results.
Instead of placing such hard constraints, bounded parameters are mathematically transformed using the formulation
devised (and documented) for MINUIT. This is implemented following (and borrowing heavily from) the leastsqbound
from J. J. Helmus. Parameter values are mapped from internally used, freely variable values 𝑃internal to bounded
parameters 𝑃bounded . When both min and max bounds are specified, the mapping is:
(︀ 2(𝑃bounded − min) )︀
𝑃internal = arcsin −1
(max − min)
(︀ )︀ (max − min)
𝑃bounded = min + sin(𝑃internal ) + 1
2
With only an upper limit max supplied, but min left unbounded, the mapping is:
√︀
𝑃internal = (max − 𝑃bounded + 1)2 − 1
√︁
𝑃bounded = max + 1 − 𝑃internal 2 +1
With only a lower limit min supplied, but max left unbounded, the mapping is:
√︀
𝑃internal = (𝑃bounded − min + 1)2 − 1
√︁
𝑃bounded = min − 1 + 𝑃internal 2 +1
With these mappings, the value for the bounded Parameter cannot exceed the specified bounds, though the internally
varied value can be freely varied.
It bears repeating that code from leastsqbound was adopted to implement the transformation described above. The
challenging part (thanks again to Jonathan J. Helmus!) here is to re-transform the covariance matrix so that the uncer-
tainties can be estimated for bounded Parameters. This is included by using the derivate 𝑑𝑃internal /𝑑𝑃bounded from the
equations above to re-scale the Jacobin matrix before constructing the covariance matrix from it. Tests show that this
re-scaling of the covariance matrix works quite well, and that uncertainties estimated for bounded are quite reasonable.
Of course, if the best fit value is very close to a boundary, the derivative estimated uncertainty and correlations for that
parameter may not be reliable.
The MINUIT documentation recommends caution in using bounds. Setting bounds can certainly increase the number
of function evaluations (and so computation time), and in some cases may cause some instabilities, as the range of
acceptable parameter values is not fully explored. On the other hand, preliminary tests suggest that using max and min
to set clearly outlandish bounds does not greatly affect performance or results.
153
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
ELEVEN
Being able to fix variables to a constant value or place upper and lower bounds on their values can greatly simplify
modeling real data. These capabilities are key to lmfit’s Parameters. In addition, it is sometimes highly desirable to
place mathematical constraints on parameter values. For example, one might want to require that two Gaussian peaks
have the same width, or have amplitudes that are constrained to add to some value. Of course, one could rewrite the
objective or model function to place such requirements, but this is somewhat error-prone, and limits the flexibility so
that exploring constraints becomes laborious.
To simplify the setting of constraints, Parameters can be assigned a mathematical expression of other Parameters,
builtin constants, and builtin mathematical functions that will be used to determine its value. The expressions used for
constraints are evaluated using the asteval module, which uses Python syntax, and evaluates the constraint expressions
in a safe and isolated namespace.
This approach to mathematical constraints allows one to not have to write a separate model function for two Gaussians
where the two sigma values are forced to be equal, or where amplitudes are related. Instead, one can write a more
general two Gaussian model (perhaps using GaussianModel) and impose such constraints on the Parameters for a
particular fit.
11.1 Overview
Just as one can place bounds on a Parameter, or keep it fixed during the fit, so too can one place mathematical constraints
on parameters. The way this is done with lmfit is to write a Parameter as a mathematical expression of the other
parameters and a set of pre-defined operators and functions. The constraint expressions are simple Python statements,
allowing one to place constraints like:
pars = Parameters()
pars.add('frac_curve1', value=0.5, min=0, max=1)
pars.add('frac_curve2', expr='1-frac_curve1')
as the value of the frac_curve1 parameter is updated at each step in the fit, the value of frac_curve2 will be updated
so that the two values are constrained to add to 1.0. Of course, such a constraint could be placed in the fitting function,
but the use of such constraints allows the end-user to modify the model of a more general-purpose fitting function.
Nearly any valid mathematical expression can be used, and a variety of built-in functions are available for flexible
modeling.
155
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
The mathematical expressions used to define constrained Parameters need to be valid Python expressions. As you
would expect, the operators +, -, *, /, and **, are supported. In fact, a much more complete set can be used, including
Python’s bit- and logical operators:
The values for e (2.7182818. . . ) and pi (3.1415926. . . ) are available, as are several supported mathematical and
trigonometric function:
In addition, all Parameter names will be available in the mathematical expressions. Thus, with parameters for a few
peak-like functions:
pars = Parameters()
pars.add('amp_1', value=0.5, min=0, max=1)
pars.add('cen_1', value=2.2)
pars.add('wid_1', value=0.2)
In fact, almost any valid Python expression is allowed. A notable example is that Python’s 1-line if expression is
supported:
pars.add('param_a', value=1)
pars.add('param_b', value=2)
pars.add('test_val', value=100)
A rather common question about how to set up constraints that use an inequality, say, 𝑥 + 𝑦 ≤ 10. This can be done
with algebraic constraints by recasting the problem, as 𝑥 + 𝑦 = 𝛿 and 𝛿 ≤ 10. That is, first, allow 𝑥 to be held by the
freely varying parameter x. Next, define a parameter delta to be variable with a maximum value of 10, and define
parameter y as delta - x:
pars = Parameters()
pars.add('x', value=5, vary=True)
pars.add('delta', value=5, max=10, vary=True)
pars.add('y', expr='delta-x')
The essential point is that an inequality still implies that a variable (here, delta) is needed to describe the constraint.
The secondary point is that upper and lower bounds can be used as part of the inequality to make the definitions more
convenient.
The expression used in a constraint is converted to a Python Abstract Syntax Tree, which is an intermediate version of
the expression – a syntax-checked, partially compiled expression. Among other things, this means that Python’s own
parser is used to parse and convert the expression into something that can easily be evaluated within Python. It also
means that the symbols in the expressions can point to any Python object.
In fact, the use of Python’s AST allows a nearly full version of Python to be supported, without using Python’s built-in
eval() function. The asteval module actually supports most Python syntax, including for- and while-loops, conditional
expressions, and user-defined functions. There are several unsupported Python constructs, most notably the class
statement, so that new classes cannot be created, and the import statement, which helps make the asteval module
safe from malicious use.
One important feature of the asteval module is that you can add domain-specific functions into the it, for later use in
constraint expressions. To do this, you would use the _asteval attribute of the Parameters class, which contains
a complete AST interpreter. The asteval interpreter uses a flat namespace, implemented as a single dictionary. That
means you can preload any Python symbol into the namespace for the constraints, for example this Lorentzian function:
You can add this user-defined function to the asteval interpreter of the Parameters class:
pars = Parameters()
pars._asteval.symtable['lorentzian'] = mylorentzian
and then initialize the Minimizer class with this parameter set:
Alternatively, one can first initialize the Minimizer class and add the function to the asteval interpreter of Minimizer.
params afterwards:
pars = Parameters()
fitter = Minimizer(userfcn, pars)
fitter.params._asteval.symtable['lorentzian'] = mylorentzian
In both cases the user-defined lorentzian() function can now be used in constraint expressions.
TWELVE
RELEASE NOTES
This section discusses changes between versions, especially changes significant to the use and behavior of the library.
This is not meant to be a comprehensive list of changes. For such a complete record, consult the lmfit GitHub repository.
New features:
• add create_params function (PR #844)
• add chi2_out and nsigma options to conf_interval2d()
• add ModelResult.summary() to return many resulting fit statistics and attributes into a JSON-able dict.
• add correl_table() function to lmfit.printfuncs and correl_mode option to fit_report() and
ModelResult.fit_report() to optionally display a RST-formatted table of a correlation matrix.
Bug fixes/enhancements:
• fix bug when setting param.vary=True for a constrained parameter (Issue #859; PR #860)
• fix bug in reported uncertainties for constrained parameters by better propating uncertainties (Issue #855; PR
#856)
• Coercing of user input data and independent data for Model to float64 ndarrays is somewhat less aggressive and
will not increase the precision of numpy ndarrays (see Data Types for data and independent data with Model for
details). The resulting calculation from a model or objective function is more aggressively coerced to float64.
(Issue #850; PR #853)
• the default value of epsfcn is increased to 1.e-10 to allow for handling of data with precision less than float64
(Issue #850; PR #853)
• fix conf_interval2d to use “increase chi-square by sigma**2*reduced chi-square” to give the sigma-level
probabilities (Issue #848; PR #852)
• fix reading of older ModelResult (Issue #845; included in PR #844)
• fix deepcopy of Parameters and user data (mguhyo; PR #837)
• improve Model.make_params and create_params to take optional dict of Parameter attributes (PR #844)
• fix reporting of nfev from least_squares to better reflect actual number of function calls (Issue #842; PR
#844)
• fix bug in Model.eval when mixing parameters and keyword arguments (PR #844, #839)
• re-adds residual to saved Model result (PR #844, #830)
159
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
• ConstantModel and ComplexConstantModel will return an ndarray of the same shape as the independent
variable x (JeppeKlitgaard, Issue #840; PR #841)
• update tests for latest versions of NumPy and SciPy.
• many fixes of doc typos and updates of dependencies, pre-commit hooks, and CI.
New features:
• add Pearson4Model (@lellid; PR #800)
• add SplineModel (PR #804)
• add R^2 rsquared statistic to fit outputs and reports for Model fits (Issue #803; PR #810)
• add calculation of dely for model components of composite models (Issue #761; PR #826)
Bug fixes/enhancements:
• make sure variable spercent is always defined in params_html_table functions (reported by @MySlien-
tWind; Issue #768, PR #770)
• always initialize the variables success and covar the MinimizerResult (reported by Marc W. Pound; PR
#771)
• build package following PEP517/PEP518; use pyproject.toml and setup.cfg; leave setup.py for now (PR
#777)
• components used to create a CompositeModel can now have different independent variables (@Julian-
Hochhaus; Discussion #787; PR #788)
• fixed function definition for StepModel(form='linear'), was not consistent with the other ones (@matpom-
pili; PR #794)
• fixed height factor for Gaussian2dModel, was not correct (@matpompili; PR #795)
• for covariances with negative diagonal elements, we set the covariance to None (PR #813)
• fixed linear mode for RectangleModel (@arunpersaud; Issue #815; PR #816)
• report correct initial values for parameters with bounds (Issue #820; PR #821)
• allow recalculation of confidence intervals (@jagerber48; PR #798)
• include ‘residual’ in JSON output of ModelResult.dumps (@mac01021; PR #830)
• supports and is tested against Python 3.11; updated minimum required version of SciPy, NumPy, and asteval (PR
#832)
Deprecations:
• remove support for Python 3.6 which reached EOL on 2021-12-23 (PR #790)
Version 1.0.2 officially supports Python 3.9 and has dropped support for Python 3.5. The minimum version of the
following dependencies were updated: asteval>=0.9.21, numpy>=1.18, and scipy>=1.3.
New features:
• added two-dimensional Gaussian lineshape and model (PR #642; @mpmdean)
• all built-in models are now registered in lmfit.models.lmfit_models; new Model class attribute
valid_forms (PR #663; @rayosborn)
• added a SineModel (PR #676; @lneuhaus)
• add the run_mcmc_kwargs argument to Minimizer.emcee to pass to the emcee.EnsembleSampler.
run_mcmc function (PR #694; @rbnvrw)
Bug fixes:
• ModelResult.eval_uncertainty should use provided Parameters (PR #646)
• center in lognormal model can be negative (Issue #644, PR #645; @YoshieraHuang)
• restore best-fit values after calculation of covariance matrix (Issue #655, PR #657)
• add helper-function not_zero to prevent ZeroDivisionError in lineshapes and use in exponential lineshape (Issue
#631, PR #664; @s-weigand)
• save last_internal_values and use to restore internal values if fit is aborted (PR #667)
• dumping a fit using the lbfgsb method now works, convert bytes to string if needed (Issue #677, PR #678;
@leonfoks)
• fix use of callable Jacobian for scalar methods (PR #681; @mstimberg)
• preserve float/int types when encoding for JSON (PR #696; @jedzill4)
• better support for saving/loading of ExpressionModels and assure that init_params and init_fit are set when
loading a ModelResult (PR #706)
Various:
• update minimum dependencies (PRs #688, #693)
• improvements in coding style, docstrings, CI, and test coverage (PRs #647, #649, #650, #653, #654; #685, #668,
#689)
• fix typo in Oscillator (PR #658; @flothesof)
• add example using SymPy (PR #662)
• allow better custom pool for emcee() (Issue #666, PR #667)
• update NIST Strd reference functions and tests (PR #670)
• make building of documentation cross-platform (PR #673; @s-weigand)
• relax module name check in test_check_ast_errors for Python 3.9 (Issue #674, PR #675; @mwhudson)
• fix/update layout of documentation, now uses the sphinx13 theme (PR #687)
• fixed DeprecationWarnings reported by NumPy v1.2.0 (PR #699)
• increase value of tiny and check for it in bounded parameters to avoid “parameter not moving from initial value”
(Issue #700, PR #701)
• add max_nfev to basinhopping and brute (now supported everywhere in lmfit) and set to more uniform
default values (PR #701)
• use Azure Pipelines for CI, drop Travis (PRs #696 and #702)
Version 1.0.1 is the last release that supports Python 3.5. All newer version will require 3.6+ so that we can use
formatting-strings and rely on dictionaries being ordered.
New features:
• added thermal distribution model and lineshape (PR #620; @mpmdean)
• introduced a new argument max_nfev to uniformly specify the maximum number of function evaluations (PR
#610) Please note: all other arguments (e.g., ``maxfev``, ``maxiter``, . . . ) will no longer be passed to the
underlying solver. A warning will be emitted stating that one should use ``max_nfev``.
• the attribute call_kws was added to the MinimizerResult class and contains the keyword arguments that are
supplied to the solver in SciPy.
Bug fixes:
• fixes to the load and __setstate__ methods of the Parameter class
• fixed failure of ModelResult.dump() due to missing attributes (Issue #611, PR #623; @mpmdean)
• guess_from_peak function now also works correctly with decreasing x-values or when using pandas (PRs #627
and #629; @mpmdean)
• the Parameter.set() method now correctly first updates the boundaries and then the value (Issue #636, PR
#637; @arunpersaud)
Various:
• fixed typo for the use of expressions in the documentation (Issue #610; @jkrogager)
• removal of PY2-compatibility and unused code and improved test coverage (PRs #619, #631, and #633)
• removed deprecated isParameter function and automatic conversion of an uncertainties object (PR #626)
• inaccurate FWHM calculations were removed from built-in models, others labeled as estimates (Issue #616 and
PR #630)
• corrected spelling mistake for the Doniach lineshape and model (Issue #634; @rayosborn)
• removed unsupported/untested code for IPython notebooks in lmfit/ui/*
Version 0.9.15 is the last release that supports Python 2.7; it now also fully supports Python 3.8.
New features, improvements, and bug fixes:
• move application of parameter bounds to setter instead of getter (PR #587)
• add support for non-array Jacobian types in least_squares (Issue #588, @ezwelty in PR #589)
• add more information (i.e., acor and acceptance_fraction) about emcee fit (@j-zimmermann in PR #593)
• “name” is now a required positional argument for Parameter class, update the magic methods (PR #595)
• fix nvars count and bound handling in confidence interval calculations (Issue #597, PR #598)
• support Python 3.8; requires asteval >= 0.9.16 (PR #599)
• only support emcee version 3 (i.e., no PTSampler anymore) (PR #600)
• fix and refactor prob_bunc in confidence interval calculations (PR #604)
• fix adding Parameters with custom user-defined symbols (Issue #607, PR #608; thanks to @gbouvignies for the
report)
Various:
• bump requirements to LTS version of SciPy/ NumPy and code clean-up (PR #591)
• documentation updates (PR #596, and others)
• improve test coverage and Travis CI updates (PR #595, and others)
• update pre-commit hooks and configuration in setup.cfg
To-be deprecated: - function Parameter.isParameter and conversion from uncertainties.core.Variable to value in _getval
(PR #595)
New features:
• the global optimizers shgo and dual_annealing (new in SciPy v1.2) are now supported (Issue #527; PRs #545
and #556)
• eval method added to the Parameter class (PR #550 by @zobristnicholas)
• avoid ZeroDivisionError in printfuncs.params_html_table (PR #552 by @aaristov and PR #559)
• add parallelization to brute method (PR #564, requires SciPy v1.3)
Bug fixes:
• consider only varying parameters when reporting potential issues with calculating errorbars (PR #549) and com-
pare value to both min and max (PR #571)
• guard against division by zero in lineshape functions and FWHM and height expression calculations (PR #545)
• fix issues with restoring a saved Model (Issue #553; PR #554)
• always set result.method for emcee algorithm (PR #558)
• more careful adding of parameters to handle out-of-order constraint expressions (Issue #560; PR #561)
• make sure all parameters in Model.guess() use prefixes (PRs #567 and #569)
• use inspect.signature for PY3 to support wrapped functions (Issue #570; PR #576)
• fix result.nfev` for brute method when using parallelization (Issue #578; PR #579)
Various:
• remove “missing” in the Model class (replaced by nan_policy) and “drop” as option to nan_policy (replaced by
omit) deprecated since 0.9 (PR #565).
• deprecate ‘report_errors’ in printfuncs.py (PR #571)
• updates to the documentation to use jupyter-sphinx to include examples/output (PRs #573 and #575)
• include a Gallery with examples in the documentation using sphinx-gallery (PR #574 and #583)
• improve test-coverage (PRs #571, #572 and #585)
• add/clarify warning messages when NaN values are detected (PR #586)
• several updates to docstrings (Issue #584; PR #583, and others)
• update pre-commit hooks and several docstrings
New features:
• Clearer warning message in fit reports when uncertainties should but cannot be estimated, including guesses of
which Parameters to examine (#521, #543)
• SplitLorenztianModel and split_lorentzian function (#523)
• HTML representations for Parameter, MinimizerResult, and Model so that they can be printed better with Jupyter
(#524, #548)
• support parallelization for differential evolution (#526)
Bug fixes:
• delay import of matplotlib (and so, the selection of its backend) as late as possible (#528, #529)
• fix for saving, loading, and reloading ModelResults (#534)
• fix to leastsq to report the best-fit values, not the values tried last (#535, #536)
• fix synchronization of all parameter values on Model.guess() (#539, #542)
• improve deprecation warnings for outdated nan_policy keywords (#540)
• fix for edge case in gformat() (#547)
Project management:
• using pre-commit framework to improve and enforce coding style (#533)
• added code coverage report to github main page
• updated docs, github templates, added several tests.
• dropped support and testing for Python 3.4.
Two new global algorithms were added: basinhopping and AMPGO. Basinhopping wraps the method present in scipy,
and more information can be found in the documentation (basinhopping() and scipy.optimize.basinhopping). The
Adaptive Memory Programming for Global Optimization (AMPGO) algorithm was adapted from Python code written
by Andrea Gavana. A more detailed explanation of the algorithm is available in the AMPGO paper and specifics for
lmfit can be found in the ampgo() function.
Lmfit uses the external uncertainties (https://github.com/lebigot/uncertainties) package (available on PyPI), instead of
distributing its own fork.
An AbortFitException is now raised when the fit is aborted by the user (i.e., by using iter_cb).
Bugfixes:
• all exceptions are allowed when trying to import matplotlib
• simplify and fix corner-case errors when testing closeness of large integers
Lmfit now uses the asteval (https://github.com/newville/asteval) package instead of distributing its own copy. The
minimum required asteval version is 0.9.12, which is available on PyPI. If you see import errors related to asteval,
please make sure that you actually have the latest version installed.
Support for SciPy 0.14 has been dropped: SciPy 0.15 is now required. This is especially important for lmfit mainte-
nance, as it means we can now rely on SciPy having code for differential evolution and do not need to keep a local
copy.
A brute force method was added, which can be used either with Minimizer.brute() or using the method='brute'
option to Minimizer.minimize(). This method requires finite bounds on all varying parameters, or that parameters
have a finite brute_step attribute set to specify the step size.
Custom cost functions can now be used for the scalar minimizers using the reduce_fcn option.
Many improvements to documentation and docstrings in the code were made. As part of that effort, all API documen-
tation in this main Sphinx documentation now derives from the docstrings.
Uncertainties in the resulting best-fit for a model can now be calculated from the uncertainties in the model parameters.
Parameters have two new attributes: brute_step, to specify the step size when using the brute method, and
user_data, which is unused but can be used to hold additional information the user may desire. This will be pre-
served on copy and pickling.
Several bug fixes and cleanups.
Versioneer was updated to 0.18.
Tests can now be run either with nose or pytest.
Support for Python 2.6 and SciPy 0.13 has been dropped.
Some support for the new least_squares routine from SciPy 0.17 has been added.
Parameters can now be used directly in floating point or array expressions, so that the Parameter value does not need
sigma = params['sigma'].value. The older, explicit usage still works, but the docs, samples, and tests have been
updated to use the simpler usage.
Support for Python 2.6 and SciPy 0.13 is now explicitly deprecated and will be dropped in version 0.9.5.
This upgrade makes an important, non-backward-compatible change to the way many fitting scripts and programs will
work. Scripts that work with version 0.8.3 will not work with version 0.9.0 and vice versa. The change was not made
lightly or without ample discussion, and is really an improvement. Modifying scripts that did work with 0.8.3 to work
with 0.9.0 is easy, but needs to be done.
12.17.1 Summary
The upgrade from 0.8.3 to 0.9.0 introduced the MinimizerResult class (see MinimizerResult – the optimization result)
which is now used to hold the return value from minimize() and Minimizer.minimize(). This returned object
contains many goodness of fit statistics, and holds the optimized parameters from the fit. Importantly, the parameters
passed into minimize() and Minimizer.minimize() are no longer modified by the fit. Instead, a copy of the passed-
in parameters is made which is changed and returns as the params attribute of the returned MinimizerResult.
12.17.2 Impact
my_pars = Parameters()
my_pars.add('amp', value=300.0, min=0)
my_pars.add('center', value=5.0, min=0, max=10)
my_pars.add('decay', value=1.0, vary=False)
will still work, but that my_pars will NOT be changed by the fit. Instead, my_pars is copied to an internal set of
parameters that is changed in the fit, and this copy is then put in result.params. To look at fit results, use result.
params, not my_pars.
This has the effect that my_pars will still hold the starting parameter values, while all of the results from the fit are
held in the result object returned by minimize().
If you want to do an initial fit, then refine that fit to, for example, do a pre-fit, then refine that result different fitting
method, such as:
and have access to all of the starting parameters my_pars, the result of the first fit result1, and the result of the final
fit result2.
12.17.3 Discussion
THIRTEEN
EXAMPLES GALLERY
Below are examples of the different things you can do with lmfit. Click on any image to see the complete source code
and output.
We encourage users (i.e., YOU) to submit user-guide-style, documented, and preferably self-contained examples of
how you use lmfit for inclusion in this gallery! Please note that many of the examples below currently do not follow
these guidelines yet.
Simple example demonstrating how to read in the data using pandas and supply the elements of the DataFrame to
lmfit.
import pandas as pd
read the data into a pandas DataFrame, and use the x and y columns:
dframe = pd.read_csv('peak.csv')
model = LorentzianModel()
params = model.guess(dframe['y'], x=dframe['x'])
print(result.fit_report())
[[Model]]
Model(lorentzian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 21
# data points = 101
# variables = 3
chi-square = 13.0737250
reduced chi-square = 0.13340536
Akaike info crit = -200.496119
(continues on next page)
171
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
result.plot_fit()
print(result.fit_report())
[[Model]]
Model(_eval)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 52
# data points = 201
# variables = 3
chi-square = 0.01951689
reduced chi-square = 9.8570e-05
Akaike info crit = -1851.19580
Bayesian info crit = -1841.28588
R-squared = 0.99967271
[[Variables]]
amp: 3.40625133 +/- 0.00512077 (0.15%) (init = 5)
cen: 1.80121155 +/- 8.6847e-04 (0.05%) (init = 5)
wid: 0.50029616 +/- 8.6848e-04 (0.17%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(amp, wid) = +0.5774
plt.plot(x, y, 'o')
plt.plot(x, result.init_fit, '--', label='initial fit')
plt.plot(x, result.best_fit, '-', label='best fit')
plt.legend()
Sometimes specifying boundaries using min and max are not sufficient, and more complicated (inequality) constraints
are needed. In the example below the center of the Lorentzian peak is constrained to be between 0-5 away from the
center of the Gaussian peak.
See also: https://lmfit.github.io/lmfit-py/constraints.html#using-inequality-constraints
np.random.seed(0)
x = np.linspace(0, 20.0, 601)
Create the fitting parameters and set an inequality constraint for cen_l. First, we add a new fitting parameter
peak_split, which can take values between 0 and 5. Afterwards, we constrain the value for cen_l using the ex-
pression to be 'peak_split+cen_g':
Performing a fit, here using the leastsq algorithm, gives the following fitting results:
report_fit(out.params)
[[Variables]]
amp_g: 21.2722842 +/- 0.05138772 (0.24%) (init = 10)
cen_g: 6.10496396 +/- 0.00334613 (0.05%) (init = 5)
wid_g: 1.21434954 +/- 0.00327317 (0.27%) (init = 1)
amp_l: 9.46504173 +/- 0.05445415 (0.58%) (init = 10)
peak_split: 3.52163544 +/- 0.01004618 (0.29%) (init = 2.5)
cen_l: 9.62659940 +/- 0.01066172 (0.11%) == 'peak_split+cen_g'
wid_l: 1.21434954 +/- 0.00327317 (0.27%) == 'wid_g'
[[Correlations]] (unreported correlations are < 0.100)
C(amp_g, wid_g) = +0.6199
C(amp_g, peak_split) = +0.3796
C(wid_g, peak_split) = +0.3445
C(amp_g, amp_l) = -0.2951
C(cen_g, amp_l) = -0.2761
C(amp_g, cen_g) = +0.1936
C(wid_g, amp_l) = -0.1651
C(cen_g, wid_g) = +0.1546
and figure:
This example compares the leastsq and differential_evolution algorithms on a fairly simple problem.
import lmfit
decay = 5
offset = 1.0
amp = 2.0
omega = 4.0
np.random.seed(2)
x = np.linspace(0, 10, 101)
y = offset + amp*np.sin(omega*x) * np.exp(-x/decay)
yn = y + np.random.normal(size=y.size, scale=0.450)
params = lmfit.Parameters()
params.add('offset', 2.0, min=0, max=10.0)
params.add('omega', 3.3, min=0, max=10.0)
params.add('amp', 2.5, min=0, max=10.0)
params.add('decay', 1.0, min=0, max=10.0)
A major advantage of using lmfit is that one can specify boundaries on fitting parameters, even if the underlying
algorithm in SciPy does not support this. For more information on how this is implemented, please refer to: https:
//lmfit.github.io/lmfit-py/bounds.html
The example below shows how to set boundaries using the min and max attributes to fitting parameters.
random.seed(0)
x = linspace(0, 250, 1500)
noise = random.normal(scale=2.8, size=x.size)
data = residual(p_true, x) + noise
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 79
# data points = 1500
# variables = 4
(continues on next page)
random.seed(0)
x = linspace(0.0, 20.0, 601)
params.add(name='total_amplitude', value=20)
params.set(l_amplitude=dict(expr='total_amplitude - g_amplitude'))
params.set(l_center=dict(expr='1.5+g_center'))
params.set(l_sigma=dict(expr='2*g_sigma'))
print(result.fit_report())
[[Model]]
((Model(gaussian, prefix='g_') + Model(lorentzian, prefix='l_')) + Model(linear,␣
˓→prefix='line_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 65
# data points = 601
# variables = 6
chi-square = 71878.3055
reduced chi-square = 120.803875
Akaike info crit = 2887.26503
Bayesian info crit = 2913.65660
R-squared = -22.1967107
[[Variables]]
g_amplitude: 21.1877635 +/- 0.32192128 (1.52%) (init = 10)
g_center: 8.11125903 +/- 0.01162987 (0.14%) (init = 9)
g_sigma: 1.20925819 +/- 0.01170853 (0.97%) (init = 1)
l_amplitude: 9.41261441 +/- 0.61672968 (6.55%) == 'total_amplitude - g_amplitude
˓→'
The reduce_fcn specifies how to convert a residual array to a scalar value for the scalar minimizers. The
default value is None (i.e., “sum of squares of residual”) - alternatives are: negentropy, neglogcauchy, or
a user-specified callable. For more information please refer to: https://lmfit.github.io/lmfit-py/fitting.html#
using-the-minimizer-class
Here, we use as an example the Student’s t log-likelihood for robust fitting of data with outliers.
import lmfit
decay = 5
offset = 1.0
amp = 2.0
omega = 4.0
np.random.seed(2)
x = np.linspace(0, 10, 101)
y = offset + amp * np.sin(omega*x) * np.exp(-x/decay)
yn = y + np.random.normal(size=y.size, scale=0.250)
method = 'L-BFGS-B'
o1 = lmfit.minimize(resid, params, args=(x, yn), method=method)
print("# Fit using sum of squares:\n")
lmfit.report_fit(o1)
[[Fit Statistics]]
# fitting method = L-BFGS-B
(continues on next page)
[[Fit Statistics]]
# fitting method = L-BFGS-B
# function evals = 135
# data points = 101
# variables = 4
chi-square = 33.5081334
reduced chi-square = 0.34544467
Akaike info crit = -103.436564
Bayesian info crit = -92.9760822
[[Variables]]
offset: 1.02005965 +/- 0.06642640 (6.51%) (init = 2)
omega: 3.98224426 +/- 0.02898702 (0.73%) (init = 3.3)
amp: 1.83231421 +/- 0.27241865 (14.87%) (init = 2.5)
decay: 5.77327486 +/- 1.45140618 (25.14%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(amp, decay) = -0.7584
C(offset, amp) = -0.1067
SymPy is a Python library for symbolic mathematics. It can be very useful to build a model with SymPy and then apply
that model to the data with lmfit. This example shows how to do that. Please note that this example requires both the
sympy and matplotlib packages.
import lmfit
Instead of creating the SymPy symbols explicitly and building an expression with them, we will use the SymPy parser.
gauss_peak1 = sympy_parser.parse_expr('A1*exp(-(x-xc1)**2/(2*sigma1**2))')
gauss_peak2 = sympy_parser.parse_expr('A2*exp(-(x-xc2)**2/(2*sigma2**2))')
exp_back = sympy_parser.parse_expr('B*exp(-x/xw)')
We are using SymPy’s lambdify function to make a function from the model expressions. We then use these functions
to generate some fake data.
np.random.seed(1)
x = np.linspace(0, 10, 40)
param_values = dict(x=x, A1=2, sigma1=1, sigma2=1, A2=3, xc1=2, xc2=5, xw=4, B=5)
y = model_func(**param_values)
yi = model_list_func(**param_values)
yn = y + np.random.randn(y.size)*0.4
Next, we will just create a lmfit model from the function and fit the data.
res.plot_fit()
plt.plot(x, y, label='true')
plt.legend()
The nice thing of using SymPy is that we can easily modify our fit function. Let’s assume we know that the width
of both Gaussians are identical. Similarly, we assume that the ratio between both Gaussians is fixed to 3:2 for some
reason. Both can be expressed by just substituting the variables.
np.random.seed(2021)
x = np.linspace(-1, 2, 151)
data = []
for _ in np.arange(5):
amp = 0.60 + 9.50*np.random.rand()
cen = -0.20 + 1.20*np.random.rand()
sig = 0.25 + 0.03*np.random.rand()
dat = gauss(x, amp, cen, sig) + np.random.normal(size=x.size, scale=0.1)
data.append(dat)
data = np.array(data)
fit_params = Parameters()
for iy, y in enumerate(data):
fit_params.add(f'amp_{iy+1}', value=0.5, min=0.0, max=200)
fit_params.add(f'cen_{iy+1}', value=0.4, min=-2.0, max=2.0)
fit_params.add(f'sig_{iy+1}', value=0.3, min=0.01, max=3.0)
Constrain the values of sigma to be the same for all peaks by assigning sig_2, . . . , sig_5 to be equal to sig_1.
[[Variables]]
amp_1: 6.32742010 +/- 0.02279089 (0.36%) (init = 0.5)
(continues on next page)
plt.figure()
for i in range(5):
y_fit = gauss_dataset(out.params, i, x)
plt.plot(x, data[i, :], 'o', x, y_fit, '-')
This notebook shows a simple example of using the lmfit.Model class. For more information please refer to: https:
//lmfit.github.io/lmfit-py/model.html#the-model-class.
import numpy as np
from pandas import Series
The Model class is a flexible, concise curve fitter. I will illustrate fitting example data to an exponential decay.
The parameters are in no particular order. We’ll need some example data. I will use N=7 and tau=3, and add a little
noise.
t = np.linspace(0, 5, num=1000)
np.random.seed(2021)
data = decay(t, 7, 3) + np.random.randn(t.size)
Simplest Usage
The Model infers the parameter names by inspecting the arguments of the function, decay. Then I passed the indepen-
dent variable, t, and initial guesses for each parameter. A residual function is automatically defined, and a least-squared
regression is performed.
We can immediately see the best-fit values:
print(result.values)
and use these best-fit parameters for plotting with the plot function:
result.plot()
result.params.pretty_print()
More information about the fit is stored in the result, which is an lmfit.MimimizerResult object (see: https://lmfit.
github.io/lmfit-py/fitting.html#lmfit.minimizer.MinimizerResult)
Specifying Bounds and Holding Parameters Constant
Above, the Model class implicitly builds Parameter objects from keyword arguments of fit that match the arguments
of decay. You can build the Parameter objects explicitly; the following is equivalent.
[[Variables]]
N: 7.14669319 +/- 0.09130428 (1.28%) (init = 10)
tau: 2.89802898 +/- 0.06299118 (2.17%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(N, tau) = -0.7533
By building Parameter objects explicitly, you can specify bounds (min, max) and set parameters constant
(vary=False).
[[Variables]]
N: 7 (fixed)
tau: 2.97663118 +/- 0.04347476 (1.46%) (init = 1)
[[Variables]]
N: 7.14669316 +/- 0.09130423 (1.28%) (init = 10)
tau: 2.89802901 +/- 0.06299127 (2.17%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(N, tau) = -0.7533
Keyword arguments override params, resetting value and all other properties (min, max, vary).
[[Variables]]
N: 7.14669316 +/- 0.09130423 (1.28%) (init = 10)
tau: 2.89802901 +/- 0.06299127 (2.17%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(N, tau) = -0.7533
The input parameters are not modified by fit. They can be reused, retaining the same initial value. If you want to use
the result of one fit as the initial guess for the next, simply pass params=result.params.
#TODO/FIXME: not sure if there ever way a “helpful exception”, but currently #it raises a ValueError: The input
contains nan values.
#*A Helpful Exception*
#All this implicit magic makes it very easy for the user to neglect to set a #parameter. The fit function checks for this
and raises a helpful exception.
#An extra parameter that cannot be matched to the model function will #throw a UserWarning, but it will not raise,
leaving open the possibility #of unforeseen extensions calling for some parameters.
Weighted Fits
Use the sigma argument to perform a weighted fit. If you prefer to think of the fit in term of weights, sigma=1/
weights.
weights = np.arange(len(data))
result = model.fit(data, params, t=t, weights=weights)
report_fit(result.params)
[[Variables]]
N: 6.98535179 +/- 0.28002384 (4.01%) (init = 10)
tau: 2.97268236 +/- 0.11134755 (3.75%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(N, tau) = -0.9311
data_with_holes = data.copy()
data_with_holes[[5, 500, 700]] = np.nan # Replace arbitrary values with NaN.
[[Variables]]
N: 7.15448795 +/- 0.09181809 (1.28%) (init = 10)
tau: 2.89285089 +/- 0.06306004 (2.18%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(N, tau) = -0.7542
If you don’t want to ignore missing values, you can set the model to raise proactively, checking for missing values
before attempting the fit.
Uncomment to see the error #model = Model(decay, independent_vars=[‘t’], nan_policy=’raise’) #result =
model.fit(data_with_holes, params, t=t)
The default setting is nan_policy='raise', which does check for NaNs and raises an exception when present.
Null-checking relies on pandas.isnull if it is available. If pandas cannot be imported, it silently falls back on numpy.
isnan.
Data Alignment
Imagine a collection of time series data with different lengths. It would be convenient to define one sufficiently long
array t and use it for each time series, regardless of length. pandas (https://pandas.pydata.org/pandas-docs/stable/)
provides tools for aligning indexed data. And, unlike most wrappers to scipy.leastsq, Model can handle pandas
objects out of the box, using its data alignment features.
Here I take just a slice of the data and fit it to the full t. It is automatically aligned to the correct section of t using
Series’ index.
[[Variables]]
N: 7.10725864 +/- 0.24259071 (3.41%) (init = 10)
tau: 2.92503564 +/- 0.13481789 (4.61%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(N, tau) = -0.9320
Data with missing entries and an unequal length still aligns properly.
[[Variables]]
N: 7.11270194 +/- 0.24334895 (3.42%) (init = 10)
tau: 2.92065227 +/- 0.13488230 (4.62%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(N, tau) = -0.9320
Specifying an analytical function to calculate the Jacobian can speed-up the fitting procedure.
params = Parameters()
params.add('a', value=10)
params.add('b', value=10)
params.add('c', value=10)
'------------------------------------------')
and the best-fit to the synthetic data (with added noise) is the same for both methods:
Outliers can sometimes be identified by assessing the influence of each datapoint. To assess the influence of one point,
we fit the dataset without the point and compare the result with the fit of the full dataset. The code below shows how
to do this with lmfit. Note that the presented method is very basic.
import lmfit
params = lmfit.Parameters()
params.add_many(('a', 0.1), ('b', 1))
fit_result.plot_fit()
plt.plot(x[idx], y[idx], 'o', label='outliers')
plt.show()
print(fit_result.fit_report())
[[Model]]
Model(func)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 13
# data points = 100
# variables = 2
chi-square = 1338.34458
reduced chi-square = 13.6565773
Akaike info crit = 263.401856
Bayesian info crit = 268.612196
R-squared = 0.70062332
[[Variables]]
a: 0.08937623 +/- 0.00590174 (6.60%) (init = 0.1)
b: 1.51298991 +/- 0.46229147 (30.55%) (init = 2)
[[Correlations]] (unreported correlations are < 0.100)
C(a, b) = +0.6008
fig, ax = plt.subplots()
ax.plot(x, (fit_result.chisqr - chi_sq) / chi_sq)
ax.scatter(x[idx], fit_result.chisqr / chi_sq[idx] - 1, color='r',
label='outlier')
ax.set_ylabel(r'Relative red. $\chi^2$ change')
ax.set_xlabel('x')
ax.legend()
Plot the influence on the parameter value and error of each point:
axs[1].plot(x, best_vals['b'])
axs[1].scatter(x[idx], best_vals['b'][idx], color='r', label='outlier')
axs[1].set_ylabel('best b')
axs[2].plot(x, stderrs['a'])
axs[2].scatter(x[idx], stderrs['a'][idx], color='r', label='outlier')
axs[2].set_ylabel('err a change')
axs[3].plot(x, stderrs['b'])
axs[3].scatter(x[idx], stderrs['b'][idx], color='r', label='outlier')
axs[3].set_ylabel('err b change')
axs[3].set_xlabel('x')
import corner
import matplotlib.pyplot as plt
import numpy as np
import lmfit
model = lmfit.Model(double_exp)
Generate some fake data from the model with added noise:
Fit the model using a traditional minimizer, and show the output:
lmfit.report_fit(result)
result.plot()
[[Fit Statistics]]
# fitting method = Nelder-Mead
# function evals = 609
# data points = 250
# variables = 4
chi-square = 2.33333982
reduced chi-square = 0.00948512
Akaike info crit = -1160.54007
Bayesian info crit = -1146.45423
R-squared = 0.94237407
[[Variables]]
a1: 2.98623689 +/- 0.15010519 (5.03%) (init = 4)
t1: 1.30993186 +/- 0.13449653 (10.27%) (init = 3)
a2: -4.33525597 +/- 0.11765821 (2.71%) (init = 4)
(continues on next page)
lmfit.report_fit(result_emcee)
[[Fit Statistics]]
# fitting method = emcee
# function evals = 500000
# data points = 250
# variables = 5
chi-square = 245.221790
reduced chi-square = 1.00090526
Akaike info crit = 5.17553688
Bayesian info crit = 22.7828415
R-squared = -5.05618323
[[Variables]]
a1: 2.99546858 +/- 0.14834594 (4.95%) (init = 2.986237)
t1: 1.32127391 +/- 0.14079400 (10.66%) (init = 1.309932)
a2: -4.34376940 +/- 0.12389335 (2.85%) (init = -4.335256)
t2: 11.7937607 +/- 0.48879633 (4.14%) (init = 11.82408)
__lnsigma: -2.32712371 +/- 0.04514314 (1.94%) (init = -2.302585)
[[Correlations]] (unreported correlations are < 0.100)
C(a2, t2) = +0.9810
C(t1, a2) = -0.9367
C(t1, t2) = -0.8949
C(a1, t1) = -0.5154
C(a1, a2) = +0.2197
C(a1, t2) = +0.1868
result_emcee.plot_fit()
plt.plot(x, model.eval(params=result.params, x=x), '--', label='Nelder')
plt.legend()
plt.plot(result_emcee.acceptance_fraction, 'o')
plt.xlabel('walker')
plt.ylabel('acceptance fraction')
if hasattr(result_emcee, "acor"):
print("Autocorrelation time for the parameters:")
print("----------------------------------------")
for i, p in enumerate(result.params):
print(f'{p} = {result_emcee.acor[i]:.3f}')
highest_prob = np.argmax(result_emcee.lnprob)
hp_loc = np.unravel_index(highest_prob, result_emcee.lnprob.shape)
mle_soln = result_emcee.chain[hp_loc]
print("\nMaximum Likelihood Estimation (MLE):")
print('----------------------------------')
for ix, param in enumerate(emcee_params):
print(f"{param}: {mle_soln[ix]:.3f}")
This notebook shows how to fit the parameters of a complex resonator, using lmfit.Model and defining a custom Model
class.
Following Khalil et al. (https://arxiv.org/abs/1108.3117), we can model the forward transmission of a microwave
resonator with total quality factor 𝑄, coupling quality factor 𝑄𝑒 , and resonant frequency 𝑓0 using:
𝑄𝑄−1
𝑒
𝑆21 (𝑓 ) = 1 −
1 + 2𝑗𝑄(𝑓 − 𝑓0 )/𝑓0
import lmfit
Since scipy.optimize and lmfit require real parameters, we represent 𝑄𝑒 as Q_e_real + 1j*Q_e_imag.
class ResonatorModel(lmfit.model.Model):
__doc__ = "resonator model" + lmfit.models.COMMON_INIT_DOC
params[f'{self.prefix}Q'].set(min=Q_min, max=Q_max)
params[f'{self.prefix}f_0'].set(min=fmin, max=fmax)
return lmfit.models.update_param_vals(params, self.prefix, **kwargs)
resonator = ResonatorModel()
true_params = resonator.make_params(f_0=100, Q=10000, Q_e_real=9000, Q_e_imag=-9000)
plt.plot(f, 20*np.log10(np.abs(measured_s21)))
plt.ylabel('|S21| (dB)')
plt.xlabel('MHz')
plt.title('simulated measurement')
And now fit the data using the guess-ed values as a starting point:
print(result.fit_report() + '\n')
result.params.pretty_print()
[[Model]]
Model(linear_resonator)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 41
# data points = 200
# variables = 4
chi-square = 0.08533642
reduced chi-square = 4.3539e-04
Akaike info crit = -1543.89425
Bayesian info crit = -1530.70099
R-squared = -8.5336e+13
[[Variables]]
f_0: 100.000096 +/- 7.0309e-05 (0.00%) (init = 100.0035)
Q: 10059.4972 +/- 142.294636 (1.41%) (init = 3146.538)
Q_e_real: 9180.62017 +/- 133.777681 (1.46%) (init = 5082.247)
Q_e_imag: -9137.03667 +/- 133.769692 (1.46%) (init = 0)
[[Correlations]] (unreported correlations are < 0.100)
C(Q, Q_e_real) = +0.5175
C(f_0, Q_e_imag) = +0.5175
C(f_0, Q_e_real) = +0.5151
C(Q, Q_e_imag) = -0.5150
Now we’ll make some plots of the data and fit. Define a convenience function for plotting complex quantities:
plt.figure()
plot_ri(measured_s21, '.')
plot_ri(fit_s21, '.-', label='best fit')
plot_ri(guess_s21, '--', label='initial fit')
plt.legend()
plt.xlabel('Re(S21)')
plt.ylabel('Im(S21)')
plt.figure()
plt.plot(f, 20*np.log10(np.abs(measured_s21)), '.')
(continues on next page)
•
Total running time of the script: ( 0 minutes 0.736 seconds)
FIXME: this is a useful example; however, it doesn’t run correctly anymore as the PTSampler was removed in emcee
v3. . .
lmfit.emcee can be used to obtain the posterior probability distribution of parameters, given a set of experimental data.
This notebook shows how it can be used for Bayesian model selection.
import lmfit
x = np.linspace(3, 7, 250)
np.random.seed(0)
y = 4 + 10 * x + gauss(x, 200, 5, 0.5) + gauss(x, 60, 5.8, 0.2)
(continues on next page)
plt.errorbar(x, y)
if just_generative:
return generative
return (generative - y) / dy
def initial_peak_params(M):
p = lmfit.Parameters()
# a_max, loc and sd are the amplitude, location and SD of each Gaussian
# component
a_max = np.max(y)
loc = np.mean(x)
sd = (np.max(x) - np.min(x)) * 0.5
for i in range(M):
p.add_many((f'a_max{i}', 0.5 * a_max, True, 10, a_max),
(f'loc{i}', loc, True, np.min(x), np.max(x)),
(f'sd{i}', sd, True, 0.1, np.max(x) - np.min(x)))
return p
p1 = initial_peak_params(1)
mi1 = lmfit.minimize(residual, p1, method='differential_evolution')
lmfit.printfuncs.report_fit(mi1.params, min_correl=0.5)
From inspection of the data above we can tell that there is going to be more than 1 Gaussian component, but how
many are there? A Bayesian approach can be used for this model selection problem. We can do this with lmfit.emcee,
which uses the emcee package to do a Markov Chain Monte Carlo sampling of the posterior probability distribution.
lmfit.emcee requires a function that returns the log-posterior probability. The log-posterior probability is a sum of the
log-prior probability and log-likelihood functions.
The log-prior probability encodes information about what you already believe about the system. lmfit.emcee assumes
that this log-prior probability is zero if all the parameters are within their bounds and -np.inf if any of the parameters
are outside their bounds. As such it’s a uniform prior.
The log-likelihood function is given below. To use non-uniform priors then should include these terms in lnprob. This
is the log-likelihood probability for the sampling.
def lnprob(p):
resid = residual(p, just_generative=True)
return -0.5 * np.sum(((resid - y) / dy)**2 + np.log(2 * np.pi * dy**2))
To start with we have to create the minimizers and burn them in. We create 4 different minimizers representing 0, 1, 2
or 3 Gaussian contributions. To do the model selection we have to integrate the over the log-posterior distribution to
see which has the higher probability. This is done using the thermodynamic_integration_log_evidence method of the
sampler attribute contained in the lmfit.Minimizer object.
mini = []
# burn in the samplers
for i in range(4):
# do the sampling
mini.append(lmfit.Minimizer(lnprob, res[i].params))
out = mini[i].emcee(steps=total_steps, ntemps=ntemps, workers=workers,
reuse_sampler=False, float_behavior='posterior',
progress=False)
# get the evidence
print(i, total_steps, mini[i].sampler.thermodynamic_integration_log_evidence())
log_evidence.append(mini[i].sampler.thermodynamic_integration_log_evidence()[0])
Once we’ve burned in the samplers we have to do a collection run. We thin out the MCMC chain to reduce autocorre-
lation between successive samples.
for j in range(6):
total_steps += 100
(continues on next page)
plt.plot(log_evidence[-4:])
plt.ylabel('Log-evidence')
plt.xlabel('number of peaks')
The Bayes factor is related to the exponential of the difference between the log-evidence values. Thus, 0 peaks is not
very likely compared to 1 peak. But 1 peak is not as good as 2 peaks. 3 peaks is not that much better than 2 peaks.
These numbers tell us that zero peaks is 0 times as likely as one peak. Two peaks is 7e49 times more likely than one
peak. Three peaks is 1.1 times more likely than two peaks. With this data one would say that two peaks is sufficient.
Caution has to be taken with these values. The log-priors for this sampling are uniform but improper, i.e. they are not
normalised properly. Internally the lnprior probability is calculated as 0 if all parameters are within their bounds and -
np.inf if any parameter is outside the bounds. The lnprob function defined above is the log-likelihood alone. Remember,
that the log-posterior probability is equal to the sum of the log-prior and log-likelihood probabilities. Extra terms can
be added to the lnprob function to calculate the normalised log-probability. These terms would look something like:
∏︁ 1
log( )
𝑖
𝑚𝑎𝑥𝑖 − 𝑚𝑖𝑛𝑖
where 𝑚𝑎𝑥𝑖 and 𝑚𝑖𝑛𝑖 are the upper and lower bounds for the parameter, and the prior is a uniform distribution. Other
types of prior are possible. For example, you might expect the prior to be Gaussian.
Total running time of the script: ( 0 minutes 0.000 seconds)
Define the residual function, specify “true” parameter values, and generate a synthetic data set with some noise:
Set-up the minimizer and perform the fit using leastsq algorithm, and show the report:
fit = residual(out.params, x)
report_fit(out)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 95
# data points = 2500
# variables = 4
chi-square = 1277.24638
reduced chi-square = 0.51171730
Akaike info crit = -1670.96059
Bayesian info crit = -1647.66441
[[Variables]]
amp: 14.0708269 +/- 0.04936878 (0.35%) (init = 13)
period: 5.32980958 +/- 0.00273143 (0.05%) (init = 2)
shift: 0.12156317 +/- 0.00482312 (3.97%) (init = 0)
decay: 0.01002489 +/- 4.0726e-05 (0.41%) (init = 0.02)
[[Correlations]] (unreported correlations are < 0.100)
C(period, shift) = +0.8002
C(amp, decay) = +0.5758
Calculate the confidence intervals for parameters and display the results:
report_ci(ci)
if j > 0:
plt.setp(ax.get_yticklabels(), visible=False)
else:
ax.set_ylabel(fixed)
res = tr[fixed]
prob = res['prob']
f = prob < 0.96
x, y = res[free], res[fixed]
ax.scatter(x[f], y[f], c=1-prob[f], s=25*(1-prob[f]+0.5))
ax.autoscale(1, 1)
j += 1
i += 1
It is also possible to calculate the confidence regions for two fixed parameters using the function conf_interval2d:
names = list(out.params.keys())
plt.figure()
for i in range(4):
for j in range(4):
indx = 16-j*4-i
ax = plt.subplot(4, 4, indx)
ax.ticklabel_format(style='sci', scilimits=(-2, 2), axis='y')
if i != j:
x, y, m = conf_interval2d(mini, out, names[i], names[j], 20, 20)
plt.contourf(x, y, m, linspace(0, 1, 10))
x = tr[names[i]][names[i]]
y = tr[names[i]][names[j]]
pr = tr[names[i]]['prob']
s = argsort(x)
plt.scatter(x[s], y[s], c=pr[s], s=30, lw=1)
else:
x = tr[names[i]][names[i]]
y = tr[names[i]]['prob']
t, s = unique(x, True)
f = interp1d(t, y[s], 'slinear')
xn = linspace(x.min(), x.max(), 50)
plt.plot(xn, f(xn), lw=1)
plt.ylabel('prob')
ax.tick_params(labelleft=True)
plt.tight_layout()
plt.show()
import lmfit
from lmfit.lineshapes import gaussian2d, lorentzian
We start by considering a simple two-dimensional gaussian function, which depends on coordinates (x, y). The most
general case of experimental data will be irregularly sampled and noisy. Let’s simulate some:
npoints = 10000
np.random.seed(2021)
x = np.random.rand(npoints)*10 - 4
y = np.random.rand(npoints)*5 - 3
z = gaussian2d(x, y, amplitude=30, centerx=2, centery=-.5, sigmax=.6, sigmay=.8)
z += 2*(np.random.rand(*z.shape)-.5)
error = np.sqrt(z+1)
fig, ax = plt.subplots()
art = ax.pcolor(X, Y, Z, shading='auto')
plt.colorbar(art, ax=ax, label='z')
ax.set_xlabel('x')
ax.set_ylabel('y')
plt.show()
model = lmfit.models.Gaussian2dModel()
params = model.guess(z, x, y)
result = model.fit(z, x=x, y=y, params=params, weights=1/error)
lmfit.report_fit(result)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 87
# data points = 10000
# variables = 5
chi-square = 20618.1774
reduced chi-square = 2.06284916
Akaike info crit = 7245.87992
Bayesian info crit = 7281.93162
R-squared = 0.28378389
[[Variables]]
amplitude: 27.4195833 +/- 0.65062974 (2.37%) (init = 16.51399)
centerx: 1.99705425 +/- 0.01405864 (0.70%) (init = 1.940764)
centery: -0.49516158 +/- 0.01907800 (3.85%) (init = -0.5178641)
sigmax: 0.54740777 +/- 0.01224965 (2.24%) (init = 1.666582)
sigmay: 0.73300589 +/- 0.01617042 (2.21%) (init = 0.8332836)
(continues on next page)
To check the fit, we can evaluate the function on the same grid we used before and make plots of the data, the fit and
the difference between the two.
ax = axs[0, 0]
art = ax.pcolor(X, Y, Z, vmin=0, vmax=vmax, shading='auto')
plt.colorbar(art, ax=ax, label='z')
ax.set_title('Data')
ax = axs[0, 1]
fit = model.func(X, Y, **result.best_values)
art = ax.pcolor(X, Y, fit, vmin=0, vmax=vmax, shading='auto')
plt.colorbar(art, ax=ax, label='z')
ax.set_title('Fit')
ax = axs[1, 0]
fit = model.func(X, Y, **result.best_values)
art = ax.pcolor(X, Y, Z-fit, vmin=0, vmax=10, shading='auto')
plt.colorbar(art, ax=ax, label='z')
ax.set_title('Data - Fit')
for ax in axs.ravel():
ax.set_xlabel('x')
ax.set_ylabel('y')
axs[1, 1].remove()
plt.show()
We now go on to show a harder example, in which the peak has a Lorentzian profile and an off-axis anisotropic shape.
This can be handled by applying a suitable coordinate transform and then using the lorentzian function that lmfit
provides in the lineshapes module.
return 2*amplitude*lorentzian(R)/(np.pi*sigmax*sigmay)
Data can be simulated and plotted in the same way as we did before.
npoints = 10000
x = np.random.rand(npoints)*10 - 4
y = np.random.rand(npoints)*5 - 3
z = lorentzian2d(x, y, amplitude=30, centerx=2, centery=-.5, sigmax=.6,
sigmay=1.2, rotation=30*np.pi/180)
z += 2*(np.random.rand(*z.shape)-.5)
error = np.sqrt(z+1)
fig, ax = plt.subplots()
ax.set_xlabel('x')
ax.set_ylabel('y')
art = ax.pcolor(X, Y, Z, shading='auto')
plt.colorbar(art, ax=ax, label='z')
plt.show()
To fit, create a model from the function. Don’t forget to tell lmfit that both x and y are independent variables. Keep
in mind that lmfit will take the function keywords as default initial guesses in this case and that it will not know that
certain parameters only make physical sense over restricted ranges. For example, peak widths should be positive and
the rotation can be restricted over a quarter circle.
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 73
# data points = 10000
# variables = 6
chi-square = 11287.3823
reduced chi-square = 1.12941588
Akaike info crit = 1223.00402
(continues on next page)
ax = axs[0, 0]
art = ax.pcolor(X, Y, Z, vmin=0, vmax=vmax, shading='auto')
plt.colorbar(art, ax=ax, label='z')
ax.set_title('Data')
ax = axs[0, 1]
fit = model.func(X, Y, **result.best_values)
art = ax.pcolor(X, Y, fit, vmin=0, vmax=vmax, shading='auto')
plt.colorbar(art, ax=ax, label='z')
ax.set_title('Fit')
ax = axs[1, 0]
fit = model.func(X, Y, **result.best_values)
art = ax.pcolor(X, Y, Z-fit, vmin=0, vmax=10, shading='auto')
plt.colorbar(art, ax=ax, label='z')
ax.set_title('Data - Fit')
for ax in axs.ravel():
ax.set_xlabel('x')
ax.set_ylabel('y')
axs[1, 1].remove()
plt.show()
13.18 Global minimization using the brute method (a.k.a. grid search)
This notebook shows a simple example of using lmfit.minimize.brute that uses the method with the same name
from scipy.optimize.
The method computes the function’s value at each point of a multidimensional grid of points, to find the global minimum
of the function. It behaves identically to scipy.optimize.brute in case finite bounds are given on all varying
parameters, but will also deal with non-bounded parameters (see below).
13.18. Global minimization using the brute method (a.k.a. grid search) 233
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
import copy
def f1(p):
par = p.valuesdict()
return (par['a'] * par['x']**2 + par['b'] * par['x'] * par['y'] +
par['c'] * par['y']**2 + par['d']*par['x'] + par['e']*par['y'] +
par['f'])
def f2(p):
par = p.valuesdict()
return (-1.0*par['g']*np.exp(-((par['x']-par['h'])**2 +
(par['y']-par['i'])**2) / par['scale']))
def f3(p):
par = p.valuesdict()
return (-1.0*par['j']*np.exp(-((par['x']-par['k'])**2 +
(par['y']-par['l'])**2) / par['scale']))
(continues on next page)
def f(params):
return f1(params) + f2(params) + f3(params)
, which will increment x and y between -4 in increments of 0.25 until 4 (not inclusive).
[-4. -3.75 -3.5 -3.25 -3. -2.75 -2.5 -2.25 -2. -1.75 -1.5 -1.25
-1. -0.75 -0.5 -0.25 0. 0.25 0.5 0.75 1. 1.25 1.5 1.75
2. 2.25 2.5 2.75 3. 3.25 3.5 3.75]
The objective function is evaluated on this grid, and the raw output from scipy.optimize.brute is stored in the
MinimizerResult as brute_<parname> attributes. These attributes are:
result.brute_x0 – A 1-D array containing the coordinates of a point at which the objective function had its minimum
value.
print(result.brute_x0)
[-1. 1.75]
print(result.brute_fval)
-2.8923637137222027
result.brute_grid – Representation of the evaluation grid. It has the same length as x0.
print(result.brute_grid)
13.18. Global minimization using the brute method (a.k.a. grid search) 235
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
result.brute_Jout – Function values at each point of the evaluation grid, i.e., Jout = func(*grid).
print(result.brute_Jout)
Reassuringly, the obtained results are identical to using the method in SciPy directly!
Example 2: fit of a decaying sine wave
In this example, we will explain some of the options of the algorithm.
We start off by generating some synthetic data with noise for a decaying sine wave, define an objective function, and
create/initialize a Parameter set.
In contrast to the implementation in SciPy (as shown in the first example), varying parameters do not need to have
finite bounds in lmfit. However, if a parameter does not have finite bounds, then it does need a brute_step attribute
specified:
Our initial parameter set is now defined as shown below and this will determine how the grid is set-up.
params.pretty_print()
13.18. Global minimization using the brute method (a.k.a. grid search) 237
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
print(fit_report(result_brute))
[[Fit Statistics]]
# fitting method = brute
# function evals = 375000
# data points = 301
# variables = 4
chi-square = 11.9353671
reduced chi-square = 0.04018642
Akaike info crit = -963.508878
Bayesian info crit = -948.680437
## Warning: uncertainties could not be estimated:
[[Variables]]
amp: 5.00000000 (init = 7)
decay: 0.02500000 (init = 0.05)
shift: -0.13089969 (init = 0)
omega: 2.00000000 (init = 3)
We used two new parameters here: Ns and keep. The parameter Ns determines the 'number of grid points along the
axes' similarly to its usage in SciPy. Together with brute_step, min and max for a Parameter it will dictate how the
grid is set-up:
(1) finite bounds are specified (“SciPy implementation”): uses brute_step if present (in the example above) or uses
Ns to generate the grid. The latter scenario that interpolates Ns points from min to max (inclusive), is here shown for
the parameter shift:
par_name = 'shift'
indx_shift = result_brute.var_names.index(par_name)
grid_shift = np.unique(result_brute.brute_grid[indx_shift].ravel())
print(f"parameter = {par_name}\nnumber of steps = {len(grid_shift)}\ngrid = {grid_shift}
˓→")
parameter = shift
number of steps = 25
grid = [-1.57079633 -1.43989663 -1.30899694 -1.17809725 -1.04719755 -0.91629786
-0.78539816 -0.65449847 -0.52359878 -0.39269908 -0.26179939 -0.13089969
0. 0.13089969 0.26179939 0.39269908 0.52359878 0.65449847
0.78539816 0.91629786 1.04719755 1.17809725 1.30899694 1.43989663
1.57079633]
If finite bounds are not set for a certain parameter then the user must specify brute_step - three more scenarios are
considered here:
(2) lower bound (min) and brute_step are specified: range = (min, min + Ns * brute_step, brute_step)
par_name = 'amp'
indx_shift = result_brute.var_names.index(par_name)
grid_shift = np.unique(result_brute.brute_grid[indx_shift].ravel())
print(f"parameter = {par_name}\nnumber of steps = {len(grid_shift)}\ngrid = {grid_shift}
˓→")
parameter = amp
number of steps = 25
grid = [2.5 2.75 3. 3.25 3.5 3.75 4. 4.25 4.5 4.75 5. 5.25 5.5 5.75
6. 6.25 6.5 6.75 7. 7.25 7.5 7.75 8. 8.25 8.5 ]
(3) upper bound (max) and brute_step are specified: range = (max - Ns * brute_step, max, brute_step)
par_name = 'omega'
indx_shift = result_brute.var_names.index(par_name)
grid_shift = np.unique(result_brute.brute_grid[indx_shift].ravel())
print(f"parameter = {par_name}\nnumber of steps = {len(grid_shift)}\ngrid = {grid_shift}
˓→")
parameter = omega
number of steps = 25
grid = [-1.25 -1. -0.75 -0.5 -0.25 0. 0.25 0.5 0.75 1. 1.25 1.5
1.75 2. 2.25 2.5 2.75 3. 3.25 3.5 3.75 4. 4.25 4.5
4.75]
(4) numerical value (value) and brute_step are specified: range = (value - (Ns//2) * brute_step, value
+ (Ns//2) * brute_step, brute_step)
par_name = 'decay'
indx_shift = result_brute.var_names.index(par_name)
grid_shift = np.unique(result_brute.brute_grid[indx_shift].ravel())
print(f"parameter = {par_name}\nnumber of steps = {len(grid_shift)}\ngrid = {grid_shift}
˓→")
parameter = decay
number of steps = 24
grid = [-1.00000000e-02 -5.00000000e-03 5.20417043e-18 5.00000000e-03
1.00000000e-02 1.50000000e-02 2.00000000e-02 2.50000000e-02
3.00000000e-02 3.50000000e-02 4.00000000e-02 4.50000000e-02
5.00000000e-02 5.50000000e-02 6.00000000e-02 6.50000000e-02
7.00000000e-02 7.50000000e-02 8.00000000e-02 8.50000000e-02
9.00000000e-02 9.50000000e-02 1.00000000e-01 1.05000000e-01]
The MinimizerResult contains all the usual best-fit parameters and fitting statistics. For example, the optimal solution
from the grid search is given below together with a plot:
print(fit_report(result_brute))
[[Fit Statistics]]
# fitting method = brute
# function evals = 375000
# data points = 301
# variables = 4
chi-square = 11.9353671
reduced chi-square = 0.04018642
Akaike info crit = -963.508878
Bayesian info crit = -948.680437
## Warning: uncertainties could not be estimated:
(continues on next page)
13.18. Global minimization using the brute method (a.k.a. grid search) 239
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
We can see that this fit is already very good, which is what we should expect since our brute force grid is sampled
rather finely and encompasses the “correct” values.
In a more realistic, complicated example the brute method will be used to get reasonable values for the parameters and
perform another minimization (e.g., using leastsq) using those as starting values. That is where the keep parameter
comes into play: it determines the “number of best candidates from the brute force method that are stored in the
candidates attribute”. In the example above we store the best-ranking 25 solutions (the default value is 50 and
storing all the grid points can be accomplished by choosing all). The candidates attribute contains the parameters
and chisqr from the brute force method as a namedtuple, (‘Candidate’, [‘params’, ‘score’]), sorted on the
(lowest) chisqr value. To access the values for a particular candidate one can use result.candidate[#].params
or result.candidate[#].score, where a lower # represents a better candidate. The show_candidates(#) uses
the pretty_print() method to show a specific candidate-# or all candidates when no number is specified.
The optimal fit is, as usual, stored in the MinimizerResult.params attribute and is, therefore, identical to
result_brute.show_candidates(1).
result_brute.show_candidates(1)
In this case, the next-best scoring candidate has already a chisqr that increased quite a bit:
result_brute.show_candidates(2)
and is, therefore, probably not so likely. . . However, as said above, in most cases you’ll want to do another minimization
using the solutions from the brute method as starting values. That can be easily accomplished as shown in the code
below, where we now perform a leastsq minimization starting from the top-25 solutions and accept the solution if
the chisqr is lower than the previously ‘optimal’ solution:
best_result = copy.deepcopy(result_brute)
From the leastsq minimization we obtain the following parameters for the most optimal result:
print(fit_report(best_result))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 21
# data points = 301
# variables = 4
chi-square = 10.8653514
reduced chi-square = 0.03658367
Akaike info crit = -991.780924
Bayesian info crit = -976.952483
[[Variables]]
amp: 5.00323085 +/- 0.03805940 (0.76%) (init = 5)
decay: 0.02563850 +/- 4.4572e-04 (1.74%) (init = 0.03)
shift: -0.09162987 +/- 0.00978382 (10.68%) (init = 0)
omega: 1.99611629 +/- 0.00316225 (0.16%) (init = 2)
[[Correlations]] (unreported correlations are < 0.100)
(continues on next page)
13.18. Global minimization using the brute method (a.k.a. grid search) 241
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
As expected the parameters have not changed significantly as they were already very close to the “real” values, which
can also be appreciated from the plots below.
Finally, the results from the brute force grid-search can be visualized using the rather lengthy Python function below
(which might get incorporated in lmfit at some point).
The output file will display the chi-square value per parameter and contour
plots for all combination of two parameters.
(continues on next page)
Parameters
----------
result : :class:`~lmfit.minimizer.MinimizerResult`
Contains the results from the :meth:`brute` method.
if not varlabels:
varlabels = result.var_names
if best_vals and isinstance(best_vals, bool):
best_vals = result.params
13.18. Global minimization using the brute method (a.k.a. grid search) 243
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
13.18. Global minimization using the brute method (a.k.a. grid search) 245
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
FOURTEEN
Below are all the examples that are part of the lmfit documentation.
Below are all the examples that are part of the lmfit documentation.
14.1.1 doc_model_savemodel.py
# <examples/doc_model_savemodel.py>
import numpy as np
sinemodel = Model(mysine)
pars = sinemodel.make_params(amp=1, freq=0.25, shift=0)
save_model(sinemodel, 'sinemodel.sav')
# <end examples/doc_model_savemodel.py>
14.1.2 doc_model_savemodelresult.py
[[Model]]
Model(gaussian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 33
# data points = 101
# variables = 3
chi-square = 3.40883599
(continues on next page)
247
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
# <examples/doc_model_savemodelresult.py>
import numpy as np
data = np.loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
gmodel = GaussianModel()
result = gmodel.fit(y, x=x, amplitude=5, center=5, sigma=1)
save_modelresult(result, 'gauss_modelresult.sav')
print(result.fit_report())
# <end examples/doc_model_savemodelresult.py>
14.1.3 doc_confidence_basic.py
[[Variables]]
a: 0.09943896 +/- 1.9322e-04 (0.19%) (init = 0.1)
b: 1.98476942 +/- 0.01222678 (0.62%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(a, b) = +0.6008
99.73% 95.45% 68.27% _BEST_ 68.27% 95.45% 99.73%
a: -0.00059 -0.00039 -0.00019 0.09944 +0.00019 +0.00039 +0.00060
b: -0.03764 -0.02477 -0.01229 1.98477 +0.01229 +0.02477 +0.03764
# <examples/doc_confidence_basic.py>
import numpy as np
import lmfit
def residual(p):
return 1/(p['a']*x) + p['b'] - y
print(lmfit.fit_report(result.params))
ci = lmfit.conf_interval(mini, result)
lmfit.printfuncs.report_ci(ci)
# <end examples/doc_confidence_basic.py>
14.1.4 doc_model_loadmodelresult.py
[[Model]]
Model(gaussian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 33
# data points = 101
# variables = 3
chi-square = 3.40883599
reduced chi-square = 0.03478404
Akaike info crit = -336.263713
Bayesian info crit = -328.418352
R-squared = 0.98533348
[[Variables]]
amplitude: 8.88021907 +/- 0.11359530 (1.28%) (init = 5)
center: 5.65866105 +/- 0.01030493 (0.18%) (init = 5)
sigma: 0.69765480 +/- 0.01030508 (1.48%) (init = 1)
fwhm: 1.64285148 +/- 0.02426660 (1.48%) == '2.3548200*sigma'
height: 5.07800563 +/- 0.06495769 (1.28%) == '0.3989423*amplitude/max(1e-15,␣
˓→sigma)'
# <examples/doc_model_loadmodelresult.py>
import os
import sys
if not os.path.exists('gauss_modelresult.sav'):
os.system(f"{sys.executable} doc_model_savemodelresult.py")
data = np.loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
result = load_modelresult('gauss_modelresult.sav')
print(result.fit_report())
plt.plot(x, y, 'o')
plt.plot(x, result.best_fit, '-')
plt.show()
# <end examples/doc_model_loadmodelresult.py>
14.1.5 doc_model_loadmodelresult2.py
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='exp_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 46
# data points = 250
# variables = 8
chi-square = 1247.52821
reduced chi-square = 5.15507524
Akaike info crit = 417.864631
Bayesian info crit = 446.036318
R-squared = 0.99648654
[[Variables]]
exp_amplitude: 99.0183278 +/- 0.53748593 (0.54%) (init = 162.2102)
exp_decay: 90.9508853 +/- 1.10310778 (1.21%) (init = 93.24905)
g1_amplitude: 4257.77360 +/- 42.3836478 (1.00%) (init = 2000)
g1_center: 107.030956 +/- 0.15006851 (0.14%) (init = 105)
g1_sigma: 16.6725772 +/- 0.16048381 (0.96%) (init = 15)
g1_fwhm: 39.2609181 +/- 0.37791049 (0.96%) == '2.3548200*g1_sigma'
g1_height: 101.880230 +/- 0.59217173 (0.58%) == '0.3989423*g1_amplitude/max(1e-
(continues on next page)
# <examples/doc_model_loadmodelresult2.py>
import os
import sys
if not os.path.exists('nistgauss_modelresult.sav'):
os.system(f"{sys.executable} doc_model_savemodelresult2.py")
dat = np.loadtxt('NIST_Gauss2.dat')
(continues on next page)
result = load_modelresult('nistgauss_modelresult.sav')
print(result.fit_report())
plt.plot(x, y, 'o')
plt.plot(x, result.best_fit, '-')
plt.show()
# <end examples/doc_model_loadmodelresult2.py>
14.1.6 doc_model_gaussian.py
[[Model]]
Model(gaussian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 33
# data points = 101
(continues on next page)
# <examples/doc_model_gaussian.py>
import matplotlib.pyplot as plt
from numpy import exp, loadtxt, pi, sqrt
data = loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
gmodel = Model(gaussian)
result = gmodel.fit(y, x=x, amp=5, cen=5, wid=1)
print(result.fit_report())
plt.plot(x, y, 'o')
plt.plot(x, result.init_fit, '--', label='initial fit')
plt.plot(x, result.best_fit, '-', label='best fit')
plt.legend()
plt.show()
# <end examples/doc_model_gaussian.py>
14.1.7 doc_model_loadmodel.py
[[Model]]
Model(mysine)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 25
# data points = 101
# variables = 3
chi-square = 7.68903767
reduced chi-square = 0.07845957
Akaike info crit = -254.107813
Bayesian info crit = -246.262451
R-squared = 0.97252133
[[Variables]]
amp: 2.32733694 +/- 0.03950824 (1.70%) (init = 3)
freq: 0.50098739 +/- 5.7726e-04 (0.12%) (init = 0.52)
shift: 0.53605324 +/- 0.03383110 (6.31%) (init = 0)
[[Correlations]] (unreported correlations are < 0.100)
C(freq, shift) = -0.8663
# <examples/doc_model_loadmodel.py>
import os
import sys
if not os.path.exists('sinemodel.sav'):
os.system(f"{sys.executable} doc_model_savemodel.py")
data = np.loadtxt('sinedata.dat')
x = data[:, 0]
y = data[:, 1]
plt.plot(x, y, 'o')
plt.plot(x, result.best_fit, '-')
plt.show()
# <end examples/doc_model_loadmodel.py>
14.1.8 doc_model_with_nan_policy.py
[[Model]]
Model(gaussian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 22
# data points = 99
# variables = 3
chi-square = 3.27990355
reduced chi-square = 0.03416566
Akaike info crit = -331.323278
Bayesian info crit = -323.537918
R-squared = 0.98570688
[[Variables]]
amplitude: 8.82064881 +/- 0.11686114 (1.32%) (init = 5)
center: 5.65906365 +/- 0.01055590 (0.19%) (init = 6)
sigma: 0.69165307 +/- 0.01060640 (1.53%) (init = 1)
fwhm: 1.62871849 +/- 0.02497615 (1.53%) == '2.3548200*sigma'
height: 5.08770952 +/- 0.06488251 (1.28%) == '0.3989423*amplitude/max(1e-15,␣
˓→sigma)'
# <examples/doc_model_with_nan_policy.py>
import matplotlib.pyplot as plt
import numpy as np
data = np.loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
y[44] = np.nan
y[65] = np.nan
# nan_policy = 'raise'
# nan_policy = 'propagate'
nan_policy = 'omit'
gmodel = GaussianModel()
result = gmodel.fit(y, x=x, amplitude=5, center=6, sigma=1,
nan_policy=nan_policy)
print(result.fit_report())
14.1.9 doc_builtinmodels_stepmodel.py
[[Model]]
(Model(step, prefix='step_', form='erf') + Model(linear, prefix='line_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 55
# data points = 201
# variables = 5
chi-square = 593.709621
reduced chi-square = 3.02913072
Akaike info crit = 227.700173
Bayesian info crit = 244.216697
R-squared = 0.99897798
[[Variables]]
line_slope: 1.87162383 +/- 0.09318592 (4.98%) (init = 0)
line_intercept: 12.0964588 +/- 0.27606017 (2.28%) (init = 11.58574)
step_amplitude: 112.858576 +/- 0.65391731 (0.58%) (init = 134.7378)
step_center: 3.13494787 +/- 0.00516602 (0.16%) (init = 2.5)
step_sigma: 0.67393440 +/- 0.01091158 (1.62%) (init = 1.428571)
[[Correlations]] (unreported correlations are < 0.100)
C(line_slope, step_amplitude) = -0.8791
C(step_amplitude, step_sigma) = +0.5643
(continues on next page)
# <examples/doc_builtinmodels_stepmodel.py>
import matplotlib.pyplot as plt
import numpy as np
print(out.fit_report())
plt.plot(x, y)
plt.plot(x, out.init_fit, '--', label='initial fit')
plt.plot(x, out.best_fit, '-', label='best fit')
plt.legend()
plt.show()
# <end examples/doc_builtinmodels_stepmodel.py>
14.1.10 doc_model_uncertainty.py
[[Model]]
Model(gaussian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 33
# data points = 101
# variables = 3
chi-square = 3.40883599
reduced chi-square = 0.03478404
Akaike info crit = -336.263713
Bayesian info crit = -328.418352
R-squared = 0.98533348
[[Variables]]
amp: 8.88021893 +/- 0.11359522 (1.28%) (init = 5)
cen: 5.65866102 +/- 0.01030495 (0.18%) (init = 5)
wid: 0.69765478 +/- 0.01030505 (1.48%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(amp, wid) = +0.5774
# <examples/doc_model_uncertainty.py>
import matplotlib.pyplot as plt
from numpy import exp, loadtxt, pi, sqrt
data = loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1]
gmodel = Model(gaussian)
result = gmodel.fit(y, x=x, amp=5, cen=5, wid=1)
print(result.fit_report())
dely = result.eval_uncertainty(sigma=3)
plt.plot(x, y, 'o')
plt.plot(x, result.init_fit, '--', label='initial fit')
plt.plot(x, result.best_fit, '-', label='best fit')
plt.fill_between(x, result.best_fit-dely, result.best_fit+dely,
color="#ABABAB", label=r'3-$\sigma$ uncertainty band')
plt.legend()
plt.show()
# <end examples/doc_model_uncertainty.py>
14.1.11 doc_model_two_components.py
[[Model]]
(Model(gaussian) + Model(line))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 55
# data points = 101
# variables = 5
chi-square = 2.57855517
reduced chi-square = 0.02685995
Akaike info crit = -360.457020
Bayesian info crit = -347.381417
R-squared = 0.99194643
[[Variables]]
amp: 8.45930976 +/- 0.12414531 (1.47%) (init = 5)
cen: 5.65547889 +/- 0.00917673 (0.16%) (init = 5)
wid: 0.67545513 +/- 0.00991697 (1.47%) (init = 1)
slope: 0.26484403 +/- 0.00574892 (2.17%) (init = 0)
intercept: -0.96860189 +/- 0.03352202 (3.46%) (init = 1)
[[Correlations]] (unreported correlations are < 0.100)
C(slope, intercept) = -0.7954
C(amp, wid) = +0.6664
(continues on next page)
# <examples/doc_model_two_components.py>
import matplotlib.pyplot as plt
from numpy import exp, loadtxt, pi, sqrt
data = loadtxt('model1d_gauss.dat')
x = data[:, 0]
y = data[:, 1] + 0.25*x - 1.0
plt.plot(x, y, 'o')
plt.plot(x, result.init_fit, '--', label='initial fit')
plt.plot(x, result.best_fit, '-', label='best fit')
plt.legend()
plt.show()
# <end examples/doc_model_two_components.py>
14.1.12 doc_fitting_withreport.py
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 83
# data points = 1001
# variables = 4
chi-square = 498.811759
reduced chi-square = 0.50031270
Akaike info crit = -689.222517
Bayesian info crit = -669.587497
[[Variables]]
amp: 13.9121959 +/- 0.14120321 (1.01%) (init = 13)
period: 5.48507038 +/- 0.02666520 (0.49%) (init = 2)
shift: 0.16203673 +/- 0.01405662 (8.67%) (init = 0)
decay: 0.03264539 +/- 3.8015e-04 (1.16%) (init = 0.02)
[[Correlations]] (unreported correlations are < 0.100)
C(period, shift) = +0.7974
C(amp, decay) = +0.5816
C(amp, shift) = -0.2966
C(amp, period) = -0.2432
C(shift, decay) = -0.1819
C(period, decay) = -0.1496
# <examples/doc_fitting_withreport.py>
from numpy import exp, linspace, pi, random, sign, sin
print(fit_report(out))
# <end examples/doc_fitting_withreport.py>
14.1.13 doc_model_savemodelresult2.py
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='exp_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 46
# data points = 250
# variables = 8
chi-square = 1247.52821
reduced chi-square = 5.15507524
Akaike info crit = 417.864631
Bayesian info crit = 446.036318
R-squared = 0.99648654
[[Variables]]
exp_amplitude: 99.0183278 +/- 0.53748593 (0.54%) (init = 162.2102)
exp_decay: 90.9508853 +/- 1.10310778 (1.21%) (init = 93.24905)
g1_amplitude: 4257.77360 +/- 42.3836478 (1.00%) (init = 2000)
g1_center: 107.030956 +/- 0.15006851 (0.14%) (init = 105)
g1_sigma: 16.6725772 +/- 0.16048381 (0.96%) (init = 15)
g1_fwhm: 39.2609181 +/- 0.37791049 (0.96%) == '2.3548200*g1_sigma'
g1_height: 101.880230 +/- 0.59217173 (0.58%) == '0.3989423*g1_amplitude/max(1e-
˓→15, g1_sigma)'
# <examples/doc_model_savemodelresult2.py>
import numpy as np
dat = np.loadtxt('NIST_Gauss2.dat')
x = dat[:, 1]
y = dat[:, 0]
exp_mod = ExponentialModel(prefix='exp_')
pars = exp_mod.guess(y, x=x)
gauss1 = GaussianModel(prefix='g1_')
pars.update(gauss1.make_params(center=dict(value=105, min=75, max=125),
sigma=dict(value=15, min=0),
amplitude=dict(value=2000, min=0)))
gauss2 = GaussianModel(prefix='g2_')
pars.update(gauss2.make_params(center=dict(value=155, min=125, max=175),
sigma=dict(value=15, min=0),
amplitude=dict(value=2000, min=0)))
save_modelresult(result, 'nistgauss_modelresult.sav')
print(result.fit_report())
# <end examples/doc_model_savemodelresult2.py>
14.1.14 doc_builtinmodels_nistgauss2.py
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='exp_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 37
# data points = 250
# variables = 8
chi-square = 1247.52821
reduced chi-square = 5.15507524
(continues on next page)
# <examples/doc_nistgauss2.py>
import matplotlib.pyplot as plt
import numpy as np
dat = np.loadtxt('NIST_Gauss2.dat')
x = dat[:, 1]
y = dat[:, 0]
exp_mod = ExponentialModel(prefix='exp_')
gauss1 = GaussianModel(prefix='g1_')
gauss2 = GaussianModel(prefix='g2_')
print(out.fit_report(min_correl=0.5))
plt.plot(x, y)
plt.plot(x, out.init_fit, '--', label='initial fit')
plt.plot(x, out.best_fit, '-', label='best fit')
plt.legend()
plt.show()
# <end examples/doc_nistgauss2.py>
14.1.15 doc_model_with_iter_callback.py
˓→= 0.59841']
˓→= 0.59841']
˓→= 0.59842']
˓→= 0.59841']
˓→= 0.59841']
˓→= 0.59841']
˓→height = 1.69033']
˓→height = 1.69034']
˓→height = 1.69033']
˓→height = 1.69031']
˓→height = 1.69033']
˓→height = 1.69033']
˓→height = 1.52032']
˓→height = 0.58181']
˓→height = 0.58182']
˓→height = 0.58181']
˓→height = 0.58180']
˓→height = 0.58181']
˓→height = 0.58181']
˓→height = 0.63148']
˓→height = 0.63148']
˓→height = 0.63148']
˓→height = 0.63148']
˓→height = 0.63148']
˓→height = 64.66412']
˓→height = 0.66747']
˓→height = 0.66748']
˓→height = 0.66747']
˓→height = 0.66746']
˓→height = 0.66747']
˓→height = 0.66747']
˓→height = 0.93186']
˓→height = 0.93187']
˓→height = 0.93186']
˓→height = 0.93185']
˓→height = 0.93186']
˓→height = 0.93186']
˓→height = 0.93452']
˓→height = 0.93452']
˓→height = 0.93451']
˓→height = 0.93452']
˓→height = 0.93452']
˓→= 96.74096']
˓→height = 1.04095']
˓→height = 1.04096']
˓→height = 1.04095']
˓→height = 1.04094']
˓→height = 1.04095']
˓→height = 1.04095']
˓→height = 1.35839']
˓→height = 1.35840']
˓→height = 1.35839']
˓→height = 1.35837']
˓→height = 1.35839']
˓→height = 1.35839']
˓→height = 3.07960']
˓→height = 3.07957']
˓→height = 3.07953']
˓→height = 3.07957']
˓→height = 3.07957']
˓→= 3.62249']
˓→= 3.62253']
˓→= 3.62249']
˓→= 3.62245']
˓→= 3.62249']
˓→= 3.62249']
˓→= 0.33620']
˓→= 6.14155']
˓→= 6.14161']
˓→= 6.14155']
˓→= 6.14147']
˓→= 7.99252']
˓→= 7.99252']
˓→= 7.99214']
˓→= 7.99222']
˓→= 7.99214']
˓→= 7.99202']
˓→= 7.99214']
˓→height = 7.99214']
˓→height = 7.99214']
˓→height = 7.99214']
Nfev = 101
[[Model]]
(Model(gaussian, prefix='peak_') + Model(linear, prefix='bkg_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 101
# data points = 401
# variables = 5
chi-square = 20.0043556
reduced chi-square = 0.05051605
Akaike info crit = -1192.20257
Bayesian info crit = -1172.23276
R-squared = 0.99377421
[[Variables]]
peak_amplitude: 24.5237052 +/- 0.16281835 (0.66%) (init = 3)
peak_center: 7.63752785 +/- 0.00746969 (0.10%) (init = 6)
peak_sigma: 1.22414559 +/- 0.00811005 (0.66%) (init = 2)
bkg_slope: -0.20264093 +/- 0.00204346 (1.01%) (init = 0)
bkg_intercept: 3.36986054 +/- 0.02653942 (0.79%) (init = 0)
peak_fwhm: 2.88264251 +/- 0.01909771 (0.66%) == '2.3548200*peak_sigma'
peak_height: 7.99214038 +/- 0.04318559 (0.54%) == '0.3989423*peak_amplitude/
(continues on next page)
# <examples/doc_with_itercb.py>
import matplotlib.pyplot as plt
from numpy import linspace, random
plt.plot(x, y, '--')
print(f'Nfev = {out.nfev}')
print(out.fit_report())
14.1.16 doc_parameters_valuesdict.py
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 64
# data points = 301
# variables = 4
chi-square = 12.1867036
reduced chi-square = 0.04103267
Akaike info crit = -957.236198
Bayesian info crit = -942.407756
[[Variables]]
amp: 5.03088059 +/- 0.04005824 (0.80%) (init = 10)
decay: 0.02495457 +/- 4.5396e-04 (1.82%) (init = 0.1)
omega: 2.00026310 +/- 0.00326183 (0.16%) (init = 3)
shift: -0.10264952 +/- 0.01022294 (9.96%) (init = 0)
[[Correlations]] (unreported correlations are < 0.100)
C(omega, shift) = -0.7852
C(amp, decay) = +0.5840
C(amp, shift) = -0.1179
# <examples/doc_parameters_valuesdict.py>
import numpy as np
14.1.17 doc_builtinmodels_peakmodels.py
[[Model]]
Model(gaussian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 25
# data points = 401
# variables = 3
chi-square = 29.9943157
reduced chi-square = 0.07536260
Akaike info crit = -1033.77437
(continues on next page)
[[Correlations]]
+-----------+-----------+-----------+-----------+
| Variable | amplitude | center | sigma |
+-----------+-----------+-----------+-----------+
| amplitude | +1.0000 | -0.0000 | +0.5774 |
| center | -0.0000 | +1.0000 | -0.0000 |
| sigma | +0.5774 | -0.0000 | +1.0000 |
+-----------+-----------+-----------+-----------+
[[Model]]
Model(lorentzian)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 25
# data points = 401
# variables = 3
chi-square = 53.7535387
reduced chi-square = 0.13505914
Akaike info crit = -799.830322
Bayesian info crit = -787.848438
R-squared = 0.98289441
[[Variables]]
amplitude: 38.9726380 +/- 0.31386754 (0.81%) (init = 54.52798)
center: 9.24439393 +/- 0.00927645 (0.10%) (init = 9.25)
sigma: 1.15483177 +/- 0.01315708 (1.14%) (init = 1.35)
fwhm: 2.30966354 +/- 0.02631416 (1.14%) == '2.0000000*sigma'
height: 10.7421504 +/- 0.08634317 (0.80%) == '0.3183099*amplitude/max(1e-15,␣
˓→sigma)'
[[Correlations]]
+-----------+-----------+-----------+-----------+
| Variable | amplitude | center | sigma |
+-----------+-----------+-----------+-----------+
| amplitude | +1.0000 | -0.0002 | +0.7087 |
| center | -0.0002 | +1.0000 | -0.0002 |
| sigma | +0.7087 | -0.0002 | +1.0000 |
+-----------+-----------+-----------+-----------+
[[Model]]
Model(voigt)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 25
# data points = 401
# variables = 3
chi-square = 14.5448627
(continues on next page)
[[Correlations]]
+-----------+-----------+-----------+-----------+
| Variable | amplitude | center | sigma |
+-----------+-----------+-----------+-----------+
| amplitude | +1.0000 | -0.0001 | +0.6513 |
| center | -0.0001 | +1.0000 | -0.0001 |
| sigma | +0.6513 | -0.0001 | +1.0000 |
+-----------+-----------+-----------+-----------+
[[Model]]
Model(voigt)
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 25
# data points = 401
# variables = 3
chi-square = 14.5448627
reduced chi-square = 0.03654488
Akaike info crit = -1324.00615
Bayesian info crit = -1312.02427
R-squared = 0.99537150
[[Variables]]
amplitude: 35.7553799 +/- 0.13861559 (0.39%) (init = 65.43358)
center: 9.24411179 +/- 0.00505496 (0.05%) (init = 9.25)
sigma: 0.73015485 +/- 0.00368473 (0.50%) (init = 0.8775)
gamma: 0.73015485 +/- 0.00368473 (0.50%) == 'sigma'
fwhm: 2.62949983 +/- 0.01326979 (0.50%) == '1.0692*gamma+sqrt(0.
˓→8664*gamma**2+5.545083*sigma**2)'
[[Correlations]]
+-----------+-----------+-----------+-----------+
| Variable | amplitude | center | sigma |
+-----------+-----------+-----------+-----------+
| amplitude | +1.0000 | -0.0001 | +0.6513 |
| center | -0.0001 | +1.0000 | -0.0001 |
| sigma | +0.6513 | -0.0001 | +1.0000 |
+-----------+-----------+-----------+-----------+
# <examples/doc_builtinmodels_peakmodels.py>
import matplotlib.pyplot as plt
from numpy import loadtxt
data = loadtxt('test_peak.dat')
x = data[:, 0]
y = data[:, 1]
# Gaussian model
mod = GaussianModel()
pars = mod.guess(y, x=x)
out = mod.fit(y, pars, x=x)
print(out.fit_report(correl_mode='table'))
plt.plot(x, y)
plt.plot(x, out.best_fit, '-', label='Gaussian Model')
plt.legend()
plt.show()
# Lorentzian model
mod = LorentzianModel()
pars = mod.guess(y, x=x)
out = mod.fit(y, pars, x=x)
print(out.fit_report(correl_mode='table'))
plt.figure()
plt.plot(x, y, '-')
plt.plot(x, out.best_fit, '-', label='Lorentzian Model')
plt.legend()
plt.show()
# Voigt model
mod = VoigtModel()
pars = mod.guess(y, x=x)
out = mod.fit(y, pars, x=x)
print(out.fit_report(correl_mode='table'))
axes[0].plot(x, y, '-')
axes[0].plot(x, out.best_fit, '-', label='Voigt Model\ngamma constrained')
axes[0].legend()
(continues on next page)
axes[1].plot(x, y, '-')
axes[1].plot(x, out_gamma.best_fit, '-', label='Voigt Model\ngamma unconstrained')
axes[1].legend()
plt.show()
# <end examples/doc_builtinmodels_peakmodels.py>
14.1.18 doc_builtinmodels_nistgauss.py
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='exp_'))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 46
# data points = 250
# variables = 8
chi-square = 1247.52821
reduced chi-square = 5.15507524
Akaike info crit = 417.864631
Bayesian info crit = 446.036318
R-squared = 0.99648654
[[Variables]]
exp_amplitude: 99.0183278 +/- 0.53748593 (0.54%) (init = 162.2102)
exp_decay: 90.9508853 +/- 1.10310778 (1.21%) (init = 93.24905)
g1_amplitude: 4257.77360 +/- 42.3836478 (1.00%) (init = 2000)
g1_center: 107.030956 +/- 0.15006851 (0.14%) (init = 105)
(continues on next page)
[[Correlations]]
+---------------+---------------+---------------+---------------+---------------+------
˓→---------+---------------+---------------+---------------+
# <examples/doc_builtinmodels_nistgauss.py>
import matplotlib.pyplot as plt
import numpy as np
dat = np.loadtxt('NIST_Gauss2.dat')
x = dat[:, 1]
y = dat[:, 0]
exp_mod = ExponentialModel(prefix='exp_')
(continues on next page)
gauss1 = GaussianModel(prefix='g1_')
pars.update(gauss1.make_params(center=dict(value=105, min=75, max=125),
sigma=dict(value=15, min=0),
amplitude=dict(value=2000, min=0)))
gauss2 = GaussianModel(prefix='g2_')
pars.update(gauss2.make_params(center=dict(value=155, min=125, max=175),
sigma=dict(value=15, min=0),
amplitude=dict(value=2000, min=0)))
print(out.fit_report(correl_mode='table'))
comps = out.eval_components(x=x)
axes[1].plot(x, y)
axes[1].plot(x, comps['g1_'], '--', label='Gaussian component 1')
axes[1].plot(x, comps['g2_'], '--', label='Gaussian component 2')
axes[1].plot(x, comps['exp_'], '--', label='Exponential component')
axes[1].legend()
plt.show()
# <end examples/doc_builtinmodels_nistgauss.py>
14.1.19 doc_parameters_basic.py
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 64
# data points = 301
# variables = 4
chi-square = 12.1867036
reduced chi-square = 0.04103267
Akaike info crit = -957.236198
Bayesian info crit = -942.407756
[[Variables]]
amp: 5.03088059 +/- 0.04005824 (0.80%) (init = 10)
decay: 0.02495457 +/- 4.5396e-04 (1.82%) (init = 0.1)
omega: 2.00026310 +/- 0.00326183 (0.16%) (init = 3)
shift: -0.10264952 +/- 0.01022294 (9.96%) (init = 0)
[[Correlations]] (unreported correlations are < 0.100)
C(omega, shift) = -0.7852
C(amp, decay) = +0.5840
C(amp, shift) = -0.1179
# <examples/doc_parameters_basic.py>
import numpy as np
# ... or use
params = create_params(amp=dict(value=10, min=0),
decay=0.1,
omega=3,
shift=dict(value=0, min=-np.pi/2, max=np.pi/2))
14.1.20 doc_model_composite.py
[[Model]]
(Model(jump) <function convolve at 0x13bd86170> Model(gaussian))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 33
# data points = 201
# variables = 3
chi-square = 24.7562335
reduced chi-square = 0.12503148
Akaike info crit = -414.939746
Bayesian info crit = -405.029832
R-squared = 0.99632577
[[Variables]]
mid: 4 (fixed)
amplitude: 0.62508458 +/- 0.00189732 (0.30%) (init = 1)
center: 5.50853669 +/- 0.00973231 (0.18%) (init = 3.5)
sigma: 0.59576097 +/- 0.01348579 (2.26%) (init = 1.5)
[[Correlations]] (unreported correlations are < 0.100)
C(amplitude, center) = +0.3292
C(amplitude, sigma) = +0.2680
# <examples/doc_model_composite.py>
import matplotlib.pyplot as plt
import numpy as np
# create parameters for model. Note that 'mid' and 'center' will be highly
# correlated. Since 'mid' is used as an integer index, it will be very
# hard to fit, so we fix its value
pars = mod.make_params(amplitude=dict(value=1, min=0),
center=3.5,
sigma=dict(value=1.5, min=0),
mid=dict(value=4, vary=False))
print(result.fit_report())
# generate components
comps = result.eval_components(x=x)
# plot results
(continues on next page)
axes[0].plot(x, y, 'bo')
axes[0].plot(x, result.init_fit, 'k--', label='initial fit')
axes[0].plot(x, result.best_fit, 'r-', label='best fit')
axes[0].legend()
axes[1].plot(x, y, 'bo')
axes[1].plot(x, 10*comps['jump'], 'k--', label='Jump component')
axes[1].plot(x, 10*comps['gaussian'], 'r-', label='Gaussian component')
axes[1].legend()
plt.show()
# <end examples/doc_model_composite.py>
14.1.21 doc_builtinmodels_splinemodel.py
[[Model]]
(Model(gaussian, prefix='peak_') + Model(spline_model, prefix='bkg_'))
(continues on next page)
# <examples/doc_builtinmodels_splinemodel.py>
import matplotlib.pyplot as plt
import numpy as np
data = np.loadtxt('test_splinepeak.dat')
x = data[:, 0]
y = data[:, 1]
plt.plot(x, y, label='data')
model = GaussianModel(prefix='peak_')
params = model.make_params(amplitude=dict(value=8, min=0),
center=dict(value=16, min=5, max=25),
sigma=dict(value=1, min=0))
# make a background spline with knots evenly spaced over the background,
# but sort of skipping over where the peak is
knot_xvals3 = np.array([1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25])
knot_xvals2 = np.array([1, 3, 5, 7, 9, 11, 13, 16, 19, 21, 23, 25]) # noqa: E241
knot_xvals1 = np.array([1, 3, 5, 7, 9, 11, 13, 19, 21, 23, 25]) # noqa: E241
# <end examples/doc_builtinmodels_splinemodel.py>
14.1.22 doc_confidence_advanced.py
[[Variables]]
a1: 2.98622095 +/- 0.14867027 (4.98%) (init = 2.986237)
a2: -4.33526363 +/- 0.11527574 (2.66%) (init = -4.335256)
t1: 1.30994276 +/- 0.13121215 (10.02%) (init = 1.309932)
t2: 11.8240337 +/- 0.46316956 (3.92%) (init = 11.82408)
[[Correlations]] (unreported correlations are < 0.500)
C(a2, t2) = +0.9871
C(a2, t1) = -0.9246
C(t1, t2) = -0.8805
C(a1, t1) = -0.5988
95.45% 68.27% _BEST_ 68.27% 95.45%
a1: -0.27285 -0.14165 2.98622 +0.16354 +0.36343
a2: -0.30440 -0.13219 -4.33526 +0.10689 +0.19684
t1: -0.23392 -0.12494 1.30994 +0.14660 +0.32369
t2: -1.01937 -0.48813 11.82403 +0.46045 +0.90439
# <examples/doc_confidence_advanced.py>
import matplotlib.pyplot as plt
import numpy as np
(continues on next page)
import lmfit
def residual(p):
return p['a1']*np.exp(-x/p['t1']) + p['a2']*np.exp(-(x-0.1)/p['t2']) - y
# create Minimizer
mini = lmfit.Minimizer(residual, p, nan_policy='propagate')
lmfit.report_fit(out2.params, min_correl=0.5)
14.1.23 doc_model_uncertainty2.py
[[Model]]
((Model(gaussian, prefix='g1_') + Model(gaussian, prefix='g2_')) + Model(exponential,
˓→ prefix='bkg_'))
# <examples/doc_model_uncertainty2.py>
import matplotlib.pyplot as plt
import numpy as np
dat = np.loadtxt('NIST_Gauss2.dat')
x = dat[:, 1]
y = dat[:, 0]
comps = result.eval_components(x=x)
dely = result.eval_uncertainty(sigma=3)
plt.show()
# <end examples/doc_model_uncertainty2.py>
14.1.24 doc_fitting_emcee.py
[[Variables]]
a1: 2.98623689 +/- 0.15010519 (5.03%) (init = 4)
a2: -4.33525597 +/- 0.11765821 (2.71%) (init = 4)
t1: 1.30993186 +/- 0.13449653 (10.27%) (init = 3)
t2: 11.8240752 +/- 0.47172598 (3.99%) (init = 3)
[[Correlations]] (unreported correlations are < 0.500)
C(a2, t2) = +0.9876
C(a2, t1) = -0.9278
C(t1, t2) = -0.8852
C(a1, t1) = -0.6093
The chain is shorter than 50 times the integrated autocorrelation time for 5␣
˓→parameter(s). Use this estimate with caution and run a longer chain!
N/50 = 20;
tau: [42.15955322 47.347426 48.71211873 46.7985718 40.89881208]
# <examples/doc_fitting_emcee.py>
import numpy as np
import lmfit
try:
import matplotlib.pyplot as plt
HASPYLAB = True
except ImportError:
HASPYLAB = False
try:
import corner
HASCORNER = True
except ImportError:
HASCORNER = False
p = lmfit.Parameters()
p.add_many(('a1', 4), ('a2', 4), ('t1', 3), ('t2', 3., True))
(continues on next page)
def residual(p):
v = p.valuesdict()
return v['a1']*np.exp(-x/v['t1']) + v['a2']*np.exp(-(x-0.1) / v['t2']) - y
# Place bounds on the ln(sigma) parameter that emcee will automatically add
# to estimate the true uncertainty in the data since is_weighted=False
mi.params.add('__lnsigma', value=np.log(0.1), min=np.log(0.001), max=np.log(2))
if HASPYLAB:
plt.plot(res.acceptance_fraction, 'o')
plt.xlabel('walker')
plt.ylabel('acceptance fraction')
plt.show()
if hasattr(res, "acor"):
print("Autocorrelation time for the parameters:")
print("----------------------------------------")
for i, par in enumerate(p):
print(par, res.acor[i])
if HASPYLAB:
plt.figure()
plt.plot(x, y, 'o')
plt.plot(x, residual(mi.params) + y, label='Nelder-Mead')
plt.plot(x, residual(res.params) + y, '--', label='emcee')
plt.legend()
plt.show()
14.1.25 doc_confidence_chi2_maps.py
# <examples/doc_confidence_chi2_maps.py>
sigma_levels = [1, 2, 3]
rng = np.random.default_rng(seed=102)
set up data – deliberately adding imperfections and a small amount of non-Gaussian noise
npts = 501
x = np.linspace(1, 100, num=npts)
[[Model]]
(Model(gaussian) + Model(linear))
[[Fit Statistics]]
# fitting method = leastsq
# function evals = 31
# data points = 501
# variables = 5
chi-square = 103.861381
reduced chi-square = 0.20939794
Akaike info crit = -778.348033
Bayesian info crit = -757.265003
R-squared = 0.93782756
[[Variables]]
amplitude: 78.8171374 +/- 1.21910939 (1.55%) (init = 100)
center: 47.0751649 +/- 0.07576660 (0.16%) (init = 50)
sigma: 4.93298753 +/- 0.07984021 (1.62%) (init = 5)
slope: 0.01839006 +/- 7.1957e-04 (3.91%) (init = 0)
intercept: 4.39234411 +/- 0.04420227 (1.01%) (init = 0)
fwhm: 11.6162977 +/- 0.18800933 (1.62%) == '2.3548200*sigma'
height: 6.37412722 +/- 0.08603873 (1.35%) == '0.3989423*amplitude/max(1e-15,␣
˓→sigma)'
[[Correlations]]
+-----------+-----------+-----------+-----------+-----------+-----------+
| Variable | amplitude | center | sigma | slope | intercept |
+-----------+-----------+-----------+-----------+-----------+-----------+
| amplitude | +1.0000 | -0.0074 | +0.6371 | +0.0721 | -0.3373 |
| center | -0.0074 | +1.0000 | -0.0048 | -0.1026 | +0.0864 |
| sigma | +0.6371 | -0.0048 | +1.0000 | +0.0459 | -0.2149 |
| slope | +0.0721 | -0.1026 | +0.0459 | +1.0000 | -0.8421 |
| intercept | -0.3373 | +0.0864 | -0.2149 | -0.8421 | +1.0000 |
+-----------+-----------+-----------+-----------+-----------+-----------+
## Confidence Report:
99.73% 95.45% 68.27% _BEST_ 68.27% 95.45% 99.73%
amplitude: -3.62610 -2.41983 -1.21237 78.81714 +1.22111 +2.45479 +3.70515
center : -0.22849 -0.15214 -0.07584 47.07516 +0.07587 +0.15225 +0.22873
sigma : -0.23335 -0.15640 -0.07870 4.93299 +0.08000 +0.16158 +0.24509
slope : -0.00217 -0.00144 -0.00072 0.01839 +0.00072 +0.00144 +0.00217
intercept: -0.13326 -0.08860 -0.04423 4.39234 +0.04421 +0.08854 +0.13312
aix, aiy = 0, 0
nsamples = 50
explicitly_calculate_sigma = True
aix += 1
if aix == 2:
aix = 0
aiy += 1
ax = axes[aix, aiy]
cix = ci[xpar]
ciy = ci[ypar]
nc = len(sigma_levels)
for i in sigma_levels:
# dotted line: scaled stderr
ax.plot((xv-i*xs, xv+i*xs, xv+i*xs, xv-i*xs, xv-i*xs),
(yv-i*ys, yv-i*ys, yv+i*ys, yv+i*ys, yv-i*ys),
linestyle='dotted', color=colors[i-1])
ax.set_xlabel(xpar)
ax.set_ylabel(ypar)
ax.grid(True, color='#d0d0d0')
plt.show()
# <end examples/doc_confidence_chi2_maps.py>
l
lmfit.confidence, 141
lmfit.minimizer, 30
lmfit.model, 61
lmfit.models, 99
lmfit.parameter, 21
313
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
315
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
316 Index
Non-Linear Least-Squares Minimization and Curve-Fitting for Python, Release 1.2.0
T
ThermalDistributionModel (class in lmfit.models),
111
V
valuesdict() (Parameters method), 27
var_names (MinimizerResult attribute), 36
VoigtModel (class in lmfit.models), 102
W
weights (in module lmfit.model), 87
Index 317