Software Patches

May 31, 2017

Features and Improvements

  • Auxiliary Files (SCRIPT and DATA Sections): Added script command UpdateIslandsAndBusStatus. This is used to update system topology at the user's whim. Usually this is only done in specific spots and often requires solving the power flow. Users might want to do this without a power flow solution.
  • Available Transfer Capability (ATC) Tool: Added a new field called Transfer Limiter Result to the ATC Scenario table. This allows access to the value that is shown in the Results table when running multiple scenarios. The ATC Options Field to Show value must be changed to change the value that is shown in this field.
  • Contingency Analysis Tool: When using the Solve and Set as Reference option for a contingency, a prompt will no appear asking the user if they want to continue with this operation.
    Yes - solve the contingency and set the contingency reference to the state after the contingency is solved.
    No - do not solve the contingency and do not set the contingency reference state.
    Yes to All - solve the contingency and set the contingency reference to the state after the contingency is solved. This will then be done for each subsequent call to this option. The prompt will appear again after the contingency dialog is closed and reopened again.
  • Contingency Analysis Tool: The contingency violation field Element (using labels) is meant to show the element in the violation using its label if there is one available and if not it will revert to identifying the element the same as is done in the Element field, which is by name and number. For Custom Monitors this behavior was different. If a label existed for the violated element nothing was being written. If a label didn't exist then the default of using the same entry as the Element field was used. This doesn't make sense and there shouldn't be any reason why we don't show Custom Monitors with labels as well. This field is just informational and we don't use it for identifying when creating a violation object. We have changed the behavior so that we will see the label if one exists even if this is a Custom Monitor.
  • Contingency Analysis Tool: Added optional parameter SaveDependencies to CTGWriteAllOptions and CTGWriteResultsAndOptions script commands. Setting this to YES will also save all objects needed to define the selected objects.
  • Contingency Analysis Tool: When saving RAS and related info and auxiliary file from dependency explorer always use the concise format.
  • Sensitivity Calculations: Added option on LODF dialog to calculate line closure sensitivities based on either the post-closure flow (LCDF) or pre-closure flow (MLCDF).
  • Sensitivity Calculations: Added optional parameter called PostClosureLCDF with CalculateLODF([BRANCH nearbusnum farbusnum ckt], LinearMethod, PostClosureLCDF) script command. YES means to calculate based on post-closure flow (LCDF) and NO means to calculate based on pre-closure flow (MLCDF).
  • Sensitivity Calculations: Added optional parameter called PostClosureLCDF with CalculateLODFMatrix(WhichOnes, filterProcess, filterMonitor, MonitorOnlyClosed, LinearMethod, filterMonitorInterface, PostClosureLCDF) script command. YES means to calculate based on post-closure flow (LCDF) and NO means to calculate based on pre-closure flow (MLCDF).
  • Transient Stability: If a user chooses NOT to store results to RAM but also has configured a plot to automatically create a JPEG or any picture format.
    1. Internally we automatically detect this and then store any results to RAM that are part of a plot marked for storing an image.
    2. After the images are auto saved, we would clear out the RAM results.
  • Bug Fixes

    • Distributed Computation: Fixed a bug with Distributed CTG; if a main post contingency AUX file was specified, it wasn't being handled properly, which in some cases would lead to remote instance failure. This behavior has been resolved.
    • Transient Stability: Fixed how the Distribution Equivalent initialization works when Fb=0. Ironically this should be the easiest initialization but it was not handling the Mvars exactly correct.
    • Transient Stability: Modified REPC_A so that any value entered for dbd is interpreted as abs(dbd). Only positive numbers make sense here.
    • Transient Stability: Modified REPCA1 so that any value entered for dbd1 is interpreted as -abs(dbd1). Similarly dbd2 is interpreted as +abs(dbd2). This is because only those signs make sense for that input parameters.
    • Transient Stability: Fixed error with CIM5 and CIM6 when using the Tnom parameter as part of performing motor starting. This was not functioning correctly and resulting in the simulation aborting when attempting to start a CIM5 or CIM6 motor.
    • Transient Stability: modified the MOTORW, MOTORX, and MOTOR_CMP motor models so that when they are initialized for an out of service load we set the nominal Torque to Tnom = 1.0. Previously you could close in these models and see the start-up torque, but the motor would then settle out to 0.0 MWs because the actually torque on the motor was zero. Normally the nominal torque for an online motor is calculated as part of initializing a motor. This can not be done when the motor is out of service. A special parameter of the CIM5 and CIM6 motor models (Tnom) can be set by the user to specify this, however for the MOTORW, MOTORX, and MOTOR_CMP models there is no Tnom parameter. We now assume a value of 1.0 per unit.