Add tespy and heatpumps model export - #54
Conversation
|
There is currently the issue that the imported models in tespy are not properly configured. There are too many parameters provided. Any ideas why? |
I believe heatpumps does some kind of prerpocessing (i.e. setting up a new class instance of that heat pump and presetting the default boundary conditions). Depending on when you export the Network of the heatpumps class it might have wrong parameter specifications (or it is a bug). In any case, I like the idea and would say just merge the them? So first merge #50, then merge the changes to here, figure out what is the problem with the tespy Network deserialization and execution and then merge this one. |
|
Found it, was a bug in tespy deserialization. I will fix that and make a release. |
Add buttons in streamlit dashboard to export the model as disscussed in #53 as tespy json file or heatpumps json configuration file as implemented in PR #50.
Curretly #50 allows only an export when simulation fails, thats why I added the button in the regular result field. This could also be moved to #50 if preferred.