-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update branch adapt-costs-for-multi-year-periods to v0.5.2.dev1 #1069
Merged
SabineHaas
merged 100 commits into
features/adapt-costs-for-multi-year-periods
from
fix/update-branch_adapt-costs-for-multi-year-periods_to_052ev1_and_fix
May 29, 2024
Merged
Update branch adapt-costs-for-multi-year-periods to v0.5.2.dev1 #1069
SabineHaas
merged 100 commits into
features/adapt-costs-for-multi-year-periods
from
fix/update-branch_adapt-costs-for-multi-year-periods_to_052ev1_and_fix
May 29, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rizon in invest flow
…lculation of present values
The test seems to be designed to test if warnings can be turned off. However, the operation never created one.
* pytest.approx instead of roundin * series.iloc[int] instead of series[int]
This reverts commit 2129b0a.
As described in #979, timeincrement currently needs to be set for multi period optimisation models.
…s-parameter Remove obsolete fixed costs parameter for GenericCAES initialization
…es-of-multi-period-investments Account for remaining values in multi-period models
Fix/eliminate warnings
The time unit currently is hardcoded to be hours. The documentation now reflects that.
The constraints are actually defined in time steps. (The documentation asked for integers before, so it could be seen from the context.)
Fix/specific timeincrement docs
It is now mandatory to do so to geht the docs built.
This is now mandatory to have RTD builds.
The format seems to be different from the one below.
make BasicModel consider all constraint groups
…ulti-year-periods_to_052ev1_and_fix
As this merges into a feature branch: Do you want a review or should we just merge? |
I would just merge now. This branch was just to be careful as solph had developed further since these changes had been made. |
SabineHaas
merged commit May 29, 2024
411adb8
into
features/adapt-costs-for-multi-year-periods
6 of 10 checks passed
SabineHaas
deleted the
fix/update-branch_adapt-costs-for-multi-year-periods_to_052ev1_and_fix
branch
May 29, 2024 13:02
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v5.0.2.dev0
tov5.0.2.dev1
, as the latter is the version required in oemof.tabular