This document shows the steps of importing a PSSE model into HYPERSIM.
Step 1- Create a new HYPERSIM model
- Select New from File tab, then create a HYPERSIM file.
- Select the desired folder and choose the file name, then Save it.
Step 2- Import the PSSE model.
- The PSSE import feature can be found in the Network Import tool from the HYPERSIM ribbon, under the Network section.
- Select the *.raw file from PSSE option and Import it.
To import a PSSE model into HYPERSIM, it is necessary to provide the path to the *.raw file (or *.dyr file) in the designated "File" text field. Alternatively, users can utilize the browse option located on the right-hand side of the field for file selection.
For importing the dynamic data, the *.dyr file must bear the identical name as the *.raw file. The system automatically selects any other files within the same directory that share the same name.
While it is possible to import a model using only a *.raw file, without an accompanying *.dyr file, it is not possible to import solely a *.dyr file.
Options:
Replace machines by sources |
|
Remove not connected buses | Non-connected buses in the original circuit will not be imported. |
Group machines with controls | This feature merges the machine and its controllers into a subcircuit. |
Once the importing procedure is started, the Python API analyzes the PSSE circuit and prepares a python script. This script relies on data stored in a folder named ConversionReports_YYYY-MM-DD_HH-mm, located next to the PSSE file. Subsequently, the python script is executed, importing the model into HYPERSIM. Each component is assigned a unique identifier that corresponds precisely to its PSSE identification number, facilitating easy reference to the original design. The duration of the conversion process varies depending on the size of the model and the number of components involved, often taking several minutes.
After the import process is finished, reports are created within the aforementioned conversion report folder. These reports provide information about the overall success and performance of the conversion, along with a list of any components that may not have been successfully converted.
The figure below shows an example of the generated reports.