Skip to content
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

Facilitate compability with oemof-solph v4.0 #90

Merged
merged 61 commits into from
Aug 13, 2020
Merged

Conversation

smartie2076
Copy link
Collaborator

Fix #32

@smartie2076 smartie2076 added the enhancement New feature or request label Jul 6, 2020
@smartie2076 smartie2076 self-assigned this Jul 6, 2020
@smartie2076
Copy link
Collaborator Author

Left to do before merging: Check that outputs with oemof==0.2.2 is the same as with oemof-solph==0.4.0.

@smartie2076 smartie2076 marked this pull request as draft July 9, 2020 19:23
@smartie2076
Copy link
Collaborator Author

Update to pyomo==5.7!

@smartie2076 smartie2076 changed the title Facilitate compability with oemof v4.0 Facilitate compability with oemof-solph v4.0 Jul 21, 2020
@smartie2076
Copy link
Collaborator Author

@santiagoinfantinom I did some major updates, also regarding the oemof version used. Please uninstall oemof and install the new requirements. Update your banches ASAP, as there are many changes. I will probably will create another release soon.

@smartie2076 smartie2076 marked this pull request as ready for review August 13, 2020 10:38
@smartie2076 smartie2076 merged commit 20b1f82 into dev Aug 13, 2020
@smartie2076 smartie2076 deleted the patch/oemof-v4-0 branch August 13, 2020 14:25
@santiagoinfantinom
Copy link
Collaborator

@smartie2076 Ok. I'm going to uninstall oemof and reinstall the requirements. After that i'll merge dev into the other branches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

oemof version needs to be updated from v0.2.2 to v0.4
2 participants