Gvar

Latest version: v13.0.2

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

Scan your dependencies

Page 14 of 18

4.8.4

Not secure
===========================
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.

4.8.2

Not secure
==========================
Very small additions to facilitate pickling and other serialization of GVars. Changed
gvar.evalcov and gvar.gvar so that newg = gvar.gvar(gvar.mean(g), gvar.evalcov(g))
for some array or dictionary g containing GVars creates a new array/dictionary
with the same means and covariance matrix. Added better documentation
on the gvar page about pickling gvars, and also added new functions
(dump, dumps, load, loads) for pickling collections of GVars.

4.8.1

Not secure
===========================
Bug fix.

- fixed negative svdcuts (which one shouldn't use anyway), which were broken.

- gvar.cspline.CSpline functions now return scalars rather than 0-D numpy
arrays when given scalar arguments.

4.8

Not secure
========================
This release has a reworked framework for SVD cuts. The new framework is
simpler, but also more robust --- SVD cuts are applied separately
to each block-diagonal sub-matrix of the data-prior covariance matrix. This
is more accurate, faster, and uses less memory, though the differences
aren't substantial for most fits.

- svdnum is no longer an option for lsqfit.nonlinear_fit, raniter, etc.
This parameter makes little sense in the new framework. Make svdcut
negative if it is important to get rid of certain eigenmodes. (Generally
it is better to keep the modes, but with larger variances. This is
what happens when svdcut is positive.)

- New information included in the Settings part of a fit report:
number of eigenmodes modified by SVD cut, time needed for fit.
The number of iterations is moved from the top line of the report
to the last line, with the time.

- Better notation for lsqfit.transform_p (mostly compatible with old
usage).

- Added a new numerical analysis routine (joining gvar.ode and gvar.cspline)
in gvar for manipulating power series representations of functions:
gvar.powerseries. The numerical analysis routines in gvar have been
adapted so that they work with GVars and/or floats. More will be added
in the future.

- Fixed bug in gvar.cspline (derivatives not computed correctly); added
better tests for cspline.

- Fixed documentation errors in gvar.dataset.

- gvar.dataset.avg_data(s) for a dictionary s now (optionally) issues
a warning if different entries in s have different sample sizes. The
smallest sample size is chosen for all entries in such situations.

- Added option to gvar.ode.Integrator to allow custom adaptive
strategies. Also offers a different interface to the integrator.

- Fixed minor irregularity (not really a bug) in GVar.fmt:
x = gvar(0.999,0.999) implied that x.fmt(2) gave 1.00(100) which
is correct but non-standard (should be 1.00(1.00) and now is).

4.7

Not secure
==============
A minor upgrade but with one backwards incompatible change (that is unlikey
to affect much code). The incompatibility is the main reason for calling this
release version 4.7 rather than 4.6.2.

- GVars can be used with any comparison operator now (==, !=, >, >=, <, <=).
The comparison is made with the mean value of the GVar, ignoring the
standard deviation. This is to facilitate the use/design of numeric functions
that are designed to work with either floats or GVars. The definition of ==
and != has changed from the past. Before x==y for two GVars was true only if
both their means and standard deviations agreed; now it is true if their
means agree, but their standard deviations disagree.

- Can use keyword keys to specify the which keys to use and their order when
creating a BufferDict from a dictionary-like object.

- Significantly more documentation for the gvar module, and some rearrangement
and expansion of the overview documentation.

- New function gvar.gvar_function for creating new arithmetic Python
functions that can accept GVar arguments.

- gvar.gvar(x, xcov) now works when x and xcov are dictionaries. This allows
you to deconstruct a dictionary of GVars using gvar.mean and gvar.evalcov,
and then to reconstruct the dictionary using gvar.gvar: e.g.,
gvar.gvar(gvar.mean(g), gvar.evalcov(g)) rebuilds g when g is an array
of GVars, or a dictionary of GVars and arrays of GVars.

- gvar has two new numerical analysis modules: gvar.ode for integrating
ordinary differential equations, and gvar.cspline for creating cubic
splines from 1-d data. These modules are adapted from standard routines
so they work with GVars as well as floats, which is why they are included
here. Additional modules will be added as the need arises.

- When printing an lsqfit fit using fit.format(), setting option maxline=True
(rather than a number) now causes all data to be printed.

- Other minor rearrangements and clarifications in setup.py and a few other files.

Page 14 of 18

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.