While testing with exported esdl files from the new front-end, I ran into the following exception:
File "/usr/local/lib/python3.8/site-packages/rtctools_heat_network/esdl/esdl_mixin.py", line 1085, in _esdl_to_assets
raise Exception(f"Asset names have to be unique: '{el_name}' already exists")
Exception: Asset names have to be unique: 'Steel-S1-DN-20' already exists
I would expect that the id attribute of each asset from the esdl file would be sufficient.
Is it an option to drop this constraint on the input and use the asset id internally?
I think that would lead to better interoperability between different users of ESDL.
While testing with exported esdl files from the new front-end, I ran into the following exception:
I would expect that the
id
attribute of each asset from the esdl file would be sufficient. Is it an option to drop this constraint on the input and use the asset id internally? I think that would lead to better interoperability between different users of ESDL.ESDL file: TPG Esdl sample.esdl.txt
(Note: Demand asset is still missing a profile within the sample)