diff --git a/AUTHORS.md b/AUTHORS.md index 2dd7dd87c..a77561fb2 100644 --- a/AUTHORS.md +++ b/AUTHORS.md @@ -6,4 +6,5 @@ are considered "The Verde Developers": * [David Hoese](https://github.com/djhoese) * [Jesse Pisel](https://github.com/jessepisel) +* [Santiago R. Soler](https://github.com/santisoler) * [Leonardo Uieda](https://github.com/leouieda) diff --git a/README.rst b/README.rst index f4a0cff58..f3fe9bc4d 100644 --- a/README.rst +++ b/README.rst @@ -163,6 +163,7 @@ Documentation for other versions * `Development `__ (reflects the *master* branch on Github) * `Latest release `__ +* `v1.2.0 `__ * `v1.1.0 `__ * `v1.0.1 `__ * `v1.0.0 `__ diff --git a/doc/changes.rst b/doc/changes.rst index 9923b6c47..67ec5dd30 100644 --- a/doc/changes.rst +++ b/doc/changes.rst @@ -4,6 +4,83 @@ Changelog ========= +Version 1.2.0 +------------- + +*Released on: 2019/07/23* + +.. image:: https://zenodo.org/badge/DOI/10.5281/zenodo.3347076.svg + :target: https://doi.org/10.5281/zenodo.3347076 + +Bug fixes: + +* Return the correct coordinates when passing ``pixel_register=True`` and ``shape`` to + ``verde.grid_coordinates``. The returned coordinates had 1 too few elements in each + dimension (and the wrong values). This is because we generate grid-line registered + points first and then shift them to the center of the pixels and drop the last point. + This only works when specifying ``spacing`` because it will generate the right amount + of points. When ``shape`` is given, we need to first convert it to "grid-line" shape + (with 1 extra point per dimension) before generating coordinates. + (`#183 `__) +* Reset force coordinates when refitting splines. Previously, the splines set the force + coordinates from the data coordinates only the first time ``fit`` was called. This + means that when fitting on different data, the spline would still use the old + coordinates leading to a poor prediction score. Now, the spline will use the + coordinates of the current data passed to ``fit``. This only affects cases where + ``force_coords=None``. It's a slight change and only affects some of the scores for + cross-validation. (`#191 `__) + +New functions/classes: + +* New class ``verde.SplineCV``: a cross-validated version of ``Spline`` . that performs + grid search cross-validation to automatically tune the parameters of a ``Spline``. + (`#185 `__) +* New function ``verde.longitude_continuity`` to format longitudes to a continuous + range so that they can be indexed with ``verde.inside`` + (`#181 `__) +* New function ``verde.load_surfer`` to load grid data from a Surfer ASCII file (a + contouring, griding and surface mapping software from GoldenSoftware). + (`#169 `__) +* New function ``verde.median_distance`` that calculates the median near neighbor + distance between each point in the given dataset. + (`#163 `__) + +Improvements: + +* Allow ``verde.block_split`` and ``verde.BlockReduce`` to take a ``shape`` argument + instead of ``spacing``. Useful when the size of the block is less meaningful than the + number of blocks. + (`#184 `__) +* Allow zero degree polynomials in ``verde.Trend``, which represents a mean value. + (`#162 `__) +* Function ``verde.cross_val_score`` returns a numpy array instead of a list for easier + computations on the results. (`#160 `__) +* Function ``verde.maxabs`` now handles inputs with NaNs automatically. + (`#158 `__) + +Documentation: + +* New tutorial to explain the intricacies of grid coordinates generation, adjusting + spacing vs region, pixel registration, etc. + (`#192 `__) + +Maintenance: + +* Drop support for Python 3.5. (`#178 `__) +* Add support for Python 3.7. (`#150 `__) +* More functions are now part of the base API: ``n_1d_arrays``, ``check_fit_input`` and + ``least_squares`` are now included in ``verde.base``. + (`#156 `__) + +This release contains contributions from: + +* Goto15 +* Lindsey Heagy +* Jesse Pisel +* Santiago Soler +* Leonardo Uieda + + Version 1.1.0 -------------