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
* Fix typo
* Prefer robust scalar extraction for timestep sizes in aggregation
* Improve docs and error messages
* Update examples
* Use validated timesteps
* Remove unnessesary import
* Use FlowSystem.model instead of FlowSystem.submodel
* Fix Error message
* Improve CHANGELOG.md
* Use self.standard_effect instead of provate self._standard_effect and update docstring
* in calculate_all_conversion_paths, use `collections.deque` for efficiency on large graphs
* Make aggregation_parameters.hours_per_period more robust by using rounding
* Improve import and typos
* Improve docstring
* Use validated timesteps
* Improve error
* Improve warning
* Improve type hint
* Improve CHANGELOG.md: typos, wording and duplicate entries
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,18 +30,18 @@ Please remove all irrelevant sections before releasing.
30
30
Until here -->
31
31
32
32
## [Unreleased] - ????-??-??
33
-
This Release brings Multi-year-investments and stochastic modeling to flixopt.
34
-
Further, IO methods were improved and resampling and selection of parts of the FlowSystem is now possible.
33
+
This release brings multi-yearinvestments and stochastic modeling to flixopt.
34
+
Furthermore, I/O methods were improved, and resampling and selection of parts of the FlowSystem are now possible.
35
35
Several internal improvements were made to the codebase.
36
36
37
37
38
-
####Multi-year-investments
38
+
### Multi-yearinvestments
39
39
A flixopt model might be modeled with a "year" dimension.
40
-
This enables to model transformation pathways over multiple years with several investment decisions
40
+
This enables modeling transformation pathways over multiple years with several investment decisions
41
41
42
-
####Stochastic modeling
42
+
### Stochastic modeling
43
43
A flixopt model can be modeled with a scenario dimension.
44
-
Scenarios can be weighted and variables can be equated across scenarios. This enables to model uncertainties in the flow system, such as:
44
+
Scenarios can be weighted and variables can be equated across scenarios. This enables modeling uncertainties in the flow system, such as:
45
45
* Different demand profiles
46
46
* Different price forecasts
47
47
* Different weather conditions
@@ -52,7 +52,7 @@ Common use cases are:
52
52
53
53
The weighted sum of the total objective effect of each scenario is used as the objective of the optimization.
54
54
55
-
#### Improved Data handling: IO, resampling and more through xarray
55
+
#### Improved Data handling: I/O, resampling and more through xarray
56
56
* IO for all Interfaces and the FlowSystem with round-trip serialization support
57
57
* NetCDF export/import capabilities for all Interface objects and FlowSystem
58
58
* JSON export for documentation purposes
@@ -69,7 +69,7 @@ The weighted sum of the total objective effect of each scenario is used as the o
69
69
70
70
71
71
### Added
72
-
* FlowSystem Restoring: The used FlowSystem is now accessible directly form the results without manual restoring (lazily). All Parameters can be safely accessed anytime after the solve.
72
+
* FlowSystem restoring: The used FlowSystem is now accessible directly from the results without manual restoring (lazily). All parameters can be safely accessed anytime after the solve.
73
73
* FlowResults added as a new class to store the results of Flows. They can now be accessed directly.
74
74
* Added precomputed DataArrays for `size`s, `flow_rate`s and `flow_hour`s.
75
75
* Added `effects_per_component()`-Dataset to Results that stores the direct (and indirect) effects of each component. This greatly improves the evaluation of the impact of individual Components, even with many and complex effects.
@@ -83,7 +83,7 @@ The weighted sum of the total objective effect of each scenario is used as the o
83
83
***BREAKING**: Renamed class `SystemModel` to `FlowSystemModel`
84
84
***BREAKING**: Renamed class `Model` to `Submodel`
85
85
***BREAKING**: Renamed `mode` parameter in plotting methods to `style`
86
-
* FlowSystems can not be shared across multiple Calculations anymore. A copy of the FlowSystem is created instead, making every Calculation independent
86
+
* FlowSystems cannot be shared across multiple Calculations anymore. A copy of the FlowSystem is created instead, making every Calculation independent
87
87
* Each Subcalculation in `SegmentedCalculation` now has its own distinct `FlowSystem` object
88
88
* Type system overhaul - added clear separation between temporal and non-temporal data throughout codebase for better clarity
89
89
* Enhanced FlowSystem interface with improved `__repr__()` and `__str__()` methods
@@ -109,14 +109,12 @@ The weighted sum of the total objective effect of each scenario is used as the o
109
109
110
110
### *Development*
111
111
***BREAKING**: Calculation.do_modeling() now returns the Calculation object instead of its linopy.Model
112
-
***BREAKING**: Renamed class `SystemModel` to `FlowSystemModel`
113
-
***BREAKING**: Renamed class `Model` to `Submodel`
114
112
* FlowSystem data management simplified - removed `time_series_collection` pattern in favor of direct timestep properties
115
113
* Change modeling hierarchy to allow for more flexibility in future development. This leads to minimal changes in the access and creation of Submodels and their variables.
116
114
* Added new module `.modeling`that contains Modelling primitives and utilities
117
115
* Clearer separation between the main Model and "Submodels"
118
116
* Improved access to the Submodels and their variables, constraints and submodels
119
-
* Added __repr__() for Submodels to easily inspect its content
117
+
* Added `__repr__()` for Submodels to easily inspect its content
120
118
* Enhanced data handling methods
121
119
*`fit_to_model_coords()` method for data alignment
122
120
*`fit_effects_to_model_coords()` method for effect data processing
@@ -179,7 +177,7 @@ There are no changes or new features.
179
177
## [2.1.6] - 2025-09-02
180
178
181
179
### Changed
182
-
-`Sink`, `Source` and `SourceAndSink` now accept multiple `flows` as `inputs` and `outputs` instead of just one. This enables to model more use cases using these classes. [[#291](https://github.com/flixOpt/flixopt/pull/291) by [@FBumann](https://github.com/FBumann)]
180
+
-`Sink`, `Source` and `SourceAndSink` now accept multiple `flows` as `inputs` and `outputs` instead of just one. This enables modeling more use cases using these classes. [[#291](https://github.com/flixOpt/flixopt/pull/291) by [@FBumann](https://github.com/FBumann)]
183
181
- Further, both `Sink` and `Source` now have a `prevent_simultaneous_flow_rates` argument to prevent simultaneous flow rates of more than one of their Flows. [[#291](https://github.com/flixOpt/flixopt/pull/291) by [@FBumann](https://github.com/FBumann)]
Copy file name to clipboardExpand all lines: examples/05_Two-stage-optimization/two_stage_optimization.py
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
"""
2
2
This script demonstrates how to use downsampling of a FlowSystem to effectively reduce the size of a model.
3
-
This can be very useful when working with large models or during developement state,
3
+
This can be very useful when working with large models or during development,
4
4
as it can drastically reduce the computational time.
5
5
This leads to faster results and easier debugging.
6
-
A common use case is to do optimize the investments of a model with a downsampled version of the original model, and than fix the computed sizes when calculating th actual dispatch.
6
+
A common use case is to optimize the investments of a model with a downsampled version of the original model, and then fix the computed sizes when calculating the actual dispatch.
7
7
While the final optimum might differ from the global optimum, the solving will be much faster.
0 commit comments