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
- Added optional parameter to `geo_im_from_array`, `plot_from_gdf`, `plot_rp_imp`, `plot_rp_intensity`,
19
+
`plot_intensity`, `plot_fraction`, `_event_plot` to mask plotting when regions are too far from data points [#1047](https://github.com/CLIMADA-project/climada_python/pull/1047). To recreate previous plots (no masking), the parameter can be set to None.
20
+
- Added instructions to install Climada petals on Euler cluster in `doc.guide.Guide_Euler.ipynb`[#1029](https://github.com/CLIMADA-project/climada_python/pull/1029)
21
+
22
+
-`ImpactFunc` and `ImpactFuncSet` now support equality comparisons via `==`[#1027](https://github.com/CLIMADA-project/climada_python/pull/1027)
-`Hazard.local_exceedance_intensity`, `Hazard.local_return_period` and `Impact.local_exceedance_impact`, `Impact.local_return_period`, using the `climada.util.interpolation` module: New default (no binning), binning on decimals, and faster implementation [#1012](https://github.com/CLIMADA-project/climada_python/pull/1012)
30
+
- World Bank indicator data is now downloaded directly from their API via the function `download_world_bank_indicator`, instead of relying on the `pandas-datareader` package [#1033](https://github.com/CLIMADA-project/climada_python/pull/1033)
31
+
-`Exposures.write_hdf5` pickles geometry data in WKB format, which is faster and more sustainable. [#1051](https://github.com/CLIMADA-project/climada_python/pull/1051)
32
+
- The online documentation has been completely overhauled, now uses PyData theme: [#977](https://github.com/CLIMADA-project/climada_python/pull/977)
33
+
20
34
### Fixed
21
35
36
+
- NaN plotting issues in `geo_im_from_array`[#1038](https://github.com/CLIMADA-project/climada_python/pull/1038)
37
+
- Broken ECMWF links in pydoc of `climada.hazard.storm_europe` relocated. [#944](https://github.com/CLIMADA-project/climada_python/pull/944)
-`climada.hazard.tc_tracks.TCTracks.subset_years` function [#1023](https://github.com/CLIMADA-project/climada_python/pull/1023)
77
95
-`climada.hazard.tc_tracks.TCTracks.from_FAST` function, add Australia basin (AU) [#993](https://github.com/CLIMADA-project/climada_python/pull/993)
78
96
- Add `osm-flex` package to CLIMADA core [#981](https://github.com/CLIMADA-project/climada_python/pull/981)
79
-
-`doc.tutorial.climada_entity_Exposures_osm.ipynb` tutorial explaining how to use `osm-flex`with CLIMADA
97
+
-`doc.tutorial.climada_entity_Exposures_osm.ipynb` tutorial explaining how to use `osm-flex`with CLIMADA
80
98
-`climada.util.coordinates.bounding_box_global` function [#980](https://github.com/CLIMADA-project/climada_python/pull/980)
81
99
-`climada.util.coordinates.bounding_box_from_countries` function [#980](https://github.com/CLIMADA-project/climada_python/pull/980)
82
100
-`climada.util.coordinates.bounding_box_from_cardinal_bounds` function [#980](https://github.com/CLIMADA-project/climada_python/pull/980)
@@ -108,8 +126,8 @@ Removed:
108
126
- the _geometry_ column of the inherent `GeoDataFrame` is set up at initialization
109
127
- latitude and longitude column are no longer present there (the according arrays can be retrieved as properties of the Exposures object: `exp.latitude` instead of `exp.gdf.latitude.values`).
110
128
-`Exposures.gdf` has been renamed to `Exposures.data` (it still works though, as it is a property now pointing to the latter)
111
-
- the `check` method does not add a default "IMPF_" column to the GeoDataFrame anymore
112
-
- Updated IBTrACS version from v4.0 to v4.1 ([#976](https://github.com/CLIMADA-project/climada_python/pull/976)
129
+
- the `check` method does not add a default `'IMPF_'` column to the GeoDataFrame anymore
130
+
- Updated IBTrACS version from v4.0 to v4.1 [#976](https://github.com/CLIMADA-project/climada_python/pull/976)
113
131
- Fix xarray future warning in TCTracks for .dims to .sizes
114
132
- Fix hazard.concatenate type test for pathos pools
-`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)
192
210
-`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)
193
211
- Split `climada.hazard.trop_cyclone` module into smaller submodules without affecting module usage [#911](https://github.com/CLIMADA-project/climada_python/pull/911)
212
+
-`yearly_steps` parameter of `TropCyclone.apply_climate_scenario_knu` has been made explicit [#991](https://github.com/CLIMADA-project/climada_python/pull/991)
194
213
195
214
### Fixed
196
215
@@ -261,17 +280,17 @@ Added:
261
280
262
281
Updated:
263
282
264
-
-`contextily` >=1.3 → >=1.5
265
-
-`dask` >=2023 → >=2024
266
-
-`numba` >=0.57 → >=0.59
267
-
-`pandas` >=2.1 → >=2.1,<2.2
268
-
-`pint` >=0.22 → >=0.23
269
-
-`scikit-learn` >=1.3 → >=1.4
270
-
-`scipy` >=1.11 → >=1.12
271
-
-`sparse` >=0.14 → >=0.15
272
-
-`xarray` >=2023.8 → >=2024.1
273
-
-`overpy` =0.6 → =0.7
274
-
-`peewee` =3.16.3 → =3.17.1
283
+
-`contextily` >=1.3 → >=1.5
284
+
-`dask` >=2023 → >=2024
285
+
-`numba` >=0.57 → >=0.59
286
+
-`pandas` >=2.1 → >=2.1,<2.2
287
+
-`pint` >=0.22 → >=0.23
288
+
-`scikit-learn` >=1.3 → >=1.4
289
+
-`scipy` >=1.11 → >=1.12
290
+
-`sparse` >=0.14 → >=0.15
291
+
-`xarray` >=2023.8 → >=2024.1
292
+
-`overpy` =0.6 → =0.7
293
+
-`peewee` =3.16.3 → =3.17.1
275
294
276
295
Removed:
277
296
@@ -280,7 +299,7 @@ Removed:
280
299
### Added
281
300
282
301
- 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)
283
-
- Read and Write methods to and from csv files for the `DiscRates` class. [#818](ttps://github.com/CLIMADA-project/climada_python/pull/818)
302
+
- Read and Write methods to and from csv files for the `DiscRates` class. [#818](https://github.com/CLIMADA-project/climada_python/pull/818)
284
303
- 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)
285
304
- 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)
286
305
- Add reset_frequency option for the impact.select() function. [#847](https://github.com/CLIMADA-project/climada_python/pull/847)
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,11 @@ For orientation, these are some categories of possible contributions we can thin
12
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
13
14
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.
15
+
Please contact the [lead developers](https://climada.ethz.ch/team/) if you want to join.
16
16
17
17
## Why Should You Contribute?
18
18
19
-
* You will be listed as author of the CLIMADA repository in the [AUTHORS](AUTHORS.md) file.
19
+
* You will be listed as author of the CLIMADA repository in the [AUTHORS][authors] file.
20
20
* You will improve the quality of the CLIMADA software for you and for everybody else using it.
21
21
* You will gain insights into scientific software development.
22
22
@@ -40,7 +40,7 @@ To contribute follow these steps:
40
40
```bash
41
41
pylint
42
42
```
43
-
6. Add your name to the [AUTHORS](AUTHORS.md) file.
43
+
6. Add your name to the [AUTHORS][authors] file.
44
44
7. Push your updates to the remote repository:
45
45
46
46
```bash
@@ -83,4 +83,5 @@ It also contains a checklist for both pull request authors and reviewers to guid
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ CLIMADA is divided into two parts (two repositories):
16
16
1. the core [climada_python](https://github.com/CLIMADA-project/climada_python) contains all the modules necessary for the probabilistic impact, the averted damage, uncertainty and forecast calculations. Data for hazard, exposures and impact functions can be obtained from the [data API](https://github.com/CLIMADA-project/climada_python/blob/main/doc/tutorial/climada_util_api_client.ipynb). [Litpop](https://github.com/CLIMADA-project/climada_python/blob/main/doc/tutorial/climada_entity_LitPop.ipynb) is included as demo Exposures module, and [Tropical cyclones](https://github.com/CLIMADA-project/climada_python/blob/main/doc/tutorial/climada_hazard_TropCyclone.ipynb) is included as a demo Hazard module.
17
17
2. the petals [climada_petals](https://github.com/CLIMADA-project/climada_petals) contains all the modules for generating data (e.g., TC_Surge, WildFire, OpenStreeMap, ...). Most development is done here. The petals builds-upon the core and does not work as a stand-alone.
18
18
19
-
It is recommend for new users to begin with the core (1) and the [tutorials](https://github.com/CLIMADA-project/climada_python/tree/main/doc/tutorial) therein.
19
+
For new users, we recommend to begin with the core (1) and the [tutorials](https://github.com/CLIMADA-project/climada_python/tree/main/doc/tutorial) therein.
20
20
21
-
This is the Python (3.9+) version of CLIMADA - please see [here](https://github.com/davidnbresch/climada) for backward compatibility with the MATLAB version.
21
+
This is the Python version of CLIMADA - please see [here](https://github.com/davidnbresch/climada) for backward compatibility with the MATLAB version.
0 commit comments