Features and Improvements
- Case Information Displays: Added a new field CountTransformer (Number Of\Transformers ) for both a Bus, Zone, Area, and Substation object to show the number of Transformers attached to the Bus, or at buses inside the groupings.
- Case Information Displays: Added new fields for a Bus object named ZBRGenList, ZBRRegBusList, ZBRRegBusConflict, ZBRVoltSetList, and ZBRVoltSetConflict. These fields are then shown on a new case information display available in the Model Explorer under Solutions Details\Regulating Buses Multiple Local. The fields are populated with information when grouping of buses connected by low impedance branches have multiple generators connected to them. They will then show a list of bus number of regulated buses and a list of voltage setpoint voltages, and if there are multiples of these representing a conflict field will say YES. This can be helpful in debugging conflicting input data that is not as obvious as generators at the same bus having different regulation buses or setpoints.
- File Formats: Simulator Version 24 reads the RAW file field for a Branch and Transformer called NAME as an object label. For many years, PowerWorld has also seen RAW files in particular written out of EMS systems that included special syntax inside of Comment strings at the end of RAW file records. These comments included an object label inside of square brackets. This ad-hoc syntax had been used for years by customers to include labels. The original release of Simulator 24 read both of these locations as a label, but the NAME field was given priority and set as the Primary Label inside Simulator. Users however are finding that the values in the comment are more predictably set as labels, so we have changed it so the ad-hoc syntax in the comment string is set as the primary label instead.
- Oneline Diagrams: When reading a Shapefile (*.shp) into a oneline, Simulator will now look inside the PRJ file (if available) at the PROJECTION specified. If the PRJ file has a PROJECTION equal to "Mercator_Auxiliary_Sphere" then Simulator will automatically assume it map projection that is very commonly used for Shapefiles associated with website platforms such as Google Maps, Bing Maps, and so on. When this is detected now, Simulator will automatically convert the coordinates in the SHP files to Latitude/Longitude coordinates using this assumed map projection. In older versions of Simulator the user could click a button on the Modify Tab of the Shapefile import form, but this will now be done immediately upon loading the file.
- Oneline Diagrams: Fixed bug when loading a Shapefile (*shp) if a companion Projection file (*.prj) did not exist. The PRJ file should not be required when reading the SHP file, but an error would appear saying that the file could not be found.