The accuracy of Doppler spread of the Rayleigh and Rician Fading Channel Blocks has been improved. The blocks now give better results for high sampling rates and small Doppler frequencies, as specified in communication standards such as WCDMA.
The following demos now generate code using Real Time Workshop:
- dmt_sim
- dvbt_sim
- tstgraycod
- phasenoise_sim
- dmt_alt_sim
- tstconvcod <\ul>
The passband FSK and CPM modulators have been modified to generate more accurate waveforms by performing FIR interpolation when upsampling. The FIR filters significantly reduce the levels of any spectral copies revealed by upsampling. They also introduce delay into the modulators.
The Reed-Solomon blocks now encode and decode signals correctly.
The new function RSDEC accurately decodes Reed-Solomon codes containing up to t errors in each codeword. This new function replaces the earlier functions RSDECO and RSDECODE.
The new functions RSENC and RSDEC operate on the new Galois data type, which represents symbols using a decimal format. The formats used in the earlier functions, RSENCO, RSENCODE, RSDECO, and RSDECODE, are no longer supported. See "Updating Existing Reed-Solomon M-Code" in the Release Notes to learn how to convert your existing code data to the format used in the new coding functions.
Also, the new functions enable you to choose whether parity bits appear at the beginning or end of each codeword.
If a model's fastest block execution rate is faster than the execution rate of the codec blocks (the codec sample rate times the frame size), then incorrect code will be generated. The generated code will run at the codec rate. There is no error checking to detect this condition. If the codec block is the fastest executing block in the model, then the generated code will be correct.
If you put a source block, such as a button or slider, in a different window and change the block's value using the mouse during the simulation, then the model now responds to your change.
sos
method no longer embeds filter gain in each section.sos
method no longer normalizes the filter after converting it to SOSFor Release 13, the online help text for filter design function
firlpnorm
is now correct.
There is a change in behavior of the Quantizer object method
set
-- you can no longer enter a property value without an associated property name when you useset
.For example, let
q = quantizer;In Version 2.1 or earlier of the toolbox
set(q,'wrap',[20 18])
was equivalent to
set(q,'OverflowMode','wrap','Format',[20 18])With the new restriction requiring both the property name and value
set(q,'wrap',[20 18])
causes an error in Version 2.2 of the Filter Design Toolbox.
To maintain consistency with MATLAB objects, and other toolbox objects, the behavior of
set
needed to change.Note that the constructor still can be used without property name- property value pairs:
q = quantizer('wrap',[20 18])
is equivalent to
q = quantizer('OverflowMode','wrap','Format',[20 18])
sos
method no longer embeds filter gain in each section.The QFILT sos
method no longer embeds the filter gain in each
section. It now puts the filter gain into the ScaleValue property of the
QFILT.
sos
method no longer normalizes the filter after converting it to SOSThe QFILT sos
method no longer normalizes the filter
coefficients after converting it to second-order sections, therefore care
should be taken to avoid overflows by adjust the coefficient format of the
filter.
In Release 12, ADDVAR systematically initialized the new variable with 3 membership functions, thus breaking the command line API, where it is common first to add the variable and then define the membership functions. Release 13 added logic to allow GUIs to create 3 default membership functions without interfering with command line calls.
The cases a-b or b=c in trimmf (a-b and c=d in trapmf) caused Divide by Zero and improper results in Simulink. These blocks have been reimplemented using the IF block to always produce answers consistent with the M file implementation
cpselect
would ask to save points when it wasn't necessaryfspecial
didn't accept a parameter value of 0 for 'laplacian' and 'unsharp' optionsgray2ind
returned a logical output if the input was logicalimadjust
could error if passed degenerate inputsimerode
could get the first 32 rows wrong when performing binary erosionimhist
could cause a segmentation violation on IRIX if input contained NaNsimnoise
could return a column vector when using the Poisson optionpixval
could give a confusing error message for figures with normalized unitsimshow
sometimes not visibledicomread
dicomread
and dicominfo
cpselect
edge
function.cpselect
would ask to save points when it wasn't necessaryWhen you closed the contol-point selection tool (cpselect
, it
would ask if you wanted to save control points, even if you had already
done so. This has been fixed.
fspecial
didn't accept a parameter value of 0 for 'laplacian' and 'unsharp' optionsThe fspecial
function now accepts a parameter value of 0
for the 'laplacian' and 'unsharp' options.
gray2ind
returned a logical output if the input was logicalIf the input image togray2ind
was logical, then the output was also logical. Thegray2ind
function now returns the correct output in such situations.
imadjust
could error if passed degenerate inputsA call toimadjust
with identical low and high limits, such as
imadjust(A,[b b],[]),
would cause
imadjust
to error out. The problem was fixed by providing default limits when the input limits are degenerate.
imerode
could get the first 32 rows wrong when performing binary erosionWhen performing binary erosion with a decomposed structuring element, such
as strel(ones(5,5))
, the first 32 rows of the output image
could be wrong. This has been fixed.
imhist
could cause a segmentation violation on IRIX if input contained NaNsThe function imhist
no longer causes a segmentation violation
on IRIX if
input contained NaNs.
imnoise
could return a column vector when using the Poisson optionThe function imnoise
now returns a correctly-
sized output instead of a column vector when using the Poisson option.
pixval
could give a confusing error message for figures with normalized unitsTurning on pixval
for a figure in normalized units could
produce a
confusing error message. Pixval now issues a more informative error
message if the figure is not in pixel units.
imshow
sometimes not visibleIf invalid input was passed toimshow
, it would sometimes error out after creating an invisible figure object. Subsequent calls toimshow
would appear to not do anything, because the images were being sent to the invisible figure. The problem was fixed by adding additional input checking toimshow
.
dicomread
The dicomread
function no longer fails when reading from a
file with private data using "explicit VR" syntax.
The dicomread
function used no longer fails when reading
signed data from pixels which were not "normal" lengths.
The RLE decoder used by dicomread
used to only work for 8-bit
grayscale images (and only for certain ones at that). The decoder now
correctly handles all bit depths and image types.
dicomread
and dicominfo
dicomread
anddicominfo
parse files quicker than in the past, especially for files with a lot of metadata.
cpselect
The legend box for the control-point selection tool (cpselect
)
was
unresizable, which sometimes caused the title bar to be unreadable. This
has been fixed.
edge
function.In the Canny algorithm in the edge
function, Gaussian
smoothing should be run
perpendicular to the direction of differentiation. This has been implemented.
When using the control-point selection tool (cpselect
) in
point-prediction
mode, sometimes a stray control point would appear that could not be
deleted. This has been fixed.
Version 1.43 eliminates the round-off problem that caused the return value
of the distance
function to include a small, nonzero imaginary
part for certain inputs.
Version 1.3 fixes setpostn
to handle longitude limits that
straddle the
prime meridian.
A typographical error in defaultm
in the false northing for
Universal Transverse Mercator (UTM) has been corrected. That error had
caused incorrect UTM/geographic conversions for points in the southern
hemisphere.
Padding added as needed in etopo5
when reading different
numbers of
elements from the northern and southern hemisphere files.
'cubic'
method in griddata
no longer produces segmentation fault.filter
function has better support for multidimensional datalog10(10^i)
now returns i
, exactlylsqr
now converges for rectangular systems.sqrtm
now returns correct results for singular Hermitian matrix.diff
function'cubic'
method in griddata
no longer produces segmentation fault.Previously, the'cubic'
method of thegriddata
function would occasionally encounter a segmentation fault. This no longer happens.
filter
function has better support for multidimensional dataFor multidimensional inputs, filter
sometimes produced
incorrect error messages or the wrong results. This no longer happens.
log10(10^i)
now returns i
, exactlyPreviously,log10
was computed directly as log(x) / log(10), where log is the natural logarithm. The error in this was particularly visible in computations of the formlog10(10^i)
, for example:>> log10(1e6) ans = 5.999999999999999e+00Now,
log10
does some additional scaling to computelog10(10^i)
to the nearest bit.
lsqr
now converges for rectangular systems.Previously,lsqr
only converged for square, consistent systemsA*x=b
and returned a solutionx
wherenorm(b-A*x)
was small.Now,
lsqr
also converges for rectangular systems and returns a solutionx
wherenorm(b-A*x)
is not necessarily small, but is minimized, and in factnorm(A'*(b-A*x))
is small.
sqrtm
now returns correct results for singular Hermitian matrix.A matrix square root always exists for Hermitian matrices. Previously,sqrtm(X)
sometimes returned a matrix of allNaN
s for matricesX
that were both Hermitian and singular. Nowsqrtm(X)
returns the correct results for these matrices.sqrtm
is now also faster for Hermitian matrices.
The Array Editor can now show arrays with more than 10,000 elements. It does not support arrays with more than 65,536 (2^16) elements.
diff
functionPreviously, MATLAB encountered a segmentation fault when computing
diff(sparse([1;1]),-1)
. Now, an error message is displayed if
the order is not a real positive integer.
In previous releases, the Import Wizard was sometimes slow when opening large files, but the problem has been fixed in this version.
There is no longer a performance problem with more than 1000 variables open in the Workspace browser.
Modal dialogs on Windows platforms have been improved in terms of common appearance and stability. In Release 12, MATLAB would sometimes lock up due to modal dialogs. In Release 13, this is fixed.
- Serial port objects now work with the baud rates 128,000 and 256,000 along with all other standard baud rates listed in the BaudRate property help.
- MATLAB can now find serial ports if the MATLAB root directory contains an underscore.
- A memory leak no longer occurs when opening and closing the serial port connection.
- On Windows, serial port objects now recognize ports greater than COM4.
- On Solaris, there is no restriction on the number of times that the serial port can be opened.
- On Linux, there is a significant speed increase when writing data to the serial port.
You can now rename variables from within the Workspace Browser. Right-click a variable name, select Rename from the context menu, and edit the name.
The 3-D and 4-D design views will now correctly display all of the points in a design. Previously, for some factor ranges points at the edges of the graph, limits were not displayed.
Breakpoint filling using "ShareCurvThenAve" now works correctly in all cases and is significantly faster than the previous version.
You can now convert all Variable Dictionary items into an alias of another Variable Dictionary item. Previously, this would cause an error in some circumstances where the items were being used elsewhere in the Cage project.
The Cross Section view of the Model Selection window now displays the correct model error while the input factor lines are being dragged. Previously, the error shown while dragging the line was different to that shown when the mouse button was released.
1-D tables in Cage now correctly show the difference between two versions in the history.
Re-fitting an RBF model after pruning now uses the correct value for log10 (GCV).
You can now import large amounts of data from Excel into a Dataset. Previously, attempting to do this caused an error to occur.
When you add new data to a testplan that already has models, any sweep notes which have been made are now saved when the models are re-fitted.
Optimal designs with stratified candidate sets will now correctly fail if there are not enough stratified levels to support the model. Previously, small numerical errors allowed the optimisation to proceed, but poor conditioning meant that the optimal value oscillated up and down.
Previously, if a local sweep was removed from fitting at the local level, the global response features only showed the removed sweep in their list of removed points if one or more outliers was selected and removed at the global level. All removed points are now shown at the global response feature level all of the time.
You can now create large Latin Hypercube designs from the Classical Design Browser without MATLAB appearing to hang. Previously a full set of search iterations was erroneously done before the expected waitbar appeared and the search commenced.
Stratified Latin Hypercube designs now choose their stratified levels so they split the stratified dimension into exactly equal sections. Previously, the levels were "snapped" to the nearest non-stratified level, which depends on the total number of points in the design. This meant that some levels were shifted down slightly and others up.
You can now view Datasets that consist entirely of imported data. Previously, viewing these datasets caused Cage to crash.
You can now delete designs from anywhere in the Design Editor tree without causing errors. Previously, if your best design was at the end of the design tree and you deleted a design, you received an error when you closed the Design Editor.
fmincon
playshow
command to run slideshow style demosfmincon
The functionfmincon
would in some small number of cases hang when the problem was ill-posed or ill-conditioned. In these cases,fmincon
no longer hangs.
playshow
command to run slideshow style demosStarting in Release 13, to run slideshow style demos from the command line, you must use theplayshow
command. For example,
playshow circustent
You can continue to run other styles of demos from the command line by typing just the demo name. Optimization Toolbox demos that are affected:circustent
,molecule
,optdeblur
.
The Simulink.RTWInfo class now has an additional property, Alias. The Alias property defines an identifier to be used in the generated code for a parameter, signal or block state. This allows you to override the name of the signal, parameter, or state. If an alias is used, Real-Time Workshop checks that the alias is unique, instead of checking the data name.
The "Show eliminated statements" option (in the Real-Time Workshop General code generation options) is now off by default. As long as it remains off, the Real-Time Workshop no longer generates comments referring to blocks that have been removed from the model via block reduction optimization.
LibBlockInputSignalConnected returns 1 if the specified input port is connected to a block other than the Ground block and 0 otherwise.LibBlockOutputSignalConnected returns 1 if the specified output port is connected to a block other than the Terminator block and 0 otherwise.
The PreLook-Up Index Search block now generates correct code for the case of nonscalar vector inputs that are part of different actual signals, such as when 6 signals are combined using a Mux block.
Several problems with code generation for the pulse generator block have been fixed:
- If the block type is PulseGenerator instead of DiscretePulseGenerator, code can now be generated.
- The scalar expansion for the delay variable is now correct.
- The start function for the Time-based mode in a variable step solver now can generate code.
Note: Problems 1 and 2 also affected the Simulink Accelerator.
S-function TLC files should no longer use the BlockInstanceData method. All data used by a block should be declared using data type work vectors (DWork).
cremez
Example Fixedcremez
Example FixedThe second example on the cremez
reference page has been updated
and now works correctly.
The pole/zero plot in FDATool and FVTool now can display multiple roots at a single plot point.
The scaling of the magnitude response portion of the Magnitude and Phase Analysis plot in both FDATool and FVTool was incorrect for some filters. It now is scaled correctly.
Print Preview, when no markers are displayed in the SPTool Filter Viewer, now works correctly.
mdl
filemdl
fileThemdl
file now has a new section, "BlockParameterDefaults." The default values for the parameters used by the block types present in the model are written into this section. Then, an individual block instance's parameter values are written into themdl
file only if they differ from the default. This technique reduces the size of themdl
file, as well as reducing the file load time. A block diagram parameter,SaveDefaultBlockParams , exists to control whether or not the parameter defaults are saved to the file. By default it is set to true.
In previous releases, adding signals to a bus or otherwise changing its structure required that you update any Bus Selector blocks that select signals from the bus. In the current release, you need update the Bus Selector only if it selects signals that no longer exist or no longer have unique names.
Previous releases of Simulink prevented you from creating Simulink data object classes in the MATLAB directory or any of its subdirectories. The current release allows you to create classes in the
work
subdirectory of the MATLAB root directory.
In Release 12.1, a Dot Product block in a loop cannot determine its port dimension and hence causes a simulation error. Now the block assigns a default dimension setting to the port, thereby avoiding the simulation error.
The "Undefined variable names" error is no longer displayed when selecting Menu->Tools->Coverage Settings without an available Simulink license.
For multirate models that are simulated to very large times, Simulink would eventually miss a sample hit for one of the rates. This would cause Simulink to hang. This has now been fixed and Simulink no longer hangs.
The pulse generator block would somtimes report that the computed sample time is not an integer multiple fo the fixed step size when, in fact, it was. This has been fixed.
The option for using a fast index search algorithm that relies on evenly spaced breakpoints for look-up tables was enhanced to better detect evenly spaced breakpoints within a tolerance ofvalue*eps
. Note that breakpoint expressions such as[-5:0.1:5]
may still need to be written as0.1*[-50:50]
to generate a dataset that is evenly spaced within the required tolerance. The linear and binary search options will of course still work on any strictly increasing breakpoint data set (not just evenly spaced ones).
You can now scroll Simulink diagrams around using the keyboard by pressing the Ctrl key in conjunction with any of the arrow keys. This is sometimes more convenient than manipulating the scroll bars with the mouse.
In previous releases, pressing the Esc key while dragging a block or performing other types of drag operations caused MATLAB and Simulink to become unresponsive. In the current release, pressing the Esc key will abort the drag operation.
The behavior of the PreLook-Up Index Search block (index only mode) and the Look-Up Table n-D block (in flat interpolation mode) were changed to return the last index in the table when the input value is at or above the last breakpoint value as this is more useful than the previous behavior. For the Look-Up Table n-D block, this is done on an individual dimension basis. In previous versions (Simulink 4.0 and 4.1), the index search would deliberately return the next to last index and the n-D flat look-up would deliberately return the next to last table value even when the input value was at or above the last breakpoint.
Scope blocks with "Save To Workspace" variable names longer than the maximum MATLAB variable length (currently 31 characters) used to crash Simulink in unpredictable ways during simulation. Such variable names will no longer crash Simulink, though they will generate an error.
In previous releases, holding down the Shift key and dragging a block inside a reference block (i.e., a library link) disconnects the block's signal lines and brings up a dialog box asking if you would like to disable the link. In the current release, Simulink does not disconnect the lines.
Under certain circumstances with the Simulink Accelerator, the generated code of models containing enable, if and case subsystems could be activiated during minor time steps, causing incorrect outputs. This has been fixed.
The Simulink Accelerator no longer requires a Real-Time Workshop license to function properly.
On Unix platforms, a segmentation violation would occur if you added or deleted blocks in a Simulink model while the Model Browser was open. This has been fixed.
Releasing the left mouse button over the Simulink menu bar when drag-selecting multiple blocks caused UNIX to lock up. This has been fixed.
Grouping blocks in Simulink into a subsystem caused a divide-by-zero error if the blocks were too close to the top or left edge of the model. This has been fixed.
Library subsystems containing self-modifying masked blocks no longer have to be marked as MaskSelfModifiable for the linked blocks to be connected properly.
The Configurable Subsystem has been made faster and more robust when changing block choices. This is especially noticeable for large subsystems.
Breaking disabled library links from the command-line now works.
In the previous release, you could not use get_param or set_param to set or get the value of the CurrentBlock parameter in the command-line debugger until you selected a block. The Simulink command-line debugger now allows you to set and get the value of this parameter without having to first select a block with the mouse.
If changes are made to a linked block, propagating such changes to the library via the Link options menu now does not result in recursive links.
pprfn
fails when no breaks need be insertedsplinetool
now tracked properlyspcol
for various unusual inputs correctedplayshow
command to run slideshow style demospprfn
fails when no breaks need be insertedpprfn
now properly returns the function unchanged in case all
the
additional breaks are already breaks for the function.
splinetool
now tracked properlyEach spline fit now remembers the data to which it was fit. If, at some point, you make a previously constructed spline fit the current one, then also the data currently showing get changed to the data to which that spline was fit.
spcol
for various unusual inputs correctedspcol
now provides a correct sparse version of its output
even for knot
sequences with unusual end knot multiplicities, and when some sites lie to
the right of the last knot while some site appears more than once.
None of these cases is likely to occur in ordinary spline work since, in
all of them, the resulting matrix is not invertible.
playshow
command to run slideshow style demosStarting in R13, to run slideshow style demos from the command line, you must use theplayshow
command. For example,
playshow splexmpl
You can continue to run other styles of demos from the command line by typing just the demo name. Splines Toolbox demos that are affected:splexmpl
,histodem
,ppalldem
,spapidem
,getcurv2
,spalldem
.
ml
namespace operator and the ml functionAny chart or library chart can now export a function and any other chart or library chart can call it as long as they are both (caller and callee) accessible through the same main model.
Code generation for an RTW target failed when the chart included output array data initialized from workspace. (Occurred in versions 3.0 through 4.1.1.)
Code generated for an RTW target did not include custom code entered by user. (Occurred in versions 4.1 through 4.1.1.)
Hierachical Printing invoked from a Simulink window when the charts were closed caused transition label positions to change and also caused incorrect printouts. (Occured in version 4.0 through 4.1)
In models containing an infinite flow graph loop, simulation could not be stopped using a keyboardctrl-C , or with theStop Simulation button in the diagram editor and debug window.
ml
namespace operator and the ml functionMatrix support is enabled for theml
namespace operator and theml
function. Expressions involving theml
namespace operator and theml
function call can take 2-dimensional matrix arguments and return 2-dimensional matrices. They are no longer limited to scalar arguments and return values as in previous versions.
The Stateflow parser did not flag mismatched dimensions or array lengths in vectorized assignments such as x = y, where x and y are vector data with different dimensions and/or lengths. This caused crashes during runtime. (Occured in versions 2.0 through 4.1.)
Models containing Stateflow charts must have file names limited to 25 characters or less. When you try to save a model with more characters, an error results. If you try to load a model with more than 25 characters in its file name, a warning results telling you to reduce the number of characters in the file name to 25 or less.
Certain uses of the pointer and address operators ('->' and '&', respectively) in state and transition actions caused uncompilable generated code (occurred in versions 3.0 through 4.1.1).
The Stateflow Search and Replace Tool errored out in the presence of LaTeX format strings in Stateflow annotations. (Occured in Versions 4.0.2 through 4.1.)
When a grouped state containing "smart" transitions was resized, the transitions in the newly resized state made a graphical mess.(Occured in Version 4.1)
Stateflow now handles up to 254 events per chart. The previous maximum was 127. Stateflow now throws an error if your chart has more than 254 events.
Stateflow now supports fixed-point data. Fixed-point numbers are commonly used to perform limited range and precision floating point operations with integers in embedded environments. See "Fixed-Point Data Types" in Chapter 7, Action Language, of the the Stateflow User's Guide.
Stateflow now supports vector and matrix array data with the scope "Input to Simulink" and "Output to Simulink." Previously, Stateflow supported only scalar data for these scopes.
Transition actions were handled incorrectly for a confluence of transitions into a single destination such as the junction shown below:
During simulation an early return from an event broadcast from a transition left that transition highlighted for the rest of the simulation. (Occured in versions 3.0 through 4.1.)
Optimization of state exit functions caused incorrect code to be generated. (Occurred in version 4.2)
Charts containing unstructured flow graphs caused compilation errors during RTW build.
For some graphical functions with a return value and unusual flow graph topology, a final return statement was missing from the generated code.
Optimization of simple "if" conditional statements caused incorrect code to be generated. (Occurred in version 4.2)
Passing chart input data to graphical functions caused code generation failure for Real-Time Workshop targets.
Using min/max macros in Stateflow charts caused compilation failures during RTW builds of ert/grt embedded targets. This has been fixed.
cluster
function usable with larger problemsdendrogram
graph corrected for plotting a subset of nodespdist
more efficient for large data setsranksum
uses a continuity correctionregstats
functionclassify
nbin*
) functions no longer require an integer R
valueplayshow
command to run glmdemo
cluster
function usable with larger problemsThecluster
function is no longer recursive, so it no longer encounters a recursion limit when it is applied to a large data set. Consequently,cluster
now succeeds with larger data sets than in the past.
dendrogram
graph corrected for plotting a subset of nodesIn a plot of a subset of the nodes in a cluster tree, the
dendrogram
function now adjusts the Y axis limits to scale
the
tree properly, and it
shows the correct distance values. Before Version 4.0 (Release 13), it was
subtracting an
offset to position the minimum distance value near zero, and therefore it
was not possible to read the correct distance values from the Y axis
of the resulting plot.
pdist
more efficient for large data setspdist
now makes more efficient use of memory, so it can be
used on larger
problems than in previous releases.
ranksum
uses a continuity correctionThe ranksum
function uses an exact calculation for small
sample sizes, and
a normal approximation for larger sample sizes. Starting in Version 4.0
(Release 13),
the normal approximation now includes a continuity correction.
regstats
functionIn Version 3.0 and earlier of the Statistics Toolbox, the covratio statistic was calculated incorrectly. The calculation was fixed in Version 3.1. This statistic measures the ratio of the generalized variance of the coefficient estimates without a given row, to the generalized variance using all the data.
classify
The algorithm that was previously implemented inclassify
used the Mahalanobis distance between sample points and training groups, with stratified estimates of covariance. The new implementation adds the standard algorithms for linear (default) and quadratic discriminant analysis. Use thetype
'mahalanobis'
in the new version to duplicate the behavior of the previous version.
nbin*
) functions no longer require an integer R
valueConsistent with a more general interpretation of the negative binomial, these functions now accept any positive value, including nonintegers, for the size parameterR
:nbincdf
,nbininv
,nbinpdf
,nbinrnd
,nbinstats
.
playshow
command to run glmdemo
Starting in Release 13, to run slideshow style demos such as
glmdemo
from the command line, you must use the
playshow
command. For example,
playshow glmdemoYou can continue to run other styles of demos from the command line by typing just the demo name.
glmdemo
is the only slideshow style demo in the Statistics Toolbox Version 4.0.
std2
function in Wavelets and Image Processingcmorwavf
functionwpdec
function with a user-defined functionwptree
object from a MAT-filestd2
function in Wavelets and Image ProcessingYou no longer get slightly different results from the std
(compute
standard deviation of matrix elements) function in the Image Processing
Toolbox and the Wavelet Toolbox.
cmorwavf
functionThe two last input arguments are no longer reversed in the
cmorwavf
function.
wpdec
function with a user-defined functionUsingwpdec
with a user-defined function no longer produces errors that were caused bywpdec
's use ofwentropy
.
wptree
object from a MAT-filewptree
has been updated so that awptree
object can be loaded from a MAT-file.
Complex data cannot be loaded into the Continuous Wavlet 1-D. An error message stating that the data must be real is displayed.
Previously, when you created a Stand-alone application, polling mode did not start. Now, it does.