-
Notifications
You must be signed in to change notification settings - Fork 136
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
Merge dev into integrate_TSAM #1154
Merge dev into integrate_TSAM #1154
Conversation
Release v0.5.3
Release v0.5.3
There was a warning and a comment that having multiple inputs/outputs for one Sink/Source is unintended but should be possible. I think we can remove that "strong reccomendation" as it just works. To not let beginners fall into the trap of having a dangling Sink or Source, like the old warning also might have prevented, inputs and outputs are now explicitly named arguments without a default.
For Python 3.10+, "|" should be used instead of "or", but or is also incorrect for Python 3.9 (a typing.Union can be used). However, as date is superclass of datetime, giving the superclass shuld imply that the childs are also possible.
BaseModel was an unused superclass just for Model. At the moment it is not planned to have other models. Thus, it makes sense to merge both. Signed-off-by: Patrik Schönfeldt <[email protected]>
It seems to be a desired (and tested) feature to do so, but a typical user will probably not want to do this. So, a warning makes sense.
…-warnings-fixes
Note thatthis is just a workaround. chaned casts chould either work or be prohibited.
The test was confusing, as it added a nominal_value to a Sink. This, however, did not cause an error to be raised as the error that was tested before was first.
Allow sinks/sources to have multiple inputs/outputs
…of/oemof-solph into fix-bugs-in-parameter-as-dict
Fix bugs in parameter as dict
Replace assert by pytest use
…o esske-infeasable_message
…om_dev_into_tsam # Conflicts: # src/oemof/solph/flows/_simple_flow_block.py # src/oemof/solph/processing.py
…o_tsam' into pull_request/update_from_dev_into_tsam # Conflicts: # tests/test_scripts/test_solph/test_tsam/test_storage_invest_tsam_integration.py # tests/test_scripts/test_solph/test_tsam/test_storage_tsam_vs_original.py
Hello @p-snft! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:
|
Update the branch for the TSAM mode to current dev.