|
|
|
| R2012a Documentation → Phased Array System Toolbox | |
Learn more about Phased Array System Toolbox |
|
| Contents | Index |
This table summarizes what's new in Version 1.1 (R2011b):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
| Yes Details below | Yes Summary | Bug Reports |
New features and changes introduced in this version are
The new phased.ConstantGammaClutter System object helps you model surface clutter using the constant gamma model. You can use this object when simulating a radar system or estimating its performance statistically.
For more information, see these resources:
These new utility functions can help you implement custom clutter models:
The new phased.PhaseCodedWaveform System object generates samples of a phase-coded pulse waveform. This object supports these code types:
Barker
Frank
P1
P2
P3
P4
Px
Zadoff-Chu
For more information, see Phase-Coded Waveforms and phased.PhaseCodedWaveform.
The phased.MatchedFilter System object supports spectrum weighting using these window types:
Hamming
Chebyshev
Hann
Kaiser
Taylor
You can also specify a custom window. To do so, write a function that takes the window length as an input argument and returns window coefficients in an output argument.
For more information, see Matched Filtering or phased.MatchedFilter.
If you save a phased.MatchedFilter object in a MAT-file in V1.1 (R2011b) and then load the MAT-file in V1.0 (R2011a), the object does not perform spectrum weighting. The Command Window shows this warning:
Warning: While loading an object of class 'phased.MatchedFilter': No public field SpectrumWindow exists for class phased.MatchedFilter.
If you write code in V1.1 (R2011b) that sets or reads any of the following properties of phased.MatchedFilter object, the code produces an error message in V1.0 (R2011a).
SpectrumWindow
CustomSpectrumWindow
SpectrumRange
SampleRate
SidelobeAttenuation
Beta
Nbar
The phased.URA System object supports both triangular lattices and rectangular lattices. You use the Lattice property to select the lattice type.
In V1.0 (R2011a), phased.URA supports only rectangular lattices and does not have a Lattice property.
If you save a phased.URA object in a MAT-file in V1.1 (R2011b) and then load the MAT-file in V1.0 (R2011a), the object uses a rectangular lattice. The Command Window shows this warning:
Warning: While loading an object of class 'phased.URA': No public field Lattice exists for class phased.URA.
If you write code in V1.1 (R2011b) that sets or reads the Lattice property of a phased.URA object, the code produces an error message in V1.0 (R2011a).
The plotResponse method can plot multiple frequency responses along an azimuth cut or elevation cut. This method is available for the System objects for array design, antenna elements, and microphone elements. To create a plot of multiple frequency responses, use a plotResponse syntax in which:
FREQ is a row vector.
RespCut either does not appear explicitly, or has the value 'Az' or 'El.
The affected System objects are:
In V1.0 (R2011a), FREQ must be a scalar. The resulting plot shows one frequency response.
The phased.CustomAntennaElement System object now permits more general radiation patterns. The main beam of the pattern is no longer required to point to 0 degrees azimuth and 0 degrees elevation.
The save and clone operations now store all states of the System objects in the phased package. As a result, calling the step method on a loaded or cloned object resumes processing from the state where the original object left off. In V1.0 (R2011a), the loaded or cloned object is unlocked and uninitialized.
If your legacy code exploits the unlocked, uninitialized state of a loaded or cloned object, you should update the code in V1.1 (R2011b). You can use the release method to unlock objects.
You can now create custom System objects in MATLAB. This capability allows you to define your own System objects for time-based and data-driven algorithms, I/O, and visualizations. The System object API provides a set of implementation and service methods that you incorporate into your code to implement your algorithm. See Define New System Objects in the DSP System Toolbox™ documentation for more information.
For version 1.1 (R2011b), some error and warning message identifiers have changed in Phased Array System Toolbox software.
If you have scripts or functions that use message identifiers that changed, you must update the code to use the new identifiers. Typically, message identifiers are used to turn off specific warning messages, or in code that uses a try/catch statement and performs an action based on a specific error identifier.
For example, the 'phased:phased:RootWSFEstimator:ZeroSourceNumber' identifier and the 'phased:phased:RootMUSICEstimator:ZeroSourceNumber' identifier have both changed to 'phased:phased:doa:ZeroSourceNumber'. If your code checks for one of the earlier values, you must update it to check for 'phased:phased:doa:ZeroSourceNumber' instead.
To determine the identifier for a warning, run the following command just after you see the warning:
[MSG,MSGID] = lastwarn;
This command saves the message identifier to the variable MSGID.
To determine the identifier for an error, run the following command just after you see the error:
exception = MException.last; MSGID = exception.identifier;
Note Warning messages indicate a potential issue with your code. While you can turn off a warning, a suggested alternative is to change your code so it runs warning-free. |
 | Version 1.2 (R2012a) Phased Array System Toolbox Software | Version 1.0 (R2011a) Phased Array System Toolbox Software |  |
Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
