v1.1.2 - Minor bug fixes when working with .psout and unit measurement

Updated the old legacy name for unit measurements from '$ALIAS_UM_9124$' to '$Unit$' in:

• MTB.pslx, and
• pscad_update_ums.py

Updated figureSetup.csv so that the default EMT signals for unit measurements are:

• '$Unit$\xxxx'

Fixed the bug that plotly's create_image_plot function does not like '$' in legend names by automatically removing all '$' from signal names in the plotter.py script

This implies that the default legend names for the EMT signals from the unit measurement will simply be displayed as:

• 'Unit\xxxx'

v1.1.1 - Minor bug fixes when working with .psout

• Fixed a bug to rename and move the .psout file when running in Manual mode (for a single rank)
• Updated the _getSignal function in process_psout.py so that it is possible to access "hierarchical" signals relative to the "Main" canvas (\Root\Main), and not relative to the "MTB" canvas (\Root\Main\MTB)
• This implied that the default EMT signals names now need to include MTB\ in front of the EMT signal names (for PSCAD), which actually give a nice synergy as to how RMS signals are described (for PowerFactory)
• The default figureSetup.csv file that is supplied with the MTB has thus been updated for the default EMT signals
• It now also fixes the bug introduced with v1.1.0 that broke the ability to use measuring units
• Signals from measuring units can now be specified as Measuring Unit Name\Unit Signal Name or Plant Canvas Name\Measuring Unit Name\Unit Signal Name relative to the "Main" canvas, e.g.
  • Solar_Plant\UM_1\LV_POC_fft_pos_Id_pu
• The plotter.py was also updated so that "hierarchical" structured signal names are only used for .psout files, and not for legacy .inf / .csv or .csv or compressed .csv files where signal names have to be uniquely specified in a flat structure

v1.1.0 - Now generating .psout instead of .out in PSCAD

What's Changed

• Export of single run cases correctly named by @CVLenerginet in #163
• Update README.md by @CVLenerginet in #164
• Utility scripts by @PRWenerginet in #166
  These include scripts to:
  • Get and compare cable and transformer data between PowerFactory and PSCAD
  • Get all the checksums for the DSL encrypted models
  • Get all relay data from PowerFactory
  • Perform general checks on the PowerFactory model
• Change pscad script to generate .psout format, and update plotter script to support .psout by @PRWenerginet in #167
  • Previously the MTB generating .out files in the .ifxx working folder and then converted them into .inf and .csv files in the datetime stamped folder in the export folder
  • By generating .psout files, and moving them directly to a datetime stamped folder in the export folder, an 82% reduction in diskspace was obtained for a DSO connection case in comparison the combined .out and .inf / .csv output
  • This also necessitated that the plotter script be updated to handle .psout input directly
  • A psout_to_csv script was added to generate "human readable" .csv from the .psout files
  • This used the figureSetup.csv file to only include signals that will be used for plotting to be included in the .csv file
  • The script makes use of Pandas' .to_csv method which implies that compressed .csv files can also be generated for archiving purposes, i.e. .zip, .gz, .bz2 and .xz
  • The plotter script also supports these .csv and compressed .csv files as input as support by Pandas' .read_csv method
  • The updated plotter script also provides legacy support for the older .inf / .csv input
• Update the requirements list to include the mhi.psout library by @PRWenerginet in #169
  • The update to the plotter script and the psout_to_csv script requires the Manitoba Hydro International (MHI) PSOUT File Reader, https://pypi.org/project/mhi-psout/
• Creates a datetime stamped folder in the export folder for PowerFactory by @PRWenerginet in #170
  • The .csv output files of PowerFactory are now also stored in a datetime stamped folder in the export folder
• Update config.ini template for the plotter script by @PRWenerginet in #171

New Contributors

• @PRWenerginet made their first contribution in #166

Full Changelog: v1.0.2...v1.1.0

v1.0.2

What's Changed

• PSCAD bugfixes, including fault definition lower value and angle used for zero sequence calculation
• Specified description of export folder, as generally used, in config.ini, not only for PF

Full Changelog: v1.0.1...v1.0.2

v1.0.1

What's Changed

• Bugfixes, including phase shift definition in PF, fault definition in PSCAD and single case export in PSCAD
• Updates to testcases.xlsx and the predefined RfG case set
• Updates to plotter tool with additional html functionality and the removal of cursor.png-files
• Additional minor improvements

Full Changelog: v1.0.0...v1.0.1

v1.0.0

Official release of the Energinet MTB v1.0.0

What's Changed:

• Updates to the guidelines to match recent changes and updates
• Updates to PF MTB, with updated Qdsl default example
• Updates to PSCAD MTB, with fix of fault clearing, single single execute_pscad.py run and export
• Updates to plotter tool with enhanced html functionality and new plotted signals
• Updates to testcases.xlsx with default case sets and description
• Setup examples for PF and PSCAD has beed added
• Additional minor improvements

Full Changelog: v0.9.95...v1.0.0

v0.9.95

Update to plotter tool and default cases, with additional smaller changes.

v0.9.94

Latest batch of small(ish) improvements

v0.9.93

Updated plotter

v0.9.92

Updated default cases