PDQTracker v1.3
Official stable release of version 1.3 of the PDQTracker (v1.3.5).
NOTE: if you are upgrading from a prior version of the PDQTracker, you must migrate your existing configuration to use the latest database schema when the Configuration Setup Utility is run after the installation completes - this version includes schema updates.
See full release notes since last release.
Note: the PMU Connection Tester is no longer automatically included with the installer package and will need to be installed separately:
https://github.com/GridProtectionAlliance/PMUConnectionTester/releases
New Features and Improvements
- Added CSV source data export and e-mail options to daily quality reporting
- Fully overhauled system security
- Added eDNA historian adapters
- Added ability to control TCP Nagle algorithm through configuration and applied better defaults when applicable
- Added
quiet
/resume
console commands, withq
andr
alias shortcuts, to reduce noise during interaction - Improved sub-second time handling
- Improved startup time of applications without Internet access by allowing disabling of generate publisher evidence in the NoInetFixUtil
- Improved sub-second time handling
- Added new GSF time-series Filter Adapters and management screen
- Added new Grafana functions and capabilities (see full list)
- Better pre-compilation options of Razor web pages at service start
- Added "useSourcePrefixNames" boolean connection string parameter to DataSubscriber to allow override ability on subscription prefixes applied to devices names
- Included new GSF adapter to allow selection of a "best" value based on configuration options
- Modified the latest values cache in DynamicCalculator to be fed by the concentration engine to resolve usability issues
- Fixed memory leak in MultiProtocolFrameParser when replay start time and stop time is specified
- Fixed logic error in AverageFrequency calculator when reporting unreasonable results as NaN
- Fixed SQL syntax for updated Phasor synchronization in DataSubscriber
- Updated LDAP security provider to allow UserData.IsDefined to be assumed to be true if no cached user can be found to allow authentication to be attempted
- Added a safety check around target cache acquisition for cases where cache may have been disposed
- Handled edge case in SIDToAccountName to resolve errors with null input
- Removed references and dependencies on to Thread.CurrentPrincipal throughout system as part of security overhaul