Code Analyzer Checks

R2026b

List of Code Analyzer checks available in MATLAB

This page describes Code Analyzer checks available in MATLAB^®. You can enable, disable, or configure these checks in addition to writing new checks to meet your set of coding standards. See Customize Code Analyzer Checks Using Configuration File for more information.

Incomplete Analysis

`DEEPC` —
Block comments are nested too deeply.

Severity: Error

Can be disabled: false

MATLAB has a nesting limit of 7 on block comments, and this file exceeds that limit. Block comment indicators, %{ and %}, must be the only characters on the lines on which they appear. Therefore, code such as the following does not end a block comment:

%} end of block comment

This error could cause your file to appear to have deeply nested block comments, when that was not your intent.

Make sure that you have specified block comment indicators properly. Review the code in the Editor to ensure that the comments include only the lines that you expect. If so, remove some levels of nesting. Removing inner block comments lowers the nesting level.

Related Documentation: Add Comments to Code

`DEEPN` —
Functions are nested too deeply.

Severity: Error

Can be disabled: false

MATLAB enforces a nesting limit of 15 for functions. This message appears when one or more of the following is true:

Some of the functions in the file are written with end statements and others are not.
When Code Analyzer examines the file, it checks to see if functions terminate with end statements. If the functions are not nested, you can omit their corresponding end statements. However, the same file cannot have some functions with end statements and some without.
There is an extra end statement in the file and it appears to Code Analyzer that it matches a function keyword.
For example, suppose your code has nested for loops and multiple unnested functions without end statements. Furthermore, suppose there is an extra end statement for one of the for loops. If that end statement appears to match a function keyword, Code Analyzer interprets it as the situation described in the first item in this list.
Functions with end statements are nested more than 15 deep.

In the first two cases, additional messages might indicate where the extra end is. Code Analyzer indicates keywords that do not align with their matching end keywords.

If the message is due to mixing function keywords with and without corresponding end statements, fix the function style to be consistent. If there are extra end statements in the file by mistake, remove them. If you want more than 16 levels of nesting, consider using the MATLAB class system. Often the function nesting level drops and the code becomes simpler to understand when you use classes instead of nested functions.

Related Documentation: Nested Functions

`DEEPS` —
Statements are nested too deeply.

Severity: Error

Can be disabled: false

The file exceeds the limit to which statements can be nested within a MATLAB program control statement. Some MATLAB program control statements, such as if, for, while, and try can include multiple statements within them. This can result in nesting blocks of statements. The limit is exceeded most often with machine-generated M code, typically because an end is missing from a block of generated code that appears repeatedly in the input.

If the code is machine-generated, fix the generator program. If it is hand-written, rewrite the code to reduce the number of nested statements within the MATLAB program control statements.

Related Documentation: Enter Statements in Command Window

`EOFER` —
Code analysis did not complete. File contains too many syntax errors.

Severity: Error

`MXASET` —
The file is too complex to analyze. Simplify the code to improve code maintainability. For example, reduce the number of operations in expressions.

Severity: Error

Can be disabled: false

The code contains an expression that is too complex for code analysis to handle. Instead of providing complete code analysis, this message appears for the first line of code in this file. The expression causing the problem can be anywhere within the code.

Possible causes of code complexity include:

