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
- 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
+
17
20
### Fixed
18
21
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)
23
+
24
+
### Added
25
+
26
+
- Generic s-shaped impact function via `ImpactFunc.from_poly_s_shape`[#878](https://github.com/CLIMADA-project/climada_python/pull/878)
-`requirements/env_docs.yml`. The regular environment specs are now used to build the online documentation [#687](https://github.com/CLIMADA-project/climada_python/pull/687)
74
+
75
+
## 4.1.1
76
+
77
+
Release date: 2024-02-21
78
+
79
+
### Fixed
80
+
81
+
- Fix `util.coordinates.latlon_bounds` for cases where the specified buffer is very large so that the bounds cover more than the full longitudinal range `[-180, 180]`[#839](https://github.com/CLIMADA-project/climada_python/pull/839)
82
+
- Fix `climada.hazard.trop_cyclone` for TC tracks crossing the antimeridian [#839](https://github.com/CLIMADA-project/climada_python/pull/839)
83
+
84
+
## 4.1.0
85
+
86
+
Release date: 2024-02-14
87
+
88
+
### Dependency Changes
89
+
90
+
Added:
91
+
92
+
-`pyproj` >=3.5
93
+
-`numexpr` >=2.9
94
+
95
+
Updated:
96
+
97
+
-`contextily` >=1.3 → >=1.5
98
+
-`dask` >=2023 → >=2024
99
+
-`numba` >=0.57 → >=0.59
100
+
-`pandas` >=2.1 → >=2.1,<2.2
101
+
-`pint` >=0.22 → >=0.23
102
+
-`scikit-learn` >=1.3 → >=1.4
103
+
-`scipy` >=1.11 → >=1.12
104
+
-`sparse` >=0.14 → >=0.15
105
+
-`xarray` >=2023.8 → >=2024.1
106
+
-`overpy` =0.6 → =0.7
107
+
-`peewee` =3.16.3 → =3.17.1
108
+
109
+
Removed:
110
+
111
+
-`proj` (in favor of `pyproj`)
112
+
113
+
### Added
114
+
115
+
- Convenience method `api_client.Client.get_dataset_file`, combining `get_dataset_info` and `download_dataset`, returning a single file objet. [#821](https://github.com/CLIMADA-project/climada_python/pull/821)
116
+
- Read and Write methods to and from csv files for the `DiscRates` class. [#818](ttps://github.com/CLIMADA-project/climada_python/pull/818)
117
+
- Add `CalcDeltaClimate` to unsequa module to allow uncertainty and sensitivity analysis of impact change calculations [#844](https://github.com/CLIMADA-project/climada_python/pull/844)
118
+
- Add function `safe_divide` in util which handles division by zero and NaN values in the numerator or denominator [#844](https://github.com/CLIMADA-project/climada_python/pull/844)
119
+
- Add reset_frequency option for the impact.select() function. [#847](https://github.com/CLIMADA-project/climada_python/pull/847)
120
+
121
+
### Changed
122
+
123
+
- Update Developer and Installation Guides for easier accessibility by new developers. [808](https://github.com/CLIMADA-project/climada_python/pull/808)
124
+
- Add `shapes` argument to `geo_im_from_array` to allow flexible turning on/off of plotting coastline in `plot_intensity`. [#805](https://github.com/CLIMADA-project/climada_python/pull/805)
125
+
- Update `CONTRIBUTING.md` to better explain types of contributions to this repository [#797](https://github.com/CLIMADA-project/climada_python/pull/797)
126
+
- The default tile layer in Exposures maps is not Stamen Terrain anymore, but [CartoDB Positron](https://github.com/CartoDB/basemap-styles). Affected methods are `climada.engine.Impact.plot_basemap_eai_exposure`,`climada.engine.Impact.plot_basemap_impact_exposure` and `climada.entity.Exposures.plot_basemap`. [#798](https://github.com/CLIMADA-project/climada_python/pull/798)
127
+
- Recommend using Mamba instead of Conda for installing CLIMADA [#809](https://github.com/CLIMADA-project/climada_python/pull/809)
128
+
-`Hazard.from_xarray_raster` now allows arbitrary values as 'event' coordinates [#837](https://github.com/CLIMADA-project/climada_python/pull/837)
129
+
-`climada.test.get_test_file` now compares the version of the requested test dataset with the version of climada itself and selects the most appropriate dataset. In this way a test file can be updated without the need of changing the code of the unittest. [#822](https://github.com/CLIMADA-project/climada_python/pull/822)
130
+
- Explicitly require `pyproj` instead of `proj` (the latter is now implicitly required) [#845](https://github.com/CLIMADA-project/climada_python/pull/845)
131
+
132
+
### Fixed
133
+
134
+
-`Hazard.from_xarray_raster` now stores strings as default values for `Hazard.event_name`[#795](https://github.com/CLIMADA-project/climada_python/pull/795)
135
+
- Fix the dist_approx util function when used with method="geosphere" and log=True and points that are very close. [#792](https://github.com/CLIMADA-project/climada_python/pull/792)
136
+
-`climada.util.yearsets.sample_from_poisson`: fix a bug ([#819](https://github.com/CLIMADA-project/climada_python/issues/819)) and inconsistency that occurs when lambda events per year (`lam`) are set to 1. [[#823](https://github.com/CLIMADA-project/climada_python/pull/823)]
137
+
- In the TropCyclone class in the Holland model 2008 and 2010 implementation, a doublecounting of translational velocity is removed [#833](https://github.com/CLIMADA-project/climada_python/pull/833)
138
+
-`climada.util.test.test_finance` and `climada.test.test_engine` updated to recent input data from worldbank [#841](https://github.com/CLIMADA-project/climada_python/pull/841)
139
+
- Set `nodefaults` in Conda environment specs because `defaults` are not compatible with conda-forge [#845](https://github.com/CLIMADA-project/climada_python/pull/845)
140
+
- Avoid redundant calls to `np.unique` in `Impact.impact_at_reg`[#848](https://github.com/CLIMADA-project/climada_python/pull/848)
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,26 @@
1
1
# CLIMADA Contribution Guide
2
2
3
-
Thank you for contributing to CLIMADA!
3
+
We welcome any contribution to CLIMADA and want to express our thanks to everybody who contributes.
4
4
5
-
## Overview
5
+
## What Warrants a Contribution?
6
+
7
+
Anything!
8
+
For orientation, these are some categories of possible contributions we can think of:
9
+
10
+
***Technical problems and bugs:** Did you encounter a problem when using CLIMADA? Raise an [issue](https://github.com/CLIMADA-project/climada_python/issues) in our repository, providing a description or ideally a code replicating the error. Did you already find a solution to the problem? Please raise a pull request to help us resolve the issue!
11
+
***Documentation and Tutorial Updates:** Found a typo in the documentation? Is a tutorial lacking some information you find important? Simply fix a line, or add a paragraph. We are happy to incorporate you additions! Please raise a pull request!
12
+
***New Modules and Utility Functions:** Did you create a function or an entire module you find useful for your work? Maybe you are not the only one! Feel free to simply raise a pull request for functions that improve, e.g., plotting or data handling. As an entire module has to be carefully integrated into the framework, it might help if you talk to us first so we can design the module and plan the next steps. You can do that by raising an issue or starting a [discussion](https://github.com/CLIMADA-project/climada_python/discussions) on GitHub.
13
+
14
+
A good place to start a personal discussion is our monthly CLIMADA developers call.
15
+
Please contact the [lead developers](https://wcr.ethz.ch/research/climada.html) if you want to join.
16
+
17
+
## Why Should You Contribute?
18
+
19
+
* You will be listed as author of the CLIMADA repository in the [AUTHORS](AUTHORS.md) file.
20
+
* You will improve the quality of the CLIMADA software for you and for everybody else using it.
21
+
* You will gain insights into scientific software development.
22
+
23
+
## Minimal Steps to Contribute
6
24
7
25
Before you start, please have a look at our [Developer Guide][devguide].
Copy file name to clipboardExpand all lines: README.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,13 +21,14 @@ This is the Python (3.9+) version of CLIMADA - please see [here](https://github.
21
21
## Getting started
22
22
23
23
CLIMADA runs on Windows, macOS and Linux.
24
-
The released versions of the CLIMADA core can be installed directly through Anaconda:
24
+
The released versions of CLIMADA are available from [conda-forge](https://anaconda.org/conda-forge/climada).
25
+
Use the [Mamba](https://mamba.readthedocs.io/en/latest/) package manager to install it:
25
26
26
27
```shell
27
-
conda install -c conda-forge climada
28
+
mamba install -c conda-forge climada
28
29
```
29
30
30
-
It is **highly recommended** to install CLIMADA into a **separate**Anaconda environment.
31
+
It is **highly recommended** to install CLIMADA into a **separate**Conda environment.
31
32
See the [installation guide](https://climada-python.readthedocs.io/en/latest/guide/install.html) for further information.
32
33
33
34
Follow the [tutorials](https://climada-python.readthedocs.io/en/stable/tutorial/1_main_climada.html) in a Jupyter Notebook to see what can be done with CLIMADA and how.
@@ -61,7 +62,9 @@ Please use the following logo if you are presenting results obtained with or thr
61
62
62
63
## Contributing
63
64
64
-
See the [Contribution Guide](CONTRIBUTING.md).
65
+
We welcome any contribution to this repository, be it bugfixes and other code changes and additions, documentation improvements, or tutorial updates.
66
+
67
+
If you would like to contribute, please refer to our [Contribution Guide](CONTRIBUTING.md).
0 commit comments