Skip to content

DSS Sharp 0.14.3
Compare
Choose a tag to compare
@PMeira PMeira released this 14 Mar 18:20
· 1 commit to master since this release
0.14.3
5895649

Version 0.14.3 upgrades the engine to AltDSS/DSS C-API 0.14.3. There are few bugfixes. This version tracks OpenDSS v9.8.0.1, released on 2024-01-31. Read below for the list of changes.

In 0.14.x, new features at C# level include experimental whole circuit save/load using JSON-encoded strings, and a new circuit Save function that allows customization of the saved data.

The package is available as an attachment here, and from NuGet: https://www.nuget.org/packages/dss_sharp/
The package contains the required native binaries and should handle copying the DLLs to the output folders correctly for most common scenarios.
Integrating the whole project (.csproj) into an existing solution is also possible, but remember to download the native dependencies.

For an example of usage, see https://github.com/dss-extensions/dss_sharp/tree/master/examples/WinFormsAppSample

❓ What's this?

DSS Sharp is a member of DSS-Extensions, a family of multi-platform language bindings based on the AltDSS/DSS C-API project, which exposes an alternative/customized implementation of the original EPRI's OpenDSS, with a custom API intended to replace and extend the functionality of the official COM object API, while also adding and improving some of the DSS engine internals. For other languages, check: DSS-Python, OpenDSSDirect.py, DSS MATLAB, and OpenDSSDirect.jl. New projects include AltDSS-Rust and AltDSS-Go. A new style of API, with more modern and hopefully simpler approach, is being developed on AltDSS-Python -- the lessons learned from that project will reflect in the final design of the new API implementation for the other languages.

See more at https://dss-extensions.org/ and also our FAQ.

As with DSS-Python, this package tries to mimic the COM object structure to facilitate the transition and keep most of the existing code valid. The package is usually faster than the COM object for various tasks. Most of the missing features are related to the plotting methods from OpenDSS and A-Diakoptics.

Known differences and more

We maintain a list of important differences between the official COM implementation and DSS C-API at:

https://github.com/dss-extensions/dss_capi/blob/master/docs/known_differences.md

Credits / Acknowledgement

This project is derived from EPRI's OpenDSS and the same style of license (BSD style) is used. As OpenDSS, the project also depends on KLUSolve and SuiteSparse, licensed under the LGPL. The licenses are included in the installation packages.

See the DSS C-API project for more details and source files.

⚙️ AltDSS/DSS C-API Version 0.14.x

Changes from 0.14.1 to 0.14.3

  • Header/Alt: fix dss_obj_float64_int32_func_t (returns double, not int32_t).
  • Header: add enums for (state) variables for several components (Generator, IndMach012, PVSystem, Storage, UPFC, VCCS).
  • API/YMatrix: check for valid circuit in a few more functions.
  • API/Circuit: adjust SetActiveElement to be more conformant with the official version, i.e., returns -1 for non-circuit elements.
  • API/CircuitElement: in the classic API, call the Alt implementations for Open/Close/IsOpen to reduce code duplication.
  • Alt/CircuitElement:
    • Fix error message
    • Fix logic for DisplayName
    • Fix 13+ old bug in Open/Close/IsOpen -- the terminal parameters was being effectively ignored, applying the operations to the active terminal; also add check for valid terminal index.
  • API/Capacitors: fix Close (same issue as CE).
  • API/Batch:
    • Implement BatchOperation_Divide; needed for integers, and could be slightly better for floats, even though it's a tiny bit slower in modern processors.
    • Generalize Batch_SetFloat64Array/Batch_SetIn32Array to Batch_Float64Array/Batch_In32Array. This allows dropping the basic batch operations to the engine for array values, and allow for future optimizations in C++. In the current Pascal codebase, this is still better than running the operations on user-side due to memory layout and potential extra memory allocations when running on user-side.
    • Add Batch_CreateByFloat64PropertyRange to allow creating batches based on the value of a float64 property.
    • Add Batch_FilterByFloat64PropertyRange and Batch_FilterByInt32Property to allow filtering existing batches into new batches.
    • Make sure to zero all elements in intermediate buffers to avoid potential issues, especially with disabled elements grabbing values from the previous element.

Full Git Changelog: dss-extensions/dss_capi@0.14.1...0.14.3

Changes from 0.13.4 to 0.14.1

Long list, click to expand Starting on this version, we will call DSS C-API and related projects AltDSS, an alternative implementation of OpenDSS, to make it more clear that this is not supported by EPRI and many extra features are not present in the official OpenDSS. Watch the DSS-Extensions org on GitHub for more announcements soon, including some support for the official implementation (still Windows-only at the moment). The name change **does not** mean compatibility or other aspects are expected to change, the project will still follow the basic guidelines of compatibility that have been followed since 2018.

