Revision history [back]
 | 1 | initial version |
Simulation time of Doing Power Flow Cyclically
Hello everyone,
I met a time issue when doing the power flow cyclically. I use python 2.7.13 (in VS Code) to control PSS/E executing the power flow process cyclically and export the overloading report. During testing, I read the csv file of branch and set each branch out-of-service in each run.The number of branch is 1790, and I set executing the process for 12 times (which means "half a day"). Thus, I expect that it will export (12*1790) overloading reports and tell me which branches out-of-service will cause other branches overloading.
Then, I find that it takes for over 18 hours to complete the entire 12 times simulation. In first run, it took around 5 mins, then second run took 7 mins, and the simulation time in each run is irregularly and extremely increasing. The followings are the simulation time in per run (min): [4.454, 6.7685, 13.7459, 25.1792, 39.6676, 59.3887, 85.0343, 112.3582, 143.5624, 178.5427, 205.1365, 219.4923]
Since each run do the same work (csv file is same to verify each run gives the same results), I could not figure out the problem during simulation: 1) why each run took different time to export the report, and 2) the time is extremely increasing? Does anyone meet this problem before? and know the reason?
| | 2 | No.2 Revision |
Simulation time of Doing Power Flow Cyclically
Hello everyone,
I met a time issue when doing the power flow cyclically. I use python 2.7.13 (in VS Code) to control PSS/E executing the power flow process cyclically and export the overloading report. During testing, I read the csv file of branch and set each branch out-of-service in each run.The number of branch is 1790, and I set executing the process for 12 times (which means "half a day"). Thus, I expect that it will export (12*1790) overloading reports and tell me which branches out-of-service will cause other branches overloading.
Then, I find that it takes for over 18 hours to complete the entire 12 times simulation. In first run, it took around 5 mins, then second run took 7 mins, and the simulation time in each run is irregularly and extremely increasing. The followings are the simulation time in per run (min): [4.454, 6.7685, 13.7459, 25.1792, 39.6676, 59.3887, 85.0343, 112.3582, 143.5624, 178.5427, 205.1365, 219.4923]
Since each run do the same work (csv file is same to verify each run gives the same results), I could not figure out the problem during simulation: 1) why each run took different time to export the report, and 2) the time is extremely increasing? Does anyone meet this problem before? and know the reason?
