09.03.2013 Views

Simulator 16 User Guide - PowerWorld

Simulator 16 User Guide - PowerWorld

Simulator 16 User Guide - PowerWorld

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SCOPF Control<br />

The control dialog allows the user to manually or automatically run a SCOPF simulation and visualize<br />

the execution of the simulation. The SCOPF solution process involves three steps: base case solution<br />

and initialization, contingency analysis, and SCOPF iterations.<br />

Run Full Security Constrained OPF<br />

Press this button to run the three steps of the SCOPF solution automatically. The SCOPF will solve<br />

the base case using the selected method, will use the currently stored list of contingencies during<br />

the contingency analysis step, and will take the CA results and sensitivities to iterate in order to<br />

obtain the optimal solution that minimizes cost and enforces contingency violations.<br />

Maximum Number of Outer Loop Iterations<br />

©2011 <strong>PowerWorld</strong> Corporation<br />

Options<br />

Indicates the number of maximum outer loop iterations. The outer loop iterations determines how<br />

many times the contingency analysis will be re-run following a successful SCOPF dispatch. In this<br />

manner, <strong>Simulator</strong> will look for new violations that may occur due to the new generation dispatch.<br />

Consider Binding Contingent Violations from Last SCOPF Solution<br />

When checked, this option ensures that the contingent violations from the last SCOPF solution are<br />

included in the current SCOPF solution. This option is helpful in preventing the SCOPF from hunting<br />

between having a constraint binding in one solution, and resolving with it not binding in a later<br />

solution because it was previously remedied. This option should generally always be checked, unless<br />

the user is sure that the previous solution has no bearing on the current solution, such as having<br />

made major changes to the system since the previous solution.<br />

Initialize SCOPF with Previously Binding Constraints<br />

When checked, this option results in the SCOPF solution process starts with the exact same LP<br />

tableau from the last solution. This can make for fairly fast solutions (recognizing that the<br />

contingency analysis needs to be resolved) when the changes to the system are small. <strong>Simulator</strong><br />

automatically uses this option when doing multiple outer loops of the SCOPF. This option allows the<br />

user to solve the outer loops (set the outer loop counter to 1) by repeatedly solving the SCOPF<br />

manually, potentially making modifications between solutions if desired.<br />

Set Solution as Contingency Analysis Reference Case<br />

Check this field to set the solution of the SCOPF as the contingency analysis reference. If the system<br />

has enough controls to remove all the contingency violations, a rerun of the contingency analysis<br />

using the SCOPF solution as the reference should report no branch violations.<br />

Maximum Number of Contingency Violations Allow Per Element<br />

Specify the maximum number of contingency violations that the SCOPF analysis should allow per<br />

element. After completing the power flow solutions for the base case and the contingencies, only<br />

this number of contingency violations per element are then passed to the linear programming<br />

algorithm. The assumption is that if you fix the 10 worst contingency violations for an element then<br />

the others will also be fixed.<br />

Basecase Solution Method<br />

Specifies whether the solution of the base case is performed using the power flow algorithm or the<br />

optimal power flow algorithm. The selection will affect the initial conditions of the system and<br />

consequently the contingency analysis results and the sensitivities used by the LP solver. Currently<br />

1311

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!