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

cannot instantiate abstract class BmiHeat with abstract methods... #2

Open
SiccarPoint opened this issue May 18, 2020 · 1 comment
Open

Comments

@SiccarPoint
Copy link

Hi Katy,

This is awesome! But I've hit a wall with running the notebook. The Dakota run launched by the shell script (ln 9) is failing for me. A little poking reveals this is a problem with the driver, as the Dakota .log records:

Traceback (most recent call last):
  File "driver.py", line 84, in <module>
    h = Heat()
TypeError: Can't instantiate abstract class BmiHeat with abstract methods get_grid_face_edges, get_input_item_count, get_output_item_count

Error: cannot open results file "MULTIDIM_PARAM/run.1/results.out" for evaluation 1

This is apparently an issue in the driver code. I checked I can import BmiHeat itself just fine, but if I try h = heat() as at line 84, I get that same TypeError Dakota is reporting:

In [2]: from heat import BmiHeat as heat                                        

In [3]: h = heat()                                                              
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-3-b4884c508061> in <module>
----> 1 h = heat()

TypeError: Can't instantiate abstract class BmiHeat with abstract methods get_grid_face_edges, get_input_item_count, get_output_item_count

I'm in the conda env created from environment_everything_but_dakota.yml, so should not be a local versioning issue.

I've never seen python complain about abstract methods before, so struggling to diagnose.

@SiccarPoint
Copy link
Author

...having played with this for 10 more mins, I suspect that upstream changes in bumpy have broken the code. i.e., more implemented classes are now required (SO MANY!) I can fix this myself I think...

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

No branches or pull requests

1 participant