This version should match OpenDSS v9.8.0.1 (SVN r3723). Remember to check the compatibility flags and Known differences.

  • Another large internal (Pascal) code refactoring step and general clean-up. Check the commits for details, too many to list. A last step is under progress and will be merged in the next major release.

  • Capitalization of property names adjusted! A first pass was done to try to make the property names more uniform. Since OpenDSS is case insensitive, we are free to change the capitalization as we see fit. In the past, the official OpenDSS already changed some property names, so a general suggestion for users that process the property names is to transform the names to upper or lower cases before comparing. This should ensure better stability across past and future versions of both DSS-Extensions and the official OpenDSS. For code that do not check the names in a case insensitive approach, DSS C-API 0.14.0 provides a function to adjust the property names (Settings_SetPropertyNameStyle), allowing the user to choose between three alternatives: the "Modern" version with adjusted capitalization; "Lowercase" names; and "Legacy" names. "Legacy" names can be used to avoid updating the names.

  • Introduces a preview of JSON schema (new), JSON export (updated) and import (new). Too many details to include in the changelog. Includes many updates to the internal metadata. A separate project will be posted at https://github.com/dss-extensions/AltDSS-Schema and community feedback is welcome. Note: the JSON schema will be used for projects and features beyond JSON IO.

  • Introduced options and improve correctness for save circuit. During the testing of the JSON dump, issues were fixed when saving Line, LineGeometry, Transformer, AutoTrans, XfmrCode. The issues vary from simple omissions to invalid exported DSS code. The property tracking feature below also helps generating clear and valid DSS scripts from save circuit, eliminating properties invalidated when changing some component definitions. To allow easier control of the save function without modifying the DSS language, a new Save function was added to the circuit API (Circuit_Save), coupled with the new DSSSaveFlags enumeration, which contains the option flags. This function also allows exporting the whole circuit as a single string.

  • Introduce property tracking. Setting some properties now mark conflicting property definitions as unset. This affects some functionality for saving circuits and is also used for the JSON schema, for instance. An example: a user creates a load with kW=10 kvar=0. Later, the user updates the load, setting PF=0.9. Setting the power factor toggles the load internal state to use kW and PF as the load definition, but kvar is still marked as set. The DSS engine correctly tracks the order that properties were defined, so everything works as expected. Now, with the growing usage of DSS implementation to export the circuit, every single user is required to correctly implement this tracking if they want to ensure compatibility. That is, dumping the data from this example generator in an unordered dictionary/map/etc. for processing and later dumping back to DSS scripts will result in the wrong model.

    • Users can, of course, still query the value of all properties.
    • See also NoPropertyTracking compat flag.
    • Currently implemented, at least partially, in the following DSS classes (plus Lines and Loads API): LineCode, LineGeometry, LoadShape, Generator, Load, PVSystem, Storage, VSource, Fault, Line, Reactor, Transformer.
    • This functionally may be extended to other classes in future versions, if required.

  • Introduce "Setter" flags. These are flags used to tweak how the property update is done. Notably,AvoidFullRecalc (some other flags are only using by the engine, internally): some specific properties like Load.kW can be updated both directly through a DSS script (or Text interface), or through the dedicated Loads API in any of the specific language bindings of the many APIs. The dedicated API does not force a YPrim update and full load model recalculation.

    • When using this flag AvoidFullRecalc in the Obj/Batch APIs, the behavior will follow the dedicated Loads API.
    • Other flags include ImplicitSizes and AllowAllConductors. Both are currently used for enabling some of the JSON Schema functionally.
    • For batch operations, SkipNA was introduced to allow handling scenarios with non-uniform data.
    • The relevant API functions were updated to include an extra function argument with the setter flags.
    • Is this AvoidFullRecalc the same as SkipSideEffects compat flag? No. AvoidFullRecalc is still valid and by design (including some behavior listed in OpenDSS docs), whereas SkipSideEffects is potentially unintended behavior.

  • New compatibility flags in DSSCompatFlags:

    • ActiveLine (0x10). In the official OpenDSS implementation, the Lines API use the active circuit element instead of the active line. This can lead to unexpected behavior if the user is not aware of this detail. For example, if the user accidentally enables any other circuit element, the next time they use the Lines API, the line object that was previously enabled is overwritten with another unrelated object. This flag enables this behavior above if compatibility at this level is required. On DSS-Extensions, we changed the behavior to follow what most of the other APIs do: use the active object in the internal list, starting on version v0.14.0.
    • NoPropertyTracking (0x20): On DSS-Extensions/AltDSS, when setting a property invalidates a previous input value, the engine will try to mark the invalidated data as unset. This allows for better exports and tracking of the current state of DSS objects. Set this flag to disable this behavior, following the original OpenDSS implementation for potential compatibility with older software that may require the original behavior; note that may lead to erroneous interpretation of the data in the DSS properties. This was introduced in DSS C-API v0.14.0 and will be further developed for future versions.
    • SkipSideEffects (0x40). Some specific functions on the official OpenDSS APIs and internal code skip important side-effects. By default, on DSS-Extensions/AltDSS, those side-effects are enabled. Use this flag
      to try to follow the behavior of the official APIs. Beware that some side-effects are
      important and skipping them may result in incorrect results.
      This flag affects some of the classic API functions (Loads, Generators, Vsources) as well as the behavior of some specific DSS properties (Line: Rg, Xg, rho; Transformer/AutoTrans: XSCArray).

  • New Alt and Obj families of functions. A new family of functions was added to allow most legacy API operations and new functionality directly on objects and batches, instead of relying on "active..." idiom. A new package, AltDSS-Python, will be published to illustrate the new approach. Since the engine is shared, users can mix both approach (e.g. use AltDSS-Python and OpenDSSDirect.py in the same script).

  • Batch/API:

    • Allow using batches with simple functions that return float64/int32 for each object.
    • Allow using INT32_MAX and NaN for missing values, which can be skipped with the SetterFlags_SkipNA flag. Sooner or later, there should a better alternative, but this can be useful in the time being.

  • Headers:

    • Remove stdint_compat.h. This was only required for very old or non-standard compiler like MSVC 2008. Users that require that can still source the file from older releases or get similar files from other sources.
    • Include stddef.h when building as C code.
    • Mark CktElement_Get_IsIsolated with (API Extension)
    • Add more const qualifiers. Especially useful for the new Rust and Golang bindings.

  • Specific bug fixes:

    • AutoTrans: fix DumpProperties, readd bank property (unused internally).
    • Commands/Save: add version and timestamp to master file.
    • DynamicExp and DynEqPCE: fix DumpProperties; extend to support JSON in/out.
    • Generator: fix default value for D (as DSS property); previously, the value was left uninitialized. It seems to only affect user models, so it doesn't seem like a big issue. Explicitly providing a value would also work fine as a workaround.
    • Line and LineCode: fix formatting issues in DumpProperties
    • LoadShape: fix some issues when copying/saving data when using float32 data (which users need to explicitly opt-in).
    • PriceShape/TempShape: adjust setters for mean/stddev properties
    • Relay: fix handling of DOC_PhaseCurveInner (DSS property)
    • Reactor: in some situations, R and X were not synched with Z. Fixed by removing the internal duplication (does not affect user code).
    • Sensor: DeltaDirection was not initialized; make clear an explicit action.
    • SwtControl: If no element is attached (misuse), set state as "none".
    • Transformers/API: Transformers_Get_LossesByType and Transformers_Get_AllLossesByType now check if the transformer is enabled.
    • API/general: avoid tiny memory leaks (pointer size, 8 bytes) on empty data and some error situations.
    • Bus/classic API: fix Bus_Get_N_interrupts; was previously returning the duration instead.
    • Circuit_Capacity (API, command): fix register index, remove magic numbers. (Bug introduced back in 2008!)
    • Circuit/API: fix Circuit_Enable and Circuit_Disable (enabling/disabling circuit elements by name). An equivalent fix is included in the official OpenDSS v9.7.1.1, in the COM interface. Additionally, provide error message when trying to use invalid element names.
    • Obj/Batch API: better handling of booleans. With this change, any non-zero value is interpreted as true, which simplifies integration with other programming languages. This was the original intention.
    • API/Iteration: Fix issues with iteration in a few of the internal functions which could have resulted in empty results in some situations. These situations occurred only during testing, so we don't expect many users were affected.

  • Misc:

    • Error handling: add a few numeric checks, and check for errors in more places during solution algorithms. The changes should help finding issues earlier and/or more easily.
    • Check for null pointers (usually missing circuit solution) in a few more places.
    • Properties/capitalization: adjust capitalization of nearly all property names. Use lowercase for description keys (help strings). Feedback on the capitalization is welcome. As a reminder, OpenDSS is case-insensitive, but other other are not. Providing a better internal representation of the properties will help other tools to use the internal names without extra work (no need for each tool to adjust capitalization), and it doesn't affect the DSS engine itself nor compatibility with the upstream OpenDSS.
    • Obj/API: introduce ExtraClassIDs to get some special lists.
    • Classic to Obj/Alt API bridge: add many *_Get_Pointer functions (e.g. CktElement_Get_Pointer, Loads_Get_Pointer). These functions return a pointer that can be used in the Obj API. This should enable an easier migration from the classic API, or allow users to use the Obj API to complement the classic API where the latter is lacking.
    • API/Callbacks: dss_callback_message_t function signature extended with two more arguments. We are not aware of any user using these, but if you are, remember to update your callbacks.
    • API/Extended errors: add a few more checks, and disable some error messages when extended errors are disabled. (Extended errors are extra error checks introduced to signal wrong usage of the DSS engine; extra = not present in the original/official codebase)
    • API/Text: microoptimize Text_CommandBlock for single commands. That is, users could use Text_CommandBlock for both single and multi-line strings without performance impacts. We did not replace Text_Set_Command in order to avoid potential compatibility issues.
    • API/Events: generalize the API for event extensions.
    • API/Obj: handle incorrect array sizes better, add error messages.

  • Ported from the official SVN:

    • r3637: "Removing force EventLog for StorageController to match all the other controls and their defaults." (by davismont)
    • r3640: "Updated "Show" fault study report to better arrange output. (...)" (by aovallev)
    • r3642: "Skipping disabled meters when interpolating all meters." (by celsorocha)
    • r3646: updates to TInvDynamicVars.CalcGFMYprim (by davismont)

Full Git Changelog: dss-extensions/dss_capi@0.13.4...0.14.1

Assets 3
Loading