HELICS #77
Comments
Updates/Additions for HELICS:Name: HELICS, the Hierarchical Engine for Large-scale Infrastructure Co-SimulationFocus TopicCo-simulation of multi-energy systems Primary PurposeFlexible and scalable open-source co-simulation framework is designed to integrate simulators designed for separate energy domains to simulate regional and interconnection-scale power system behaviors at unprecedented levels of detail and speed. Co-simulation enables multiple existing simulators to act like one large simulation by coordinating time and exchanging data at every timestep. DescriptionFlexible and scalable open-source co-simulation framework is designed to integrate simulators designed for separate energy system domains--such as transmission, distribution, communications, natural gas, buildings, transportation, natural gas, water, control schemes, etc. Together these simulations can co-simulate a wide range of grid-related applications ranging in spatial scale from a single controller managing an electric vehicle charging station up to regional and interconnection-scale power system behaviors at unprecedented levels of detail and speed. For example, HELICS can link multi-faceted large-scale (20,000+ node) bulk power simulations (markets, powerflow, dynamics) with thousands of distribution simulations (each with thousands of nodes), in combination with hundreds of thousands of controllers, communication simulation with hundreds of thousands of communication points, and more. This comprehensive multi-energy simulation tool is fundamental for investment decision-making by industry. It's also important to help quantify the impact of the ever-increasing high penetration variable generation, DERs, control schemes, and other changes on the power grid reliability and resiliency; and to simulate possible solutions at scale in silico. Documentationhttps://docs.helics.org/en/latest/index.html Sourcehttps://github.com/GMLC-TDC/HELICS Year2018 (First release) InstitutionNREL, PNNL, LLNL Funding SourceDOE GMLC PublicationsLots, please add the following, plus some extras coming from PNNL and other locations and then update the sum _(Additional) Publication ListNote: the current list is mostly presentations, not sure if you would want to include all of these or are focussed more on papers.
If you do want more Presentations: Use CasesI'll point @lmramirea1 to some slides from various workshops showcasing past use cases What Infrastructure Sector does this software tool model?Note: only included relevant ones Buildings Represented BehaviorWhat is the represented behavior that the tool is modeling? Built Infrastructure Modeling ParadigmWhat modeling Paradigm does this software tool follow? Discrete Simulation CapabilitiesIn addition to the summary in original issue entry
Programming LanguageC – ISO/IEC 9899 Required DependenciesOnly other open-source libraries What is the software tool's license?BSD-3 Operating System SupportWindows User InterfaceWhat user interfaces are supported by the software tool? Programmatic Parallel Computing ParadigmMulti-threaded computing What is the highest temporal resolution supported by the tool?Instant What is the typical temporal resolution supported by the tool?1 ms to 1 hr depending on application and which other tools are connected What is the largest temporal scope supported by the tool?Arbitrary, 1 year common max What is the typical temporal scope supported by the tool?1-hour (e.g. dynamic response to grid outage) to 1-year (e.g. integrated T&D production cost) depending on application and which other tools are connected What is the highest spatial resolution supported by the tool?Component What is the typical spatial resolution supported by the tool?Varies by use case, component common, What is the largest spatial scope supported by the tool?Grid intercection (e.g. Western US, Europe, etc.) What is the typical spatial scope supported by the tool?Varies by application, data, and which other tools are connected Input Data FormatVaries by tools integrated. Input Data DescriptionInterconnected tools generally use their own native input formats. HELICS provides built-in "player" file support (CSV) to substitute for missing simulators during development or to provide known inputs to subsets of a federation Output Data FormatVaries by tools integrated Output Data DescriptionInterconnected tools generally use their own native output formats. In addition, HELICS provides built-in "recorder" file support (CSV) to capture data exchanged as desired Interface, Integration, and LinkageSee list above |
|
Thank you @bpalmintier . I included all your comments except the interface, integration and linkage list because I couldn't see it. |
GordStephen
added
the
needs-transferring
GordStephen
added
transferred
and removed
needs-transferring
Name
HELICS
Screenshots
Focus Topic
Co-simulation of multi-energy systems
Primary Purpose
Flexible and scalable open-source co-simulation framework is designed to integrate simulators designed for separate energy domains to simulate regional and interconnection-scale power system behaviors at unprecedented levels of detail and speed. Co-simulation enables multiple existing simulators to act like one large simulation by coordinating time and exchanging data at every timestep.
Description
Flexible and scalable open-source co-simulation framework is designed to integrate simulators designed for separate energy system domains--such as transmission, distribution, communications, natural gas, buildings, transportation, natural gas, water, control schemes, etc. Together these simulations can co-simulate a wide range of grid-related applications ranging in spatial scale from a single controller managing an electric vehicle charging station up to regional and interconnection-scale power system behaviors at unprecedented levels of detail and speed. For example, HELICS can link multi-faceted large-scale (20,000+ node) bulk power simulations (markets, powerflow, dynamics) with thousands of distribution simulations (each with thousands of nodes), in combination with hundreds of thousands of controllers, communication simulation with hundreds of thousands of communication points, and more.
This comprehensive multi-energy simulation tool is fundamental for investment decision-making by industry. It's also important to help quantify the impact of the ever-increasing high penetration variable generation, DERs, control schemes, and other changes on the power grid reliability and resiliency; and to simulate possible solutions at scale in silico.
Mathematical Description
No response
Website
https://helics.org/
Documentation
https://docs.helics.org/en/latest/user-guide/index.html
Source
https://github.com/GMLC-TDC/HELICS
Year
2018 (First release)
Institution
NREL, PNNL, LLNL
Funding Source
DOE GMLC
Publications
More than 20
Publication List
Use Cases
Infrastructure Sector
Represented Behavior
Modeling Paradigm
Capabilities
-Co-simulation platform that has been designed to allow integration of these simulators across a variety of computation platforms and languages.
-Scalable: 2-1,000,000+ federates
-Modular: mix and match existing tools.
-Differentiates physical values exchange from communication/control messages
-Supports co-iteration to converge physical values between federates before advancing time (aka tight coupling)
-Built-in support for communication message "Filters" to add delays, drop packets, change data, reroute to different simulators, etc.
-Built-in unit management
-Tools for managing large runs
-Existing interfaces for: PSS/E, GridDyn, PowerWorld, SIIP, MATPOWER, CYME, PyDSS, OpenDSS, GridLAB-D, NS-3, SAInt, NG-Fast, NG-Transient, BEAM, Polaris, Opal-RT, and others
-Supports multiple simulation types including: Time series, dynamics, discrete event
-Interfaces for FMI
Programming Language
Required Dependencies
Only other open-source libraries
What is the software tool's license?
BSD-3
Operating System Support
User Interface
Parallel Computing Paradigm
What is the highest temporal resolution supported by the tool?
Instant
What is the typical temporal resolution supported by the tool?
1 ms to 1 hr depending on application and which other tools are connected
What is the largest temporal scope supported by the tool?
Arbitrary, 1 year common max
What is the typical temporal scope supported by the tool?
1-hour (e.g. dynamic response to grid outage) to 1-year (e.g. integrated T&D production cost) depending on application and which other tools are connectedNone
What is the highest spatial resolution supported by the tool?
Component
What is the typical spatial resolution supported by the tool?
Varies by use case, component common,
What is the largest spatial scope supported by the tool?
Grid intersection (e.g. Western US, Europe, etc.)
What is the typical spatial scope supported by the tool?
Varies by application, data, and which other tools are connected
Input Data Format
Varies by tools integrated.
Input Data Description
Interconnected tools generally use their own native input formats. HELICS provides built-in "player" file support (CSV) to substitute for missing simulators during development or to provide known inputs to subsets of a federation
Output Data Format
Varies by tools integrated
Output Data Description
Interconnected tools generally use their own native output formats. In addition, HELICS provides built-in "recorder" file support (CSV) to capture data exchanged as desired
Contact Details
helicsteam@helics.org
Interface, Integration, and Linkage
No response
The text was updated successfully, but these errors were encountered: