phased.STAPSMIBeamformer
Sample matrix inversion (SMI) beamformer
Description
The SMIBeamformer
object implements a sample
matrix inversion space-time adaptive beamformer. The beamformer works
on the space-time covariance matrix.
To compute the space-time beamformed signal:
Define and set up your SMI beamformer. See Construction.
Call
step
to execute the SMI beamformer algorithm according to the properties ofphased.STAPSMIBeamformer
. The behavior ofstep
is specific to each object in the toolbox.
Note
Starting in R2016b, instead of using the step
method
to perform the operation defined by the System object™, you can
call the object with arguments, as if it were a function. For example, y
= step(obj,x)
and y = obj(x)
perform
equivalent operations.
Construction
H = phased.STAPSMIBeamformer
creates a
sample matrix inversion (SMI) beamformer System object, H
.
The object performs the SMI space-time adaptive processing (STAP)
on the input data.
H = phased.STAPSMIBeamformer(
creates
an SMI object, Name
,Value
)H
, with each specified property
Name set to the specified Value. You can specify additional name-value
pair arguments in any order as (Name1
,Value1
,...,NameN
,ValueN
).
Properties
|
Sensor array Sensor array specified as an array System object belonging
to the Default: | ||||
|
Signal propagation speed Specify the propagation speed of the signal, in meters per second, as a positive scalar. You can specify this property as single or double precision. Default: Speed of light | ||||
|
System operating frequency Specify the operating frequency of the system in hertz as a positive scalar. The default value corresponds to 300 MHz. You can specify this property as single or double precision. Default: | ||||
|
Source of pulse repetition frequency Source of the PRF values for the STAP processor, specified as
Default: | ||||
|
Pulse repetition frequency Pulse repetition frequency (PRF) of the received signal, specified as a positive scalar. Units are in Hertz. This property can be specified as single or double precision. DependenciesTo enable this property, set the Default: | ||||
|
Source of targeting direction Specify whether the targeting direction for the STAP processor
comes from the
Default: | ||||
|
Targeting direction Specify the targeting direction of the SMI processor as a column vector of length 2. The
direction is specified in the format of Default: | ||||
|
Number of phase shifter quantization bits The number of bits used to quantize the phase shift component of beamformer or steering vector weights. Specify the number of bits as a non-negative integer. A value of zero indicates that no quantization is performed. You can specify this property as single or double precision. Default: | ||||
|
Source of targeting Doppler Specify whether the targeting Doppler for the STAP processor
comes from the
Default: | ||||
|
Targeting Doppler frequency Specify the targeting Doppler of the STAP processor as a scalar. This property applies when
you set the Default: | ||||
|
Number of guarding cells Specify the number of guard cells used in the training as an even integer. This property specifies the total number of cells on both sides of the cell under test. You can specify this property as single or double precision. Default: | ||||
|
Number of training cells Specify the number of training cells used in the training as an even integer. Whenever possible, the training cells are equally divided before and after the cell under test. You can specify this property as single or double precision. Default: | ||||
|
Output processing weights To obtain the weights used in the STAP processor, set this property to
Default: |
Methods
step | Perform SMI STAP processing on input data |
Common to All System Objects | |
---|---|
release | Allow System object property value changes |
Examples
Algorithms
References
[1] Guerci, J. R. Space-Time Adaptive Processing for Radar. Boston: Artech House, 2003.
[2] Ward, J. “Space-Time Adaptive Processing for Airborne Radar Data Systems,” Technical Report 1015, MIT Lincoln Laboratory, December, 1994.
Extended Capabilities
Version History
Introduced in R2011a