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

Error: Cannot run example "simple_dispatch" #464

Closed
henhuy opened this Issue Mar 15, 2018 · 6 comments

Comments

Projects
None yet
6 participants
@henhuy
Copy link
Contributor

henhuy commented Mar 15, 2018

We just tried to simply run:
oemof_examples/examples/oemof_2.0/simple_dispatch/simple_dispatch.py
within a fresh environment and oemof installed via
pip install oemof
But the following error occured:
"Index '(<oemof.solph.network.Bus object at 0x7f1681a639a8>, 0)' is not valid for indexed component 'Bus.balance'"
Any hints?

@uvchik

This comment has been minimized.

Copy link
Member

uvchik commented Mar 15, 2018

Which commit or version?

@uvchik

This comment has been minimized.

Copy link
Member

uvchik commented Mar 15, 2018

Sorry, if you have used pip install oemof you have v0.2.0 installed.

This is an Pyomo issue. Use pip install pyomo==5.3.

@uvchik

This comment has been minimized.

Copy link
Member

uvchik commented Mar 15, 2018

This issuee will be fixed with the release of v0.2.1 which is delayed due to illness. It will be released in a few days. Afterwards you can update pyomo again using pip install pyomo --upgrade.

@uvchik uvchik removed the help wanted label Mar 15, 2018

@uvchik uvchik added this to the v0.2.1 milestone Mar 15, 2018

@henhuy

This comment has been minimized.

Copy link
Contributor Author

henhuy commented Mar 15, 2018

Works again! thank you!

@uvchik uvchik closed this Mar 15, 2018

@uvchik

This comment has been minimized.

Copy link
Member

uvchik commented Mar 16, 2018

I reopen this as a reminder.

I suggest to limit the version of each required package in the setup.py to the most actual (working) version on every oemof release. The reason is that otherwise pip install oemof will always install the most actual version of each package at the moment of the installation. This behaviour may lead to errors (as seen above) if the the API of one required package changed since the last oemof release.

@henhuy and @ckaldemeyer already agree on that.

@uvchik

This comment has been minimized.

Copy link
Member

uvchik commented Mar 19, 2018

Closed in favour of #465.

@uvchik uvchik closed this Mar 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment