You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the data model leaves open to some extend, how capacitive and inductive reactive power of assets can be defined. However, introducing just a flag to toggle the behavior is not sufficient, because then all reactive power characteristics would have to provide the same information as well.
Proposal from my side:
The sign of the power factor defines the sign of reactive power: Positive means reactive power is consumed, regardless of if active power is consumed or not
For assets that change between infeed and consumption and if a active power dependent factor shall be used, then the characteristic needs to be defined for negative values as well, if also the reactive power direction is meant to change
It would have the advantage, that it would also work with the definition of characteristics.
The text was updated successfully, but these errors were encountered:
Addition: This approach might bring the drawback of potentially misleading calculations. Typically, if you'd like to calculate active apparent power, you'd directly go ahead and multiply apparent power with power factor. This could then lead to wrong results...
Counterargument: Generally, in PowerSystemDataModel, the given apparent power values also don't reflect the direction of power. E.g. dependent on your preference, you'd need to add a minus sign to all assets feeding in or consuming energy.
Currently, the data model leaves open to some extend, how capacitive and inductive reactive power of assets can be defined. However, introducing just a flag to toggle the behavior is not sufficient, because then all reactive power characteristics would have to provide the same information as well.
Proposal from my side:
It would have the advantage, that it would also work with the definition of characteristics.
The text was updated successfully, but these errors were encountered: