Uses of Package
org.yamcs.algorithms
-
Packages that use org.yamcs.algorithms Package Description org.yamcs.algorithms org.yamcs.commanding org.yamcs.xtceproc -
Classes in org.yamcs.algorithms used by org.yamcs.algorithms Class Description AbstractAlgorithmExecutor Skeleton implementation for algorithms conforming to the XTCEAlgorithmdefinitionAlgorithmEngine Handles algorithms for one language.AlgorithmException exception thrown when unexpected things happen during the loading and execution of algorithms.AlgorithmExecListener AlgorithmExecutionContext Algorithms for command verifiers must execute in parallel in different contexts - meaning that each algorithm will have their own values for inputs referring to command specifics (e.g. command sequence count) That's why we associate to each AlgorithmExecutor (which represents the instantiation of one algorithm) one of these AlgorithmExecutionContext.AlgorithmExecutor Represents the execution context of one algorithm.AlgorithmExecutorFactory Responsible for creating executorsAlgorithmManager Manages the provision of requested parameters that require the execution of one or more XTCE algorithms.ScriptAlgorithmExecutor Represents the execution context of one algorithm.ValueBinding A ParameterValue as passed to an algorithm. -
Classes in org.yamcs.algorithms used by org.yamcs.commanding Class Description AlgorithmExecListener AlgorithmExecutionContext Algorithms for command verifiers must execute in parallel in different contexts - meaning that each algorithm will have their own values for inputs referring to command specifics (e.g. command sequence count) That's why we associate to each AlgorithmExecutor (which represents the instantiation of one algorithm) one of these AlgorithmExecutionContext.AlgorithmManager Manages the provision of requested parameters that require the execution of one or more XTCE algorithms. -
Classes in org.yamcs.algorithms used by org.yamcs.xtceproc Class Description AlgorithmExecListener AlgorithmExecutionContext Algorithms for command verifiers must execute in parallel in different contexts - meaning that each algorithm will have their own values for inputs referring to command specifics (e.g. command sequence count) That's why we associate to each AlgorithmExecutor (which represents the instantiation of one algorithm) one of these AlgorithmExecutionContext.AlgorithmExecutor Represents the execution context of one algorithm.