You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+67-5Lines changed: 67 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,19 +10,54 @@ Code freeze date: YYYY-MM-DD
10
10
11
11
### Dependency Changes
12
12
13
+
### Added
14
+
15
+
-`climada.util.interpolation` module for inter- and extrapolation util functions used in local exceedance intensity and return period functions [#930](https://github.com/CLIMADA-project/climada_python/pull/930)
16
+
13
17
### Changed
14
18
15
-
- Remove content tables and make minor improvements (fix typos and readability) in
- Centroids complete overhaul. Most function should be backward compatible. Internal data is stored in a geodataframe attribute. Raster are now stored as points, and the meta attribute is removed. Several methds were deprecated or removed. [#787](https://github.com/CLIMADA-project/climada_python/pull/787)
18
-
- Improved error messages produced by `ImpactCalc.impact()` in case impact function in the exposures is not found in impf_set [#863](https://github.com/CLIMADA-project/climada_python/pull/863)
19
+
- In `climada.util.plot.geo_im_from_array`, NaNs are plotted in gray while cells with no centroid are not plotted [#929](https://github.com/CLIMADA-project/climada_python/pull/929)
20
+
- Renamed `climada.util.plot.subplots_from_gdf` to `climada.util.plot.plot_from_gdf`[#929](https://github.com/CLIMADA-project/climada_python/pull/929)
19
21
20
22
### Fixed
21
23
22
-
- Avoid an issue where a Hazard subselection would have a fraction matrix with only zeros as entries by throwing an error [#866](https://github.com/CLIMADA-project/climada_python/pull/866)
24
+
### Deprecated
25
+
26
+
### Removed
27
+
28
+
## 5.0.0
29
+
30
+
Release date: 2024-07-19
31
+
32
+
### Dependency Changes
33
+
34
+
Added:
35
+
36
+
-`bayesian-optimization`
37
+
-`seaborn` >=0.13
38
+
39
+
Updated:
40
+
41
+
-`bottleneck` >=1.3 → >=1.4
42
+
-`cartopy` >=0.22 → >=0.23
43
+
-`contextily` >=1.5 → >=1.6
44
+
-`dask` >=2024.1,<2024.3 → >=2024.2,<2024.3
45
+
-`matplotlib-base` >=3.8 → >=3.9
46
+
-`numba` >=0.59 → >=0.60
47
+
-`numexpr` >=2.9 → >=2.10
48
+
-`pint` >=0.23 → >=0.24
49
+
-`pycountry` >=22.3 → >=24.6
50
+
-`requests` >=2.31 → >=2.32
51
+
-`salib` >=1.4 → >=1.5
52
+
-`scikit-learn` >=1.4 → >=1.5
53
+
-`scipy` >=1.12 → >=1.13
54
+
-`xarray` >=2024.2 → >=2024.6
23
55
24
56
### Added
25
57
58
+
- GitHub actions workflow for CLIMADA Petals compatibility tests [#855](https://github.com/CLIMADA-project/climada_python/pull/855)
59
+
-`climada.util.calibrate` module for calibrating impact functions [#692](https://github.com/CLIMADA-project/climada_python/pull/692)
60
+
- Method `Hazard.check_matrices` for bringing the stored CSR matrices into "canonical format" [#893](https://github.com/CLIMADA-project/climada_python/pull/893)
26
61
- Generic s-shaped impact function via `ImpactFunc.from_poly_s_shape`[#878](https://github.com/CLIMADA-project/climada_python/pull/878)
- Centroids complete overhaul. Most function should be backward compatible. Internal data is stored in a geodataframe attribute. Raster are now stored as points, and the meta attribute is removed. Several methds were deprecated or removed. [#787](https://github.com/CLIMADA-project/climada_python/pull/787)
82
+
- Improved error messages produced by `ImpactCalc.impact()` in case impact function in the exposures is not found in impf_set [#863](https://github.com/CLIMADA-project/climada_python/pull/863)
83
+
- Update the Holland et al. 2010 TC windfield model and introduce `model_kwargs` parameter to adjust model parameters [#846](https://github.com/CLIMADA-project/climada_python/pull/846)
84
+
- Changed module structure: `climada.hazard.Hazard` has been split into the modules `base`, `io` and `plot`[#871](https://github.com/CLIMADA-project/climada_python/pull/871)
85
+
- Ensure `csr_matrix` stored in `climada.hazard.Hazard` have consistent data format and store no explicit zeros when initializing `ImpactCalc`[#893](https://github.com/CLIMADA-project/climada_python/pull/893)
86
+
-`Impact.from_hdf5` now calls `str` on `event_name` data that is not strings, and issue a warning then [#894](https://github.com/CLIMADA-project/climada_python/pull/894)
87
+
-`Impact.write_hdf5` now throws an error if `event_name` is does not contain strings exclusively [#894](https://github.com/CLIMADA-project/climada_python/pull/894)
88
+
- Split `climada.hazard.trop_cyclone` module into smaller submodules without affecting module usage [#911](https://github.com/CLIMADA-project/climada_python/pull/911)
89
+
90
+
### Fixed
91
+
92
+
- Avoid an issue where a Hazard subselection would have a fraction matrix with only zeros as entries by throwing an error [#866](https://github.com/CLIMADA-project/climada_python/pull/866)
93
+
- Allow downgrading the Python bugfix version to improve environment compatibility [#900](https://github.com/CLIMADA-project/climada_python/pull/900)
94
+
- Fix broken links in `CONTRIBUTING.md`[#900](https://github.com/CLIMADA-project/climada_python/pull/900)
95
+
- When writing `TCTracks` to NetCDF, only apply compression to `float` or `int` data types. This fixes a downstream issue, see [climada_petals#135](https://github.com/CLIMADA-project/climada_petals/issues/135)[#911](https://github.com/CLIMADA-project/climada_python/pull/911)
-`scheduler` parameter in `climada.util.coordinates.set_df_geometry_points`, as dask is not used anymore, leaving all calculation to shapely [#912](https://github.com/CLIMADA-project/climada_python/pull/912)
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Please contact the [lead developers](https://wcr.ethz.ch/research/climada.html)
22
22
23
23
## Minimal Steps to Contribute
24
24
25
-
Before you start, please have a look at our [Developer Guide][devguide].
25
+
Before you start, please have a look at our Developer Guide section in the [CLIMADA Docs][docs].
26
26
27
27
To contribute follow these steps:
28
28
@@ -65,21 +65,22 @@ To contribute follow these steps:
65
65
66
66
## Resources
67
67
68
-
The CLIMADA documentation provides a [Developer Guide][devguide].
68
+
The [CLIMADA documentation][docs] provides several Developer Guides.
69
69
Here's a selection of the commonly required information:
70
70
71
71
* How to use Git and GitHub for CLIMADA development: [Development and Git and CLIMADA](https://climada-python.readthedocs.io/en/latest/guide/Guide_Git_Development.html)
72
-
* Coding instructions for CLIMADA: [Python Dos and Don'ts](https://climada-python.readthedocs.io/en/latest/guide/Guide_PythonDos-n-Donts.html), [Performance Tips](https://climada-python.readthedocs.io/en/latest/guide/Guide_Py_Performance.html), [CLIMADA Conventions](https://climada-python.readthedocs.io/en/latest/guide/Guide_Miscellaneous.html)
73
-
* How to execute tests in CLIMADA: [Testing and Continuous Integration][testing]
72
+
* Coding instructions for CLIMADA: [Python Dos and Don'ts](https://climada-python.readthedocs.io/en/latest/guide/Guide_PythonDos-n-Donts.html), [Performance Tips](https://climada-python.readthedocs.io/en/latest/guide/Guide_Py_Performance.html), [CLIMADA Conventions](https://climada-python.readthedocs.io/en/latest/guide/Guide_CLIMADA_conventions.html)
73
+
* How to execute tests in CLIMADA: [Testing][testing] and [Continuous Integration](https://climada-python.readthedocs.io/en/latest/guide/Guide_continuous_integration_GitHub_actions.html)
74
74
75
75
## Pull Requests
76
76
77
77
After developing a new feature, fixing a bug, or updating the tutorials, you can create a [pull request](https://docs.github.com/en/pull-requests) to have your changes reviewed and then merged into the CLIMADA code base.
78
78
To ensure that your pull request can be reviewed quickly and easily, please have a look at the _Resources_ above before opening a pull request.
79
-
In particular, please check out the [Pull Request instructions](https://climada-python.readthedocs.io/en/latest/guide/Guide_Git_Development.html#Pull-requests).
79
+
In particular, please check out the [Pull Request instructions](https://climada-python.readthedocs.io/en/latest/guide/Guide_Git_Development.html#pull-requests).
80
80
81
81
We provide a description template for pull requests that helps you provide the essential information for reviewers.
82
82
It also contains a checklist for both pull request authors and reviewers to guide the review process.
0 commit comments