From 8b2038a16cf3ce87c25c35d224093ce3e8dc2af3 Mon Sep 17 00:00:00 2001 From: Matthew Newville Date: Thu, 13 Jul 2023 20:52:27 -0500 Subject: [PATCH] final updates for v 1.2.2 --- doc/parameters.rst | 2 ++ doc/whatsnew.rst | 4 ++-- lmfit/__init__.py | 2 +- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/parameters.rst b/doc/parameters.rst index 1f9924ab..7b331cee 100644 --- a/doc/parameters.rst +++ b/doc/parameters.rst @@ -96,6 +96,8 @@ The :class:`Parameters` class The :func:`create_params` function ================================== +.. versionadded:: 1.2.0 + The :func:`create_params` function is probably the easiest method for making :class:`Parameters` objects, as it allows defining Parameter names by keyword with values either being the numerical initial value for the Parameter or being diff --git a/doc/whatsnew.rst b/doc/whatsnew.rst index 8df23dd1..8473cdea 100644 --- a/doc/whatsnew.rst +++ b/doc/whatsnew.rst @@ -24,7 +24,7 @@ New features: 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 + explicitly coerced to 1d-arrays of datatype 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) @@ -88,7 +88,7 @@ New features: 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) +- fix bug in reported uncertainties for constrained parameters by better propagating 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 :ref:`model_data_coercion_section` for details). The resulting calculation from a model or objective function is more aggressively coerced to float64. (Issue #850; PR #853) diff --git a/lmfit/__init__.py b/lmfit/__init__.py index 2e31e817..960c1913 100644 --- a/lmfit/__init__.py +++ b/lmfit/__init__.py @@ -30,7 +30,7 @@ * Many built-in models for common lineshapes are included and ready to use. -Copyright (c) 2022 Lmfit Developers ; BSD-3 license ; see LICENSE +Copyright (c) 2023 Lmfit Developers ; BSD-3 license ; see LICENSE """ from asteval import Interpreter