Releases: Energinet-AIG/PP-MTB
Releases · Energinet-AIG/PP-MTB
v0.8.1
v0.8
PSCAD
No changes.
PLOTTER
No changes.
POWERFACTORY
- Crash when signal names are empty fixed by @ZRPedro . Closes #62
- Issue loading C-events from sheet fixed. Closes #90
- Major refactor of the execute.py script. Closes #61
- Alternative to variation consolidation added. With the new alternative (set script input parameter 'consolidate' to 0), currently active variations remain active along the test case variations created during script execution. The test case variation expansion stage activation time is set from the study time of the study case active when executing the script, hence the recording expansion stage of your active variation cannot be active at the same time, as the study time of the active study case. The PP-MTB setup (base setup) and individual case setup is now grouped in a single variation per study case instead of two. Closes #60
- Option for parallel computation added by @ZRPedro. Fixes #100
Contributors
ZRPedro
Assets 2
v0.7
PSCAD
- Significant cleanup and refactor. Closes #8.
- Old messy plotting code has been removed. Results now needs to be plotted manually with Plotter tool. This has been done to keep the PSCAD python script very simple. If automation of this is desired it is trivial for the user to setup. Closes #23.
- The project description are no longer automatically suffixed with "_Energinet_[Date and time]".
- csv and inf files are moved to a new subfolder of the output folder named "MTB_[Date and time]" at end of execution. Closes #33.
- out files are moved to a new subfolder of the temp/building folder named "MTB_[Date and time]" at end of execution. Closes #33.
PLOTTER
No changes.
POWERFACTORY
No changes.
v0.6.3
v0.6.2
PSCAD
Fixes #2. POC voltage is correctly initializing to 1.0 pu. This was done by adding a PI-controller to the thevenin equivalent. After three seconds the PI-controller output is locked and if voltage source control is activated the case setpoint/ramps will be followed.
PLOTTER
No changes.
POWERFACTORY
No changes.
v0.6.1
v0.6
PSCAD
No changes.
PLOTTER
The Plotter script has been updated to ease comparing different projects or different versions of the same project.
- The script now identifies simulation data using the filename AND path. For example, data files such as "res1/fredericia_1.csv" and "res2/aarhus_1.csv" are identified as belonging to the "res1/fredericia" and "res2/aarhus" projects, respectively. The last number in the file name represents the case number. The regular expression for a valid simulation data file name is:
^(\w+?)_([0-9]+).(inf|csv)$ - Projects found in the "[Simulation data paths]" paths are now automatically categorized as either EMT or RMS results.
A RMS resultsfile is defined as a .csv file with a leftmost column namedb:tnow in s. A EMT resultsfile (metafile) is defined as a .inf file where the first line starts withPGB(1). EMT datafiles are still assumed to be in the same folder as the metafile. - All found projects are added to relevant case plot exports.
The previous version paired the RMS results with the corresponding EMT results (and vice-versa) for each project for all relevant cases. A resultsfolder with the plots for each project was created when exporting. Now all project-data with a case ID of for example 1 is added to the "1.html" and "1.jpeg" exports. The "pairing" should now be done manually by only including the relevant data in the "[Simulation data paths]" paths. - Signal coloring has been updated: If more than two projects are plotted, all signals belonging to a project will be colored the same. Otherwise, all signals will be colored differently.
- Time start parameter removed. Plots starts at first data.
POWERFACTORY
No changes.
v0.5
PSCAD
No changes.
PLOTTER
No changes.
POWERFACTORY
- Partial refactor.
- Uses newest PF plotting framework (Thanks @CVLenerginet).
- Better support for DLL based models.
Including: compiled models does not always populate the input signal vector. A work around has been included. - Parameter event only option added.
Some models have issues back-initializing with a DSL model connected to its inputs. This is non-compliant but should still be testable. - Inputblocks (P reference, Q reference etc.) can now be a composite frame. Known issues:
- Composite frames does not support parameter events on input signals.
- Composite frame input signals (for references) are not plotted. - Column separator symbol now strictly semi-colon and not system dependent. (Thanks to Bakhtyar Hoseinzadeh from NextConsult for noticing)
Contributors
CVLenerginet