Revision history [back]
 | 1 | initial version |
pssarrays accc_solution mvaflow directon/sign
The mvaflow array returned by pssarrays.accc_solution() appears to not always return flow direction calculated in the same way.
I'm monitoring ~2000 branches and performing ~1000 contingencies. For each contingency, there are 5-10 branches that show a flow direction change that isn't correct. Taking the contingency manually in the case shows that the flow direction did not change.
For example:
In the 'BASE CASE' contingency, branch 100-200-1 shows a mvaflow of -168.34.
In 'CONTINGENCY 1', branch 100-200-1 shows a mvaflow of 169.32.
Opening the case will show that the magnitude is correct in both cases, but the direction should be the same.
Is this a known issue with a solution?
| | 2 | No.2 Revision |
pssarrays accc_solution mvaflow directon/sign
The mvaflow array returned by pssarrays.accc_solution() appears to not always return flow direction calculated in the same way.
I'm monitoring ~2000 branches and performing ~1000 contingencies. For each contingency, there are 5-10 branches that show a flow direction change that isn't correct. Taking the contingency manually in the case shows that the flow direction did not change.
For example:
In the 'BASE CASE' contingency, branch 100-200-1 shows a mvaflow of -168.34.
In 'CONTINGENCY 1', branch 100-200-1 shows a mvaflow of 169.32.
Opening the case will show that the magnitude is correct in both cases, but the direction should be the same.
Is this a known issue with a solution?
