-
Notifications
You must be signed in to change notification settings - Fork 70
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
import name 'trapz' from 'scipy.integrate' #657
Comments
Hey @Norah135, I just ran |
@dhblum I really appreciate your quick response. I tried using both an Apple and a Windows device running Docker version 26.1.4, but I'm facing the same issues on both. I downloaded the latest version (6) of BOPTEST from the website and haven't made any changes to the Docker file. |
@dhblum I wanted to ask if you can help me use the BOPTEST API without running it on Docker. I'm facing issues with Docker. I found an example on Colab, but I'm a little confused about how to connect this example with a simple control algorithm to understand how the system works. I am looking for examples similar to what we have in the GitHub repository (the test case and the interface file). Sorry to bother you, but I am new to this field and using the software. I really appreciate any guidance and help from you. |
Ok I've reproduced your error on a MacBook (Intel). This needs to be looked into. I don't know why Docker would be trying to, potentially, use a different version of scipy for Mac OS vs Ubuntu. If you open the colab of the first tutorial listed here, it will take you through using the BOPTEST public web service to test a simple controller. Using the web service, you don't need to build BOPTEST locally. Hopefully that's helpful for you to get started and thanks again for reporting the issue. |
Ok specifying the version of scipy to 1.13.0 in this line fixes this issue. On the MacBook it was operating with scipy v1.14.0, while on Ubuntu it was operating with v1.13.0. Using I could PR this fix and then treat updating package versions to a new issue. But any ideas from anyone why two different scipy versions would be installed in a Docker container depending on Platform under which Docker is operating? @kbenne @javiarrobas @EttoreZ? This might be related to what I'm observing in #655. |
Hi @dhblum, @EttoreZ and @Norah135, Hope this was helpful! |
Hi @dhblum |
Thanks @Jaap-Neven your insight is helpful. In any case, I will specify the version of scipy for now to fix this issue. Looking at removing reliance on scipy in the first place will be another issue. Note this will be included in this existing PR #659, and I'll close this issue when PR is merged. @Norah135 Here is documentation for how test cases are designed: https://ibpsa.github.io/project1-boptest/docs-design/testcasedev.html. Additionally, here is a basic tutorial for putting together a test case: https://github.com/ibpsa/project1-boptest/blob/master/docs/tutorials/tutorial1_developer/BOPTEST_Tutorial1_developer_20230416.pdf. |
Closed by #659. |
I am having an issue deploying the test case in Docker using
Do you have any suggestions on how I can fix it?"TESTCASE=test_case docker-compose up
. Here is an image that describes the problem(cannot import name 'trapz' from 'scipy.integrate').The text was updated successfully, but these errors were encountered: