Revision history [back]
 | 1 | initial version |
Interesting, I like the powerpoint idea. I often need to generate SLDs showing results of overload violations under different contingencies for reports. When there are a lot of overloads it can be very tedious to manually generate an SLD for each one. So I made a python script to do it :)
I use a python script ran from inside the GUI with a SLD and case already open. The code reads and parses the ".con" file used in ACCC. Using the contingency definitions in the ".con" file it applies the contingency to the case, solves, refreshes the open SLD, saves a pdf of it, then reload the original case and repeat for the next contingency. I use sliderpy to add a title to each SLD with the respective contingency name read from the ".con" file before saving the SLD pdf.
Prior to running the code, I make sure the SLD is setup with any diagram annotation or contouring settings I desire in my output files.
Couple issues: user needs to ensure solution settings used in ACCC and SLD automation are same. extra coding is needed to handle dispatch mode, induction machine stalls, and load throwover if required
| | 2 | No.2 Revision |
Interesting, I like the powerpoint idea. I often need to generate SLDs showing results of overload violations under different contingencies for reports. When there are a lot of overloads it can be very tedious to manually generate an SLD for each one. So I made a python script to do it :)
I use a python script ran from inside the GUI with a SLD and case already open. The code reads and parses the ".con" file used in ACCC. Using the contingency definitions in the ".con" file it applies the contingency to the case, solves, refreshes the open SLD, saves a pdf of it, then reload the original case and repeat for the next contingency. I use sliderpy to add a title to each SLD with the respective contingency name read from the ".con" file before saving the SLD pdf.
Prior to running the code, I make sure the SLD is setup with any diagram annotation or contouring settings I desire in my output files.
Couple issues:
user needs to ensure solution settings used in ACCC and SLD automation are same.
extra coding is needed to handle dispatch mode, induction machine stalls, and load throwover if required
