Open AnkurArohi opened 2 years ago
geofjamg
commented
2 years ago What do you mean by unspecified? zero? Generator with a zero target p are not discarded from calculation but are discarded from slack distribution. So it means that even if network is not balanced, target will remain constante during calculation. Are you asking to not discard from slack distribution, generators with a zero target P ?
AnkurArohi
commented
2 years ago @geofjamg I understand your point but there are certain cases where the generator has zero target P value because it has to be calculated/estimated from power flow algorithm, as it has a potential to produce /have a target P but only that it is not defined in cgmes or so to say it is not specified before.
Hence these generators will take part also in slack distribution or active power distribution.
Hence this is an additional advanced feature, in which the generators which do not have a predefined target P in cgmes can have one after the calculation (like after OPF set points) and its output is written in SV file after power flow.
A suggestion of how it can be executed is also explained in the ticket , it is simply a statistical analysis
Do you want to request a feature or report a bug? Feature
What is the current behavior? If target P of Generator is unspecified the generator is discarded from LoadFlow calculation and if one tried to fix this value to another average value, the load Flow is not able to determine the correct P value / modify it after the iterations, Leading to non convergence
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior? The expected behavior is to let a random value/initial value be allowed for TargetP, and in each LU decomposition or Netwon Raphson iteration let this P value be variable till the Newton Raphson converges, variations could be +-10% after each unsuccessful result
What is the motivation / use case for changing the behavior? When the CGMES file does not provide a TargetP for generators the NR algorithmn just fails, leading to non convergence which should be avoided, also the current OLF is very strictly dependent on the TargetP values of the genarators, so if these values are erroneous, it also leads to false results/non convergence of OLF Load Flow algorithm.
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)