Uses of Package
org.yamcs.xtceproc
-
Packages that use org.yamcs.xtceproc Package Description org.yamcs org.yamcs.algo org.yamcs.algorithms org.yamcs.container org.yamcs.parameter org.yamcs.xtceproc -
Classes in org.yamcs.xtceproc used by org.yamcs Class Description ContainerProcessingOptions ProcessorData Holds information related and required for XTCE processing.XtceTmProcessor Does the job of getting containers and transforming them into parameters which are then sent to the parameter request manager for the distribution to the requesters. -
Classes in org.yamcs.xtceproc used by org.yamcs.algo Class Description AbstractDataDecoder stubbed implementation of DataDecoder that "removes" all the AlgorithmExecutor methods - to be used until the data decoders will work as algorithms, or for data decoders that do not need any input parametersAbstractDataEncoder stubbed implementation of DataEncoder that "removes" all the AlgorithmExecutor methods - to be used until the data decoders will work as algorithms, or for data decoders that do not need any input parametersDataDecoder Interface to be implemented by the custom XTCE DataEncoding decoders - fromBinaryTransformAlgorithm TODO: unify somehow with the algorithms in order to allow for example to use input parameters (i.e. value of other parameters may be needed in the decoding) Until then, please use the AbstractDataDecoder interface to not need to implement any of the AlgorithmExecutorDataEncoder Interface to be implemented by the custom XTCE DataEncoding decoders - toBinaryTransformAlgorithm -
Classes in org.yamcs.xtceproc used by org.yamcs.algorithms Class Description ProcessorData Holds information related and required for XTCE processing. -
Classes in org.yamcs.xtceproc used by org.yamcs.container Class Description ContainerListener Used together with the XtceTmProcessor to find out which containers a specific data packet is representingXtceTmProcessor Does the job of getting containers and transforming them into parameters which are then sent to the parameter request manager for the distribution to the requesters. -
Classes in org.yamcs.xtceproc used by org.yamcs.parameter Class Description ParameterAlarmChecker Part of the TM processing chain.XtceTmProcessor Does the job of getting containers and transforming them into parameters which are then sent to the parameter request manager for the distribution to the requesters. -
Classes in org.yamcs.xtceproc used by org.yamcs.xtceproc Class Description CalibratorProc ContainerListener Used together with the XtceTmProcessor to find out which containers a specific data packet is representingContainerProcessingContext Keeps track of where we are when processing a packet.ContainerProcessingOptions ContainerProcessingResult DataDecoder Interface to be implemented by the custom XTCE DataEncoding decoders - fromBinaryTransformAlgorithm TODO: unify somehow with the algorithms in order to allow for example to use input parameters (i.e. value of other parameters may be needed in the decoding) Until then, please use the AbstractDataDecoder interface to not need to implement any of the AlgorithmExecutorDataEncoder Interface to be implemented by the custom XTCE DataEncoding decoders - toBinaryTransformAlgorithmDataEncodingDecoder Decodes TM data according to the specification of the DataEncoding This is a generic catch all decoder, relies on specific custom decoders implementing the DataDecoder interface when necessary.MetaCommandProcessor.CommandBuildResult ParameterTypeProcessor Responsible for converting between raw and engineering value by usage of calibrators or by simple type conversions.ProcessingStatistics ProcessorData Holds information related and required for XTCE processing.SequenceContainerProcessor SequenceEntryProcessor Subscription keeps track of the parameters and containers subscribed (because we only want to extract those)TcProcessingContext Keeps track of where we are when filling in the bits and bytes of a commandValueProcessor