lmfit/lmfit-py: 1.2.2rc1
Authors/Creators
- Matt Newville1
- Renee Otten
- Andrew Nelson
- Till Stensitzki2
- Antonino Ingargiola
- Dan Allan3
- Austin Fox
- Faustin Carter
- Michał
- Ray Osborn
- Dima Pustakhod
- lneuhaus
- Sebastian Weigand
- Andrey Aristov4
- Glenn
- Christoph Deil5
- mgunyho
- Mark6
- Allan L. R. Hansen
- Gustavo Pasquevich
- Leon Foks7
- Nicholas Zobrist8
- Oliver Frost
- Stuermer9
- azelcer
- Anthony Polloreno10
- Arun Persaud
- Jens Hedegaard Nielsen11
- Matteo Pompili12
- Pieter Eendebak
- 1. University of Chicago
- 2. Universität Potsdam
- 3. Brookhaven National Lab
- 4. Insitut Pasteur
- 5. HeidelbergCement
- 6. Brookhaven National Laboratory
- 7. Contractor U.S. Geological Survey
- 8. Google Quantum AI
- 9. University of Heidelberg
- 10. University of Colorado Boulder
- 11. @qdev-dk
- 12. Amazon Web Services, Center for Quantum Networking
Description
New features:
add
ModelResult.uvarsoutput to aModelResultafter a successful fit that containsufloatsfrom theuncertaintiespackage which can be used for downstream calculations that propagate the uncertainties (and correlations) of the variable Parameters. (PR #888)Outputs of residual functions, including
Model._residual, are more explicitly coerced to 1d-arrays of dataype Float64. This decreases the expectation for the user-supplied code to return ndarrays, and increases the tolerance for more "array-like" objects or ndarrays that are not Float64 or 1-dimensional. (PR #899)Model.fitnow takes acoerce_farrayoption, defaulting toTrueto control whether to input data and independent variables that are "array-like" are coerced to ndarrays of datatype Float64 or Complex128. If set toFalsethen independent data that "array-like" (pandas.Series, int32 arrays, etc) will be sent to the model function unaltered. The user may then use other features of these objects, but may also need to explicitly coerce the datatype of the result the change described above about coercing the result causes problems. (Discussion #873; PR #899)
Bug fixes/enhancements:
fixed bug in
Model.make_params()for non-composite models that use a prefix (Discussion #892; Issue #893; PR #895)fixed bug with aborted fits for several methods having incorrect or invalid fit statistics. (Discussion #894; Issue #896; PR #897)
Model.eval_uncertaintynow correctly calculates complex (real/imaginary pairs) uncertainties for Models that generate complex results. (Issue #900; PR #901)Model.evalnow returns and array-like value. This adds to the coercion features above and fixes a bug for composite models that return lists (Issue #875; PR #901)the HTML representation for a
ModelResultorMinimizerResultare improved, and create fewer entries in the Table of Contents for Jupyter lab. (Issue #884; PR #883; PR #902)
Files
lmfit/lmfit-py-1.2.2rc1.zip
Files
(396.5 kB)
| Name | Size | Download all |
|---|---|---|
|
md5:b0976ce4836bf833f8bc629f1c327bfb
|
396.5 kB | Preview Download |
Additional details
Related works
- Is supplement to
- https://github.com/lmfit/lmfit-py/tree/1.2.2rc1 (URL)