@@ -4,6 +4,83 @@ Changelog
44=========
55
66
7+ Version 1.2.0
8+ -------------
9+
10+ *Released on: 2019/07/23 *
11+
12+ .. image :: https://zenodo.org/badge/DOI/10.5281/zenodo.3347076.svg
13+ :target: https://doi.org/10.5281/zenodo.3347076
14+
15+ Bug fixes:
16+
17+ * Return the correct coordinates when passing ``pixel_register=True `` and ``shape `` to
18+ ``verde.grid_coordinates ``. The returned coordinates had 1 too few elements in each
19+ dimension (and the wrong values). This is because we generate grid-line registered
20+ points first and then shift them to the center of the pixels and drop the last point.
21+ This only works when specifying ``spacing `` because it will generate the right amount
22+ of points. When ``shape `` is given, we need to first convert it to "grid-line" shape
23+ (with 1 extra point per dimension) before generating coordinates.
24+ (`#183 <https://github.com/fatiando/verde/pull/183 >`__)
25+ * Reset force coordinates when refitting splines. Previously, the splines set the force
26+ coordinates from the data coordinates only the first time ``fit `` was called. This
27+ means that when fitting on different data, the spline would still use the old
28+ coordinates leading to a poor prediction score. Now, the spline will use the
29+ coordinates of the current data passed to ``fit ``. This only affects cases where
30+ ``force_coords=None ``. It's a slight change and only affects some of the scores for
31+ cross-validation. (`#191 <https://github.com/fatiando/verde/pull/191 >`__)
32+
33+ New functions/classes:
34+
35+ * New class ``verde.SplineCV ``: a cross-validated version of ``Spline `` . that performs
36+ grid search cross-validation to automatically tune the parameters of a ``Spline ``.
37+ (`#185 <https://github.com/fatiando/verde/pull/185 >`__)
38+ * New function ``verde.longitude_continuity `` to format longitudes to a continuous
39+ range so that they can be indexed with ``verde.inside ``
40+ (`#181 <https://github.com/fatiando/verde/pull/181 >`__)
41+ * New function ``verde.load_surfer `` to load grid data from a Surfer ASCII file (a
42+ contouring, griding and surface mapping software from GoldenSoftware).
43+ (`#169 <https://github.com/fatiando/verde/pull/169 >`__)
44+ * New function ``verde.median_distance `` that calculates the median near neighbor
45+ distance between each point in the given dataset.
46+ (`#163 <https://github.com/fatiando/verde/pull/163 >`__)
47+
48+ Improvements:
49+
50+ * Allow ``verde.block_split `` and ``verde.BlockReduce `` to take a ``shape `` argument
51+ instead of ``spacing ``. Useful when the size of the block is less meaningful than the
52+ number of blocks.
53+ (`#184 <https://github.com/fatiando/verde/pull/184 >`__)
54+ * Allow zero degree polynomials in ``verde.Trend ``, which represents a mean value.
55+ (`#162 <https://github.com/fatiando/verde/pull/162 >`__)
56+ * Function ``verde.cross_val_score `` returns a numpy array instead of a list for easier
57+ computations on the results. (`#160 <https://github.com/fatiando/verde/pull/160 >`__)
58+ * Function ``verde.maxabs `` now handles inputs with NaNs automatically.
59+ (`#158 <https://github.com/fatiando/verde/pull/158 >`__)
60+
61+ Documentation:
62+
63+ * New tutorial to explain the intricacies of grid coordinates generation, adjusting
64+ spacing vs region, pixel registration, etc.
65+ (`#192 <https://github.com/fatiando/verde/pull/192 >`__)
66+
67+ Maintenance:
68+
69+ * Drop support for Python 3.5. (`#178 <https://github.com/fatiando/verde/pull/178 >`__)
70+ * Add support for Python 3.7. (`#150 <https://github.com/fatiando/verde/pull/150 >`__)
71+ * More functions are now part of the base API: ``n_1d_arrays ``, ``check_fit_input `` and
72+ ``least_squares `` are now included in ``verde.base ``.
73+ (`#156 <https://github.com/fatiando/verde/pull/156 >`__)
74+
75+ This release contains contributions from:
76+
77+ * Goto15
78+ * Lindsey Heagy
79+ * Jesse Pisel
80+ * Santiago Soler
81+ * Leonardo Uieda
82+
83+
784Version 1.1.0
885-------------
986
0 commit comments