Too many concurrent indexing operators.
Too many concurrent suffixed unary operators, e.g. x'''''...
Too many concurrent binary operators, e.g. a > b > c > d > ....

Follow these steps:

Run checkcode from the Command Window to view all the messages for this file.
Correct the reported problems.

If this message persists after correcting the other problems, attempt to simplify the code. For instance, reduce the levels of nested expressions and make long expressions shorter wherever possible. Not only do the tools work more efficiently when you make such changes, but you and others can more easily understand, change, and debug the resulting code.

`NOFIL` —
Unable to open file VAR_FILE. File is not found.

Severity: Error

Can be disabled: false

Related Documentation: File Operations

`NOSPC` —
The file is too complex to analyze. Refactor the code to improve code maintainability. For example, reduce the nesting level of conditions or functions.

Severity: Error

Can be disabled: false

Code Analyzer reached a built-in limit while processing the file. Some of the built-in limits are intended to prevent errors which are fatal in the operating systems on which MATLAB runs. Other limits are intended to prevent the waste of time and memory that could occur if the Code Analyzer attempts to process a corrupt file. Instead of providing complete code analysis, this message appears for the first line of code in this file.

Possible causes include:

Too many nested conditionals or switch statements.
Too many nested functions/nested anonymous functions.
Too many prefixed operators, e.g. ...-+-+-+-+-x.

Related Documentation: Check Code for Errors and Warnings Using the Code Analyzer

`QUIT` —
Code analysis did not complete. Code Analyzer encountered an error.

Severity: Error

Can be disabled: false

Although it rarely occurs, when this message displays, it is typically caused by one or more syntax errors in the file. After a syntax error, Code Analyzer attempts to process the rest of the file, assuming a particular fix to the syntax error. However, there can be many different kinds of errors, and what Code Analyzer assumes is a fix might not be a fix to the actual problem. This assumption can lead Code Analyzer to detect inconsistencies in its own internal data structures, and elicit this message.

In most cases, syntax errors display in red when the file is open in the Editor. Fixing these errors usually eliminates this message. If this message displays when there are no other errors in the file, it exposes a bug in Code Analyzer. In that case, submit this message and the file information to customer support as follows:

Go to https://www.mathworks.com/support/contact_us.html
Select Product Usage.
Select Report a bug, and then answer the questions.

`RDERR` —
Unable to read file VAR_FILE.

Severity: Error

Can be disabled: false

Related Documentation: File Operations

`TEXTL` —
Text is too long for MATLAB to parse.

Severity: Error

Can be disabled: false

`TMMSG` —
More than 10,000 Code Analyzer messages were generated, leading to some being deleted.

Severity: Error

Can be disabled: false

`TMSMS` —
More than 1,000 parse error messages were generated, leading to some being deleted.

Severity: Error

Can be disabled: false

Syntax Errors

`BADCH` —
Invalid text character(s).

Severity: Error

Related Documentation: MATLAB Operators and Special Characters

`BADCT` —
Unicode explicit directional formatting characters are not supported.

Severity: Error

`BADFP` —
Invalid floating-point constant.

Severity: Error

`BADNOT` —
Using ~ to ignore a value is not permitted in this context.

Severity: Error

Related Documentation: MATLAB Operators and Special Characters

`BADNOTLHS` —
Invalid use of logical not operator (~) on left side of an assignment. To use ~ to ignore function outputs, separate output variables with commas.

Severity: Error

`BADOT` —
Use of two dots (..) is an invalid MATLAB construction.

Severity: Error

Two consecutive dots does not comprise a valid MATLAB construction. This message might indicate a typographical error. For example, if you meant to specify the ellipsis (...) line continuation operator, but accidentally specified two dots instead of three. Or, if you did not insert a space before the ellipsis, when needed.

For example, in processing the following line, Code Analyzer generates this message because the first dot is evaluated as a decimal point associated with the 3, leaving two consecutive dots:

x = 3...

Fix the code by adding or removing a dot, or by inserting a space before the ellipsis (...).

`ENDCT` —
An END might be missing, possibly matching VAR_RESERVED_WORD.

Severity: Error

The program has at least one keyword that is missing a required end statement. Code Analyzer attempts to identify and print the last keyword for which there is no end statement. Although there is definitely a missing end statement, it is possible that the indicated keyword is not the one that needs to be fixed. Code Analyzer cannot always accurately determine which keyword is missing the end statement.

Determine which keyword is missing an end statement, and supply it. If it is not obvious where the missing end statement is needed, insert an end statement at the end of the program. Then, look for new messages indicating that there are keywords not aligned with their end statement.

For a list of MATLAB keywords, type iskeyword in the Command Window.

`ENDCT2` —
An END might be missing (after line VAR_RESERVED_WORD), possibly matching VAR_NUMBER.

Severity: Error

`ENDCT3` —
An END might be missing (before VAR_RESERVED_WORD on line VAR_NUMBER), possibly matching VAR_RESERVED_WORD.

Severity: Error

`ENDCT4` —
A METHODS block or END might be missing before the function definition. This might be causing additional error messages.

Severity: Error

`ENDPAR` —
A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at end of file.

Severity: Error

Related Documentation: MATLAB Operators and Special Characters

`EOLPAR` —
A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at end of line.

Severity: Error

Severity: Error

Related Documentation: Function Argument Validation

`FVSYN` —
Invalid function argument syntax at VAR_RESERVED_WORD.

Severity: Error

For more information, see arguments Block Syntax.

`HEXTOOLONG` —
Hexadecimal literal has too many digits.

Severity: Error

`INBLK` —
A block comment is unterminated at the end of the file.

Severity: Error

Related Documentation: Add Comments to Code

`LHROW` —
The left side of an assignment cannot have multiple rows (';').

Severity: Error

Related Documentation: Creating, Concatenating, and Expanding Matrices

`MCPLD` —
Invalid property syntax at VAR_RESERVED_WORD.

Severity: Error

Related Documentation: MATLAB Operators and Special Characters

`VTPOD` —
Specify validation in the following order: size, then class, then functions.

Severity: Error

Related Documentation: Validate Property Values

Language Specification Errors

`MCCBU` —
This superclass constructor is called after a use of the constructed object.

Severity: Error

For information on constructing superclass objects in subclass constructors, see Constructing Subclasses.

`MCCMC` —
Constructor for superclass can only be called once.

Severity: Error

`MCSCM` —
To call a superclass method, the method name VAR_NAME must match the name of the subclass method VAR_NAME.

Severity: Error

`MCSCN` —
Method VAR_NAME tries to set a constant property.

Severity: Error

`MCSCO` —
A superclass constructor must be called using the first constructor output argument.

Severity: Error

For information on constructing superclass objects in subclass constructors, see Constructing Subclasses.

`MCSCT` —
Superclass constructor call must not be conditionalized or be part of another expression.

Severity: Error

Subclass calls to superclass constructors cannot be part of other expressions, contained in conditional statements, or made after references to the object.

The following code illustrates some examples of invalid superclass constructor calls because of the use of brackets, parentheses, or conditional statements.

classdef MyClass < A & B
    methods
        function obj = MyClass
            obj = [obj@A] % Invalid call to A constructor
            (obj@B) % Invalid call to B constructor
            if 1
                obj@B % Invalid conditional call to B constructor
            end
        end
    end
end

Severity: Error

The code uses a load function within a parfor (MATLAB Coder) loop to load variables. However, to classify variables correctly, the body of the parfor loop must be transparent. Transparency means that all references to variables must be visible in the text of the code. If a load function inside a parfor loop does not assign the MAT-file data to a MATLAB structure, variables that are not visible in the text of code might be loaded into the workspace.

For information on loading MAT-file data into a structure, see the help for load (Instrument Control Toolbox). For information on transparency, see Transparency (Parallel Computing Toolbox).

Call load as a function, assigning the output argument to a variable. For example:

x = load('myfile.mat')

`PFPF` —
parfor loops cannot be used inside other parfor loops.

Severity: Error

For additional information, see Nested parfor-Loops (Parallel Computing Toolbox).

`PFRFH` —
The parfor reduction function VAR_NAME must either be a function name or a broadcast variable.

Severity: Error

In analyzing a parfor loop, Code Analyzer has found a reduction variable that appears to be using a nonbroadcast variable reference as the reduction function. A reduction function must be either a function name or a broadcast variable. This message typically appears because there is an assignment to the named reduction function within the parfor loop.

For more information, see the topics on broadcast variables and reduction assignments under Classification of Variables in parfor-Loops (Parallel Computing Toolbox).

Ensure that you intend for the reduction to be within the loop, and that you define the variable used for the reduction function before the loop.

`PFRNG` —
The range of a PARFOR statement must be consecutive integers.

Severity: Error

The parfor (MATLAB Coder) statement allows only a range of increasing sequential numbers with a step value of 1.

Adjust your code, as follows:

If your code contains a statement such as parfor 1:2:10, rewrite your code so that step intervals of 1 return the expected results.

If your code contains a statement such as parfor i = V, ensure that V resolves to a contiguous series of values in a vector array, and the step between values is 1.

For example, assume your code is similar to the following, where <myArray> is an actual array, such as [2, 6, 7]:

vectorValues = [1, 4, 9, 16, 25, 36, 49];
vectorSequence = <myArray>;
parfor ii = vectorSequence
    val = vectorValues(ii);
    sprintf('index = %d  value = %d\n', ii, val)
end

Change your code as follows, depending on whether the vectorSequence array is sparse. Keep in mind that MATLAB transfers data to workers once per iteration.

If the vectorSequence array is sparse, use this code, which results in fewer data transfers than the original code, but incurs the cost of copying the data into vectorValueSubset.

vectorValues = [1, 4, 9, 16, 25, 36, 49];
vectorSequence = [2, 6, 7];
vectorValueSubset = vectorValues(vectorSequence);
parfor jj = 1:length(vectorSequence)
    val = vectorValueSubset(jj);
    sprintf('index = %d  value = %d\n', vectorSequence(jj), val)
end

If the vectorSequence array is not sparse, use this code, which results in more data transfers than the original code, but does not incur the cost of copying data. The extra transfers are computationally lightweight.

vectorValues = [1, 4, 9, 16, 25, 36, 49];
vectorSequence = [2:3, 5:7];
parfor kk = min(vectorSequence):max(vectorSequence)
    if (find( vectorSequence == kk))
        val = vectorValues(kk);
        sprintf('index = %d  value = %d\n', kk, val)
    end
end

`PFSPMD` —
spmd statements cannot be used inside parfor loops.

Severity: Error

For additional information, see Nested spmd Statements (Parallel Computing Toolbox).

`PFSV` —
SAVE cannot be called in a PARFOR loop without the '-fromstruct' option.

Severity: Error

save can be called inside a parfor-loop when using the -fromstruct option. For additional information, see Save Variables in parfor-Loops (Parallel Computing Toolbox).

`PFUNK` —
Unable to classify variable VAR_NAME in the body of the parfor loop.

Severity: Error

MATLAB runs loops in parfor functions by dividing the loop iterations into groups, and then sending them to MATLAB workers where they run in parallel. For MATLAB to do this in a repeatable, reliable manner, it must be able to classify all the variables used in the loop. The code uses the indicated variable in a way that is incompatible with classification.

Fix the usage of the indicated variable.

For an example, see Loop Variable under Loop Variables (Parallel Computing Toolbox).

If this message is the result of a typographical error in your code, fix it. Otherwise, rewrite the application to avoid assigning a value to the parfor (MATLAB Coder) loop index within the loop body.

`ROWLN` —
All matrix rows must be the same length.

Severity: Error

There may be two rows of different lengths in this matrix initialization. MATLAB requires each row of a matrix to be the same length. Note that when variables are included in a matrix initialization, Code Analyzer often cannot determine whether the variable is a scalar or a vector. Therefore, it could fail to find problems that appear when you run the code. Because Code Analyzer issues this message conservatively, when it does display this message, there is probably a problem.

This appears to be a call to warning that specifies a message ID, but no warning message. Code Analyzer might produce this message incorrectly.

If there is none, add a warning message to the call. If the message is incorrect, suppress it, as described in Adjust Code Analyzer Message Indicators and Messages

Bugs

`ASSRT` —
The first input argument to 'assert' must be a condition. To always throw an error, use 'error(msg)' instead.

Severity: Error

`BDSCA2` —
Operands to '||' and '&&' must be scalar values. Use 'all' or 'any' to convert this value into a scalar value or use the element-wise operators '|' or '&' instead.

Severity: Error

Operands to || and && must be scalar values.

Use all or any to convert this value into a scalar value or use the element-wise operators | or & instead.

Old	Scalar Conversion	Element-wise Comparison
A = [1 2]\|\|false	A = any([1 2])\|\|false	A = [1 2]\|false

`CFALSE` —
This logical comparison always returns false. Did you mean to use VAR_NAME to evaluate function argument: VAR_NAME(...VAR_NAME...)?

Severity: Error

A comparison operator is applied to a function that returns logical values (true or false). In this case, the comparison always returns false. Therefore, it is performed incorrectly.

If you want to perform a comparison, rewrite your code by placing the operator inside the function call. This example shows how to fix the code to determine whether any element in a vector A is greater than 1.

Original		Revised
A = [6 3 7 5]; B = any(A)>1		A = [6 3 7 5]; B = any(A>1)

In the original code, B evaluates to false regardless of the value of A, because the any function can return only logical 0 or 1 values. The revised code correctly determines whether any element in A is greater than 1.

`CMDAND` —
Use 'A && B' or 'A & B' to test whether A and B are both true in MATLAB.

Severity: Error

`CMDOR` —
Use 'A || B' or 'A | B' to test whether either A or B is true in MATLAB.

Severity: Error

`CTRUE` —
This logical comparison always returns true. Did you mean to use VAR_NAME to evaluate function argument: VAR_NAME(...VAR_NAME...)?

Severity: Error

A comparison operator is applied to a function that returns logical values (true or false). In this case, the comparison always returns true. Therefore, it is performed incorrectly.

Original		Revised
A = [6 3 7 5]; B = any(A)<=1		A = [6 3 7 5]; B = any(A<=1)

In the original code, B evaluates to true regardless of the value of A, because the any function can return only logical 0 or 1 values. The revised code correctly determines whether any element in A is less than or equal to 1.

`DEBUGFUN` —
Debug functions are intended to be used at the command line. At runtime, they will generate an error. Remove the debug function.

Severity: Error

`DECR` —
--x operation does not decrement the value of x. To decrease the value by 1, use x = x - 1.

Severity: Error

`DEFSIZE` —
Do not overload 'size' for fundamental data types.

Severity: Error

`FNAN` —
Use ISNAN when comparing values to NaN.

Severity: Error

When comparing values to NaN using the relational equals operator (==), MATLAB always returns false. For example, the following code displays false even though it compares NaN to NaN:

x = NaN;
if x == NaN
    disp('true')
else
    disp('false')
end

Instead of using the relational equals operator to compare a variable to NaN, use isnan. For example, the following code displays true:

x = NaN;
if isnan(x)
    disp('true')
else
    disp('false')
end

`FPFORP` —
'fprintf' is writing to a file that is opened with read permission only. Open a file using 'fopen(...,'W',...)' instead.

Severity: Error

`FUNFUN` —
The first input argument must be a function handle. Did you mean '@VAR_NAME'?

Severity: Error

<MAIN FUNCTION> takes a function handle or an anonymous function as its first input argument.

To pass a handle to a function as the argument, prepend an @ before the function call. See Pass Function to Another Function or the documentation for <MAIN FUNCTION> for usage examples.

If you see this error on a function that returns a function handle, add empty parentheses to the function call:

Before	After
<Main Fcn>(<Arg Fcn>, ...)	<Main Fcn>(<Arg Fcn>(), ...)

`FWFORP` —
'fwrite' is writing to a file that is opened with read permission only. Open a file using 'fopen(...,'W',...)' instead.

Severity: Error

`IFBDUP` —
This condition has no effect because all blocks in this if statement are identical. This indicates a bug in the code. Remove the condition or change the code blocks.

Severity: Error

The code contained in all blocks of this if statement are identical. This indicates a bug in the code because the if statement does not have any effect.

This error is not an execution error and will not stop code from running.

Remove the if statement or change the code blocks.

`IFCDUP` —
The statements under this VAR_RESERVED_WORD condition cannot be reached because it is a duplicate of the VAR_RESERVED_WORD condition on line VAR_NUMBER. This indicates a bug in the code. Remove or change the condition.

Severity: Error

The code contained in this condition are identical another condition. This indicates a bug in the code because the condition does not have any effect.

This error is not an execution error and will not stop code from running.

Remove the condition or change the code blocks.

`INCR` —
++x operation does not increment the value of x. To increase the value by 1, use x = x + 1.

Severity: Error

`LBODUP` —
Since both operands are identical, the second operand has no effect on the VAR_RESERVED_WORD operation. This indicates a bug in the code. Change one of the operands or remove the VAR_RESERVED_WORD operation.

Severity: Error

Since both operands are identical, the second operand has no effect on the operation. This indicates a bug in the code.

This error is not an execution error and will not stop code from running.

Change one of the operands or remove the operation.

`LOGEMP` —
Using 'isempty' on a logical expression creates incorrect results. To determine if all the conditions are false, use '~any(..., "all")' instead.

Severity: Error

Using isempty on a logical expression creates incorrect results.

To determine if all the conditions are false, use ~any(...) or ~any(..., "all") for matrices instead. For example:

Old	Replacement	Replacement For Matrices
isempty(x == y)	~any(x == y)	~any(x == y, "all")
isempty(x ~= y)	~any(x ~= y)	~any(x ~= y, "all")
isempty(x < y)	~any(x < y)	~any(x < y, "all")
isempty(x && y)	~any(x && y)	~any(x && y, "all")

`MDUPC` —
The case value VAR_NAME is a duplicate of one on line VAR_NUMBER.

Severity: Error

`MEXCEP` —
To report an MException as a warning, use a format specifier to ensure the message is printed correctly. For example, 'warning(E.identifier, "%s", E.message)'.

Severity: Error

If the first input argument to the warning function is a warning identifier, MATLAB interprets the second input argument as formatting operators that can include ordinary text and escape characters. When the message property of an MException object is passed as the second input, any backslashes within it are treated as escape characters and are translated during display, which is likely not intended.

When using the message property of an MException object as the warning message, add the string format specifier ("%s") to the warning function call. For example, create an MException object.

E = MException("myComponent:myID","Cannot open file: %s","C:\data\sample.txt");

To display the message, call the warning function as follows:

warning(E.identifier,"%s",E.message)

If you call the warning function without the specifier, MATLAB interprets the backslashes in the folder path as escape characters.

For more information, see Formatting text.

`MNANC` —
NaN never compares equal to any value, so this case will never be matched.

Severity: Error

When comparing values to NaN, MATLAB always returns false. For example, the following code displays other value even though it compares NaN to NaN:

x = NaN;
switch x
    case -1
        disp('negative one');
    case 0
        disp('zero');
    case 1
        disp('positive one');
    case NaN
        disp('NaN');
    otherwise
        disp('other value')
end

Rewrite your code so it does not compare a variable to NaN. For example, you can rewrite the previous code like this, using isnan to determine if the variable is NaN:

x = NaN;
switch x
    case -1
        disp('negative one');
    case 0
        disp('zero');
    case 1
        disp('positive one');
    otherwise
        if isnan(x)
            disp('NaN')
        else
            disp('other value')
        end
end

`MOCUP` —
Variable VAR_NAME may be cleared before the cleanup function that references VAR_NAME executes, resulting in an undefined variable error.

Severity: Error

MATLAB implicitly clears all local variables at the termination of a function, whether by normal completion, or a forced exit, such as an error, or Ctrl+C. When an onCleanup object is destroyed the onCleanup function is called. Local variables from the terminated function may no longer exist at the time the onCleanup function is executed.

Pass an anonymous function as the onCleanup Function. This saves a separate copy of variables included in the anonymous function which persist as long as the anonymous function persists.

Old	Replacement
function clearedFunction k = 10; c = onCleanup(@nested); function nested disp(k) end end	function clearedFunction k = 10; c = onCleanup(@()nested(k)); function nested(k) disp(k) end end

For example, to determine whether both a and b are empty:

a = 1;
b = 2;
isnan(a) && isnan(b)

To determine whether a is empty, and then determine the logical AND of the result and b:

a = 1;
b = 2;
isnan(a) && b

`SHOCIRT` —
The VAR_NAME operator is unexpected because VAR_NAME(A VAR_NAME B) always returns true.

Severity: Error

The indicated statement always returns true or results in an error. This is because the statements A && B and A || B always either return a logical value or throw an error.

Rewrite the code to perform the logical operation outside of the indicated function.

For example, to determine whether both a and b are scalars:

a = 1;
b = 2;
isscalar(a) && isscalar(b)

To determine whether a is a scalar, and then determine the logical AND of the result and b:

a = 1;
b = 2;
isscalar(a) && b

`STCUL` —
The comparison will likely fail due to case mismatch.

Severity: Error

`STRCMPCSTR` —
'strcmp' always returns false for string elements of a cell array. Use ["str1", "str2"] instead of {"str1", "str2"}.

Severity: Error

`VARARG` —
Initialize VARARGOUT with a CELL.

Severity: Error

Custom Checks

Using external operating system commands decreases robustness and portability of code.

Remove instances of the bang (!) operator from your code.

Naming Checks

Severity: Error

For additional information, see autocorr (Econometrics Toolbox).

Related Documentation: autocorr (Econometrics Toolbox)

`ACTXC` —
'actxcontrol' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: actxcontrol

`ACTXL` —
'actxcontrollist' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: actxcontrollist

`ACTXS` —
'actxcontrolselect' has been removed. There is no simple replacement for this.

Severity: Error

`ATVIZW` —
The 'Visible' attribute has been removed. Use the '~Hidden' attribute instead or omit the attribute since 'Hidden' is false by default.

Severity: Error

`AVRREM` —
The 'Aero.VirtualRealityAnimation' class has been removed. With appropriate code changes, use sim3d classes to create and view a 3D environment instead.

Severity: Error

Simulink 3D Animation Viewer used by Aero.VirtualRealityAnimation has been removed. Aero.VirtualRealityAnimation does not open or play animations.

Use sim3d classes in Unreal Engine 3d Environment (Aerospace Toolbox) to create and view a 3D environment instead. For more information on transitioning to the new 3D environment, see Transition Aero.VirtualRealityAnimation to Unreal Engine 3D Environment (Aerospace Toolbox).

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`AXSTATE` —
'axis('state')' has been removed. With appropriate code changes, use 'XLimMode', 'YLimMode', 'ZLimMode', 'Visible', 'XDir', and 'YDir' properties of an axes object instead.

Severity: Error

Related Documentation: axis

`B2G` —
'bin2gray' has been removed. Use the appropriate modulation object or function to remap constellation points instead.

Severity: Error

For any given of modulation scheme, you can provide decimal values when calling the modulation and demodulation functions. When calling the modulation and demodulation functions, specify symbol order as 'bin' for natural binary encoding or 'gray' for Gray encoding.

Modulation Scheme	Before	After
QAM	x = randi([0 63],1,100); y = bin2gray(x,'qam',64); z = qammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = qamdemod(x,64,'bin'); z = gray2bin(y,'qam',64);	x = randi([0 63],1,100); z = qammod(x,64,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = qamdemod(x,64,'gray')
PAM	x = randi([0 63],1,100); y = gray2bin(x,'pam',64); z = pammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pamdemod(x,64,pi/4,'bin'); z = bin2gray(y,'pam',64);	x = randi([0 63],1,100); z = pammod(x,64,pi/4,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pamdemod(x,64,pi/4,'gray')
FSK	x = randi([0 63],1,100); y = gray2bin(x,'fsk',64); z = fskmod(y,64,1,256,256,'cont','bin') x = 2(randn(512,1)+1jrandn(512,1)); y = fskdemod(x,64,1,256,256,'bin'); z = bin2gray(y,'fsk',64)	x = randi([0 63],1,100); z = fskmod(x,64,1,256,256,'cont','gray') x = 2(randn(512,1)+1jrandn(512,1)); z = fskdemod(x,64,1,256,256,'gray');
DPSK	x = randi([0 63],1,100); y = gray2bin(x,'dpsk',64); z = dpskmod(y,64,pi/4,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = dpskdemod(x,64,pi/4,'bin'); z = bin2gray(y,'dpsk',64);	x = randi([0 63],1,100); z = dpskmod(x,64,pi/4,'gray'); x=2(randn(100,1)+1jrandn(100,1)); z = dpskdemod(x,64,pi/4,'gray');
PSK	x=randi([0 63],1,100); y=gray2bin(x,'psk',64); z=pskmod(y,64,0,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pskdemod(x,64,0,'bin'); z = bin2gray(y,'psk',64);	x=randi([0 63],1,100); z=pskmod(x,64,0,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pskdemod(x,64,0,'gray');

`BLIBS` —
'InputBufferSize' property of 'bluetooth' class will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`BLKDEINT` —
'comm.BlockDeinterleaver' has been removed. With appropriate code changes, use 'deintrlv' instead.

Severity: Error

`BLKINT` —
'comm.BlockInterleaver' has been removed. With appropriate code changes, use 'intrlv' instead.

Severity: Error

`BLREN` —
'RemoteName' property of 'bluetooth' class will be removed in a future release. With appropriate code changes, use 'Name' property of 'bluetooth' class instead.

Severity: Warning

`CHKGR` —
The 'CheckGradients' option has been removed from 'optimoptions'. With appropriate code changes, use the 'checkGradients' function instead.

Severity: Error

The CheckGradients option in optimoptions will be removed in a future release. With appropriate code changes, use the checkGradients function instead.

For additional information, see checkGradients (Optimization Toolbox).

Update existing code to use checkGradients instead. For example:

Old	New
opts = optimoptions("fmincon",SpecifiObjectiveGradient=true,... CheckGradients=true); x = fmincon(fun,x0,A,b,Aeq,beq,lb,ub,nonlcon,opts);	tf = checkGradients(fun, x0);

Related Documentation: checkGradients (Optimization Toolbox)

`CLASSREGTREE` —
'classregtree' has been removed. With appropriate code changes, use 'fitctree' or 'fitrtree' instead.

Severity: Error

`CLRMENU` —
'clrmenu' has been removed. With appropriate code changes, use 'colormapeditor' instead.

Severity: Error

`CLRUI` —
'colorui' has been removed. With appropriate code changes, use 'uisetcolor' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`CMAMP` —
'AMPMConversion' property of 'comm.MemorylessNonlinearity' class will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`CMBNT` —
'combntns' has been removed. Use 'nchoosek' instead, which is a direct replacement.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`CMCMA` —
'cma' has been removed. With appropriate code changes, use 'comm.LinearEqualizer' or 'comm.DecisionFeedbackEqualizer' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMCMAAD` —
'adaptalg.cma' has been removed. With appropriate code changes, use 'comm.LinearEqualizer' or 'comm.DecisionFeedbackEqualizer' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMCPMCPS` —
'comm.CPMCarrierPhaseSynchronizer' has been removed. With appropriate code changes, use 'comm.CarrierSynchronizer' instead.

Severity: Error

`CMDFE` —
'dfe' has been removed. With appropriate code changes, use 'comm.DecisionFeedbackEqualizer' instead.

Severity: Error

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMLMSAD` —
'adaptalg.lms' has been removed. With appropriate code changes, use 'comm.LinearEqualizer' or 'comm.DecisionFeedbackEqualizer' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMLRQ` —
'lineareq' has been removed. With appropriate code changes, use 'comm.LinearEqualizer' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMLRQEQ` —
'equalizer.lineareq' has been removed. With appropriate code changes, use 'comm.LinearEqualizer' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMLSV` —
'saveCompactModel' has been removed. Use 'saveLearnerForCoder' instead, which is a direct replacement.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`CMMGM` —
'Ghorbani model' value for the 'Method' property on 'comm.MemorylessNonlinearity' class will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`CMMHT` —
'Hyperbolic tangent' value for the 'Method' property on 'comm.MemorylessNonlinearity' class will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`CMMMTS` —
'comm.MuellerMullerTimingSynchronizer' has been removed. With appropriate code changes, use 'comm.SymbolSynchronizer' instead.

Severity: Error

`CMNLMS` —
'normlms' has been removed. With appropriate code changes, use 'comm.LinearEqualizer' or 'comm.DecisionFeedbackEqualizer' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMNLMSAD` —
'adaptalg.normlms' has been removed. With appropriate code changes, use 'comm.LinearEqualizer' or 'comm.DecisionFeedbackEqualizer' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Aerospace Toolbox).

`CMPLW` —
'PowerLowerLimit' property of 'comm.MemorylessNonlinearity' class will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`CMPSKCPS` —
'comm.PSKCarrierPhaseSynchronizer' has been removed. With appropriate code changes, use 'comm.CarrierSynchronizer' instead.

Severity: Error

Severity: Error

Related Documentation: colordef

`COLORM` —
'colorm' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`COMET` —
'cometm' has been removed. With appropriate code changes, use 'comet' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`COMET3` —
'comet3m' has been removed. With appropriate code changes, use 'comet3' instead.

Related Documentation: comm.PSKDemodulator (Communications Toolbox)

`COMMPSKMSO` —
'comm.PSKModulator' will be removed in a future release. With appropriate code changes, use 'pskmod' instead.

Severity: Warning

Related Documentation: comm.PSKModulator (Communications Toolbox)

`COMMQAMC` —
'comm.QAMCoarseFrequencyEstimator' has been removed. With appropriate code changes, use 'comm.CoarseFrequencyCompensator' instead.

Severity: Error

`COMMQAMD` —
'comm.RectangularQAMDemodulator' has been removed. With appropriate code changes, use 'qamdemod' instead.

Severity: Error

`COMMQAMM` —
'comm.RectangularQAMModulator' has been removed. With appropriate code changes, use 'qammod' instead.

Severity: Error

`COMMQPSKDSO` —
'comm.QPSKDemodulator' will be removed in a future release. With appropriate code changes, use 'pskdemod' instead.

Severity: Warning

Related Documentation: comm.QPSKDemodulator (Communications Toolbox)

`COMMQPSKMSO` —
'comm.QPSKModulator' will be removed in a future release. With appropriate code changes, use 'pskmod' instead.

Severity: Warning

`CRCDE` —
'crc.detector' has been removed. With appropriate code changes, use 'crcDetect' instead.

Severity: Error

`CRCGE` —
'crc.generator' has been removed. With appropriate code changes, use 'crcGenerate' instead.

Severity: Error

`DACPR` —
'commmeasure.ACPR' has been removed. With appropriate code changes, use 'comm.ACPR' instead.

Severity: Error

`DAFINF` —
'avifinfo' will be removed in a future release. With appropriate code changes, use 'VideoReader' instead.

Severity: Warning

Related Documentation: VideoReader

`DAVIINF` —
'aviinfo' will be removed in a future release. With appropriate code changes, use 'VideoReader' instead.

Severity: Warning

`DMOD` —
'modem.dpskmod' has been removed. With appropriate code changes, use 'comm.DPSKModulator' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Communications Toolbox).

`DMSSPEC` —
'dspdata.msspectrum' will be removed in a future release. Use 'periodogram' or 'pwelch' instead.

Severity: Warning

`DNDLA` —
'discard' has been removed. There is no simple replacement for this.

Severity: Error

Severity: Error

Related Documentation: pagesetupdlg

`DPOOL` —
'matlabpool' has been removed. With appropriate code changes, use 'parpool' instead.

Severity: Error

matlabpool has been removed. Use parpool instead.

parpool creates a pool of workers on the current cluster and connects the MATLAB client. It enables the full functionality of the MATLAB parallel language features including parfor, spmd, and the distributed function.

Replace occurrences of matlabpool with parpool. In some instances, parpool uses a different syntax than matlabpool. For example:

To start a pool using the current cluster profile, replace matlabpool with parpool.
To query whether a pool exists, replace matlabpool('size') == 0 with isempty(gcp('nocreate')).
To close the current pool, replace matlabpool close or matlabpool('close') with delete(gcp('nocreate')).

`DSPAUDIOREC` —
'dsp.AudioRecorder' has been removed. With appropriate code changes, use 'audioDeviceReader' instead.

Severity: Error

Severity: Error

Related Documentation: dsp.AsyncBuffer (DSP System Toolbox)

Severity: Error

`DSPDCT` —
'dsp.DCT' has been removed. With appropriate code changes, use 'dct' instead.

Severity: Error

`DSPDELAYLINE` —
'dsp.DelayLine' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: dsp.AsyncBuffer (DSP System Toolbox)

`DSPDF` —
'dsp.DigitalFilter' has been removed. Use 'dsp.FIRFilter', 'dsp.IIRFilter', or 'dsp.AllpoleFilter' instead.

Severity: Error

dsp.DigitalFilter has been removed. Use dsp.FIRFilter, dsp.IIRFilter, or dsp.AllpoleFilter instead.

For FIR filter structures, use dsp.FIRFilter (DSP System Toolbox).
For non-SOS IIR filter structures, use dsp.IIRFilter (DSP System Toolbox).
For All pole structures, use dsp.AllpoleFilter (DSP System Toolbox).

`DSPFDF` —
'DirectFeedthrough' property of 'dsp.VariableFractionalDelay' class has been removed.

Severity: Error

`DSPHIST` —
'dsp.Histogram' has been removed. With appropriate code changes, use 'histogram' or 'histcounts' instead.

Severity: Error

`DSPIDCT` —
'dsp.IDCT' has been removed. With appropriate code changes, use 'idct' instead.

Severity: Error

`DSPIDF` —
'DirectFeedthrough' property of 'dsp.VariableIntegerDelay' class has been removed.

Severity: Error

`DSPINTERP` —
'dsp.Interpolator' has been removed. With appropriate code changes, use 'dsp.FIRInterpolator' instead.

Severity: Error

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`DSPLPC2LSF` —
'dsp.LPCToLSF' has been removed. With appropriate code changes, use 'poly2lsf' instead.

Severity: Error

`DSPLPC2RC` —
'dsp.LPCToRC' has been removed. With appropriate code changes, use 'poly2rc' instead.

Severity: Error

`DSPLSF2LPC` —
'dsp.LSFToLPC' has been removed. With appropriate code changes, use 'lsf2poly' instead.

Severity: Error

`DSPLSP2LPC` —
'dsp.LSPToLPC' has been removed. There is no simple replacement for this.

Severity: Error

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`DSPSCALARQUANTENC` —
'dsp.ScalarQuantizerEncoder' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`DSPSTATELVLS` —
'dsp.StateLevels' has been removed. With appropriate code changes, use 'statelevels' instead.

Severity: Error

`DSPSTD` —
'dsp.StandardDeviation' has been removed. With appropriate code changes, use 'std' instead.

Severity: Error

`DSPTMS` —
'dsp.TransitionMetrics' has been removed. With appropriate code changes, use 'falltime', 'overshoot', 'risetime', 'settlingtime', 'slewrate' or 'undershoot' instead.

Severity: Error

`DSPTS` —
'dsp.TimeScope' has been removed. Use 'timescope' instead, which is a direct replacement.

Severity: Error

`DSPVECQUANTENC` —
'dsp.VectorQuantizerEncoder' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`DSPWIN` —
'dsp.Window' has been removed. With appropriate code changes, use 'window' instead.

Severity: Error

`DSPXCORR` —
'dsp.Crosscorrelator' has been removed. With appropriate code changes, use 'xcorr' instead.

Severity: Error

`DSP_LINKS` —
'dsp_links' will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`FEGLO` —
'global' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: feval

`FGREM` —
'RendererMode' will be removed in a future release and currently has no effect. There is no simple replacement for this.

Severity: Warning

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`FGREN` —
'Renderer' will be removed in a future release and currently has no effect. There is no simple replacement for this.

Severity: Warning

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`FINSI` —
Support for 'inputname' in a script has been removed.

Severity: Error

`FINSNI` —
Support for 'nargin' in a script has been removed.

Severity: Error

`FINSNO` —
Support for 'nargout' in a script has been removed.

Severity: Error

`FISADV` —
'addvar' has been removed. With appropriate code changes, use 'addInput' or 'addOutput' instead.

Severity: Error

addvar has been removed. To add input or output variables to a fuzzy system, use addInput (Fuzzy Logic Toolbox) or addOutput (Fuzzy Logic Toolbox), respectively.

This table shows some typical usages of addvar and how to update your code to use addInput or addOutput instead.

If your code has this form:	Use this code instead:
fis = addvar(fis,'input','service',[0 10])	fis = addInput(fis,[0 10],'Name',"service")
fis = addvar(fis,'output','tip',[0 30])	fis = addOutput(fis,[0 30],'Name',"tip")

`FISGET` —
'getfis' has been removed. Access FIS properties using dot notation instead.

Severity: Error

getfis has been removed. Access fuzzy inference system properties using dot notation instead. For more information on fuzzy inference system objects, see mamfis (Fuzzy Logic Toolbox) and sugfis (Fuzzy Logic Toolbox).

This table shows some typical usages of getfis for accessing fuzzy inference system properties and how to update your code to use dot notation instead.

If your code has this form:	Use this code instead:
get(fis,'andmethod')	fis.AndMethod
get(fis,'input',1)	fis.Inputs(1)
getfis(fis,'input',1,'name')	fis.Inputs(1).Name
getfis(fis,'input',2,'mf',1)	fis.Inputs(2).MembershipFunctions(1)
getfis(fis,'input',2,'mf',1,params)	fis.Inputs(2).MembershipFunctions(1).Parameters

`FISM2M` —
'mf2mf' has been removed. Convert membership functions using dot notation on 'fismf' objects instead.

Severity: Error

mf2mf has been removed. Convert membership functions using dot notation on fismf (Fuzzy Logic Toolbox) objects instead.

Previously, membership functions were represented as structures within a fuzzy inference system structure. Now, membership functions are represented as fismf objects within mamfis (Fuzzy Logic Toolbox) and sugfis (Fuzzy Logic Toolbox) objects.

Previously, to change the type of a membership function in a fuzzy inference system, you converted the parameters using mf2mf.

fis = readfis('tipper');
oldType = fis.input(1).mf(1).type;
oldParams = fis.input(1).mf(1).params;
fis.input(1).mf(1).type = newType;
fis.input(1).mf(1).params = mf2mf(oldParams,oldType,newType);

Now, when you change the type of membership function, the parameters are converted automatically.

fis = readfis('tipper');
fis.Inputs(1).MembershipFunctions(1).Type = newType;

`FISM2S` —
'mam2sug' has been removed. Use 'convertToSugeno' instead, which is a direct replacement.

Severity: Error

mam2sug has been removed. Use convertToSugeno (Fuzzy Logic Toolbox) instead. To update your code, change the function name from mam2sug to convertToSugeno. The syntaxes are equivalent.

`FISNEW` —
'newfis' has been removed. With appropriate code changes, use 'mamfis' or 'sugfis' instead.

Severity: Error

newfis has been removed. To create a Mamdani or Sugeno FIS, use mamfis (Fuzzy Logic Toolbox) or sugfis (Fuzzy Logic Toolbox), respectively.

This table shows some typical usages of newfis for creating fuzzy systems and how to update your code to use mamfis or sugfis instead.

If your code has this form:	Use this code instead:
fis = newfis(name)	fis = mamfis('Name',name)
s = newfis(name,'FISType','mamdani')	fis = mamfis('Name',name)
fis = newfis(name,'FISType','sugeno')	fis = sugfis('Name',name)
fis = newfis(name,'FISType','mamdani','AndMethod','prod')	fis = mamfis('Name',name,'AndMethod','prod')
fis = newfis(name,'FISType','sugeno','OrMethod','probor')	fis = sugfis('Name',name,'OrMethod','probor')

`FISPSR` —
'parsrule' has been removed. With appropriate code changes, use 'addRule' or 'fisrule' instead.

Severity: Error

parsrule has been removed. Use addRule (Fuzzy Logic Toolbox) instead.

If you previously added rules using linguistic or symbolic expressions with parsrule, you can specify rules using the same expressions with addrule. addRule automatically detects the format of the strings or character vectors in your rule list. Therefore, it is no longer necessary to specify the rule format. To add a rule list using addRule, use the following command:

fis = addRule(fis,rules);

Previously, you could add rules using indexed expressions with parsrule.

rule1 = "1 2, 1 4 (1) : 1";
rule2 = "-1 1, 3 2 (1) : 1";
rules = [rule1 rule2];
fis = parsrule(fis,rules,'Format','indexed');

Now, specify these rules using arrays of indices.

rule1 = [1 2 1 4 1 1];
rule2 = [-1 1 3 2 1 1];
rules = [rule1; rule2];
fis = addRule(fis,rules);

If you previously specified rules using the 'Language' name-value pair argument with parsrule, this functionality has been removed and there is no replacement. Specify your rules using addRule with a different rule format.

Previously, parsrule replaced the entire rule list in your fuzzy system. addRule appends your specified rules to the rule list.

`FISRMF` —
'rmmf' has been removed. With appropriate code changes, use 'removeMF' instead.

Severity: Error

rmmf has been removed. Use removeMF (Fuzzy Logic Toolbox) instead.

The following table shows some typical usages of rmmf and how to update your code to use removeMF instead. Previously, you specified the index of the variable from which you wanted to remove the membership function and the index of the membership function that you wanted to remove. Now, to remove a membership function, specify the variable name and the membership function name.

If your code has this form:	Use this code instead:
fis = rmmf(fis,'input',1,'mf',1)	fis = removeMF(fis,"service","poor")
fis = rmmf(fis,'output',1,'mf',1)	fis = removeMF(fis,"tip","cheap")

Previously, you had to delete any references to a membership function you wanted to remove from the rule set. removeMF automatically removes these references from the rule set of your fuzzy system.

`FISRMV` —
'rmvar' has been removed. With appropriate code changes, use 'removeInput' or 'removeOutput' instead.

Severity: Error

rmvar has been removed. To remove input or output variables from a fuzzy system, use removeInput (Fuzzy Logic Toolbox) or removeOutput (Fuzzy Logic Toolbox), respectively.

This table shows some typical usages of rmvar and how to update your code to use removeInput or removeOutput instead. Previously, you specified the index of the variable that you wanted to remove. Now, to remove a variable, specify the variable name.

If your code has this form:	Use this code instead:
fis = rmvar(fis,'input',1)	fis = removeInput(fis,"service")
fis = rmvar(fis,'output',1)	fis = removeOutput(fis,"tip")

Previously, you had to delete any rules from your fuzzy system that contained the variable you wanted to remove. removeInput and removeOutput automatically remove these variables from the rule set of your fuzzy system.

`FISSET` —
'setfis' has been removed. Set FIS properties using dot notation instead.

Severity: Error

setfis has been removed. Set fuzzy inference system properties using dot notation instead. For more information on fuzzy inference system objects, see mamfis (Fuzzy Logic Toolbox) and sugfis (Fuzzy Logic Toolbox).

This table shows some typical usages of setfis for setting fuzzy inference system properties and how to update your code to use dot notation instead.

If your code has this form:	Use this code instead:
fis = setfis(fis,'andmethod','prod')	fis.AndMethod = 'prod'
fis = setfis(fis,'input',1,'name','service')	fis.Inputs(1).Name = "service"
fis = setfis(fis,'input',2,'mf',1,params,[5 10 15])	fis.Inputs(2).MembershipFunctions(1).Parameters = [5 10 15]

If your code has this form:

Use this code instead:

fis = setfis(fis,'andmethod','prod')

fis.AndMethod = 'prod'

fis = setfis(fis,'input',1,'name','service')

fis.Inputs(1).Name = "service"

fis = setfis(fis,'input',2,'mf',1,params,[5 10 15])

fis.Inputs(2).MembershipFunctions(1).Parameters = [5 10 15]

`FISSHW` —
'showfis' has been removed. View FIS properties using dot notation instead.

Severity: Error

showfis has been removed. View the properties of your FIS directly instead.

Previously, you could view the properties of your fuzzy system, myFIS, using the showfis function.

showfis(myFIS)

Now, you can view the properties directly instead.

myFIS

To view additional FIS properties, use dot notation. For example, view information about the membership functions of the first input variable.

myFIS.Inputs(1).MembershipFunctions

For more information on fuzzy inference systems and their properties, see mamfis (Fuzzy Logic Toolbox) and sugfis (Fuzzy Logic Toolbox).

`FITNAIVEBAYES` —
'fitNaiveBayes' has been removed. With appropriate code changes, use 'fitcnb' instead.

Severity: Error

`FPRENAME` —
Input argument 'fixpoint' will be removed in a future release. Use 'fixedpoint' instead.

Severity: Warning

`FPSNM` —
'fipsname' has been removed. With appropriate code changes, use 'readgeotable' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`FROPT` —
'-dill' has been removed. Use Encapsulated PostScript instead.

Severity: Error

`FROPTX` —
'-adobecset' has been removed. There is no simple replacement for this.

Severity: Error

`FVTOOL` —
'fvtool' will be removed in a future release. With appropriate code changes, use 'filterAnalyzer' instead.

Severity: Warning

`G2B` —
'gray2bin' has been removed. Use the appropriate modulation object or function to remap constellation points instead.

Severity: Error

Modulation Scheme	Before	After
QAM	x = randi([0 63],1,100); y = bin2gray(x,'qam',64); z = qammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = qamdemod(x,64,'bin'); z = gray2bin(y,'qam',64);	x = randi([0 63],1,100); z = qammod(x,64,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = qamdemod(x,64,'gray')
PAM	x = randi([0 63],1,100); y = gray2bin(x,'pam',64); z = pammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pamdemod(x,64,pi/4,'bin'); z = bin2gray(y,'pam',64);	x = randi([0 63],1,100); z = pammod(x,64,pi/4,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pamdemod(x,64,pi/4,'gray')
FSK	x = randi([0 63],1,100); y = gray2bin(x,'fsk',64); z = fskmod(y,64,1,256,256,'cont','bin') x = 2(randn(512,1)+1jrandn(512,1)); y = fskdemod(x,64,1,256,256,'bin'); z = bin2gray(y,'fsk',64)	x = randi([0 63],1,100); z = fskmod(x,64,1,256,256,'cont','gray') x = 2(randn(512,1)+1jrandn(512,1)); z = fskdemod(x,64,1,256,256,'gray');
DPSK	x = randi([0 63],1,100); y = gray2bin(x,'dpsk',64); z = dpskmod(y,64,pi/4,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = dpskdemod(x,64,pi/4,'bin'); z = bin2gray(y,'dpsk',64);	x = randi([0 63],1,100); z = dpskmod(x,64,pi/4,'gray'); x=2(randn(100,1)+1jrandn(100,1)); z = dpskdemod(x,64,pi/4,'gray');
PSK	x=randi([0 63],1,100); y=gray2bin(x,'psk',64); z=pskmod(y,64,0,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pskdemod(x,64,0,'bin'); z = bin2gray(y,'psk',64);	x=randi([0 63],1,100); z=pskmod(x,64,0,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pskdemod(x,64,0,'gray');

Severity: Error

`GTR2GLT` —
'geocentric2geodeticLat' has been removed. With appropriate code changes, use 'geodeticLatitudeFromGeocentric' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`GTSEED` —
'getseeds' has been removed. There is no simple replacement for this.

Severity: Error

`HDFSD` —
'hdfsd' has been removed. With appropriate code changes, use 'matlab.io.hdfeos.sd' instead.

Severity: Error

Related Documentation: matlab.io.hdf4.sd

`HDFSW` —
'hdfsw' has been removed. With appropriate code changes, use 'matlab.io.hdfeos.sw' instead.

Severity: Error

Related Documentation: matlab.io.hdfeos.sw

`HDFTL` —
'hdftool' has been removed. There is no simple replacement for this.

Severity: Error

`HELSCANDEINTRLV` —
'helscandeintrlv' will be removed in a future release. With appropriate code changes, use 'deintrlv' instead.

Severity: Warning

`HELSCANINTRLV` —
'helscanintrlv' will be removed in a future release. With appropriate code changes, use 'intrlv' instead.

`HPFLTR` —
Positional syntax for optional arguments has been removed from 'hpfilter'. Use name-value pairs instead.

Severity: Error

Related Documentation: hpfilter (Econometrics Toolbox)

`HYPERCUBE` —
'hypercube' will be removed in a future release. With appropriate code changes, use 'imhypercube', 'geohypercube', 'immulticube' or 'geomulticube' instead.

Severity: Warning

Related Documentation: hypercube (Image Processing Toolbox)

`I2CFUN` —
'i2c' has been removed. With appropriate code changes, use 'device' method of 'ni845x' or 'aardvark' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`IMAGEVW` —
'imageview' has been removed. Use 'imshow' instead, which is a direct replacement.

Severity: Error

Related Documentation: imshow (Image Processing Toolbox)

`IMCLASS` —
In a future release, 'ismethod' will treat a string or character vector in its first input as a 'string' or 'char' class object. Pass an object to 'ismethod' or use any(strcmp('methodName', methods('ClassName'))) instead.

Severity: Warning

`IMJAV` —
'im2java2d' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: im2java2d (Image Processing Toolbox)

`IMJAVA` —
'im2java' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`IMPIVD` —
Malformed import argument VAR_NAME will not be supported in a future release.

Severity: Warning

Related Documentation: import

`IMPKEY` —
Importing VAR_NAME will not be supported in a future release because VAR_NAME is a reserved word.

Severity: Warning

Related Documentation: import

`IMTOOL` —
'imtool' will be removed in a future release. With appropriate code changes, use 'imageViewer' instead.

Severity: Warning

imtool will be removed in a future release.

Use the Image Viewer app. This example shows how to open an image in Image Viewer instead of the Image tool.

Old	New
I = imread("cameraman.tif"); imtool(I)	I = imread("cameraman.tif"); imageViewer(I)

When you want to set the display range or the colormap, rewrite your code to specify the DisplayRange or Colormap name-value argument, respectively. This example shows how to fix code that sets the display range using a positional argument.

Old	New
I = imread("cameraman.tif"); imtool(I,[5 250])	I = imread("cameraman.tif"); imageViewer(I,DisplayRange=[5 250])

If you want to return the figure that contains the Image tool, then use the images.compatibility.imtool.r2023b.imtool function instead. This example shows how to return the figure containing the Image tool.

Old	New
I = imread("cameraman.tif"); htool = imtool(I);	I = imread("cameraman.tif"); htool = images.compatibility.imtool.r2023b.imtool(I);

Related Documentation: imtool (Image Processing Toolbox)

`INDWT` —
'indwt' has been removed. With appropriate code changes, use 'imodwt' instead.

Severity: Error

`INDWT2` —
'indwt2' has been removed. With appropriate code changes, use 'iswt2' instead.

Severity: Error

`INSTCA` —
'instrcallback' has been removed. There is no simple replacement for this.

Severity: Error

`INSTFA` —
'instrfindall' has been removed. With appropriate code changes, instead use 'serialportfind', 'tcpclientfind', 'tcpserverfind', 'udpportfind', 'visadevfind', 'aardvarkfind', 'ni845xfind', or 'icdevicefind' when 'LegacyMode' for icdevice is false.

Severity: Error

This function is used by the serial, Bluetooth, tcpip, udp, visa, gpib and i2c interfaces. These interfaces will also be removed in a future release, as previously announced. Use the following interfaces instead:

Functionality	Use This Instead	Additional Information
`serial`	`serialport`	Transition Your Code to `serialport` Interface
`Bluetooth`	`bluetooth` (case-sensitive)	Transition Your Code to `bluetooth` Interface
`tcpip`	`tcpclient`	Transition Your Code to `tcpclient` Interface (Instrument Control Toolbox)
`tcpip`	`tcpserver`	Transition Your Code to `tcpserver` Interface (Instrument Control Toolbox)
`udp`	`udpport`	Transition Your Code to `udpport` Interface (Instrument Control Toolbox)
`visa`	`visadev`	Transition Your Code to `visadev` Interface (Instrument Control Toolbox)
`gpib`	VISA-GPIB interface with `visadev`	Transition Your Code to VISA-GPIB Interface (Instrument Control Toolbox)
`i2c`	`device` function with `aardvark` or `ni845x` object	Transition Your Code to `aardvark` or `ni845x` Interface (Instrument Control Toolbox)
`icdevice` when `legacyMode` is `false`	(use `icdevicefind` (Instrument Control Toolbox) instead	Legacy mode will be removed (Instrument Control Toolbox)

The recommended interfaces have additional capabilities and improved performance. For more information about the recommended interfaces, see Interface-Based Instrument Communication (Instrument Control Toolbox).

Related Documentation: instrfindall (Instrument Control Toolbox)

`INSTHWB` —
'instrhwinfo('bluetooth',...)' has been removed. With appropriate code changes, use 'bluetoothlist' instead.

Severity: Error

`INSTHWG` —
'instrhwinfo('gpib')' has been removed. With appropriate code changes, use 'visadevlist' instead.

Severity: Error

Related Documentation: Transition Your Code to VISA-GPIB Interface (Instrument Control Toolbox)

`INSTHWI2C` —
'instrhwinfo('i2c')' has been removed. With appropriate code changes, use 'ni845xlist' or 'aardvarklist' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`INSTHWS` —
'instrhwinfo('serial')' has been removed. With appropriate code changes, use 'serialportlist' instead.

Related Documentation: instrnotify (Instrument Control Toolbox)

`INSTRR` —
'instrreset' has been removed. With appropriate code changes, instead use 'delete(serialportfind)', 'delete(tcpclientfind)', 'delete(tcpserverfind)', 'delete(udpportfind)', 'delete(visadevfind)', 'delete(aardvarkfind)', 'delete(ni845xfind)', or 'delete(icdevicefind)' when 'LegacyMode' for icdevice is false.

Severity: Error

Functionality	Use This Instead	Additional Information
`serial`	`serialport`	Transition Your Code to `serialport` Interface
`Bluetooth`	`bluetooth` (case-sensitive)	Transition Your Code to `bluetooth` Interface
`tcpip`	`tcpclient`	Transition Your Code to `tcpclient` Interface (Instrument Control Toolbox)
`tcpip`	`tcpserver`	Transition Your Code to `tcpserver` Interface (Instrument Control Toolbox)
`udp`	`udpport`	Transition Your Code to `udpport` Interface (Instrument Control Toolbox)
`visa`	`visadev`	Transition Your Code to `visadev` Interface (Instrument Control Toolbox)
`gpib`	VISA-GPIB interface with `visadev`	Transition Your Code to VISA-GPIB Interface (Instrument Control Toolbox)
`i2c`	`device` function with `aardvark` or `ni845x` object	Transition Your Code to `aardvark` or `ni845x` Interface (Instrument Control Toolbox)

Related Documentation: intlinprog (Optimization Toolbox)

`INTLPOUTA` —
'algorithm' field of the 'intlinprog' solution process summary has been removed. 'intlinprog' always uses the 'highs' algorithm.

Severity: Error

Related Documentation: intlinprog (Optimization Toolbox)

`INVHCRM` —
The 'InvertHardCopy' property will be removed in a future release and currently has no effect. With appropriate code changes, set the 'Color' property of the figure before printing or call the 'exportgraphics' function to control the color for exporting.

Severity: Warning

`IS2GD` —
'iso2geod' has been removed. With appropriate code changes, use 'map.geodesy.IsometricLatitudeConverter' instead.

Severity: Error

Related Documentation: map.geodesy.IsometricLatitudeConverter (Mapping Toolbox)

`ISAUG` —
'augmentedImageSource' has been removed. Use 'augmentedImageDatastore' instead, which is a direct replacement.

Severity: Error

Related Documentation: augmentedImageSource (Deep Learning Toolbox)

`ISDNS` —
'denoisingImageSource' has been removed. Use 'denoisingImageDatastore' instead, which is a direct replacement.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`LATLON2PIX` —
'latlon2pix' has been removed. With appropriate code changes, use 'geographicToIntrinsic' instead.

Severity: Error

`LDPCD` —
'comm.LDPCDecoder' has been removed. With appropriate code changes, use 'ldpcDecode' instead.

Severity: Error

Related Documentation: comm.LDPCDecoder (Communications Toolbox)

`LDPCE` —
'comm.LDPCEncoder' has been removed. With appropriate code changes, use 'ldpcEncode' instead.

Severity: Error

Related Documentation: comm.LDPCEncoder (Communications Toolbox)

`LEGCHN` —
'legacychannelsim' has been removed. There is no simple replacement for this.

Severity: Error

`LEGMOP` —
Syntax to call 'legend' with multiple outputs will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`LIMIM` —
'limitm' has been removed. With appropriate code changes, use 'LatitudeLimits' and 'LongitudeLimits' properties of a geographic raster reference object instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`LINPROGA` —
'active-set' algorithm for 'linprog' solver has been removed. With appropriate code changes, set 'Algorithm' value to 'interior-point' or 'dual-simplex' instead.

Severity: Error

Related Documentation: linprog (Optimization Toolbox)

`LINPROGD` —
'dual-simplex-legacy' algorithm for 'linprog' solver has been removed. With appropriate code changes, set 'Algorithm' value to 'dual-simplex-highs' or 'interior-point' instead.

Severity: Error

Related Documentation: linprog (Optimization Toolbox)

`LINPROGS` —
'simplex' algorithm has been removed. With appropriate code changes, set 'Algorithm' value to 'interior-point' or 'dual-simplex' instead.

Severity: Error

`MAP2PIX` —
'map2pix' has been removed. With appropriate code changes, use 'worldToIntrinsic' instead.

Severity: Error

`MAPBX` —
'mapbbox' has been removed. With appropriate code changes, use 'XWorldLimits' and 'YWorldLimits' properties of a map raster reference object instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`MAPFIL` —
'mapprofile' with referencing matrix or referencing vector has been removed. With appropriate code changes, use a geographic or map raster reference object as input instead.

Severity: Error

Related Documentation: mapprofile (Mapping Toolbox)

`MAPTM` —
'maptrims' has been removed. With appropriate code changes, use 'geocrop' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`MAPTOOL` —
'maptool' has been removed. There is no simple replacement for this.

Severity: Error

`MAPTRIM` —
'maptrim' has been removed. With appropriate code changes, use 'geocrop' or 'geoclip' instead.

Severity: Error

`MAPVW` —
'mapview' has been removed. With appropriate code changes, use 'mapshow' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`MASHL` —
'meshlsrm' with referencing matrix or referencing vector has been removed. With appropriate code changes, use a geographic or map raster reference object as input instead.

Severity: Error

Related Documentation: meshlsrm (Mapping Toolbox)

`MASHM` —
'meshm' with referencing matrix or referencing vector has been removed. With appropriate code changes, use a geographic or map raster reference object as input instead.

Severity: Error

Severity: Error

Related Documentation: vec2mtx (Mapping Toolbox)

`MAVWSH` —
'viewshed' with referencing matrix or referencing vector has been removed. With appropriate code changes, use a geographic or map raster reference object as input instead.

Severity: Error

Related Documentation: viewshed (Mapping Toolbox)

`MAWFW` —
'worldfilewrite' with referencing matrix has been removed. With appropriate code changes, use a geographic or map raster reference object as input instead.

Severity: Error

Related Documentation: worldfilewrite (Mapping Toolbox)

`MCASCADE` —
'mfilt.cascade' will be removed in a future release. With appropriate code changes, use 'dsp.FilterCascade' instead.

Severity: Warning

Related Documentation: mfilt.cascade (DSP System Toolbox)

`MCATP` —
Using an @ sign to specify a class property restriction is unsupported and has been removed. Use property validation syntax instead.

Severity: Error

For more information, see Validate Property Values.

Related Documentation: Validate Property Values

`MCDECIM` —
'mfilt.cicdecim' will be removed in a future release. With appropriate code changes, use 'dsp.CICDecimator' instead.

Severity: Warning

Related Documentation: mfilt.cicdecim (DSP System Toolbox)

`MCGCP` —
Defining a get method for a constant property is not supported.

Severity: Error

`MCINTERP` —
'mfilt.cicinterp' has been removed. With appropriate code changes, use 'dsp.CICInterpolator' instead.

Severity: Error

Related Documentation: mfilt.cicinterp (DSP System Toolbox)

`MCPDC` —
Specifying both the 'Constant' and 'Dependent' attributes on the same property is not supported.

Severity: Error

Related Documentation: Property Attributes

`MDEMOD` —
'modem.mskdemod' has been removed. With appropriate code changes, use 'comm.MSKDemodulator' or 'mskdemod' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Communications Toolbox).

`MDTED` —
'dted' has been removed. With appropriate code changes, use 'readgeoraster' instead.

Severity: Error

Related Documentation: dted (Mapping Toolbox)

`MESHGRAT` —
'meshgrat' has been removed. With appropriate code changes, use 'geographicGrid', 'linspace' or 'ndgrid' instead.

Severity: Error

`MEXTM` —
'extractm' has been removed. With appropriate code changes, use geospatial tables instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`MFARROW` —
'mfilt.farrowsrc' has been removed. With appropriate code changes, use 'dsp.FarrowRateConverter' instead.

Severity: Error

Related Documentation: mfilt.farrowsrc (DSP System Toolbox)

`MFDECIM` —
'mfilt.firdecim' will be removed in a future release. With appropriate code changes, use 'dsp.FIRDecimator' instead.

Severity: Warning

Related Documentation: mfilt.firdecim (DSP System Toolbox)

`MFFDCM` —
'mfilt.firfracdecim' has been removed. With appropriate code changes, use 'dsp.FIRRateConverter' instead.

Severity: Error

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`MOVIE2` —
'movie2avi' has been removed. With appropriate code changes, use 'VideoWriter' instead.

Severity: Error

`MOVIEVW` —
'movieview' has been removed. Use 'implay' instead, which is a direct replacement.

Severity: Error

`MSYSTEM` —
matlab.system.System has been removed. Use matlab.System instead.

Severity: Error

Will be removed	Recommended
[Z,refvec] = nanm(latlim,lonlim,scale);	R = georefcells(latlim,lonlim,1/scale,1/scale); Z = NaN(R.RasterSize);

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`NCHKNO` —
NARGOUTCHK using more than two inputs will be removed in a future release. There is no simple replacement for this.

Severity: Warning

Related Documentation: nargoutchk

`NDWT` —
'ndwt' has been removed. With appropriate code changes, use 'modwt' instead.

Severity: Error

`NDWT2` —
'ndwt2' has been removed. With appropriate code changes, use 'swt2' instead.

Severity: Error

`NOV6` —
'v6' will be removed in a future release. There is no simple replacement for this.

Severity: Warning

`NPI22PI` —
'zero22pi' has been removed. With appropriate code changes, use 'wrapTo360' or 'wrapTo2Pi' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`NPI2PI` —
'npi2pi' has been removed. With appropriate code changes, use 'wrapTo180' or 'wrapToPi' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`OBJMPOOL` —
'MATLABPOOL' has been removed. Use 'PARPOOL' instead.

Severity: Error

`ODEMOD` —
'modem.oqpskdemod' has been removed. With appropriate code changes, use 'comm.OQPSKDemodulator' instead.

Severity: Error

For more information, see comm.OQPSKDemodulator (Communications Toolbox).

`OMOD` —
'modem.oqpskmod' has been removed. With appropriate code changes, use 'comm.OQPSKModulator' instead.

Severity: Error

For more information, see comm.OQPSKModulator (Communications Toolbox).

`ONEM` —
'onem' has been removed. With appropriate code changes, use 'ones' instead.

Severity: Error

Instead of using the onem function, create a geographic cells reference object using the georefcells function and a matrix of ones using the ones function. This example shows how to update your code.

Will be removed	Recommended
[Z,refvec] = onem(latlim,lonlim,scale);	R = georefcells(latlim,lonlim,1/scale,1/scale); Z = ones(R.RasterSize);

Related Documentation: solve (Optimization Toolbox)

`OQPDEM` —
'oqpskdemod' has been removed. With appropriate code changes, use 'comm.OQPSKDemodulator' instead.

Severity: Error

`OQPMOD` —
'oqpskmod' has been removed. With appropriate code changes, use 'comm.OQPSKModulator' instead.

Severity: Error

`ORIGINUI` —
'originui' has been removed. With appropriate code changes, use 'setm' instead.

Severity: Error

`PADEMOD` —
'modem.pamdemod' has been removed. With appropriate code changes, use 'pamdemod' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Communications Toolbox).

`PAMOD` —
'modem.pammod' has been removed. With appropriate code changes, use 'pammod' instead.

Severity: Error

Severity: Error

Related Documentation: propagationModel (Communications Toolbox)

`PMRTM2` —
'propagationModel('raytracing-imagemethod')' syntax has been removed. With appropriate code changes, use 'propagationModel('raytracing', 'Method', 'image')' syntax instead.

Severity: Error

Related Documentation: propagationModel (Communications Toolbox)

`PMRTM3` —
'propagationModel('raytracingimage-method')' syntax has been removed. With appropriate code changes, use 'propagationModel('raytracing', 'Method', 'image')' syntax instead.

Severity: Error

Related Documentation: propagationModel (Communications Toolbox)

`PMRTM4` —
'propagationModel('raytracingimagemethod')' syntax has been removed. With appropriate code changes, use 'propagationModel('raytracing', 'Method' , 'image')' syntax instead.

Severity: Error

Related Documentation: propagationModel (Communications Toolbox)

`PNZOM` —
'panzoom' has been removed. With appropriate code changes, use 'zoom' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`POLYBFO` —
'polyspace.BugFinderOptions' has been removed. With appropriate code changes, use 'polyspace.Options' instead.

Severity: Error

`POLYCPO` —
'polyspace.CodeProverOptions' has been removed. With appropriate code changes, use 'polyspace.Options' instead.

Severity: Error

`POLYCS` —
Use 'MergedComputingSettings' instead of 'ComputingSettings' for polyspace.Options.

Severity: Error

Replace ComputingSettings.Batch with either MergedComputingSettings.BatchBugFinder or MergedComputingSettings.BatchCodeProver. For example, for Polyspace^® Bug Finder™ options myOpts, change myOpts.ComputingSettings.Batch to myOpts.MergedComputingSettings.BatchBugFinder.

Replace ComputingSettings.AddToResultsRepository with either MergedComputingSettings.AddToResultsRepositoryBugFinder or MergedComputingSettings.AddToResultsRepositoryCodeProver. For example, for Polyspace Code Prover™ option myOpts, change myOpts.ComputingSettings.AddToResultsRepository tomyOpts.MergedComputingSettings.AddToResultsRepositoryCodeProver.

For more information, see polyspace.Project.Configuration properties in the Polyspace Bug Finder or Polyspace Code Prover documentation.

`POLYREP` —
Use 'MergedReporting' instead of 'Reporting' for polyspace.Options.

Severity: Error

Use MergedReporting instead of Reporting for polyspace.Options. All sub-properties remain the same except ReportTemplate, which can be replaced by either BugFinderReportTemplate or CodeProverReportTemplate.

For more information, see polyspace.Project.Configuration properties in the Polyspace Bug Finder or Polyspace Code Prover documentation.

`PR2GD` —
'par2geod' has been removed. With appropriate code changes, use 'geodeticLatitudeFromParametric' instead.

Severity: Error

Related Documentation: geodeticLatitudeFromParametric (Mapping Toolbox)

`PRDLG` —
'printdlg' will be removed in a future release. With appropriate code changes, use 'uiprintdlg' instead.

Severity: Warning

Severity: Error

`PSMOD` —
'modem.pskmod' has been removed. With appropriate code changes, use 'pskmod' instead.

Severity: Error

For more information, see Communications Toolbox Release Notes (Communications Toolbox).

`PSRENAME` —
Input argument 'powersys' will be removed in a future release. Use 'sps' instead.

Severity: Warning

`PSTAT` —
The 'Static' attribute on properties has been removed. Use the 'Constant' attribute instead.

Severity: Error

`RANDSD` —
'randseed' has been removed. With appropriate code changes, use 'rng' instead.

Severity: Error

`RESOU` —
'resources' is a reserved folder. Running MATLAB files located in a folder named 'resources' is not supported.

Severity: Error

`RESZM` —
'resizem' has been removed. With appropriate code changes, use 'georesize' or 'imresize' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`RETPRI` —
Positional syntax for optional arguments has been removed from 'ret2price'. Use name-value pairs instead.

Severity: Error

Related Documentation: ret2price (Econometrics Toolbox)

`RICHN` —
'ricianchan' has been removed. With appropriate code changes, use 'comm.RicianChannel' instead.

Severity: Error

`RLCHN` —
'rayleighchan' has been removed. With appropriate code changes, use 'comm.RayleighChannel' instead.

Severity: Error

`RM2VEC` —
'refmat2vec' has been removed. With appropriate code changes, construct a geographic raster reference object using 'refvecToGeoRasterReference' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`RNG2BW` —
'range2bw' will be removed in a future release. Use 'rangeres2bw' instead, which is a direct replacement.

Severity: Warning

`RSTCK` —
'restack' has been removed. With appropriate code changes, use 'uistack' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`RTLYR` —
'rootlayr' has been removed. There is no simple replacement for this.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`RTWHWDR` —
'RTW.HWDeviceRegistry' is unsupported and has been removed. The replacement strategy can be found in MATLAB documentation.

Severity: Error

For information about upgrading data definitions for your hardware, see Upgrade Data Definitions for Hardware Devices (MATLAB Coder).

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`RV2MAT` —
'refvec2mat' has been removed. With appropriate code changes, construct a geographic raster reference object using 'refvecToGeoRasterReference' instead.

Severity: Error

`SDTSINFO` —
'sdtsinfo' has been removed. With appropriate code changes, use 'georasterinfo' instead.

To access a data acquisition device, use a DataAcquisition object with its functions and properties instead. You can replace the queueOutputData function with one of the following:

Use preload if the DataAcquisition is not running and you do not want to start it at this time. This is necessary before starting background operations.
Use write if you want to immediately start the DataAcquisition with the data you are writing (foreground), or if the DataAcquisition is already running and you want to add output data (background).

Severity: Error

`SETPOSTN` —
'setpostn' has been removed. With appropriate code changes, use 'geographicToDiscrete' instead.

Severity: Error

`SFTSPC` —
'shiftspc' has been removed. With appropriate code changes, use 'strjust' instead.

Severity: Error

`SIZEM` —
'sizem' has been removed. With appropriate code changes, use 'rastersize' property of a map raster reference object instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`SLLERR1` —
'sllasterror' will be removed in a future release. Use an identifier on the CATCH block instead.

Severity: Warning

sllastdiagnostic and sllasterror will be removed in a future release. To obtain information about an error (such as the message ID and the stack trace), use an identifier on the catch block instead.

If you specify a variable with a catch block and an error occurs in the try block, MATLAB enters the catch block and assigns the MException object to the catch variable. The MException object contains the error message, the message ID, and the stack trace. To pass this information to a calling function, either return the MException object as an output of your function, or call its rethrow method to rethrow the error. There is no need to save and restore sllasterror around such a try/catch block.

Specify a variable with a catch block, as described in ”The try-catch Statement”.

`SLLERR2` —
'sllastdiagnostic' will be removed in a future release. Use an identifier on the CATCH block instead.

Severity: Warning

data = [-0.4+0.02i -0.05+0.63i 0.32+0.71i 0.5+0.67i];
[hlineseries,hsc] = smithchart(data);
hlineseries.LineWidth = 2;
hsc.Type = 'Y';

The following code produces an equivalent Smith chart using smithplot instead.

data = [-0.4+0.02i -0.05+0.63i 0.32+0.71i 0.5+0.67i];
smithplot(data,'LineWidth',2,'GridType','Y');

If your code uses the lineseries or smithchart handles, rewrite your code to use the equivalent properties of smithplot. For example, to replace the smithchart property Value, use 'GridValue' in the call to smithplot.

Otherwise just replace the call to smithchart with a call to smithplot.

For more information, see smithplot in the RF Toolbox™ or Antenna Toolbox™ documentation.

`SMTHF` —
'FontSmoothing' property will be removed in a future release. Font smoothing behavior has been enabled by default. Editing this property does not have an effect.

Severity: Warning

For additional information, see Axes Properties.

Related Documentation: Axes Properties

`SMTHFA` —
'DefaultAxesFontSmoothing' setting will be removed in a future release. Font smoothing behavior has been enabled by default. Editing this setting does not have an effect.

Severity: Warning

For additional information, see Axes Properties.

Related Documentation: Axes Properties

`SMTHFT` —
'DefaultTextFontSmoothing' setting will be removed in a future release. Font smoothing behavior has been enabled by default. Editing this setting does not have an effect.

Severity: Warning

For additional information, see Text Properties.

Related Documentation: Text Properties

`SMTHG` —
'GraphicsSmoothing' property will be removed in a future release. Graphics smoothing behavior has been enabled by default. Editing this property does not have an effect.

Severity: Warning

Related Documentation: Transition Your Code to serialport Interface (Instrument Control Toolbox)

Severity: Warning

For more information, see Transition Your Code to serialport Interface.

`SPTMT` —
Manually setting 'Terminator' property of 'serialport' class will be removed in a future release. With appropriate code changes, use 'configureTerminator' method of 'serialport' class to set value instead.

Severity: Warning

For more information, see Transition Your Code to serialport Interface.

`SPZER` —
'spzerom' has been removed. With appropriate code changes, use 'sparse' instead.

Severity: Error

Instead of using the spzerom function, create a geographic cells reference object using the georefcells function and a matrix of NaN values using the NaN function. This example shows how to update your code.

Will be removed	Recommended
[Z,refvec] = spzerom(latlim,lonlim,scale);	R = georefcells(latlim,lonlim,1/scale,1/scale); Z = sparse(R.RasterSize(1),R.RasterSize(2));

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`SURFDIST` —
'surfdist' has been removed. With appropriate code changes, use 'distance' instead.

Severity: Error

`SVFIGC` —
'compact' argument will be removed in a future release and currently has no effect. 'compact' behavior is always enabled.

Severity: Warning

Related Documentation: savefig

`SVM2SUB` —
'Simulink.VariantManager.convertToVariant' will be removed in a future release. Use 'Simulink.VariantUtils.convertToVariantSubsystem' instead, which is a direct replacement.

Severity: Warning

Related Documentation: Simulink.VariantUtils.convertToVariantSubsystem (Simulink)

`SVM2SUBA` —
'Simulink.VariantManager.convertToVariantAssemblySubsystem' will be removed in a future release. Use 'Simulink.VariantUtils.convertToVariantAssemblySubsystem' instead, which is a direct replacement.

Severity: Warning

Related Documentation: Simulink.VariantUtils.convertToVariantAssemblySubsystem (Simulink)

`SVMCLASSIFY` —
'svmclassify' has been removed. With appropriate code changes, use 'ClassificationSVM' instead.

Severity: Error

`SVMSMOSET` —
'svmsmoset' has been removed. With appropriate code changes, use 'fitcsvm' instead.

Severity: Error

svmsmoset has been removed.

Replace all instances of svmsmoset with the corresponding name-value pair argument to fitcsvm.

Instead of svmsmoset('TolKKT',value) use fitcsvm(X,Y,'DeltaGradientTolerance',value). For equivalent functionality, the 'Solver' must have a value of 'SMO'.
Instead of svmsmoset('MaxIter',value) use fitcsvm(X,Y,'IterationLimit',value).
Instead of svmsmoset('Display',value) use fitcsvm(X,Y,'Verbose',value). The values for 'Verbose' do not directly correspond to the values for 'Display'.
There is no replacement for svmsmoset('KKTViolationLevel',value).
Instead of svmsmoset('KernelCacheLimit',value) use fitcsvm(X,Y,'CacheSize',value). The values for 'CacheSize' do not directly correspond to the values for 'KernelCacheLimit'.

For more information, see the fitcsvm reference page in the Statistics and Machine Learning Toolbox documentation.

`SVMTRAIN` —
'svmtrain' has been removed. With appropriate code changes, use 'fitcsvm' instead.

Severity: Error

`SVMVL` —
'Simulink.VariantManager.variantLegend' will be removed in a future release. Use 'Simulink.VariantUtils.variantLegend' instead, which is a direct replacement.

Severity: Warning

Related Documentation: Simulink.VariantUtils.variantLegend (Simulink)

`SYMBM` —
'symbolm' has been removed. With appropriate code changes, use 'scatterm' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`SZCLN` —
Colon operands must now be scalar, but 'size(A)' usually returns a nonscalar value. To revert to the old behavior, use 'size(A,1)' instead, or index into the first element of the variable assigned to 'size(A)'.

Severity: Error

Severity: Warning

`TCNTR` —
'NetworkRole' property of 'tcpclient' class will be removed in a future release. With appropriate code changes, use 'tcpclient' constructor instead.

Severity: Warning

For more information, see Transition Your Code to tcpclient Interface (Instrument Control Toolbox).

Related Documentation: Transition Your Code to tcpclient Interface (Instrument Control Toolbox)

`TCPC` —
'tcpip' with 'client' as a 'NetworkRole' has been removed. With appropriate code changes, use 'tcpclient' instead.

Severity: Error

`TCPS` —
'tcpip' with 'server' as a 'NetworkRole' has been removed. With appropriate code changes, use 'tcpserver' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`TCQRY` —
'query' method of 'tcpclient' class will be removed in a future release. With appropriate code changes, use 'writeread' method of 'tcpclient' class instead.

Severity: Warning

For more information, see Transition Your Code to tcpclient Interface (Instrument Control Toolbox).

Related Documentation: Transition Your Code to tcpclient Interface (Instrument Control Toolbox)

`TCRESULT` —
'testconsole.Results' has been removed. Use 'comm.ErrorRate' or BERTool instead.

Severity: Error

The testconsole.Results object has been removed. To compute error rates, use the comm.ErrorRate (Communications Toolbox) System object or the Bit Error Rate Analysis (Communications Toolbox) app instead.

`TCRHT` —
'RemoteHost' property of 'tcpclient' class will be removed in a future release. With appropriate code changes, use 'Address' property of 'tcpclient' class instead.

Severity: Warning

For more information, see Transition Your Code to tcpclient Interface (Instrument Control Toolbox).

Related Documentation: Transition Your Code to tcpclient Interface (Instrument Control Toolbox)

`TCRPT` —
'RemotePort' property of 'tcpclient' class will be removed in a future release. With appropriate code changes, use 'Port' property of 'tcpclient' class instead.

Severity: Warning

For more information, see Transition Your Code to tcpclient Interface (Instrument Control Toolbox).

Related Documentation: Transition Your Code to tcpclient Interface (Instrument Control Toolbox)

`TCSTR` —
'scanstr' method of 'tcpclient' class will be removed in a future release. With appropriate code changes, use 'readline' method of 'tcpclient' class instead.

Severity: Warning

`TCTDY` —
'TransferDelay' property of 'tcpclient' class will be removed in a future release. With appropriate code changes, use 'EnableTransferDelay' property of 'tcpclient' class instead.

Severity: Warning

For more information, see Transition Your Code to tcpclient Interface (Instrument Control Toolbox).

Related Documentation: Transition Your Code to tcpclient Interface (Instrument Control Toolbox)

`TCTMT` —
Manually setting 'Terminator' property of 'tcpclient' class will be removed in a future release. With appropriate code changes, use 'configureTerminator' method of 'tcpclient' class to set value instead.

Severity: Warning

To create a regression tree, use fitrtree to construct a RegressionTree object.

For more information, see the fitctree or fitrtree reference pages in the Statistics and Machine Learning Toolbox documentation.

`TREEPRUNE` —
TREEPRUNE has been removed. Use ClassificationTree or RegressionTree PRUNE methods instead.

Severity: Error

treeprune has been removed.

Replace instances of treeprune with the prune method of a ClassificationTree object (created using fitctree) or RegressionTree object (created using fitrtree).

For more information, see the prune method reference page of the ClassificationTree or RegressionTree class in the Statistics and Machine Learning Toolbox documentation.

`TREETEST` —
'treetest' has been removed. Use ClassificationTree or RegressionTree methods instead.

Severity: Error

treetest has been removed.

Create a tree object, T, using fitctree for a ClassificationTree object or fitrtree for a RegressionTree object, and replace treetest with the appropriate method.

Replace treetest(T,'resubstitution') with resubLoss(T).
Replace treetest(T,'test',X,Y) with loss(T,X,Y).
Replace treetest(T,'crossvalidate',X,Y) with cvloss(T).

For more information, see the resubLoss, loss, or cvloss method reference pages of the ClassificationTree or RegressionTree class in the Statistics and Machine Learning Toolbox documentation.

`TREEVAL` —
TREEVAL has been removed. Use ClassificationTree or RegressionTree PREDICT methods instead.

Severity: Error

treeval has been removed.

Replace instances of treeval with the predict method of a ClassificationTree object (created using fitctree) or RegressionTree object (created using fitrtree).

For more information, see the predict method reference page of the ClassificationTree or RegressionTree class in the Statistics and Machine Learning Toolbox documentation.

Related Documentation: Transition Your Code to tcpserver Interface (Instrument Control Toolbox)

`TSSTR` —
'scanstr' method of 'tcpserver' class will be removed in a future release. With appropriate code changes, use 'readline' method of 'tcpserver' class instead.

Severity: Warning

`TSTMT` —
Manually setting 'Terminator' property of 'tcpserver' class will be removed in a future release. With appropriate code changes, use 'configureTerminator' method of 'tcpserver' class to set value instead.

Severity: Warning

`UNRPWR` —
Combining exponentiation operators with unary operators (such as logical negation) without parentheses will not be supported in a future release. Use parentheses to clarify the evaluation order.

Severity: Warning

Although most operators work from left to right, the operators ^-, .^-, ^+, .^+, ^~, and .^~ work from second from the right to left. For more information, see Operator Precedence.

Use parentheses to specify the intended precedence of statements containing these operator combinations explicitly.

`USGDM` —
'usgsdem' has been removed. With appropriate code changes, use 'readgeoraster' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`USGKD` —
'usgs24kdem' has been removed. With appropriate code changes, use 'readgeoraster' instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

Severity: Error

Severity: Error

Related Documentation: vrjoystick (Simulink 3D Animation)

`VRNDE` —
'vrnode' has been removed. With appropriate code changes, use sim3d classes to create and view a 3D environment instead.

Severity: Error

The vrnode has been removed. For alternate functionality, see Transition Virtual Reality World to Unreal Engine 3D Environment (Simulink 3D Animation).

Related Documentation: vrnode (Simulink 3D Animation)

`VRPLY` —
'vrplay' and the Simulink 3D Animation Player have been removed. With appropriate code changes, use sim3d classes to create and view a 3D environment instead.

Severity: Error

The vrplay has been removed. For alternate functionality, see Transition Virtual Reality World to Unreal Engine 3D Environment (Simulink 3D Animation).

Related Documentation: vrplay (Simulink 3D Animation)

`VRSPCMOUSE` —
'vrspacemouse' has been removed. Use 'sim3d.io.SpaceMouse' instead, which is a direct replacement.

Severity: Error

Related Documentation: vrspacemouse (Simulink 3D Animation)

`VRVIEW` —
'vrview' and the Simulink 3D Animation Viewer have been removed. With appropriate code changes, use sim3d classes to create and view a 3D environment instead.

Severity: Error

The vrview has been removed. For alternate functionality, see Transition Virtual Reality World to Unreal Engine 3D Environment (Simulink 3D Animation).

Related Documentation: vrview (Simulink 3D Animation)

`VRWRLD` —
'vrworld' has been removed. With appropriate code changes, use sim3d classes to create and view a 3D environment instead.

Severity: Error

The vrworld has been removed. For alternate functionality, see Transition Virtual Reality World to Unreal Engine 3D Environment (Simulink 3D Animation).

Related Documentation: vrworld (Simulink 3D Animation)

`VSBBR` —
'binblockread' method of 'visadev' class will be removed in a future release. With appropriate code changes, use 'readbinblock' method of 'visadev' class instead.

Severity: Warning

For more information, see Transition Your Code to visadev Interface (Instrument Control Toolbox).

Related Documentation: Transition Your Code to visadev Interface (Instrument Control Toolbox)

`VSBBW` —
'binblockwrite' method of 'visadev' class will be removed in a future release. With appropriate code changes, use 'writebinblock' method of 'visadev' class instead.

Severity: Warning

For more information, see Transition Your Code to visadev Interface (Instrument Control Toolbox).

`WAVLAZ` —
'waveletAnalyzer' has been removed. With appropriate code changes, use Signal Multiresolution Analyzer, Wavelet Image Analyzer, Wavelet Signal Analyzer, Wavelet Signal Denoiser, or Wavelet Time-Frequency Analyzer instead.

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`WAVMENU` —
'wavemenu' has been removed. With appropriate code changes, use Signal Multiresolution Analyzer, Wavelet Image Analyzer, Wavelet Signal Analyzer, Wavelet Signal Denoiser, or Wavelet Time-Frequency Analyzer instead.

Severity: Error

`WEBMP` —
'webmap' will be removed in a future release. With appropriate code changes, use a geographic axes object instead.

Severity: Warning

`WEBREMOVE` —
The 'web' function does not return a handle or URL for pages that open in the system browser. Use 'stat = web(___, '-browser')' instead.

Severity: Warning

The web function currently opens external sites using your system browser by default, unless configured otherwise in the MATLAB Web Preferences. For a site that opens in the system browser, the returned handle or URL will be empty.

In a future release, the web function will open sites only in the system browser. Therefore, MATLAB will produce an error if your code contains a web syntax that returns a handle or URL.

Remove the handle and URL output arguments of the web function. Consider using the '-browser' option to open all pages in your system browser. This table shows some examples of how you can update your code.

Before		After
[stat,h] = web('https://www.mathworks.com');		stat = web('https://www.mathworks.com','-browser');
[stat,h,url] = web('https://www.mathworks.com');		stat = web('https://www.mathworks.com','-browser');

`WEIBCDF` —
'weibcdf' has been removed. With appropriate code changes, use 'wblcdf' instead.

Severity: Error

Related Documentation: wblcdf (Statistics and Machine Learning Toolbox)

`WEIBFIT` —
'weibfit' has been removed. With appropriate code changes, use 'wblfit' instead.

Severity: Error

Related Documentation: wblfit (Statistics and Machine Learning Toolbox)

`WEIBINV` —
'weibinv' has been removed. With appropriate code changes, use 'wblinv' instead.

Severity: Error

Related Documentation: wblinv (Statistics and Machine Learning Toolbox)

`WEIBLIKE` —
'weiblike' has been removed. With appropriate code changes, use 'wbllike' instead.

Severity: Error

Related Documentation: wbllike (Statistics and Machine Learning Toolbox)

Severity: Error

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`ZADOF` —
'lteZadoffChuSeq' has been removed. Use 'zadoffChuSeq' instead, which is a direct replacement.

Severity: Error

Related Documentation: zadoffChuSeq (Communications Toolbox)

`ZEROM` —
'zerom' has been removed. With appropriate code changes, use 'zeros' instead.

Severity: Error

Instead of using the zerom function, create a geographic cells reference object using the georefcells function and a matrix of zeros using the zeros function. This example shows how to update your code.

Will be removed	Recommended
[Z,refvec] = zerom(latlim,lonlim,scale);	R = georefcells(latlim,lonlim,1/scale,1/scale); Z = zeros(R.RasterSize);

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

Forward Compatibility Considerations

Severity: Warning

Setting the class attribute Abstract to false causes an error if that class then does any of the following.

Contains any abstract methods or properties
Inherits and does not implement abstract methods or properties

Do not set the Abstract attribute in this class definition. It is a good practice to set the Abstract class attribute to true or not to set it at all.

`BDLGI` —
Variable might be set by a nonlogical operator.

Severity: Warning

It appears the code sets the specified variable with an operator that does not yield a logical value where Code Analyzer expects one. Code Analyzer can incorrectly display this message if the operator is overloaded. For information on overloading operators, see “Implementing Operators for Your Class”.

Severity: Warning

MATLAB does not support using this syntax to compare b to a and c using logical operators, e.g. <, >=, ==, etc.

Instead, MATLAB evaluates operators of equal precedence from left to right. This means that the statement, a < b < c, is equivalent to the statement (a < b) < c, comparing the logical result of a < b (either 0 or 1) to the value c. Statements using this type of interval testing rarely yield useful results.

Break the comparison, a < b < c, into a series of binary comparisons. If all arguments are numeric scalars, use the form:

(a < b) && (b < c)

Otherwise, use the form:

(a < b) & (b < c)

For more information, see Operator Precedence.

`COMNC` —
Comment with percent (%) following comma acts as a row separator. Replace the comma with a semicolon to make the row separation clearer. Alternatively, replace the percent (%) with an ellipsis (...) to add a comment inside a row.

Severity: Warning

Comment with percent (%) following comma acts as a row separator. Your use of a comma suggests that you are trying to create a row vector, rather than a column vector. Within array initializations, this can cause unintended errors by spitting an into separate rows in unintended locations.

To comment within an array without splitting rows, replace the percent (%) with an ellipsis(…).

Old	New
The comment acts as a row separator causing the array to have uneven dimensions. This generates an error. x = [ 1, 2, ... % My comment 3, 4, ... 5, 6];	The comment does not act as a row separator. x = [ 1, 2, ... ... My comment 3, 4, ... 5, 6];

Old

New

The comment acts as a row separator causing the array to have uneven dimensions.

This generates an error.

x = [ 1, 2, ...
      % My comment
      3, 4, ...
      5, 6];

The comment does not act as a row separator.

x = [ 1, 2, ...
      ... My comment
      3, 4, ...
      5, 6];

If the row separation is intentional, replace the comma with a semicolon to make the row separation clearer.

`COMPNOP` —
This logical comparison simplifies to VAR_NAME(...). Did you mean to use VAR_NAME to evaluate function argument: VAR_NAME(...VAR_NAME...)?

Severity: Warning

A comparison operator is applied to a function that returns logical values (true or false). In this case, the comparison always returns the same value as the logical function. Therefore, it is either unnecessary or performed incorrectly.

If you want to perform a comparison, rewrite your code by placing the operator inside the function call. Otherwise, simplify your code by replacing the comparison statement with the function call.

This example shows how to rewrite your code. Option 1 (B1) shows how to simplify your code to determine whether all elements in each column of a matrix A are nonzero. Option 2 (B2) shows how to perform a comparison to determine whether all elements in each column of A are equal to 1.

Original		Revised
A = [0 3 5 1; 0 0 -2 1]; B = all(A)==1; % B = [0 0 1 1]		A = [0 3 5 1; 0 0 -2 1]; B1 = all(A); % B1 = [0 0 1 1] B2 = all(A==1); % B2 = [0 0 0 1]

`COMPNOT` —
This logical comparison simplifies to ~VAR_NAME(...). Did you mean to use VAR_NAME to evaluate function argument: VAR_NAME(...VAR_NAME...)?

Severity: Warning

A comparison operator is applied to a function that returns logical values (true or false). In this case, the comparison always returns the logical negation of the function output. Therefore, it is either unnecessary or performed incorrectly.

If you want to perform a comparison, rewrite your code by placing the operator inside the function call. Otherwise, simplify your code by replacing the comparison statement with the logical negation of the function call.

This example shows how to rewrite your code. Option 1 (B1) shows how to simplify your code to determine whether one or more elements in each column of a matrix A are 0. Option 2 (B2) shows how to perform a comparison to determine whether all elements in each column of A are equal to 0.

Original		Revised
A = [0 3 5 1; 0 0 -2 1]; B = all(A)==0; % B = [1 1 0 0]		A = [0 3 5 1; 0 0 -2 1]; B1 = ~all(A); % B1 = [1 1 0 0] B2 = all(A==0); % B2 = [1 0 0 0]

`CPROP` —
VAR_NAME is also the name of a property, which may be confusing. Use obj.PropertyName syntax to reference the property, or rename the property to improve readability.

Severity: Warning

Because the code has never initialized the indicated name, Code Analyzer treats it as a function call. However, because this call occurs within a class method and there is a property with the same name as the apparent function being called, it is unclear whether you intended to refer to the property rather than to a function of the same name. Even if the code is correct it might confuse others who read the code.

For information about using properties in methods, see Ways to Use Properties.

If you want to refer to a property of an object, find the appropriate object (often the first input argument of the method) and place the object name and a dot before the property name.

If you want to call a function that has the same name as a property in the class, consider renaming the property to avoid confusing someone unfamiliar with the code.

If you want to keep the current name, suppress the message as described in Adjust Code Analyzer Message Indicators and Messages.

`CTCH` —
Best practice is for CATCH to be followed by an identifier that gets the error information.

Severity: Warning

When an error occurs in a try block, MATLAB transfers control to the catch block. If the catch block has an identifier, MATLAB enters the catch block with the identifier set to an MException object that contains the error message, the message ID, and the stack trace. You can use this object with functions such as rethrow to pass the error to the code that called it. Not only does the object always contain information about the correct error, there is no longer any need to save the lasterr around the try/catch block to avoid breaking old code. For more information, see “Capturing Information About the Error”.

Use an identifier on the catch block. If the catch block has an identifier, the state of lasterr and lasterror are unchanged. Typically, you can replace a call to lasterror with the catch block identifier, and you can replace a call to lasterr by referencing the message field of this identifier. You can probably remove any code that saves the previous state of lasterr and lasterror. The resulting code is typically smaller, clearer, and faster than the older code.

`CTOINW` —
Use of constructed object as input to constructor is not necessary.

Severity: Warning

`CTPCT` —
The format might not agree with the argument count.

Severity: Warning

In analyzing a call to a function that uses a format specifier to guide its operation, Code Analyzer has determined that the number of format operators (%d,%f, and so on) does not match the number of arguments supplied. This message is typically the result of one of the following:

The code supplies more arguments than the format specifies.
The format requires arguments, but the code supplies none.

Be aware that Code Analyzer processes format specifiers differently from C or C++, so the rules for matching arguments to the format specifiers are also different. For details, see “Formatting Strings”.

Note that Code Analyzer can display this message erroneously for error or warning functions, because Code Analyzer is also trying to determine whether the first argument is a message ID or a format specifier.

Make sure that the number of supplied values matches the number of format operators. If not, fix the code. If the message is incorrect, suppress it as described in Adjust Code Analyzer Message Indicators and Messages.

`DISPLAY` —
Overloading DISPLAY is not recommended.

Severity: Warning

To customize display of your object, it is best practice to either subclass matlab.mixin.CustomDisplay or overload the disp (DSP System Toolbox) function. It is rarely necessary to overload display.

MATLAB calls the display function whenever an object is referred to in a statement that is not terminated by a semicolon. If an assignment is made, the display function prints the name of the variable that is being displayed. Otherwise display uses ans as the variable name. The display function then calls disp to handle the actual display of the values. For more information, see Overload the disp Function.

`DSPMDA` —
Distributed array must be created outside of an SPMD block.

Severity: Warning

`DUALC` —
Command might be prematurely ended by comma.

Severity: Warning

The arguments to a MATLAB command (or a declaration such as global or persistent) are typically a sequence of character vectors or names with spaces separating them. Code Analyzer has found a comma in such a sequence. Rather than separating the arguments, the comma ends the statement.

If you intended to specify a sequence of command arguments, replace the comma with white space.

If you intended to end the command, use a semicolon instead of a comma.

`DUPNAMEARG` —
This named argument was already provided. If this function does not allow or ignores repeated named arguments, remove one of the duplicated named arguments.

Severity: Warning

Most functions do not allow repeated named arguments. Any function that uses an arguments block only uses the last supplied value for a given named argument.

Remove duplicate named arguments.

Old	Replacement
ax = axes; Y = meshgrid(1:5); b = bar(Y); set(b([3 4 2 1 5]),Parent=[],Parent=ax)	ax = axes; Y = meshgrid(1:5); b = bar(Y); set(b([3 4 2 1 5]),Parent=ax)

`ELARLOG` —
The VAR_NAME operator in the expression VAR_NAME(A VAR_NAME B) is unexpected. Should this be VAR_NAME(A) VAR_NAME B?

Severity: Warning

`ERTAG` —
The first argument of ERROR should be a message identifier.

Severity: Warning

`EVLCS` —
'eval' is inefficient and makes code less clear. Call the statement directly.

Severity: Warning

MATLAB is unable to analyze code within statements called by eval. This prevents MATLAB from performing any performance optimization and limits the guidance that the editor is able to provide. This makes code less efficient and difficult to debug.

Furthermore, concatenated character vectors within an eval statement are often difficult to read. This makes code less clear and causes issues with sharing and maintaining code.

To allow MATLAB to perform performance optimization, call the statement directly.

Old	New
str = ([ 'save("a.mat");']); eval(str);	save("a.mat");

`EVLDOT` —
'eval' is inefficient and makes code less clear. Use dynamic field names to access structure fields or object properties instead.

Severity: Warning

Furthermore, concatenated character vectors within an eval statement are often difficult to read. This makes code less clear and causes issues with sharing and maintaining code.

Structure fields or object properties can be accessed using dynamic field names. The example shows how code using eval to assign numbered field names can be refactored to use dynamic field names.

Old	New
for i = 1:5 eval(['handles.axes', num2str(i)]) end	for i = 1:5 handles.("axes" + num2str(i)) end

MATLAB is able to detect that fields of handles will be accessed and this allows performance optimization.

For more information, see Generate Field Names from Variables .

`EVLDUAL` —
This use of 'eval' is unnecessary and can be removed. Call the evaluated function directly using parentheses. For example, use 'load(filename)' instead of 'eval(['load ' filename])'.

Severity: Warning

Furthermore, concatenated character vectors within an eval statement are often difficult to read. This makes code less clear and causes issues with sharing and maintaining code.

Use function syntax instead of using eval to use command syntax. This allows you to pass variables as inputs. For example:

Old	New
eval(['load ' theFilename])	load(theFilename)
eval(['save ' theFilename ' bigArray'])	save(theFilename, "bigArray")
eval(['cd ' labdata])	cd(labdata)
eval(['mex ', myOptions, ' -c modlab.c '])	mex(myOptions, "-c", "modlab.c")
eval(['clear selectMode ' tempvar])	clear("selectMode", tempvar)

For more information see Choose Command Syntax vs Function Syntax

`EVLEQ` —
'eval' is inefficient and makes code less clear. Assign to the variable directly.

Severity: Warning

Furthermore, concatenated character vectors within an eval statement are often difficult to read. This makes code less clear and causes issues with sharing and maintaining code.

To allow MATLAB to perform performance optimization, use the variable directly and use eval for the right hand side of the assignment.

Old	New
eval( [ 'signal=', varname, ';' ] )	signal = eval(varname);

`EVLSEQVAR` —
Using 'eval' to dynamically assign variables is not recommended.

Severity: Warning

MATLAB cannot perform any performance optimization on statements called by eval. This can cause code to run less efficiently. eval statements make code less clear and cause issues with sharing and maintaining code. One use of the eval function is to create sets of variables such as A1, A2, ..., An, but this approach does not use the array processing power of MATLAB.

The preferred method is to store related data in a single array. If the data sets are of different types or sizes, use a structure or cell array.

For example, create a cell array that contains 10 elements, where each element is a numeric array:

Old	New
eval(['A', int2str(n),' = magic(n)'])	numArrays = 10; A = cell(numArrays,1); for n = 1:numArrays A{n} = magic(n); end

Access the data in the cell array by indexing with curly braces. For example, display the fifth element of A:

A{5}

ans =
    17    24     1     8    15
    23     5     7    14    16
     4     6    13    20    22
    10    12    19    21     3
    11    18    25     2     9

For more information see Alternatives to the eval Function.

`EVLSYS` —
'eval' is inefficient and makes code less clear. To make calls to the operating system use the system function instead.

Severity: Warning

To make calls to the operating system use the system function instead without the '!' at the beginning of the command:

Old	New
eval( [ '!open -a "Google Chrome" ''', openUrl, '''' ] )	system( [ 'open -a "Google Chrome" ''', openUrl, '''' ] )

Old	Replacement
for ind = 1:10 ind = ind + 1; end	for ind = 1:10 newind = ind + 1; end

`FXSETL` —
VAR_NAME is also the loop variable for an outer loop. Rename this variable, so this loop does not affect the outer loop variable.

Severity: Warning

It appears that the index value of the indicated for loop reuses the name of an outer loop index. Because MATLAB resets the loop index to the next value when it returns to the top of the outer loop, it ignores any changes that took place within a nested loop. If the code does not to refer to the outer loop index value after the inner loop changes it, no problem results. However if you attempt to use the outer loop index value after the inner loop completes, it is likely to result in a bug.

Change the name of one of the for loop indexes.

Old	Replacement
for ind = 1:10 for ind = 1:10; end end	for ind1 = 1:10 for ind2 = 1:10; end end

`FXUP` —
Outer loop variable VAR_NAME is set inside a nested function.

Severity: Warning

It appears that the index value of a for loop changes within a nested function. In some cases, nested functions can be called by callbacks or other function calls leading to the loop index changing. This kind of bug is exceptionally hard to find, so Code Analyzer signals this situation even though in many cases the usage is benign.

Change the name of the for loop index or the variable of the same name in the nested function. If you must keep them as is, add a comment indicating the need and suppress the message as described in Adjust Code Analyzer Message Indicators and Messages.

`GTARG` —
Function might be called with too many arguments.

Severity: Warning

It appears the code calls the specified MATLAB library function with too many arguments. This message can be incorrect if the code is using an overloaded function in a class, and the overloaded function has different calling conventions than the MATLAB library function.

Check the function call to ensure that you specified the required number of arguments. If you are using an overloaded function, consider suppressing the message as described in Adjust Code Analyzer Message Indicators and Messages. For information on overloading functions, see “Overloading Functions for Your Class”.

`GVMIS` —
Global variables are inefficient and make errors difficult to diagnose. Use a function with input variables instead.

Severity: Warning

Global variables have their own workspace, which is separate from the base and function workspaces.

Using global variables is inefficient. MATLAB applies memory optimization to input variables in functions, but not to global variables. For more information see Avoid Unnecessary Copies of Data.

Also, global variables carry notable risks. Any function can access and update a global variable. Other functions that use the variable might return unexpected results. For example:

If you unintentionally give a “new” global variable the same name as an existing global variable, one function can overwrite the values expected by another. This error is difficult to diagnose.
If a global variable is changed in multiple functions, calling those functions in a different order can lead different results.

Use global variables sparingly, if at all.

For more information on variables and the workspace, see Global Variables subsection on Share Data Between Workspaces page.

`ISEQ` —
The context surrounding this expression expects a scalar value. Consider using 'isequal', which returns a scalar value, instead of '==' or '~='.

Severity: Warning

The context surrounding this expression expects a scalar value but == or ~= return a nonscalar array.

Consider using isequal instead of == or ~isequal instead of ~=.

Old	Replacement
if [2] == {1, 2, 3} end	if isequal([2],{1, 2, 3}) end
if [2] ~= {1, 2, 3} end	if ~isequal([2],{1, 2, 3}) end

`ITERS` —
The Code Analyzer type analysis may be incorrect here.

Severity: Warning

Code Analyzer cannot resolve the types of variables in this region of the program consistently, which can indicate a bug or inefficiency in the code. For example, the code might assign different types to a variable. Furthermore, due to the dynamic nature of MATLAB, other messages in this region of the program might be incorrect.

Review your code, including a search for typographical errors, and make sure the code assigns types to variables appropriately. Even if your code assigns types appropriately and is correct technically, consider rewriting it to clarify your intent. Typically, if Code Analyzer cannot analyze your code correctly, people can have difficultly understanding it as well. In addition, rewriting your code may resolve this message and any erroneous messages that appear in this region of the code.

If you prefer to keep your code as it is, suppress the message as described in Adjust Code Analyzer Message Indicators and Messages.

`KEYBOARDFUN` —
Consider removing 'keyboard' function once you have finished debugging. This function may have security implications.

Severity: Warning

`LNGNM` —
Names longer than VAR_NUMBER characters are not supported. This name has been truncated to VAR_NUMBER characters.

Severity: Warning

`LOAD` —
To avoid conflicts with functions on the path, specify variables to load from file.

Severity: Warning

When you load data from a file, there might be conflicts with functions on the path, which include MATLAB built-in functions. Consider the following function in which myData.mat contains the variable theta.

function z = myFun
    load myData.mat
    z = theta(1);
end

If there is a function theta on the MATLAB path, the variable theta conflicts with the function theta. To avoid possible conflict, specify the theta variable in the call to load.

function z = myFun
    load myData.mat theta
    z = theta(1);
end

To avoid conflict with functions on the path, load data from a file using one of these syntaxes.

Specify variables to load. For example,

load mydata.mat a b c
load('mydata.mat','a','b','c')

Specify an output argument to load data into a structure or array. For example,
```
S = load('mydata.mat')
```

Best practice is to load only the variables you will use or load the variables into a structure. For more information, see load (Instrument Control Toolbox).

`LOGMAX` —
Using 'max' on a logical expression is hard to understand and might be incorrect. Consider using 'any' instead.

Severity: Warning

Using max on a logical expression makes code difficult to read and might be incorrect.

To determine if one or more entries in an array are true, use any instead. For example:

Old	Replacement
max(x == y)	any(x == y)

`LOGMIN` —
Using 'min' on a logical expression is hard to understand and might be incorrect. Consider using 'all' instead.

Severity: Warning

Using min on a logical expression makes code difficult to read and might be incorrect.

To determine if all entries in an array are true, use all instead. For example:

Old	Replacement
min(x == y)	all(x == y)

`LOGPROD` —
Using 'prod' on a logical expression is hard to understand and might be incorrect. Consider using 'all' instead.

Severity: Warning

Using prod on a logical expression makes code difficult to read and may be incorrect.

To determine if all entries in an array are true, use all instead. For example:

Old	Replacement
prod(x == y)	all(x == y)

`LTARG` —
Function might be called with too few arguments.

Severity: Warning

It appears the code calls the specified MATLAB library function with too few arguments. This message can be incorrect if the code is using an overloaded function in a class, and the overloaded function has different calling conventions than the MATLAB library function.

`M3COL` —
Using three colons (a:b:c:d) in an expression is probably unintended.

Severity: Warning

An expression exists that is equivalent to a : b : c : d. Although MATLAB will execute the code, it is unlikely to return your intended results.

For example, suppose your code is this:

a:b+c:d+a:b

Due to operator precedence rules, MATLAB processes the code as though you specified parenthesis, like this:

a:(b+c):(d+a):b

Rewrite the code to remove one or more of the colons.

Severity: Warning

A class definition can reference properties only when they are defined in the class or in one of its superclasses.

To reference a property of this class:

Fix the code on the indicated line if the property has been defined in the class.
Define the property in the class if the property has not been defined.

Severity: Warning

For additional information, see Get and Set Methods for Dependent Properties.

`MHERM` —
Parenthesize the multiplication of VAR_NAME and its transpose to ensure the result is Hermitian.

Severity: Warning

`MIPC1` —
Calling the computer function with 'arch' returns 'win64', 'glnxa64', or 'maca64'.

Severity: Warning

The code calls the computer function with an argument (for example computer('arch')). On Windows systems, this returns win32 or win64, but never PCWIN or PCWIN64.

Replace the test with win32 or win64.

`MNUML` —
To create a square matrix, use VAR_NAME(numel(...), numel(...)). Alternatively, use VAR_NAME(size(...)) to create an array with same size as input array.

Severity: Warning

The indicated statement creates a numel(<arg>) by numel(<arg>) array. This is not a common use case and can lead to more memory usage than intended.

Rewrite the code to generate an array of data of the intended size and shape. For example, if the original call is ones(numel(x)), write:

ones(numel(x), 1) to create a vector of ones with the same number of elements as x.
ones(size(x)) to create an array of ones that is the same size as x.
ones(numel(x), numel(x)) to create an array of ones that is numel(x) by numel(x).

Global and persistent variables behave differently in parfor loops than in for loops. Because parfor loops run on many different MATLAB workers simultaneously, there are many different active workspaces and global contexts. Some assignments to global or persistent variables inside parfor loops affect only the value of the variable on the MATLAB client. Some assignments do not affect either the value of the variable on the MATLAB client or the value of the variable on the MATLAB workers.

In other words, the behavior of global and persistent variables within parfor loops can be surprising and using these variables inside parfor loops should be avoided.

Change the program logic to not assign to global or persistent variables inside a parfor (MATLAB Coder) loop. For example, you can do either of the following:

Copy the global or persistent variable to a temporary variable before the parfor loop begins, and then copy it back to the global or persistent variable after the parfor loop ends.
Rewrite the code so that it does not use global or persistent variables.

`PFGV` —
Avoid using GLOBAL variable VAR_NAME in a PARFOR loop.

Severity: Warning

The code uses a global variable in a parfor loop. Because parfor loops run on several different machines simultaneously, the global workspace might not be the same on each machine. Therefore, using a global variable in a parfor loop could have unpredictable or unexpected results.

Make local copies of the global variables that you want to use within the parfor (MATLAB Coder) loop before beginning the parfor loop.

`PFIIN` —
The input variable VAR_NAME should be initialized before the PARFOR loop.

Severity: Warning

It appears that the code uses the indicated variable inside a parfor (MATLAB Coder) loop, but evidently the code does not initialize the variable before the loop. This message can indicate:

A coding problem, because the code should initialize the variable.
Code Analyzer’s inability to determine when the code sets the variables. In this case, Code Analyzer could produce an incorrect message.
For example, Code Analyzer could be unaware of variables set by the load (Instrument Control Toolbox) function.

If the code uses the variable, initialize it (for correctness and efficiency). If the message is incorrect, suppress it as described in Adjust Code Analyzer Message Indicators and Messages.

`PFOUS` —
The output variable VAR_NAME might not be used after the PARFOR loop.

Severity: Warning

The parfor (MATLAB Coder) function computes a variable in a loop body, but that variable is apparently unused after the loop completes. For example, a call to save (Instrument Control Toolbox) or eval might use the variable in such a way that Code Analyzer cannot detect.

If the variable is unnecessary, do not compute it. If it is necessary, use it and suppress the warning message as described in Adjust Code Analyzer Message Indicators and Messages.

`PFRIN` —
The reduction variable VAR_NAME might not be set before the PARFOR loop.

Severity: Warning

The code uses the indicated variable as a reduction variable in the loop, but does not initialize it before the loop. If the variable is not initialized, the result might be undefined. The parfor function supports reductions, which are a kind of parallel construct. Reductions compute a value with contributions from all the iterations (for example, the sum of a vector), but the iterations can still run in an arbitrary order.

Initialize the reduction variable before the parfor (MATLAB Coder) loop starts. For more information, see Reduction Variables (Parallel Computing Toolbox).

`PFRUS` —
The reduction variable VAR_NAME might not be used after the PARFOR loop.

Severity: Warning

The code computes the indicated variable in a parfor loop as a reduction variable, but it appears not to use the reduction variable after the loop. This could be the result of a typographical error in the variable name. However, Code Analyzer can produce this message inappropriately.

See also Reduction Variables (Parallel Computing Toolbox).

Severity: Warning

An assignment statement makes an assignment to multiple values, but the expression on the right side of the assignment does not appear to produce multiple values. For example, code such as the following causes Code Analyzer to display this message:

[m, n] = [1, 2];

[m,n]= A + B;

Code Analyzer can incorrectly produce this message if scalar operators are overloaded. For information on overloading operators, see “Implementing Operators for Your Class.

If Code Analyzer evaluated the situation correctly, correct the code. Otherwise, suppress the message as described in Adjust Code Analyzer Message Indicators and Messages.

`RMFLD` —
RMFIELD output must be assigned back to the structure.

Severity: Warning

`RMWRN` —
The warning with tag VAR_NAME has been removed from MATLAB, so this statement has no effect.

Severity: Warning

`SEPEX` —
Consider using newline, semicolon, or comma before this statement for readability.

Severity: Warning

The indicated token appears to be the beginning of a statement that is not preceded by a separator (a comma, semicolon, or newline). Following conditional expressions inside of if, elseif, and while statements with a separator makes it clear and unambiguous where the expression ends and the next statement begins.

Sometimes, this message arises from a typographical error. For example, if you type:

 if  a ~  b

when you meant to type:

 if  a ~=  b

then MATLAB interprets a as the conditional expression, and ~ b as a statement to execute.

If the indicated token is the beginning of the next statement, precede the statement with a comma, semicolon, or newline character. If the message is the result of a typographical error, then correct it.

`SHOCIRAA` —
Using the VAR_NAME operator in the expression VAR_NAME(A VAR_NAME B) is probably unintended.

Severity: Warning

The indicated statement most likely will result in unexpected behavior. This is because the statements A && B and A || B always either return a logical value or throw an error.

Rewrite the code to perform the logical operation outside of the specified function.

For example, to determine whether the scalars a and b are both nonzero:

a = 1;
b = 2;
a && b

To determine if the arrays A and B each have at least one nonzero element:

A = [1 2 3];
B = [0 0 0];
any(A & B)

To determine whether any of the elements in array A and array B are nonzero:

A = [1 2 3];
B = [0 0 0];
any(A) && any(B)

To determine whether any of the elements in the array A are nonzero, and then determine the logical AND of the result and B:

 A = [1 2 3];
 B = [0 0 0];
any(A) && B

The code compares a character vector to another scalar using either the equal to (==) or not equal to (~=) relational operator. MATLAB software returns an error at run time if the vectors being compared are different lengths.

Use the strcmp function instead of a relational operator or convert the character vector to a string scalar for direct comparison.

Old	Use `strcmp`	Convert to string
function tf = textEqualToFoo(text) tf = 'foo' == text end	function tf = textEqualToFoo(text) tf = strcmp('foo',text) end	function tf = textEqualToFoo(text) tf = "foo" == text end

`STFLD` —
SETFIELD output must be assigned back to the structure.

Severity: Warning

`STISA` —
Consider using ISA instead of comparing the class name.

Severity: Warning

When you use isa, MATLAB returns true if the class name of the first input argument is either the specified class, or a subclass of the specified class. When you use strcmp, MATLAB returns true only if the input arguments match, and therefore subclasses are not considered a match.

If you want a comparison to return true only if the input arguments match, leave your code as is.

If you want a comparison to return true if the class of the first input argument matches, or is a subclass of the specified class, use isa.

For example, change code such as this,

strcmp(class(x),'className');

to this:

isa(x,'className');

`STRNU` —
This variable, apparently a structure, is changed but the value might be unused.

Severity: Warning

Code Analyzer has identified a variable that appears to be a struct. It also appears that this struct variable had one or more fields changed, but the code never uses the variable, nor is the variable returned. This scenario indicates that the assignment to the variable has no effect.

Although Code Analyzer generates this message conservatively, it is possible for Code Analyzer to identify the variable incorrectly as a struct when it actually is an object. It is possible for an assignment to an object property to have side effects that make this assignment appropriate. If the object is a handle object, this usage is not only appropriate, but common.

If the message is appropriate, you can either:

Remove the assignment, if it is not useful
Correct the program so that it either assigns or returns the value

If the message is inappropriate, do one of the following:

Suppress the message for this assignment.
Suppress the message for the entire file.
Suppress this message for all files, if your programming style is such that this message frequently appears inappropriately.

For details, see Adjust Code Analyzer Message Indicators and Messages.

`STRSZ` —
Use STRCMP to compare character vectors that can have different sizes.

Severity: Warning

It appears the code compares two texts of different sizes, which will result in a run-time error. The source of the problem could be a program bug or a typographical error. However, complicated code can result in Code Analyzer generating this message inappropriately.

Change the code, if appropriate. You might consider using the strcmp function along with the strncmp, strfind, or strcmpi, function instead of the current code. Otherwise, suppress the message as described in Adjust Code Analyzer Message Indicators and Messages.

`SUBSASGN` —
Output of 'subsasgn' should be assigned to a variable.

Severity: Warning

`SUBSINDEX` —
Do not overload 'subsindex' for fundamental data types.

Severity: Warning

`TLEV` —
VAR_NAME could be very inefficient unless it is a top-level statement in its function.

Severity: Warning

`TRYNC` —
TRY statement should have a CATCH statement to check for unexpected errors.

Severity: Warning

A try statement appears with no corresponding catch block; therefore, the code will not capture the error. Although this is valid code, it is not recommended, even if you know what the error is or are not concerned with what it is.

Use a catch block and place an identifier after the catch keyword.
When the catch block executes, the identifier is set to an object that contains the message, message ID, and call stack.
Perform error cleanup, if needed.
Use the message ID as an argument to the rethrow function.
Ideally, check the message ID for all errors (including those you want to ignore, so as to avoid masking serious low-level errors).
(For more information see the documentation for rethrow and MException.)

To disregard this suggestion, suppress the warning message, as described in Adjust Code Analyzer Message Indicators and Messages.

`UNONC` —
Assign the onCleanup output argument to a variable. Do not use the tilde operator (~) in place of a variable.

Severity: Warning

Calling onCleanup(@functionhandle) without an output argument can lead to unexpected behavior that is difficult to debug.

Severity: Warning

Chained exponentiation in MATLAB is evaluated from left to right. For example, 2^3^2 is evaluated as (2^3)^2 = 64. This behavior can differ from that of other programming languages, such as Python, where chained exponentiation is evaluated from right to left, as in 2^(3^2) = 512.

Use parentheses to explicitly specify the intended order of evaluation for chained exponents. For example:

Not Recommended	Recommended
x = 2^3^2^3;	x = ((2^3)^2)^3; %Evaluate from left to right
x = 2^3^2^3;	x = 2^(3^(2^3)); %Evaluate from right to left

Unset Variables

`NODEF` —
Variable might be used before it is defined.

Severity: Warning

Code Analyzer returns this message because it appears the code accesses the value of the named variable before it sets that variable. Sometimes, this message results from an error in the code logic or a typographical error. Other times, Code Analyzer generates this message incorrectly because MATLAB has functions, such as load and eval, which can set new variables in the workspace without Code Analyzer detecting it.

This message is incorrect more often than most messages. However, when it is correct, this message reveals problems that might otherwise cause obscure run-time bugs in your program.

If Code Analyzer generated this message as the result of an error in the code, fix the error. Otherwise, if Code Analyzer generated this message incorrectly, do one or more of the following:

Give Code Analyzer (and anyone else reading the program) more information about where the variable gets set.
For example, sometimes initializing the variable can remove the message.
Be explicit about which variables are loaded through a load (Instrument Control Toolbox) command.
Simplify complicated program logic for the benefit of both Code Analyzer and human readers of the program.
Suppress the message as described in Adjust Code Analyzer Message Indicators and Messages.

`PSET` —
Persistent variable is used, but might be unset.

Severity: Warning

`STOUT` —
Function return value might be unset.

Severity: Warning

It appears that the indicated function return value is never set. This message might be incorrect if the code sets variables in ways that Code Analyzer cannot detect, for example, with the load (Instrument Control Toolbox) function.

If the program is incorrect, assign a value to the specified return value, or remove it. If the program is correct, suppress the message, as described in Adjust Code Analyzer Message Indicators and Messages.

`SUSENS` —
Variable is used, but might be unset (within a script).

Severity: Warning

Scripts are used for several different purposes in MATLAB. In some cases, such as for examples, a script is a standalone file that runs by itself. In other cases, scripts are used to initialize variables in functions or other utility tasks. The messages appropriate for one style of script are not always appropriate for the other.

Code Analyzer has found a variable in a script that the script appears to use, but not set. This might represent a problem in a standalone script, but be acceptable in other kinds of scripts. This message is off by default, but can be enabled, as appropriate.

If this message has detected a problem in the script, fix the problem. Otherwise, suppress the message on this line, for the entire script. Or, if you commonly do this kind of coding, leave the message disabled in your default Code Advisor preference settings, as described in Adjust Code Analyzer Message Indicators and Messages.

`SVNODEF` —
Variable might not have a value, because variable definition may not be executed.

Severity: Warning

`USENS` —
Explicitly initialize this variable to avoid a potential uninitialized variable, or use a valid syntax for function call on line VAR_NUMBER.

Severity: Warning

Unused Constructions

`ASGLU` —
Value assigned to variable might be unused. Consider replacing the variable with ~ instead.

Severity: Warning

The code does not appear to use the assignment to the indicated variable. This situation occurs when any of the following are true:

The specified argument value contains a typographical error, causing it to appear unused.
The code does not use all values returned by a function call.
The function requires a specific number of output arguments to execute the wanted behavior.

If the message displays because of a typographical error, fix the error.

If the code must ignore some output argument values, use the tilde operator (~) to replace the unused argument. This tilde operator eliminates unused argument names from your program, and clarifies your intent to ignore the returned values. MATLAB introduced the tilde operator in R2009b; therefore, use it only when running version R2009b or later.

If the message is unwarranted, suppress it, as described in Adjust Code Analyzer Message Indicators and Messages. Consider including a comment in your code explaining the reason for this suppression. For more information, see “Ignoring Selected Outputs or Input Arguments”.

`DEFNU` —
Function might be unused.

Severity: Warning

It appears that the code never uses the indicated local function or nested function because:

There is no obvious call of the function.
The code does not compute a function handle for the function.
The code does not include a character vector containing the name of the function.
If the code had such a character vector, Code Analyzer would not produce this message because it would indicate that the character vector might be passed to feval or a callback.

Code Analyzer can present this message erroneously for several reasons, including:

MATLAB used ways of calling the function that Code Analyzer cannot detect.
Although you intend to call the function eventually, you have not yet written the code that calls it.

If the message is correct, but the situation is temporary, consider placing the function definition within a block comment. This makes your intention clear and is easy to reverse.

If machine-generated files contain stubs or template functions that you must complete to obtain the behavior you want, consider keeping this message enabled as a reminder that you still have work to do.

If the message is wrong, suppress it, as described in Adjust Code Analyzer Message Indicators and Messages.

`EQEFF` —
To assign values to variables, use =. The == operator compares equality of values.

Severity: Warning

`INUSA` —
Input argument might be unused after the function arguments block(s).

Severity: Warning

`INUSD` —
Input argument might be unused. Consider replacing the argument with ~ instead.

Severity: Warning

Code Analyzer detects an input argument to a function or method that the code does not use. This message might result because there is a typographical error in the declaration or the body of the function or method. This message could also result because your code intentionally does not use the specified input argument.

If the message results from a typographical or other error in the function or method definition, correct the error. If you intended to leave the argument unused, replace it in functions and methods with the tilde operator (~). One advantage of using a tilde is that it reduces the number of names in the workspace, making your program easier to inspect and debug. For more information, see “Ignoring Selected Outputs or Input Arguments”.

MATLAB introduces the ability to use a tilde instead of an argument name in R2009b. Therefore, if your program runs in versions of MATLAB before R2009b, do not use the tilde operator. Instead, consider suppressing this message as described in Adjust Code Analyzer Message Indicators and Messages.

`MANU` —
Input argument might be unused. Consider replacing the argument with ~, or make this method Static instead.

Severity: Warning

Code Analyzer detects that the only argument to a class method is unused. In other words, the value that the method returns is independent of the object that calls it. This can happen due to a typographical error in the method body, or it can be the desired behavior. However, it might be appropriate to make the method a static method, so your code can call it when there is no object available.

Do one of the following:

If the code produces this message due to an error in the method definition, fix the definition.
If the definition is correct and you want to make the method static, put the method into a method block with the Static attribute. Then, remove the unused argument.
If you do not want to make the method Static, suppress this message as described in Adjust Code Analyzer Message Indicators and Messages.

For more information, see “Defining a Static Method”.

`MSNE` —
No Code Analyzer check is found for this check ID.

Severity: Info

`MSNU` —
A Code Analyzer message was once suppressed here, but the message is no longer generated.

Severity: Info

Your code contains the message suppression directive, %#ok. If you remove this directive, no Code Analyzer message will appear because one or more of the following are true:

The code was changed such that the message is no longer triggered.
You disabled the message in the Code Analyzer preferences after you added the %#ok directive to your code.
The rules that Code Analyzer follows for generating the message have changed.

Right-click %#ok in your code, and then select Remove the Message Suppression.

`NASGU` —
Value assigned to variable might be unused.

Severity: Warning

The code does not appear to use the assignment to the indicated variable. This situation occurs when any of the following are true:

Another assignment overwrites the value of the variable before an operation uses it.
The specified argument value contains a typographical error, causing it to appear unused.
The code does not use all values returned by a function call.
The function requires a specific number of output arguments to execute the wanted behavior.

Because MATLAB can use variables in unusual ways, Code Analyzer can produce this message inappropriately. For example, Code Analyzer is unable to detect which variables eval and similar functions use.

If a value is unnecessary, delete the assignment.

If the message displays because of a typographical error, fix the error.

`NOEFF` —
The operation or expression VAR_OPERATOR has no evident effect.

Severity: Warning

`NUSED` —
Global or persistent variable might be unused or unset in this function or script.

Severity: Warning

`PREALL` —
The preallocated value assigned to variable might be unused.

Severity: Warning

Preallocation is a valuable tool for code that requires frequent memory reallocation. However, it is best to avoid using preallocated memory for a variable that is unused or whose value is reassigned, such as when you assign it output from another function.

For example, assume a function, fetchData, returns a 100–element row vector, and the output is assigned to a variable with preallocated memory. The code might look like this:

myData = zeros(1,100); % preallocated vector populated with zeros
myData = fetchData();

The fetchData function allocates memory for its output data. Therefore, a successful call to the fetchData function returns a replacement for the preallocated memory. Here, the memory is allocated twice and preallocation has no benefit.

Avoid preallocating memory to a variable that is unused or assigned to the output of another function.

`PUSE` —
Persistent variable might be unused.

Severity: Warning

`SETNU` —
Variable is set, but might be unused.

Severity: Warning

`UNRCH` —
This statement (and possibly following ones) cannot be reached.

Severity: Warning

It appears that MATLAB will never execute the indicated statement. Typically, Code Analyzer displays this message if a statement is:

Preceded by a break, continue, or return call
Preceded by an error, throw, rethrow, or throwAsCaller call
Preceded by an exit or quit call
Inserted between a switch program control statement and the first case keyword
Controlled by a conditional expression that is coded such that it always returns a value of true or always returns a value of false. For example, in the following code, Code Analyzer returns this warning on the d=10 statement because flag in the if statement always returns a value of true:
```
flag = true;
if flag
    d = 11;
 else
    d = 10;
 end
```

Check to see if this is a typographical error or other simple mistake and fix it. If the message is incorrect, suppress it as described in Adjust Code Analyzer Message Indicators and Messages.

`VANUS` —
Input argument 'varargin' might be unused.

Severity: Warning

`VUNUS` —
VAR_OPERATOR produces a value that might be unused.

Severity: Warning

The indicated operator computes a value that is apparently unused. This can happen for a number of reasons, including typographical errors, unmatched parenthesis, or editing errors.

Remove or modify the expression. Place the expression in a comment if you think you will need it later.

Suggested Improvements

`AGRED` —
'arcgridread' is not recommended. With appropriate code changes, use 'readgeoraster' instead.

Severity: Info

Related Documentation: arcgridread (Mapping Toolbox)

Severity: Info

`COMMPAMD` —
'comm.PAMDemodulator' is not recommended. With appropriate code changes, use 'pamdemod' instead.

Severity: Info

Related Documentation: comm.PAMDemodulator (Communications Toolbox)

`COMMPAMM` —
'comm.PAMModulator' is not recommended. With appropriate code changes, use 'pammod' instead.

Severity: Info

Severity: Info

`DBHRRS` —
'sigwin.blackmanharris' is not recommended. With appropriate code changes, use 'blackmanharris' instead.

Severity: Info

`DBLKMN` —
'sigwin.blackman' is not recommended. With appropriate code changes, use 'blackman' instead.

Severity: Info

`DBLKPRC` —
'blkproc' is not recommended. With appropriate code changes, use 'blockproc' instead.

Severity: Info

`DEPNOE` —
'numberofelements' is not recommended. With appropriate code changes, use 'numel' instead.

Severity: Info

`DETIM` —
'etime' is not recommended. With appropriate code changes, use 'datetime' and the minus operator instead.

Severity: Info

Related Documentation: etime

Severity: Info

Severity: Info

Related Documentation: imtransform (Image Processing Toolbox)

`DISEQN` —
'isequalwithequalnans' is not recommended. With appropriate code changes, use 'isequaln' instead.

Severity: Info

Related Documentation: isequalwithequalnans

`DISPLAYPROG` —
Programmatic use of DISPLAY is not recommended. Use DISP or FPRINTF instead.

Severity: Info

`DISSTR` —
'isstr' is not recommended. With appropriate code changes, use 'ischar' instead.

Severity: Info

`DLMWT` —
'dlmwrite' is not recommended. With appropriate code changes, use 'writematrix' instead.

Severity: Info

Related Documentation: dlmwrite

`DMCOV` —
'spectrum.mcov' is not recommended. With appropriate code changes, use 'pmcov' instead.

Severity: Info

Related Documentation: Autoregressive PSD Object to Function Replacement Syntax (Signal Processing Toolbox)

`DMTM` —
'spectrum.mtm' is not recommended. With appropriate code changes, use 'pmtm' instead.

Severity: Info

Related Documentation: Nonparametric Spectrum Object to Function Replacement (Signal Processing Toolbox)

`DMUSIC` —
'spectrum.music' is not recommended. With appropriate code changes, use 'pmusic' instead.

Severity: Info

Related Documentation: Subspace Pseudospectrum Object to Function Replacement Syntax (Signal Processing Toolbox)

`DNLWN` —
'sigwin.nuttallwin' is not recommended. With appropriate code changes, use 'nuttallwin' instead.

Severity: Info

`DNUMLABS` —
'numlabs' is not recommended. Use 'spmdSize' instead, which is a direct replacement.

Severity: Info

`DPNWN` —
'sigwin.parzenwin' is not recommended. With appropriate code changes, use 'parzenwin' instead.

Severity: Info

`DPRDGRM` —
'spectrum.periodogram' is not recommended. With appropriate code changes, use 'periodogram' instead.

Severity: Info

Related Documentation: Nonparametric Spectrum Object to Function Replacement (Signal Processing Toolbox)

`DQUAD` —
'quad' is not recommended. With appropriate code changes, use 'integral' instead.

Severity: Info

Related Documentation: quad

`DQUADL` —
'quadl' is not recommended. With appropriate code changes, use 'integral' instead.

Severity: Info

Related Documentation: quadl

`DQUADV` —
'quadv' is not recommended. With appropriate code changes, use 'integral' instead.

Severity: Info

Related Documentation: quadv

`DRCTWN` —
'sigwin.rectwin' is not recommended. With appropriate code changes, use 'rectwin' instead.

Severity: Info

`DSTRMT` —
'str2mat' is not recommended. With appropriate code changes, use 'char' instead.

Severity: Info

Related Documentation: str2mat

`DSTRRD` —
'strread' is not recommended. With appropriate code changes, use 'textscan' instead.

Severity: Info

Related Documentation: strread

`DSTRVCT` —
'strvcat' is not recommended. With appropriate code changes, use 'char' instead.

Severity: Info

Related Documentation: strvcat

`DSTSTR` —
'setstr' is not recommended. With appropriate code changes, use 'char' instead.

Severity: Info

`DTKYWN` —
'sigwin.tukeywin' is not recommended. With appropriate code changes, use 'tukeywin' instead.

Severity: Info

`DTRIINT` —
'TriScatteredInterp' is not recommended. With appropriate code changes, use 'scatteredInterpolant' instead.

Severity: Info

Related Documentation: TriScatteredInterp

`DTRIQD` —
'triplequad' is not recommended. With appropriate code changes, use 'integral3' instead.

Severity: Info

Related Documentation: triplequad

`DTRIREP` —
'TriRep' is not recommended. With appropriate code changes, use 'triangulation' instead.

Severity: Info

Related Documentation: TriRep

`DTRNG` —
'sigwin.triang' is not recommended. With appropriate code changes, use 'triang' instead.

Severity: Info

`DTSET` —
'dataset' is not recommended. With appropriate code changes, use 'table' instead.

Severity: Info

`DTXTRD` —
'textread' is not recommended. With appropriate code changes, use 'textscan' instead.

Severity: Info

Related Documentation: textread

`DTYLRWN` —
'sigwin.taylorwin' is not recommended. With appropriate code changes, use 'taylorwin' instead.

Severity: Info

`DWELCH` —
'spectrum.welch' is not recommended. With appropriate code changes, use 'pwelch' instead.

Severity: Info

Related Documentation: Nonparametric Spectrum Object to Function Replacement (Signal Processing Toolbox)

`DYULEAR` —
'spectrum.yulear' is not recommended. With appropriate code changes, use 'pyulear' instead.

Severity: Info

Related Documentation: Autoregressive PSD Object to Function Replacement Syntax (Signal Processing Toolbox)

`EMDATE` —
'eomdate' is not recommended. With appropriate code changes, use 'dateshift' with a 'datetime' input instead.

Severity: Info

Severity: Info

Before MATLAB supported try and catch blocks, you could use evalin with two arguments to obtain some of the same functionality. In most cases, try/catch blocks are much faster.

Convert evalin('base' 'foo', 'fclose(fid)') to:

try
  foo
catch ME
  fclose(fid)
end

To match the behavior specified by 'base', the replacement code should be called outside of a function. To match the behavior specified by 'caller', the replacement code should be placed inside the desired function.

For more information and examples, see The try/catch Statement.

`EVLC` —
Using 'evalc' with two arguments is not recommended. Use try/catch statements instead to make code more clear and efficient.

Severity: Info

Before MATLAB supported try and catch blocks, you could use eval and evalc with two arguments to obtain some of the same functionality. In most cases, try/catch blocks are much faster.

Convert eval('foo', 'fclose(fid)') to:

try
  foo
catch ME
  fclose(fid)
end

For more information and examples, see “The try-catch Statement”.

Related Documentation: try

`EZCNTRF` —
EZCONTOURF is not recommended. Use FCONTOUR instead, and set the 'Fill' value to 'on'.

Severity: Info

The fcontour function requires that the input function to plot is a function handle. The ezcontourf function accepted either a function handle or character vector.

For example, use fcontour(@(x,y) sin(x)+cos(y),'Fill','on') instead of ezcontourf('sin(x)+cos(y)').

Related Documentation: ezcontourf

`EZCONTR` —
'ezcontour' is not recommended. With appropriate code changes, use 'fcontour' instead.

Severity: Info

The fcontour function requires that the input function to plot is a function handle. The ezcontour function accepted either a function handle or character vector.

For example, use fcontour(@(x,y) sin(x)+cos(y)) instead of ezcontour('sin(x)+cos(y)').

Related Documentation: ezcontour

Severity: Info

If the expression you are plotting uses the assignment operator (=), the equality relation operator (==), or more than 1 variable, use the fimplicit function instead of ezplot. Otherwise, use fplot instead of ezplot.

Both fplot and fimplicit require that the input function to plot is a function handle. The ezplot function accepted either a function handle or character vector.

For example, use fplot(@(x) sin(x.^2)) instead of ezplot('sin(x^2)') or fimplicit(@(x,y) sin(x)-cos(y)) instead of ezplot('sin(x)=cos(y)').

Related Documentation: ezplot

`EZPLT3` —
'ezplot3' is not recommended. With appropriate code changes, use 'fplot3' instead.

Severity: Info

The fplot3 function requires that the input functions to plot are function handles. The ezplot3 function accepted either function handles or character vectors.

For example, use fplot3(@(t) sin(t),@(t) cos(t),@(t) t) instead of ezplot3('sin(t)','cos(t)','t').

Related Documentation: ezplot3

`EZPOLAR` —
'ezpolar' is not recommended. With appropriate code changes, use 'fpolarplot' instead.

Severity: Info

ezpolar is not recommended. To plot a mathematical expression in polar coordinates, use the fpolarplot function instead.

For additional information, see ezpolar Version History.

Related Documentation: ezpolar

`EZSRFC` —
EZSURFC is not recommended. Use FSURF instead, and set the 'ShowContours' value to 'on'.

Severity: Info

The fsurf function requires that the input functions to plot are function handles. The ezsurfc function accepted either function handles or character vectors.

For example, use fsurf(@(x,y) sin(x)+cos(y),'ShowContours','on') instead of ezsurfc('sin(x)+cos(y)').

Related Documentation: ezsurfc

`EZSURF` —
'ezsurf' is not recommended. With appropriate code changes, use 'fsurf' instead.

Severity: Info

The fsurf function requires that the input functions to plot are function handles. The ezsurf function accepted either function handles or character vectors.

For example, use fsurf(@(x,y) sin(x)+cos(y)) instead of ezsurf('sin(x)+cos(y)').

Related Documentation: ezsurf

`FEATGPID` —
'feature('getpid')' is unsupported and not recommended. With appropriate code changes, use the function 'matlabProcessID' instead.

Severity: Info

`FILEATTRIB` —
'fileattrib' is not recommended. With appropriate code changes, use 'filePermissions' instead.

Severity: Info

`FISADM` —
'addmf' is not recommended. With appropriate code changes, use 'addMF' instead.

Severity: Info

Support for representing fuzzy inference systems as structures will be removed in a future release. Use mamfis (Fuzzy Logic Toolbox) and sugfis (Fuzzy Logic Toolbox) objects with this function instead. To convert existing fuzzy inference system structures to objects, use the convertfis function from R2025a or earlier.

Severity: Info

Severity: Info

Related Documentation: hough (Image Processing Toolbox)

`IM2BW` —
'im2bw' is not recommended. With appropriate code changes, use 'imbinarize' instead.

Severity: Info

`IMELLPS` —
'imellipse' is not recommended. With appropriate code changes, use 'drawellipse' or 'drawcircle' instead.

Severity: Info

Related Documentation: imellipse (Image Processing Toolbox)

`IMFREEH` —
'imfreehand' is not recommended. With appropriate code changes, use 'drawfreehand' instead.

Severity: Info

Related Documentation: imfreehand (Image Processing Toolbox)

`IMGDT` —
Using 'DataAugmentation' in function 'imageInputLayer' is not recommended. Use function 'augmentedImageDatastore' instead.

Severity: Info

`IMLINE` —
'imline' is not recommended. With appropriate code changes, use 'drawline' instead.

Severity: Info

Related Documentation: imline (Image Processing Toolbox)

`IMPNT` —
'impoint' is not recommended. With appropriate code changes, use 'drawpoint' instead.

Severity: Info

Severity: Info

Related Documentation: interp1

`INWVX` —
'instrhwinfo('vxipnp')' is not recommended. With appropriate code changes, use 'ividriverlist' or 'ividevlist' instead.

Severity: Info

`MASSO` —
'MasterSolverOptions' is not recommended. Use 'MainSolverOptions' instead, which is a direct replacement.

Severity: Info

`MATCH2` —
STRMATCH is not recommended. Use STRNCMP or VALIDATESTRING instead.

Severity: Info

strmatch is not recommended. Use strncmp instead.

To find possible partial matches for a character vector, use strncmp or validatestring, depending on your requirements. strncmp returns the numeric index of all array elements that begin with the specified character vector, whereas validatestring returns a single character vector that represents the best match to the specified character vector. To find an exact match for a character vector, use strcmp.

For instance, if your code currently contains lines such as these:

list = {'max', 'minimax', 'maximum', 'max'} 
x = strmatch('max',list)

MATLAB returns the numeric indices of the list array elements that begin with max:

Replace strmatch with one of the following:

validatestring
MATLAB returns the character vector representing the best match, and if multiple or no matches exist, returns an error.
For instance, this code returns a character vector:
```
list = {'max', 'minimax', 'maximum', 'max'}
x = validatestring('max', list)
x =

max
```
strncmp
MATLAB returns a logical array indicating which character vectors match the specified character vector.
For instance, if you specify this code:
```
list = {'max', 'minimax', 'maximum', 'max'}
x = strncmp('max', list, 3)
```
MATLAB returns logical value true (1) to indicate that the first, third, and fourth list elements begin with max and logical value false (0) to indicate that the second list element does not begin with max.
```
x =

     1     0     1     1
```
If you prefer for MATLAB to return the numeric indices of list, use find, as follows:
```
list = {'max', 'minimax', 'maximum', 'max'}
x = find(strncmp(list, 'max', 3))
```

If your input to strmatch is a character matrix, then first convert the matrix to a cell array using cellstr. Then, pass the output from cellstr to strncmp or validatestring. For example, if your code is currently this:

 x = strmatch('max', char('max','minimax', 'maximum', 'max'))

Replace it with this:

list = cellstr(char('max', 'minimax', 'maximum', 'max'))
x = strncmp('max', list, 3)

MATLAB returns:

Related Documentation: strmatch

`MATCH3` —
STRMATCH is not recommended. Use STRCMP instead.

Severity: Info

strmatch is not recommended. Use strncmp instead.

To find exact matches for a character vector, use strcmp. For example, if your code currently contains lines such as these:

list = {'max','minimax','maximum','max'} 
x = strmatch('max',list,'exact')

Then, MATLAB returns the following to indicate that the first and fourth array elements are the only exact matches for max:

Replace the original code with this:

list = {'max','minimax','maximum','max'}
x = strcmp(list,'max')

MATLAB now returns the following logical array. MATLAB returns true (logical 1) to indicate that the first and fourth list elements are max and false (logical 0) to indicate that the second and third list elements are not max.

x =

     1     0     0     1

If you prefer for MATLAB to return the numeric indices of list, use find, as follows:

list = {'max','minimax','maximum','max'}
x = find(strcmp(list,'max'))

Now, MATLAB returns the following to indicate that the first and fourth array elements are the only exact matches for max:

x =

     1     4

To find values that contain a given character vector, rather than those that are an exact match, use strncmp.

`MATDTSET` —
'mat2dataset' is not recommended. With appropriate code changes, use 'array2table' instead.

Severity: Info

Related Documentation: mat2dataset (Statistics and Machine Learning Toolbox)

`MDFCHL` —
'channelList' method of 'mdf' class is not recommended. With appropriate code changes, use 'mdfChannelInfo' function instead.

Severity: Info

For additional information, see Transition Your mdf Object Code (Vehicle Network Toolbox).

Related Documentation: mdfChannelInfo (Vehicle Network Toolbox)

`MXDATE` —
'm2xdate' is not recommended. With appropriate code changes, use 'exceltime' with a 'datetime' input instead.

Severity: Info

Severity: Info

Related Documentation: nargoutchk

`NCHKN` —
NARGCHK is not recommended. Use NARGINCHK without ERROR instead.

Severity: Info

Related Documentation: nargchk

`NCHKO` —
Using NARGCHK with NARGOUT is not recommended. Use NARGOUTCHK instead.

Severity: Info

`PLBL` —
'polybool' is not recommended. With appropriate code changes, use 'polyshape' instead.

Severity: Info

Related Documentation: polybool (Mapping Toolbox)

`PLOTYY` —
'plotyy' is not recommended. With appropriate code changes, use 'yyaxis' instead.

Severity: Info

Related Documentation: plotyy

`PMTMCONF` —
When using PMTM with three output arguments, the 'ConfidenceLevel' input argument is recommended.

Severity: Info

`POLAR` —
'polar' (MATLAB) is not recommended. Use 'polarplot' instead.

Severity: Info

Related Documentation: polar

`PRTOG` —
'-opengl' is not recommended. Use '-image' instead, which is a direct replacement.

Severity: Info

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`PRTPT` —
'-painters' is not recommended. Use '-vector' instead, which is a direct replacement.

Severity: Info

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`PSOPT` —
'psoptimset' is not recommended. With appropriate code changes, use 'optimoptions' instead.

Severity: Info

Related Documentation: psoptimset (Global Optimization Toolbox)

`PYVER` —
'pyversion' is not recommended. With appropriate code changes, use 'pyenv' instead.

Severity: Info

`RAND` —
RAND or RANDN with the 'seed', 'state', or 'twister' inputs is not recommended. Use RNG instead.

Severity: Info

Controlling random number generation using rand or randn is no longer recommended. Use these functions only to generate random numbers and the new rng function to control the generation process.

Update your code using the following table that shows replacements for discouraged syntaxes with an integer seed sd or a time-dependent seed.

Before		After
`rand('twister',sd)`		`rng('default')`
`rand('seed',sd)`		`rng(sd)`
`randn('seed',sd)`		`rng(sd)`
`rand('state',sd)`		`rng(sd)`
`randn('state',sd)`		`rng(sd)`
`rand('seed',sum(100*clock))`		`rng('shuffle')`

For more information including how to reproduce discouraged behavior with the rng function, see Replace Discouraged Syntaxes of rand and randn.

Related Documentation: Replace Discouraged Syntaxes of rand and randn

Severity: Info

Related Documentation: roifill (Image Processing Toolbox)

`ROSE` —
'rose' is not recommended. With appropriate code changes, use 'polarhistogram' instead.

Severity: Info

`SAOPT` —
'saoptimset' is not recommended. With appropriate code changes, use 'optimoptions' instead.

Severity: Info

Related Documentation: saoptimset (Global Optimization Toolbox)

`SETFMT` —
Using set for assigning values of numeric display format is not recommended. With appropriate code changes, use 'settings' object instead.

Severity: Info

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`SETFSP` —
Using set for assigning values of line spacing is not recommended. With appropriate code changes, use 'settings' object instead.

Severity: Info

Severity: Info

In general, use webread instead of urlread. However, the decision to use webread or webwrite depends on the Name-Value arguments in the function call. For example,

Instead of urlread(url,'Get',{name,value},...) use webread(url,name,value).
Instead of urlread(url,'Post',{name,value},...) use webwrite(url,name,value).
Instead of the name-value pair arguments 'Charset', 'Timeout', 'Username', or 'Password' use webwrite with an appropriately configured weboptions object. For example, instead of urlread(url,'Post',{'term','myterm'},'Username','jdoe') use webwrite(url,'term','myterm',weboptions('Username','jdoe')).

`URLWR` —
'urlwrite' is not recommended. With appropriate code changes, use 'websave' instead.

Severity: Info

In general, use websave instead of urlwrite. For example, use websave(name,url) instead of urlwrite(url,name).

However, the decision to use websave or webwrite depends on the Name-Value arguments in the function call. For example,

Instead of urlwrite(url,filename,'Get',{name,value},...) use websave(filename,url,name,value).
Instead of the name-value pair arguments 'Charset', 'Timeout', 'Username', or 'Password' use websave with an appropriately configured weboptions object. For example, instead of urlwrite(url,filename,'Timeout',t) use websave(filename,url,weboptions('Timeout',t)).

Instead of urlwrite(url,filename,'Post',{name1,value1},...) use code similar to the following.

data = webwrite(url,name1,value1,...,weboptions('ContentType',binary)); 
f = fopen(name,'w'); 
fwrite(data); 
fclose(f);

`VEMAT` —
'vec2mat' is not recommended. With appropriate code changes, use 'reshape' instead.

Severity: Info

`VERLESSMATLAB` —
verLessThan('matlab', ...) is not recommended. With appropriate code changes, use 'isMATLABReleaseOlderThan' instead.

Severity: Info

`VERMATLAB` —
ver('matlab') is not recommended. With appropriate code changes, use 'matlabRelease' instead.

Severity: Info

`VIDREAD` —
'NumberOfFrames' is not recommended. Use 'NumFrames' instead.

Severity: Info

`WKNUM` —
'weeknum' is not recommended. With appropriate code changes, use 'week' with a 'datetime' input instead.

Severity: Info

Related Documentation: weeknum

`XFRWSB` —
The 'TransferBaseWorkspaceVariables' option is not recommended for 'batchsim'. With appropriate code changes, consider using project startup scripts or the 'SetupFcn' option instead.

Severity: Info

Related Documentation: parsim (Simulink)

`XFRWSP` —
The 'TransferBaseWorkspaceVariables' option is not recommended for 'parsim'. With appropriate code changes, consider using project startup scripts or the 'SetupFcn' option instead.

Severity: Info

`XLSRD` —
'xlsread' is not recommended. With appropriate code changes, use 'readtable', 'readmatrix' or 'readcell' instead.

Severity: Info

Related Documentation: xlsread

`XLSWT` —
'xlswrite' is not recommended. With appropriate code changes, use 'writematrix' or 'writecell' instead.

Severity: Info

Related Documentation: xlswrite

`XMDATE` —
'x2mdate' is not recommended. With appropriate code changes, use 'datetime(..., "ConvertFrom", "excel")' instead.

Severity: Info

Related Documentation: x2mdate

Readability Improvements

Using sum on a logical expression makes code difficult to read.

To determine the number of true entries, use nnz instead. For example:

Old	Replacement
sum(x == y)	nnz(x == y)

A call to error appears to use sprintf to construct the error message. Because you can call error in numerous ways (with or without error tags, with or without formats and extra arguments, and so on), sometimes Code Analyzer mistakenly produces this message when you use sprintf to produce an error tag or use it as an argument to an existing format specifier.

Remove the sprintf call and pass the format specifier and arguments directly to the error function. For example, replace code such as this:

error('prog:input', ...
sprintf('Cannot open %s because %s\n', ...
filename, reason));

with this code:

error('prog:input', ...
'Cannot open %s because %s\n', ...
filename, reason);

Note that MATLAB converts special characters (such as \n, \t, %s, and %d) in the error message only when you specify more than one input argument with error.

If Code Analyzer produced this message erroneously, you can suppress it, as described in Adjust Code Analyzer Message Indicators and Messages.

`SPRINTFN` —
For readability, consider using the 'newline' function instead of 'sprintf('\\n')'.

Severity: Info

`SPWRN` —
WARNING takes SPRINTF-like arguments directly.

Severity: Info

A call to warning appears to use sprintf to generate the warning message. Because you can call warning in numerous ways (with or without the warning tag, with or without a format specifier), sometimes Code Analyzer mistakenly produces this message when you use sprintf to generate the warning tag or as an argument to the warning format specifier.

Remove the sprintf call and pass the arguments directly to the warning function. For example, replace code such as this:

warning('prog:Nneg', sprintf('Input N=%d must be positive\n',N));

With this code:

warning('progr:Nneg', 'Input N=%d must be positive\n',N);

Note that MATLAB converts special characters (such as \n, \t, %s, and %d) in the warning message only when you specify more than one input argument with warning.

`ALIGN` —
This keyword might not be aligned with its matching END on line VAR_NUMBER.

Severity: Info

A block of code is initiated by a reserved word, but the corresponding end statement for this block does not appear to line up with the opening statement. This message appears only if the end is at least two lines lower than the opening reserved word, and the number of indentation characters is off by more than one. Because Code Analyzer counts a tab character and a single space as one character each, you are likely to see this message if you mix tabs and spaces to indent text. Even though the code appears aligned to you, Code Analyzer interprets it as misaligned.

The most common cause for this message is a missing or extra end statement, which causes the end statements to be paired with the wrong reserved words.

Severity: Info

A statement in a script appears to produce a value that will display when the script runs. Although this is usually a problem in functions, it might be desirable behavior in scripts.

If you do not want the output to display for this statement, then terminate it with a semicolon.

If you want the output to display, suppress this message, as described in Adjust Code Analyzer Message Indicators and Messages. (Code Analyzer generates a different message to notify you of statements in functions that are not terminated with a semicolon—that message is not affected when you suppress this one.)

`NOSEMI` —
Extra semicolon is unnecessary.

Severity: Info

`PRTCAL` —
Add a semicolon after the function call to hide the output.

Severity: Info

Performance Improvements

`AGROW` —
Variable appears to change size on every loop iteration. Consider preallocating for speed.

Severity: Info

The size of the indicated variable or array appears to be changing with each loop iteration. Commonly, this message appears because an array is growing by assignment or concatenation. Growing an array by assignment or concatenation can be expensive. For large arrays, MATLAB must allocate a new block of memory and copy the older array contents to the new array as it makes each assignment. Programs that change a variable's size in this way can spend most of their run time in this inefficient activity.

For the same reasons, there is significant overhead in shrinking an array or in changing the size of a variable on each iteration.

Consider preallocating a variable or array before entering the loop by using zeros, ones, cell, or a similar function. Preallocating avoids the need for MATLAB to copy the data from one array to another inside the loop. For examples of code that do and do not preallocate an array, see “Preallocating Arrays”.

When an array grows by assigning past the end of the array or by using concatenation, preallocation alone does not improve the performance. The code must also use explicit indices.

If you do not know the size of an array before the loop begins, preallocate it, and then if necessary, shrink it after the loop completes.

If any of the following conditions are true, it might be appropriate to suppress this message, as described in Adjust Code Analyzer Message Indicators and Messages:

The loop code contains a conditional block where the array grows. (In this case, it can be reasonable to grow the array only as the loop finds such conditions.)
For each iteration in the loop, the length of the concatenation varies (such as character vectors with variable length). The total size of the array is not calculable before entering the loop.
The array is small and will remain small; therefore, the impact of recopying is also small.
The code preallocates the array, but in a way that Code Analyzer does not recognize.

`AND2` —
When both arguments are numeric scalars, consider replacing & with && for performance.

Severity: Info

`CCAT` —
For improved performance, concatenate cell arrays using [] instead of extracting cell arrays and reconstructing them.

Severity: Info

Code Analyzer has detected a cell array that is constructed, in part, by extracting all the elements from another cell array. This operation can be inefficient, especially if the existing cell array is large. Typically, it is better to concatenate the new elements with the existing cell array.

Replace {A{:} X} with [A(:)' {X}]. Instead of extracting the cell array (A{:}), reshape the cell array into a row vector (A(:)') and then concatenate the two cell arrays.

If A has a single row, you can simplify the replacement even further to [A {X}].

You also might be able to simplify {X}, depending on what kind of expression it is. For example, if {X} is an expression similar to B{J}, then you might be able to replace it with B(J) or B(J)', depending on the shape of B and J.

For more information, see Access Data in Cell Array.

`CCAT1` —
{ A{I} } can usually be replaced by A(I) or A(I)', which can be much faster.

Severity: Info

`CLALL` —
Using 'clear' with the 'all' option usually decreases code performance and is often unnecessary.

Severity: Info

clear all should not be used to clear only workspace variables. In addition to clearing workspace variables, it also clears functions and scripts. Using clear all causes MATLAB to recompile previously cached code, and can decrease performance.

When possible, replace instances of clear all in your code.

To clear one or more specific variables from the current workspace, use clear var1 var2.
To clear all variables from the current workspace, consider using clear variables or clearvars.
To clear all global variables, consider using clear global or clearvars –global.
To clear a function or script, consider clearing only the specific function or script. For example, clear myFun.

For more information, see clear (Instrument Control Toolbox) and clearvars.

`CLCLS` —
Using 'clear' with the 'classes' option will decrease code performance and is often unnecessary.

Severity: Info

clear classes is not recommended. If you modify a class definition, MATLAB automatically updates it. You do not need to clear classes to instantiate objects using the new definition.

In addition to clearing class definitions, clear classes also clears variables, scripts and functions. Using clear classes causes MATLAB to recompile previously cached code, and can decrease performance.

When possible, remove or replace instances of clear classes in your code.

To instantiate an object with an updated class definition, it is not necessary to clear classes.
To clear a particular class, consider clearing only the specific class. For example, clear myClass.

For more information, see Automatic Updates for Modified Classes.

`CLEAR0ARGS` —
Avoid using 'clear' to clear more than necessary, this decreases code performance and is usually unnecessary.

Severity: Info

clear should not be used to clear more than necessary. This decreases code performance and is usually unnecessary.

When possible, replace instances of clear in your code.

To clear one or more specific variables from the current workspace, use clear var1 var2.
To clear all variables from the current workspace, consider using clear variables or clearvars.
To clear all global variables, consider using clear global or clearvars –global.
To clear a function or script, consider clearing only the specific function or script. For example, clear myFun.

For more information, see clear (Instrument Control Toolbox) and clearvars.

`CLFUNC` —
Using 'clear' with the 'functions' option usually decreases code performance and is often unnecessary.

Severity: Info

Use clear functions only if you need to clear all scripts and functions. In addition to clearing scripts and functions, it also clears persistent variables and MEX functions. Using clear functions causes MATLAB to recompile previously cached code, and can decrease performance.

When possible, replace instances of clear functions in your code.

To clear a function or script, consider clearing only the specific function or script. For example, clear myFun.
To clear only all MEX functions, consider using clear mex.

Severity: Info

The sort function supports a 'descend' argument that sorts in descending order. Code Analyzer is indicating a case where this might be useful.

Previously, if you wanted to sort an array in descending order, you had to call the sort function, and then reverse the result by calling the flipud or fliplr function. Now MATLAB supports the 'descend' argument.

Rewrite the expression using the 'descend' argument. For example, if your code currently looks like this, and a is a row vector:

a = fliplr(sort( a ));

consider rewriting it like this:

a = sort(a, 'descend');

`FNDSB` —
For array or cell array, performance can be improved using logical indexing instead of 'find'.

Severity: Info

MATLAB enables you to use logical arrays for indexing elements in both arrays and cell arrays. This code calls find to create an array of indices from a logical vector, when you can probably use the logical vector directly instead. Using logical indexing directly is usually faster because it avoids the work find does when it creates a vector of indices.

Code Analyzer also reports this message when the subscript is an array of indices resulting from a call to find and the indicated subscript is the only use of this array of indices.

To speed up and simplify the program, replace the call to find with logical array indexing. If the logical array is not a vector, the shape of the output could change when you remove (or use Code Analyzer automatic fix feature to remove) the find call. To retain the same output shape, you might need to replace find(L) by L(:) or L(:)'. Even with these changes, it is faster than calling find.

If the argument to find is not a logical array, suppress this message, as described in Adjust Code Analyzer Message Indicators and Messages.

`FREAD` —
FREAD(FID,...,'*char') is more efficient than CHAR(FREAD(...)).

Severity: Info

`GFLD` —
Use dynamic fieldnames with structures instead of GETFIELD.

Severity: Info

For more information, see Generate Field Names from Variables.

`GRIDD` —
Consider replacing GRIDDATA with SCATTEREDINTERPOLANT for better performance.

Severity: Info

`ISCL` —
To improve performance, use 'isscalar' instead of length comparison.

Severity: Info

Use isscalar to check if a variable is scalar to provide improved performance.

Replace comparisons to 1 with direct calls of isscalar.

Old	Replacement
length(x) == 1	isscalar(x)
numel(x) == 1	isscalar(x)

`ISMT` —
Using ISEMPTY is usually faster than comparing LENGTH to 0.

Severity: Info

`LAXES` —
Calling AXES(h) in a loop can be slow. Consider moving the call to AXES outside the loop.

Severity: Info

When you call axes(h) within a loop, MATLAB makes the specified axes the current axes. However, MATLAB also attempts to give focus to the axes and its parent figure with every loop iteration, which slows performance significantly.

If you are calling axes because you have multiple axes and you need to specify in which axes to plot, pass the axes handle as an argument to the plot function instead. For example, replace code such as this:

a1 = subplot(1,2,1)
a2 = subplot(1,2,2);
while 1
    axes(a1)
    plot(rand(3))
    axes(a2)
    plot(rand(3))
    drawnow
end

with this:

a1 = subplot(1,2,1);
a2 = subplot(1,2,2);
while 1
   plot(a1, rand(3))
   plot(a2, rand(3))
   drawnow
end

For more information, see “Judicious Object Creation”.

`MINV` —
INV(A)b can be slower and less accurate than A\\b. Consider using A\\b for INV(A)b or b/A for b*INV(A).

Severity: Info

Code Analyzer has detected a call to inv in a multiplication operation.

For solving a system of linear equations, the inverse of a matrix is primarily of theoretical value. Never use the inverse of a matrix to solve a linear system Ax=b with x=inv(A)*b, because it is slow and inaccurate.

Instead of multiplying by the inverse, use matrix right division (/) or matrix left division (\). That is:

Replace inv(A)*b with A\b
Replace b*inv(A) with b/A

In longer expressions, parentheses might be necessary to preserve the order of operations. For example, replace A*inv(B)*C with A*(B\C).

Frequently, an application needs to solve a series of related linear systems Ax=b, where A does not change, but b does. In this case, use lu, chol, or qr instead of inv, depending on the matrix type.

`MMTC` —
This use of MAT2CELL should probably be replaced by a simpler, faster call to NUM2CELL.

Severity: Info

`MRPBW` —
To use less memory, replace BWLABEL(bw) by LOGICAL(bw) in a call of REGIONPROPS.

Severity: Info

Code Analyzer has found a call of regionprops with a first argument that is a call to bwlabel. In many cases, the argument of bwlabel is a logical matrix, or you can convert it to one. Beginning in MATLAB Version 7.8 (release R2009a), you can pass this logical matrix directly to regionprops without the call to bwlabel. This is faster and uses less space than the previous method.

If bw is a logical matrix, make the indicated change. If bw is not a logical matrix, convert it to a logical matrix, and then pass the converted matrix as the first argument to regionprops.

For example, if bw is a logical matrix, replace:

regionprops(bwlabel(bw), ...)

with:

regionprops(bw, ....)

`MXFND` —
Use FIND with the 'first' or 'last' option.

Severity: Info

The code uses the max or min function on the result of find, which is not as fast as using the find options, first and last.

Remove the call to min or max and pass arguments directly to the find function instead.

For example, replace code such as min(find(A)) with find(A,1).

Similarly, replace max(find(A)) with find(A, 1, 'last').

`N2UNI` —
Instead of using 'native2unicode' with 'fread', specify the character encoding scheme in the call to 'fopen'.

Severity: Info

`OR2` —
When both arguments are numeric scalars, consider replacing | with || for performance.

Severity: Info

`PFBNS` —
The entire array or structure VAR_NAME is a broadcast variable. This might result in unnecessary communication overhead.

Severity: Info

The specified variable appears inside a parfor (MATLAB Coder) loop within different indexing expressions. Because the indices are inconsistent across the uses of the array created by the parfor loop, MATLAB sends the entire array to each worker, resulting in high data communication overhead. For example, the following code elicits this message for c, because there are two different indexing expressions for it:

 c = foo();
 parfor i = 1:N
     a(i) = c(i,1);
     b(i) = c(i,2);
 end

When the indices are the same for all instances of the indexed variable, the variable is classified as sliced, and MATLAB sends only the required elements to the workers for each iteration of the parfor loop.

In some cases, there is no way to avoid this message, and therefore you should suppress it, as described in Adjust Code Analyzer Message Indicators and Messages

However, in most cases, you can use additional variables to avoid this problem. For example, in the following code, x and y are sliced and do not elicit the message. In effect, the temporary variables make it clear to MATLAB which data to ship to the workers:

     c = foo();
     x = c(:,1);
     y = c(:,2);
     parfor i = 1:N
         a(i) = x(i);
         b(i) = y(i);
     end

For more information, see Classification of Variables in parfor-Loops (Parallel Computing Toolbox).

`PSIZE` —
NUMEL(x) is usually faster than PROD(SIZE(x)).

Severity: Info

`RGXP1` —
Using REGEXP(str, pattern, 'ONCE') is faster in this case.

Severity: Info

`RGXPI` —
Using REGEXPI(str, pattern, 'ONCE') is faster in this case.

Severity: Info

`SAGROW` —
Variable appears to change size on every loop iteration (within a script). Consider preallocating for speed.

Severity: Info

Programs that change the size of a variable in this way can spend most of their run time in this inefficient activity. There is also significant overhead in shrinking an array on each iteration or in changing the size of a variable on each iteration. In such cases, MATLAB must reallocate and copy the contents repeatedly.

For scripts, Code Analyzer cannot determine whether the array was preallocated before the script was called. Depending on your use of scripts, you might want to enable or disable this message independently of the related message (with message ID AGROW) that applies to functions and class methods.

When an array grows by assigning past the end of the array or using concatenation, preallocation alone does not improve the performance. The code must use explicit indices also.

Assigning to an array in a script that the caller of the script preallocated provides an opportunity to create bugs that are difficult to detect. If the script is called multiple times, these bugs are particularly difficult to detect. However, there are other uses of scripts where preallocating in this manner is necessary or even desirable. In this case, suppress the message for specific assignments or for the whole script, as described in Adjust Code Analyzer Message Indicators and Messages. It might also be appropriate to suppress this message if any of the following is true:

The loop code is searching for rare or exceptional events (especially if you do not expect it to find any).
In this case, it can be reasonable to grow the array only as the loop code finds such events.
The array is small and will always be small.
In this case, the impact of recopying is also small.
The array was preallocated, but in a way that Code Analyzer does not recognize.

If you do not know the size of an array before the loop begins, preallocate it, and then shrink it, if necessary, after the loop completes.

`SFLD` —
Use dynamic fieldnames with structures instead of SETFIELD.

Severity: Info

For more information, see Generate Field Names from Variables.

`SPRIX` —
This sparse indexing expression is likely to be slow.

Severity: Info

Code Analyzer detects an indexing pattern for a sparse array that is likely to be slow. An assignment that changes the nonzero pattern of a sparse array can cause this error because such assignments result in considerable overhead.

If possible, build sparse arrays using sparse as follows, and do not use indexed assignments (such as C(4) = B) to build them:

Create separate index and value arrays.
Call sparse to assemble the index and value arrays.

If you must use indexed assignments to build sparse arrays, you can optimize performance by first preallocating the sparse array with spalloc.

If the code changes only array elements that are already nonzero, then the overhead is reasonable. Suppress this message as described in Adjust Code Analyzer Message Indicators and Messages.

For more information, see “Constructing Sparse Matrices”.

`ST2NM` —
If you are operating on scalar values, consider using 'str2double' for faster performance.

Severity: Info

str2double cannot evaluate mathematical expressions, such as division or multiplication. For strings containing mathematical expressions use str2num instead.

`STCCS` —
It appears that STRCMPI/STRNCMPI can be replaced by a faster, case sensitive compare.

Severity: Info

`STNCI` —
Use STRNCMPI(str1,str2) instead of using UPPER/LOWER in a call to STRNCMP.

Severity: Info

`STTOK` —
Use one call to 'split' instead of calling 'strtok' in a loop.

Severity: Info

Dividing a string into multiple elements by calling strtok in a while loop can be inefficient, especially if multiple calls to strtok are made. Generally, using one call to split is clearer and faster.

Replace the while loop that includes the call to the strtok function with a single call to the split function. For example, if you have this code that calls the strtok function in a while loop:

while ~isempty(remain)
    [token,remain]=strtok(remain, delimiter);
end

Replace the code with a single call to the split function.

tokens = split(str,delimiter)

`TNMLP` —
Move the toolbox function out of the loop for better performance.

Severity: Info

`TRIM1` —
Use STRTRIM(str) instead of nesting FLIPLR and DEBLANK calls.

Severity: Info

Although you can remove leading and trailing white space using nested fliplr and deblank calls, strtrim results in code that executes much faster and is easier to read.

Convert code such as

fliplr(deblank(fliplr(deblank(str))))

and

deblank(fliplr(deblank(fliplr(str))))

strtrim(str)

`TRIM2` —
Use STRTRIM(str) instead of DEBLANK(STRJUST(str,'left')).

Severity: Info

`TRSRT` —
Transposing the input to 'sort' is often unnecessary.

Severity: Info

It appears you are using the transpose character (') to influence the results of the sort function. Depending on what you are trying to accomplish, this might be inefficient or ineffective.

The sort function with no input arguments sorts the columns of a matrix and the row of a row vector.

If you want to change the order of the input matrix, while maintaining its original shape, do one of the following, depending on the type of array you input to the sort function:

Note

If a variable you pass to the sort function could be matrix or a vector because the variable's size varies, use the syntax suggested for matrix input.

Matrix input
Specify the dimension of the matrix as the second input argument. For instance, in the following example, the variables y and z are identical, but the syntax used to specify z is more efficient.
```
x = [5, 1, 3; 2, 4, 0];
y = sort(x')'
z = sort(x, 2)
```
Vector input
Remove the transpose character ('). For example, if your code looks like this,
```
y = [ 9; 4; 6; 2 ]
sort(y')
```
then replace it with this:
```
y = [ 9; 4; 6; 2 ]
sort(y)
```

`UDIM` —
Instead of using transpose (' or .'), consider using a different DIMENSION input argument to VAR_NAME.

Severity: Info

MATLAB for Code Generation Messages

`FPASE` —
Direct assignment to a possible fixed-point type is not recommended. Use the subscripted assignment syntax 'var(:) =' instead.

Severity: Warning

MATLAB Compiler (Deployment) Messages

`MCABF` —
MCC use of absolute file names is likely to fail.

Severity: Warning

It appears that there is a reference to an absolute file name in a deployed application. Because the application could be running on a system with a file system configuration that is different from yours, the reference is likely to be incorrect.

Rewrite the code to do one of the following:

Use relative file names.
Obtain an absolute file location from the user of the deployed application.
Specify the location of the file relative to the folder that ctfroot returns.
For more information, see the function reference page for ctfroot in the MATLAB Compiler documentation.

`MCCD` —
MCC use of the CD function is problematic.

Severity: Warning

Changing the folder using the cd function affects the MATLAB search path, which in turn can affect which functions get called and how MATLAB performs input and output operations. When deploying the application using any of the following products, the cd function is unlikely to have the effect you expect when it executes in the deployed application:

MATLAB Compiler
MATLAB Compiler SDK

Rewrite the program to avoid using the cd function.

`MCHLP` —
MCC does not permit the HELP function.

Severity: Error

`MCKBD` —
MCC does not permit the KEYBOARD function.

Severity: Error

`MCLL` —
MCC does not allow C++ files to be read directly using LOADLIBRARY.

Severity: Warning

The loadlibrary function generates .m files when the code calls it with C/C++ header files. Because deployed applications cannot access .m files generated by the MATLAB Compiler at runtime, this form of loadlibrary does not work in a deployed application.

Change the code to use the .m file prototype form of loadlibrary.

`MCMFL` —
MCC allows writing .m files, but they cannot be executed by the deployed application.

Severity: Warning

It appears that the application to be deployed is creating or modifying a .m file. Although this is valid, the deployed application cannot execute that file.

If you want a deployed application to execute the .m file it creates or modifies, consider doing one of the following:

Construct a character vector and use the eval function on it.
Use an anonymous function, which enables you to create a simple function without having to create a .m file to reduce the impact of this restriction.
For details, see Anonymous Functions.

`MCMLR` —
MCC use of the MATLABROOT function is problematic.

Severity: Warning

The matlabroot function is rarely appropriate in a deployed application because MATLAB software might not be installed and therefore there is no matlabroot.

Rewrite the program to eliminate the use of matlabroot in the deployed application. Consider using ctfroot instead. For more information, see the function reference page for ctfroot in the MATLAB Compiler documentation.

`MCPRD` —
MCC allows only one argument in the PRINTDLG function.

Severity: Error

The code calls the printdlg function and specifies too few or too many arguments. The MATLAB Compiler allows one argument only.

Either rewrite the program to call printdlg with one argument only, or remove the call to printdlg.

`MCSVP` —
MCC does not permit the SAVEPATH function.

Severity: Error

`MCTBX` —
MCC use of toolbox folder file names is likely to fail.

Severity: Warning

It appears that the application is accessing a file in the toolbox folder. This is likely to fail if the application you are writing is deployed to a system where MATLAB software is not installed.

Rewrite the application code to avoid dependencies on files in the toolbox folder.

System Objects

Severity: Warning

Related Documentation: Update Code for R2019b Changes to Function Precedence Order

`INTRPC` —
'interp1(...,'cubic')' changed in R2020b to perform cubic convolution. To continue using shape-preserving piecewise cubic interpolation, use 'interp1(...,'pchip')' instead.

Severity: Warning

`LEGPVPAIR` —
'legend' has changed and might interpret the name of an argument as a legend property instead of a label. To include a label with the same name as a legend property, specify the labels using a cell array or string array. Refer to the documentation for a list of affected property names.

Severity: Warning

Related Documentation: legend

`LENEMP` —
Passing in text with no characters will omit the object from appearing in the legend. To revert to the old behavior, use a whitespace character instead of text with no characters.

Severity: Warning

Related Documentation: Release Notes for Aerospace Toolbox (Aerospace Toolbox)

`SHVAI` —
Explicitly define shared variables in the parent function before calling the nested function. MATLAB does not share uninitialized variables between a nested function and the parent function.

Severity: Warning

The nested function includes an assignment to this variable, and the variable is not

Listed as an input or output variable in the nested function definition
Listed as an input or output variable in the parent function definition
Assigned a value in the parent function

If there is a function on the path with the same name as the variable, MATLAB interprets the variable in the parent function as a function call. Otherwise, the variable is shared between parent and nested function. This code might result in unintended behavior.

To clarify which behavior you expect, modify your code.

To share the variable between the parent and nested function, assign a value to the variable in the parent function.
To use the function on the path, rename the variable in the nested function if it has the same name as the function.

Related Documentation: Update Code for R2019b Changes to Function Precedence Order

Behavior Changes with Low Reliability Messages

For more information, see MATLAB Release Notes.

Related Documentation: Update Code for R2019b Changes to Function Precedence Order

`PTCLO` —
Changing the axes LineStyleOrder or ColorOrder properties of an existing chart now affects the chart immediately. To revert to the old behavior, set either the axes LineStyleOrderIndex or ColorOrderIndex to any value (such as its current value) before changing LineStyleOrder or ColorOrder.

Severity: Warning

`PTDLO` —
Specifying multiple line styles in the axes LineStyleOrder might result in charts that render differently than in the previous releases. MATLAB uses a new indexing scheme to select colors and line styles. To revert to the old behavior, set either the axes LineStyleOrderIndex or ColorOrderIndex to any value (such as its current value) and call 'hold on' before creating your chart.

Severity: Error

`CFERR` —
Cannot open or read the Code Analyzer settings from file VAR_FILE. Using default settings instead.

Severity: Error

`CFIG` —
The Code Analyzer settings file, VAR_FILE, has an error on line VAR_NUMBER.

Severity: Error

Code Analyzer active settings file syntax is incorrect on the indicated line. For example, a line might begin with a comment character (%), which is not permitted in the active settings file. Code Analyzer ignores misspelled tag names to maintain compatibility from release to release. This message appears only when the active settings file in Code Analyzer preferences:

Was edited or written by hand (rather than by generating it using Code Analyzer preferences).
Includes incorrect syntax.

Correct the syntax on the indicated line. For more information on Code Analyzer preferences, see “Setting Code Analyzer Preferences”.

Modulation Scheme	Before	After
QAM	x = randi([0 63],1,100); y = bin2gray(x,'qam',64); z = qammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = qamdemod(x,64,'bin'); z = gray2bin(y,'qam',64);	x = randi([0 63],1,100); z = qammod(x,64,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = qamdemod(x,64,'gray')
PAM	x = randi([0 63],1,100); y = gray2bin(x,'pam',64); z = pammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pamdemod(x,64,pi/4,'bin'); z = bin2gray(y,'pam',64);	x = randi([0 63],1,100); z = pammod(x,64,pi/4,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pamdemod(x,64,pi/4,'gray')
FSK	x = randi([0 63],1,100); y = gray2bin(x,'fsk',64); z = fskmod(y,64,1,256,256,'cont','bin') x = 2(randn(512,1)+1jrandn(512,1)); y = fskdemod(x,64,1,256,256,'bin'); z = bin2gray(y,'fsk',64)	x = randi([0 63],1,100); z = fskmod(x,64,1,256,256,'cont','gray') x = 2(randn(512,1)+1jrandn(512,1)); z = fskdemod(x,64,1,256,256,'gray');
DPSK	x = randi([0 63],1,100); y = gray2bin(x,'dpsk',64); z = dpskmod(y,64,pi/4,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = dpskdemod(x,64,pi/4,'bin'); z = bin2gray(y,'dpsk',64);	x = randi([0 63],1,100); z = dpskmod(x,64,pi/4,'gray'); x=2(randn(100,1)+1jrandn(100,1)); z = dpskdemod(x,64,pi/4,'gray');
PSK	x=randi([0 63],1,100); y=gray2bin(x,'psk',64); z=pskmod(y,64,0,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pskdemod(x,64,0,'bin'); z = bin2gray(y,'psk',64);	x=randi([0 63],1,100); z=pskmod(x,64,0,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pskdemod(x,64,0,'gray');

Modulation Scheme	Before	After
QAM	x = randi([0 63],1,100); y = bin2gray(x,'qam',64); z = qammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = qamdemod(x,64,'bin'); z = gray2bin(y,'qam',64);	x = randi([0 63],1,100); z = qammod(x,64,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = qamdemod(x,64,'gray')
PAM	x = randi([0 63],1,100); y = gray2bin(x,'pam',64); z = pammod(y,64,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pamdemod(x,64,pi/4,'bin'); z = bin2gray(y,'pam',64);	x = randi([0 63],1,100); z = pammod(x,64,pi/4,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pamdemod(x,64,pi/4,'gray')
FSK	x = randi([0 63],1,100); y = gray2bin(x,'fsk',64); z = fskmod(y,64,1,256,256,'cont','bin') x = 2(randn(512,1)+1jrandn(512,1)); y = fskdemod(x,64,1,256,256,'bin'); z = bin2gray(y,'fsk',64)	x = randi([0 63],1,100); z = fskmod(x,64,1,256,256,'cont','gray') x = 2(randn(512,1)+1jrandn(512,1)); z = fskdemod(x,64,1,256,256,'gray');
DPSK	x = randi([0 63],1,100); y = gray2bin(x,'dpsk',64); z = dpskmod(y,64,pi/4,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = dpskdemod(x,64,pi/4,'bin'); z = bin2gray(y,'dpsk',64);	x = randi([0 63],1,100); z = dpskmod(x,64,pi/4,'gray'); x=2(randn(100,1)+1jrandn(100,1)); z = dpskdemod(x,64,pi/4,'gray');
PSK	x=randi([0 63],1,100); y=gray2bin(x,'psk',64); z=pskmod(y,64,0,'bin'); x = 2(randn(100,1)+1jrandn(100,1)); y = pskdemod(x,64,0,'bin'); z = bin2gray(y,'psk',64);	x=randi([0 63],1,100); z=pskmod(x,64,0,'gray'); x = 2(randn(100,1)+1jrandn(100,1)); z = pskdemod(x,64,0,'gray');

Code Analyzer Checks

Incomplete Analysis

DEEPC — Block comments are nested too deeply.

DEEPN — Functions are nested too deeply.

DEEPS — Statements are nested too deeply.

EOFER — Code analysis did not complete. File contains too many syntax errors.

EOFMI — Invalid syntax at end of file. File is incomplete.

MBIG — Code analysis did not complete. File VAR_FILE is too large.

MDEEP — Parentheses, brackets, and braces are nested too deeply.

MDMCR — Unable to run code analysis. VAR_FILE is a deployed MATLAB file.

MDOTM — Unable to run code analysis. VAR_FILE has an invalid file extension.

MXASET — The file is too complex to analyze. Simplify the code to improve code maintainability. For example, reduce the number of operations in expressions.

NOFIL — Unable to open file VAR_FILE. File is not found.

NOSPC — The file is too complex to analyze. Refactor the code to improve code maintainability. For example, reduce the nesting level of conditions or functions.

QUIT — Code analysis did not complete. Code Analyzer encountered an error.

RDERR — Unable to read file VAR_FILE.

TEXTL — Text is too long for MATLAB to parse.

TMMSG — More than 10,000 Code Analyzer messages were generated, leading to some being deleted.

TMSMS — More than 1,000 parse error messages were generated, leading to some being deleted.

Syntax Errors

BADCH — Invalid text character(s).

BADCT — Unicode explicit directional formatting characters are not supported.

BADFP — Invalid floating-point constant.

BADHBB — Invalid digit in binary literal. Supported binary digits are 0 and 1. Supported type suffixes are u8, u16, u32, u64, and s8, s16, s32, s64.

BADHBBT — Binary literal has too many digits for specified type suffix.

BADHBH — Invalid digit in hexadecimal literal. Supported hexadecimal digits are 0-9 and A-F. Supported type suffixes are u8, u16, u32, u64, and s8, s16, s32, s64.

BADHBHT — Hexadecimal literal has too many digits for specified type suffix.

BADNE — 'Not Equals' is spelled ~= in MATLAB, not !=.

BADNOT — Using ~ to ignore a value is not permitted in this context.

BADNOTLHS — Invalid use of logical not operator (~) on left side of an assignment. To use ~ to ignore function outputs, separate output variables with commas.

BADOT — Use of two dots (..) is an invalid MATLAB construction.

BADSP — Invalid text character(s). The text contains an unsupported non-ASCII whitespace character.

BDFIL — Invalid MATLAB file name. MATLAB file names must start with a letter, contain only letters, numbers, or underscores, and have no more than VAR_NUMBER characters.

BINARYTOOLONG — Binary literal has too many digits.

CLIS — Defining a class in script is not allowed.

CLTWO — Only one class definition is allowed per file, and it must come at the head of the file.

DOUQT — A double quoted string is unterminated.

ENDCT — An END might be missing, possibly matching VAR_RESERVED_WORD.

ENDCT2 — An END might be missing (after line VAR_RESERVED_WORD), possibly matching VAR_NUMBER.

ENDCT3 — An END might be missing (before VAR_RESERVED_WORD on line VAR_NUMBER), possibly matching VAR_RESERVED_WORD.

ENDCT4 — A METHODS block or END might be missing before the function definition. This might be causing additional error messages.

ENDPAR — A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at end of file.

EOLPAR — A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at end of line.

FNDOT — Function name can only contain dots if it is a class method.

FNSWA — Function name must start with alphabetic character.

FVACI — Use of name-value arguments in cell indexing is not supported.

FVACS — Using a character vector or string as a name in name=value syntax is not supported. Remove the quotes around the name.

FVAMI — Name in name-value argument syntax must be a valid MATLAB identifier.

FVNST — Arguments blocks in nested function declarations are not supported.

FVSYN — Invalid function argument syntax at VAR_RESERVED_WORD.

HEXTOOLONG — Hexadecimal literal has too many digits.

INBLK — A block comment is unterminated at the end of the file.

LHROW — The left side of an assignment cannot have multiple rows (';').

MCPLD — Invalid property syntax at VAR_RESERVED_WORD.

NOLHS — Left side of an assignment is empty.

NOPAR — A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at VAR_NAME.

NOPAR2 — A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at VAR_NAME on line VAR_NUMBER.

REDEF — The current use of VAR_NAME is inconsistent with its previous use or definition (line VAR_NUMBER).

RESWD — Invalid use of a reserved word.

SBTMP — Invalid array indexing or function call. Chaining outputs after parenthesis is not supported.

SEMFU — Script file must contain executable code. Remove empty statements to make this file a function file.

SEPEXC — Use comma to separate between input arguments.

SEPEXR — Use a newline, semicolon, or comma before this statement.

SOFOC — Statement outside a class definition is not allowed.

STRIN — A quoted character vector is unterminated.

SYNEND — Invalid use for END operator.

SYNER — Parse error at VAR_RESERVED_WORD: usage might be invalid MATLAB syntax.

TWOCM — A comma cannot immediately follow another comma.

UNSET — Invalid use of VAR_OPERATOR on the left side of an assignment.

VTPOD — Specify validation in the following order: size, then class, then functions.

Language Specification Errors

ATAS — The attribute value is unexpected. Use a single meta-class object or a cell array of meta-class objects.

ATLAB — Attribute 'Input' and 'Output' must not be assigned a value or negated.

ATNAS — Set attribute to a single meta-class object or a cell array of meta-class objects.

ATNPI — Set attribute to 'public', 'private', 'protected', 'immutable', or a cell array of meta-classes instead.

ATNPP — Set attribute to 'public', 'private', 'protected', or a cell array of meta-classes instead.

ATPPI — The attribute value is unexpected. Use 'public', 'private', 'protected', 'immutable', or a cell array of meta-classes instead.

ATPPP — The attribute value is unexpected. Use 'public', 'private', 'protected', or a cell array of meta-classes instead.

ATUNK — Unknown attribute name.

ATVIZE — The 'Visible' attribute is invalid for classes and events. Use the '~Hidden' attribute instead or omit the attribute since 'Hidden' is false by default.

`DEEPC` —
Block comments are nested too deeply.

`DEEPN` —
Functions are nested too deeply.

`DEEPS` —
Statements are nested too deeply.

`EOFER` —
Code analysis did not complete. File contains too many syntax errors.

`EOFMI` —
Invalid syntax at end of file. File is incomplete.

`MBIG` —
Code analysis did not complete. File VAR_FILE is too large.

`MDEEP` —
Parentheses, brackets, and braces are nested too deeply.

`MDMCR` —
Unable to run code analysis. VAR_FILE is a deployed MATLAB file.

`MDOTM` —
Unable to run code analysis. VAR_FILE has an invalid file extension.

`MXASET` —
The file is too complex to analyze. Simplify the code to improve code maintainability. For example, reduce the number of operations in expressions.

`NOFIL` —
Unable to open file VAR_FILE. File is not found.

`NOSPC` —
The file is too complex to analyze. Refactor the code to improve code maintainability. For example, reduce the nesting level of conditions or functions.

`QUIT` —
Code analysis did not complete. Code Analyzer encountered an error.

`RDERR` —
Unable to read file VAR_FILE.

`TEXTL` —
Text is too long for MATLAB to parse.

`TMMSG` —
More than 10,000 Code Analyzer messages were generated, leading to some being deleted.

`TMSMS` —
More than 1,000 parse error messages were generated, leading to some being deleted.

`BADCH` —
Invalid text character(s).

`BADCT` —
Unicode explicit directional formatting characters are not supported.

`BADFP` —
Invalid floating-point constant.

`BADHBB` —
Invalid digit in binary literal. Supported binary digits are 0 and 1. Supported type suffixes are u8, u16, u32, u64, and s8, s16, s32, s64.

`BADHBBT` —
Binary literal has too many digits for specified type suffix.

`BADHBH` —
Invalid digit in hexadecimal literal. Supported hexadecimal digits are 0-9 and A-F. Supported type suffixes are u8, u16, u32, u64, and s8, s16, s32, s64.

`BADHBHT` —
Hexadecimal literal has too many digits for specified type suffix.

`BADNE` —
'Not Equals' is spelled ~= in MATLAB, not !=.

`BADNOT` —
Using ~ to ignore a value is not permitted in this context.

`BADNOTLHS` —
Invalid use of logical not operator (~) on left side of an assignment. To use ~ to ignore function outputs, separate output variables with commas.

`BADOT` —
Use of two dots (..) is an invalid MATLAB construction.

`BADSP` —
Invalid text character(s). The text contains an unsupported non-ASCII whitespace character.

`BDFIL` —
Invalid MATLAB file name. MATLAB file names must start with a letter, contain only letters, numbers, or underscores, and have no more than VAR_NUMBER characters.

`BINARYTOOLONG` —
Binary literal has too many digits.

`CLIS` —
Defining a class in script is not allowed.

`CLTWO` —
Only one class definition is allowed per file, and it must come at the head of the file.

`DOUQT` —
A double quoted string is unterminated.

`ENDCT` —
An END might be missing, possibly matching VAR_RESERVED_WORD.

`ENDCT2` —
An END might be missing (after line VAR_RESERVED_WORD), possibly matching VAR_NUMBER.

`ENDCT3` —
An END might be missing (before VAR_RESERVED_WORD on line VAR_NUMBER), possibly matching VAR_RESERVED_WORD.

`ENDCT4` —
A METHODS block or END might be missing before the function definition. This might be causing additional error messages.

`ENDPAR` —
A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at end of file.

`EOLPAR` —
A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at end of line.

`FNDOT` —
Function name can only contain dots if it is a class method.

`FNSWA` —
Function name must start with alphabetic character.

`FVACI` —
Use of name-value arguments in cell indexing is not supported.

`FVACS` —
Using a character vector or string as a name in name=value syntax is not supported. Remove the quotes around the name.

`FVAMI` —
Name in name-value argument syntax must be a valid MATLAB identifier.

`FVNST` —
Arguments blocks in nested function declarations are not supported.

`FVSYN` —
Invalid function argument syntax at VAR_RESERVED_WORD.

`HEXTOOLONG` —
Hexadecimal literal has too many digits.

`INBLK` —
A block comment is unterminated at the end of the file.

`LHROW` —
The left side of an assignment cannot have multiple rows (';').

`MCPLD` —
Invalid property syntax at VAR_RESERVED_WORD.

`NOLHS` —
Left side of an assignment is empty.

`NOPAR` —
A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at VAR_NAME.

`NOPAR2` —
A VAR_NAME might be missing a closing VAR_NAME, causing invalid syntax at VAR_NAME on line VAR_NUMBER.

`REDEF` —
The current use of VAR_NAME is inconsistent with its previous use or definition (line VAR_NUMBER).

`RESWD` —
Invalid use of a reserved word.

`SBTMP` —
Invalid array indexing or function call. Chaining outputs after parenthesis is not supported.

`SEMFU` —
Script file must contain executable code. Remove empty statements to make this file a function file.

`SEPEXC` —
Use comma to separate between input arguments.

`SEPEXR` —
Use a newline, semicolon, or comma before this statement.

`SOFOC` —
Statement outside a class definition is not allowed.

`STRIN` —
A quoted character vector is unterminated.

`SYNEND` —
Invalid use for END operator.

`SYNER` —
Parse error at VAR_RESERVED_WORD: usage might be invalid MATLAB syntax.

`TWOCM` —
A comma cannot immediately follow another comma.

`UNSET` —
Invalid use of VAR_OPERATOR on the left side of an assignment.

`VTPOD` —
Specify validation in the following order: size, then class, then functions.

`ATAS` —
The attribute value is unexpected. Use a single meta-class object or a cell array of meta-class objects.

`ATLAB` —
Attribute 'Input' and 'Output' must not be assigned a value or negated.

`ATNAS` —
Set attribute to a single meta-class object or a cell array of meta-class objects.

`ATNPI` —
Set attribute to 'public', 'private', 'protected', 'immutable', or a cell array of meta-classes instead.

`ATNPP` —
Set attribute to 'public', 'private', 'protected', or a cell array of meta-classes instead.

`ATPPI` —
The attribute value is unexpected. Use 'public', 'private', 'protected', 'immutable', or a cell array of meta-classes instead.

`ATPPP` —
The attribute value is unexpected. Use 'public', 'private', 'protected', or a cell array of meta-classes instead.

`ATUNK` —
Unknown attribute name.

`ATVIZE` —
The 'Visible' attribute is invalid for classes and events. Use the '~Hidden' attribute instead or omit the attribute since 'Hidden' is false by default.

`BRKFOR` —
BREAK statement can only be used in a FOR or WHILE loop.

`CLANS` —
Using ANS as a class name is not supported.

`CLSAT` —
Specify class attributes before the name of the class.

`CLSUNK` —
This class, or one of its superclasses, could not be found on MATLAB's path.