Programming Reference:Signals: Difference between revisions
No edit summary |
Atennissen (talk | contribs) No edit summary |
||
| Line 10: | Line 10: | ||
==Signal Properties== | ==Signal Properties== | ||
Sometimes, the number of channels, elements, and | Sometimes, the number of channels, elements, and bytes | ||
required | required | ||
for storing values, are referred to as "Signal Properties". | for storing values, are referred to as "Signal Properties". | ||
| Line 16: | Line 16: | ||
those | those | ||
values, and determining whether a given signal "fits" into another | values, and determining whether a given signal "fits" into another | ||
one, i.e. | one, i.e., | ||
whether the values contained in one signal may be copied into another | whether the values contained in one signal may be copied into another | ||
signal without loss of information. | signal without loss of information. | ||
Revision as of 16:47, 7 May 2007
Signals
Many classes in both Data Acquisition and Signal Processing work on signals, i.e., continuously flowing data organized in channels and samples. The GenericSignal class contains floating point data organized as a matrix of channels and "elements" (a generalized notion of samples -- e.g., spectrally analyzed data might contain the spectrum of each channel as a list of "elements").
Signal Properties
Sometimes, the number of channels, elements, and bytes required for storing values, are referred to as "Signal Properties". There is a separate class, SignalProperties, for expressing those values, and determining whether a given signal "fits" into another one, i.e., whether the values contained in one signal may be copied into another signal without loss of information. GenericSignal uses a SignalProperties member to maintain information about its properties.