This document shows the steps of importing a PSSE model into HYPERSIM.

Step 1 - Create a new HYPERSIM model

• Select New from 

  Select New from File tab, then create

  a 

  a HYPERSIM

   file

   file.

...

• Select the desired folder and choose

  the 

  the file name,

  then 

  then Save

   it

   it.

...

Step 2 - Import the PSSE model

...

• The PSSE import feature can be found in

  the 

  the Network

   Import

   Import tool from the HYPERSIM

   ribbon,

  Ribbon Options 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.

...

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

Additional information

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 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.

Image RemovedThese reports can be shared to OPAL-RT to help debug any issues because they contain detailed information about warnings and errors that occurred during the import of the model.

The reports are as follows:

• hs_error.log:details on the state of connection to HyWorks

• hs_import.log: warnings and errors related to the addition, connection, rotation of components and setting of parameters while creating the model

• netlist.xlsx: An excel file containing all the components imported in the model with their parameters

• {model_name}_full.log: groups information found in mapper and parser logs

  • {model_name}_mapper.log: skipped or unsupported components while mapping to Unified Database components are found in this report

  • {model_name}_parser.log: information on the parsing of the input file

• {model_name}_modelexporter.log: details on the generation of the python code used to import the model, can be used for debugging purposes

• {model_name}.edd: generated edd file used to import the model to HYPERSIM

• {model_name}.py: generated python code used to import the model to HYPERSIM