Open tanushree04 opened 1 year ago
With the caveat that I haven't investigated this issue in any detail, it's possible that addressing #42 will resolve this.
Hi,
A bit of context about why this error message was introduced: previously this invalid phases=0
was being silently ignored and the phases
value was left as the previously set value, or default value (3).
You could see that by running the .dss script and then inspecting the elements through one of the APIs.
This kind of issue is usually a conversion error and blows up sooner or later.
I'd recommend either investigating why phases=0
is being used in the first place (doesn't make much sense but there could be more context I'm not aware). If the intention is to leave phases
at the default value, just removing phases=0
would do that.
To replicate the error:
In the URBANopt cli,
within PVSystems.dss file the following error occurs: PVSystem.solar_1.phases: Value (0) cannot be zero
Complete error on running DISCO
attached PVSystems.dss: