gnuplot documentation

60 gnuplot 4.3 53 FIT
FIT_SCRIPT
specifies a command that may be executed after an user interrupt. The default is replot, but a plot or
load command may be useful to display a plot customized to highlight the progress of the fit.
53.5 Multi-branch
In multi-branch fitting, multiple data sets can be simultaneously fit with functions of one independent
variable having common parameters by minimizing the total WSSR. The function and parameters
(branch) for each data set are selected by using a ’pseudo-variable’, e.g., either the dataline number (a
’column’ index of -1) or the datafile index (-2), as the second independent variable.
Example: Given two exponential decays of the form, z=f(x), each describing a different data set but
having a common decay time, estimate the values of the parameters. If the datafile has the format x:z:s,
then
f(x,y) = (y==0) ? a*exp(-x/tau) : b*exp(-x/tau)
fit f(x,y) ’datafile’ using 1:-2:2:3 via a, b, tau
For a more complicated example, see the file "hexa.fnc" used by the "fit.dem" demo.
Appropriate weighting may be required since unit weights may cause one branch to predominate if there
is a difference in the scale of the dependent variable. Fitting each branch separately, using the multibranch
solution as initial values, may give an indication as to the relative effect of each branch on the
joint solution.
53.6 Starting values
Nonlinear fitting is not guaranteed to converge to the global optimum (the solution with the smallest
sum of squared residuals, SSR), and can get stuck at a local minimum. The routine has no way to
determine that; it is up to you to judge whether this has happened.
fit may, and often will get "lost" if started far from a solution, where SSR is large and changing slowly
as the parameters are varied, or it may reach a numerically unstable region (e.g., too large a number
causing a floating point overflow) which results in an "undefined value" message or gnuplot halting.
To improve the chances of finding the global optimum, you should set the starting values at least roughly
in the vicinity of the solution, e.g., within an order of magnitude, if possible. The closer your starting
values are to the solution, the less chance of stopping at another minimum. One way to find starting
values is to plot data and the fitting function on the same graph and change parameter values and replot
until reasonable similarity is reached. The same plot is also useful to check whether the fit stopped at a
minimum with a poor fit.
Of course, a reasonably good fit is not proof there is not a "better" fit (in either a statistical sense,
characterized by an improved goodness-of-fit criterion, or a physical sense, with a solution more consistent
with the model.) Depending on the problem, it may be desirable to fit with various sets of starting
values, covering a reasonable range for each parameter.
53.7 Tips
Here are some tips to keep in mind to get the most out of fit. They’re not very organized, so you’ll have
to read them several times until their essence has sunk in.
The two forms of the via argument to fit serve two largely distinct purposes. The via "file" form is
best used for (possibly unattended) batch operation, where you just supply the startup values in a file
and can later use update to copy the results back into another (or the same) parameter file.
The via var1, var2, ... form is best used interactively, where the command history mechanism may
be used to edit the list of parameters to be fitted or to supply new startup values for the next try. This
is particularly useful for hard problems, where a direct fit to all parameters at once won’t work without