Main Content

Unbuffer

为seq Unbuffer输入帧uence of scalar outputs

Library

Signal Management / Buffers

dspbuff3

  • Unbuffer block

Description

The Unbuffer block unbuffers anMi-by-Ninput into a1-by-Noutput. That is, inputs are unbufferedrow-wiseso that each matrix row becomes an independent time-sample in the output. The rate at which the block receives inputs is generally less than the rate at which the block produces outputs.

The block adjusts the output rate so that thesample periodis the same at both the input and output, Tso=Tsi. Therefore, the output sample period for an input of frame sizeMiand frame period Tfiis Tfi/Mi, which represents arateMitimes higher than the input frame rate. In the example above, the block receives inputs only once every three sample periods, but produces an output once every sample period. To rebuffer inputs to a larger or smaller frame size, use theBufferblock.

In theex_unbuffer_ref1example model, the block unbuffers a four-channel input with a frame size of three. TheInitial conditionsparameter is set to zero and the tasking mode is set to multitasking, so the first three outputs are zero vectors.

Zero Latency

The Unbuffer block haszero-tasking延迟in Simulink®single-tasking mode. Zero-tasking latency means that the first input sample (received att=0) appears as the first output sample.

Nonzero Latency

Formultitaskingoperation, theUnbuffer block's buffer is initialized with the value specified by theInitial conditionsparameter, and the block begins unbuffering this frame at the start of the simulation. Inputs to the block are therefore delayed by one buffer length, orMisamples.

TheInitial conditionsparameter can be one of the following:

  • A scalar to be repeated for the firstMioutput samples of every channel

  • A length-Mivector containing the values of the firstMioutput samples for every channel

  • AnMi-by-Nmatrix containing the values of the firstMioutput samples in each ofNchannels

Note

For more information on latency and the Simulink tasking modes, seeExcess Algorithmic Delay (Tasking Latency)andTime-Based Scheduling and Code Generation(Simulink Coder).

Parameters

Initial conditions

The value of the block's initial output for cases of nonzero latency. You can specify a scalar, vector, or matrix.

Supported Data Types

Port Supported Data Types

Input

  • Double-precision floating point

  • Single-precision floating point

  • Fixed point (signed and unsigned)

  • Boolean

  • 8-, 16-, and 32-bit signed integers

  • 8-, 16-, and 32-bit unsigned integers

Output

  • Double-precision floating point

  • Single-precision floating point

  • Fixed point (signed and unsigned)

  • Boolean

  • 8-, 16-, and 32-bit signed integers

  • 8-, 16-, and 32-bit unsigned integers

Extended Capabilities

Fixed-Point Conversion
Design and simulate fixed-point systems using Fixed-Point Designer™.

Version History

Introduced before R2006a