|
1 |
| -## 0.7.0.dev6 |
| 1 | +## 0.7.0.dev6 (2025-03-24) |
2 | 2 |
|
3 | 3 | ### User-facing changes
|
4 | 4 |
|
5 |
| -|new| working SPORES mode, upgraded from v0.6 to include a selection of scoring algorithms. |
| 5 | +|new| working SPORES mode, upgraded from v0.6 to include a selection of scoring algorithms (#716). |
6 | 6 |
|
7 |
| -|new| backend `set_objective` method, to switch between pre-defined objectives. |
| 7 | +|new| backend `set_objective` method, to switch between pre-defined objectives (#716). |
8 | 8 |
|
9 |
| -|changed| coin-or-cbc is now available cross-platform on conda-forge and so is the recommended open-source solver to install a user environment with. |
| 9 | +|changed| |backwards-incompatible| `from` and `to` parameters (to define start and end point of a transmission link) are now `link_from` and `link_to` (#717). |
10 | 10 |
|
11 |
| -|changed| Upper bound pins for dependencies removed where possible, to minimise clashes when using calliope as a dependency in a project. |
| 11 | +|changed| |backwards-incompatible| `operate` and `spores` mode configuration options are now nested within the main configuration (e.g., `build.operate_window` is now `build.operate.window` and `solve.spores_number` is now `solve.spores.number`) (#704). |
12 | 12 |
|
13 |
| -## 0.7.0.dev5 (2024-12-04) |
| 13 | +|changed| coin-or-cbc is now available cross-platform on conda-forge and so is the recommended open-source solver to install a user environment with (#744). |
14 | 14 |
|
15 |
| -### User-facing changes |
| 15 | +|changed| Upper bound pins for dependencies removed where possible, to minimise clashes when using calliope as a dependency in a project (#744). |
| 16 | + |
| 17 | +|changed| |backwards-incompatible| to ensure the model configuration always remains in sync with the results, `kwargs` in `model.build()` and `model.solve()` now directly affect `model.config` (#704) |
| 18 | + |
| 19 | +|changed| `template:` can now be used anywhere within YAML definition files, not just in the `nodes`, `techs` and `data_tables` sections (#719). |
| 20 | + |
| 21 | +|changed| Removed `inheritance` math helper function since we use `base_tech` for abstract base technologies and templates are now applied too early to be available later (#719). |
| 22 | +To refer to template inheritance, set a parameter within a template as all children will share the same value. |
| 23 | + |
| 24 | +### Internal changes |
| 25 | + |
| 26 | +|changed| Moved to using `pydantic` to document and validate our configuration, rather than JSON schema (#704, #717). |
| 27 | + |
| 28 | +|changed| As with base dependencies, moved to pinning lower bound only for development dependencies (#744). |
16 | 29 |
|
17 |
| -|changed| to ensure the model configuration always remains in sync with the results, `kwargs` in `model.build()` and `model.solve()` now directly affect `model.config` |
| 30 | +|changed| Curtailed `calliope.AttrDict` relevance, with I/O moved to `calliope.io` and attribute access moved to `pydantic` models. |
| 31 | +`AttrDict` is still used to merge overrides and templates into the model definition dictionary, before creating the `pydantic` models. |
18 | 32 |
|
19 |
| -|changed| `template:` can now be used anywhere within YAML definition files, not just in the `nodes`, `techs` and `data_tables` sections. |
| 33 | +## 0.7.0.dev5 (2024-12-04) |
| 34 | + |
| 35 | +### User-facing changes |
20 | 36 |
|
21 | 37 | |changed| "An overview of the Calliope terminology" information admonition to remove self-references and improve understandability.
|
22 | 38 | Now also includes a visual depiction of how the different defined components connect together (#699).
|
|
0 commit comments