LimitViolationDetector.com.powsybl.security.detectors.LimitViolationDetector.SecurityAnalysis,
and provides a SecurityAnalysisResultBuilder to ease creation of results.LimitViolation to the builder.LimitViolation to the builder with a context.SecurityAnalysisInput for an actual security analysis computation,
based on the provided SecurityAnalysisExecutionInput, which may for example
be defined through a command line call.Network should be considered as LimitViolations.Network should be considered as LimitViolations.Branch should be considered as a LimitViolation or not.Branch should be considered as a LimitViolation or not.Branch
should be considered as LimitViolation(s).Branch should be considered as a LimitViolation or not.Branch should be considered as a LimitViolation or not.Branch
should be considered as LimitViolation(s).Bus
should be considered as a LimitViolation or not.Bus
should be considered as a LimitViolation or not.VoltageLevel
should be considered as a LimitViolation or not.Bus
should be considered as a LimitViolation or not.Bus
should be considered as a LimitViolation or not.VoltageLevel
should be considered as a LimitViolation or not.config.config.ContingenciesProvider into
security analysis inputs, based on the specified factory and the specified
source of data (raw bytes to be interpreted by the factory).ContingenciesProviderFactoryContingency.ContingencySecurityAnalysis for specified Network,
using specified ComputationManager to handle computations.SecurityAnalysis for specified Network,
using specified ComputationManager to handle computations.SecurityAnalysis for specified Network,
using specified ComputationManager to handle computations.config.com.powsybl.security.detectors.ExecutionHandler which distributes the security analysis execution through multiple calls
to itools security-analysis, as specified in argument.DistributedSecurityAnalysisExecution, which clarifies the input data for that kind
of execution, and tries to differentiate more between a SecurityAnalysis
and its mode of execution.ComputationManager.ExecutionHandler which distributes the security analysis execution through multiple calls
to itools security-analysis, as specified in argument.ForwardedSecurityAnalysisExecution, which clarifies the input data for that kind
of execution, and tries to differentiate more between a SecurityAnalysis
and its mode of execution.ExecutionHandler which forwards the security analysis execution through a call
to itools security-analysis.ExecutionHandler which forwards the security analysis execution through a call
to itools security-analysis, with the option --task-count.ExecutionHandler which forwards the security analysis execution through a call
to itools security-analysis.ExecutionHandler which forwards the security analysis execution through a call
to itools security-analysis, with the option --task-count.ContingenciesProvider.LimitViolationDetector.NetworkSecurityAnalysisParameters.Network with variant NetworkVariant.variantId properly set.LimitViolations.LimitViolations, in particular to ease their building and comparison.PlatformConfig.PlatformConfig.Network and the ID of one of its variants.ComponentDefaultConfig.ComponentDefaultConfig.SecurityAnalysisInterceptor.onPreContingencyResult(LimitViolationsResult, SecurityAnalysisResultContext)
Callback after the pre-contingency analysis result is createdSecurityAnalysisInterceptor.onSecurityAnalysisResult(SecurityAnalysisResult, SecurityAnalysisResultContext)
Callback after the result is createdSecurityAnalysis.run(String, SecurityAnalysisParameters, ContingenciesProvider), this method would also complete exceptionally
if there are exceptions thrown.SecurityAnalysis is a power system computation which computes, for a Network,
the LimitViolations on N-situation
and the ones caused by a specified list of Contingencies.SecurityAnalysis.SecurityAnalysisExecution,
based on specified options, in particular distribution options.ExecutionHandlers which may execute one or multiple itools security-analysis command(s).SecurityAnalysisExecution :
a Network and the variant to be considered
some SecurityAnalysisParameters
a set of requested result extensions
the set of violation types to be considered
an optional ByteSource which describes contingencies
Design note: here we only want serializable objects for forwarding purpose,
therefore some fields are fully serializable business objects
while others are more in their "source" format as they do not support serialization out of the box.SecurityAnalysis computation.SecurityAnalysisResult, for instance when adding new limit violations.SecurityAnalysisInput, in particular
contingencies and limit violations detection.SecurityAnalysisPreprocessor based on an arbitrary
configuration provided as a source of bytes.SecurityAnalysisPreprocessors or factories.AbstractSecurityAnalysis.Partition.ContingenciesProvider into
security analysis inputs, based on the specified factory and the specified
source of data (raw bytes to be interpreted by the factory).Copyright © 2020. All rights reserved.