Lsqfit

Latest version: v13.2.3

Safety actively analyzes 682404 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 13

5.0.1

===========================
This is a very minor bug fix.

- Modified gvar.mean(g), gvar.sdev(g), gvar.var(g) so that g can
include elements that are not GVars. These elements are assumed to
have zero error, so their value is their mean. This means, for
example, that g can be all GVars or all floats or a mixture.

- Fixed bug in gvar.ranseed which caused it to crash under python3 in
certain circumstances.

5.0

=========================
A minor upgrade to provide functionality for other libraries. The first
change is not backwards compatible, but is unlikely to break much or any
code (except mine).

- fit.svdcorrection is now the sum of all svdcorrections, not a vector. The
sum is all that is needed to construct error budgets, which is the
only use for fit.svdcorrection. The sum is easier to manipulate -- for
example, two svdcorrections can now be added to give a composite
svdcorrection (as opposed to concatenated before).

- Fixed innocuous bug in lsqfit.nonlinear_fit.format().

- gvar.dataset.Dataset.slice can now apply slices to multiple dimensions.

- Added __format__ to gvar.GVar. This converts the GVar to a string
and then applies the format to the string. This was needed to make
python3 and python2 function similarly in certain situations.

- More polishing of the documentation (especially about svd).

- Beginning with this version of lsqfit, version numbers will be consistent
with the rules of "semantic versioning" (http://semver.org). The most
important consequence is that any change that is *not* backwards compatible
with the current interface (as defined by the documentation) will be signaled
by a change in the major version number, where the full version number has the
format major.minor.patch (so the major version number is 5 for version 5.0).
A side effect of this is that increases in the major version number can
be triggered by relatively obscure changes in the interface that will have
no effect whatsoever on almost all existing codes. The current move to 5.0
is an example.

4.8.5.1

============================
This release is almost identical to the previous release. It is mainly to do
with getting the software registered properly online.

- Small improvement to the user interface in gvar.ode. It now works with
vectors of x values, returning vectors of y values.

4.8.5

==========================

- Bug fix so recent changes in lsqfit don't cause crashes on Windows systems.

4.8.4

===========================
Small bug fixes.

- gvar.dataset.Dataset objects now work with Python's pickle. Also
Dataset objects can now be initialized from other Dataset object, or from
dictionaries, or lists of key-data tuples (like dictionaries).

- lsqfit.wavg now works with priors.

- Removed calls to C's lgamma function because it isn't available to
old C compilers. Use Python's math.lgamma instead, which should always be
available.

4.8.3

==========================
Bug fix: the new svd system didn't work with older versions of numpy (earlier
than 1.8). It now does. The problem was in lsqfit; gvar was fine.
There was a related issue in gvar.cspline which is also fixed.

Page 9 of 13

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.