Ivan Ruiz Manuel
Ivan Ruiz Manuel
Once the industry processing module is completed, add the following: - [ ] documentation so that usage is clearly defined. - [ ] carrier renaming step so users can control...
Re-runs seem to generate different annual demands than those in the pre-builts of the model. Most of these are marginal, but in some cases they can be significant (>10%, so...
Fixes #624 ## Summary of changes in this pull request * The backend is now a module that shares only what is necessary to `model.py`. * Backend fetching is now...
### What happened? This issue came up during debugging for #625. Our current approach to the model schema introduces potential confusions for users, since schema defaults for modes that are...
### What can be improved? Our current implementation of different backends is a bit fickle. ```python _BACKENDS: dict[str, Callable] = {"pyomo": PyomoBackendModel} ... backend = self._BACKENDS[backend_name](input, self.math, **updated_build_config) ``` -...
Fixes #619 ## Summary of changes in this pull request * Introduces better handling of Calliope configuration (by differentiating between configuration from files, overrides and runtime). * Limits backend access...
### What happened? # What is happening? Our current approach of handling data and configuration updates is inconsistent across the code: - Sometimes configuration updates are passed to `model._model_data` (e.g.,...
### What happened? Calliope v0.7 keeps most of its attributes within `model._model_data.attrs[]` in the form of dictionaries. However, model math and config are replicated in `model.math` and `model.config`. This introduces...
Fixes #606 ## Summary of changes in this pull request * Introduces a new parameter (`config.init.base_math`) that will tell the model to skip base math if set to `False`. *...
### What can be improved? As of now, builds custom math "on top" of the pre-defined math. While this is good to simplify the way users interact with Calliope, it...