Simulink Editor
You can now access the self-paced, interactive Simulink® Fundamentals course that teaches you to:
Use the Simulink environment.
Model continuous and discrete dynamic systems.
Organize growing models in subsystems that create visual and functional hierarchy.
Componentize models by referencing other models and creating libraries.
Optimize simulation performance.
Simulink Fundamentals uses tasks to teach concepts incrementally, such as through a real-life example with a 3D printer. You receive automated assessments and feedback after submitting tasks. Your progress is saved when you exit the course, so you can complete the course in multiple sessions.
For more information, see Simulink Fundamentals.
The Simulink Start Page now has a Learn tab that provides access to in-product trainings, such as Simulink Onramp and Simulink Fundamentals.
In Simulink Editor panes, a new button to the right of the pane title provides options to undock, minimize, and open help for the pane.
When a pane is not docked to the Simulink Editor, the button provides the option to dock and open help for the pane.
When a pane is minimized, the button provides the option to undock, restore, and open help for the pane.
Simscape™ blocks that have unused space around the block icon and do not have a solid boundary line now get a more compact boundary in block diagrams. This enhancement affects only the block display and enables these improvements:
The signal lines pass near the new compact block boundary, which allows better autorouting of lines.
Icon, badge, annotation, and action bar for the block appears near the compact boundary of the block. The block background color applies only within the compact boundary, which improves readability.
Adjacent blocks align close to each other without overlap, which avoids truncation of content.
For example, see Resistor, Variable Resistor, and Capacitor blocks. The compact boundary improvements do not apply to blocks that have a solid boundary line, for example, PS Ramp and Gear Box blocks.
If you open a model created using a previous version of Simulink in R2022a and the model has compact blocks, then background color for such blocks is applied only within the compact boundary.
If you save a model created in R2022a to a previous version, the compact boundaries will be removed. Adjacent blocks can overlap, background color is applied to the complete block boundary, and signal lines can appear as passing through the block.
You can now highlight nonvirtual blocks that are removed to reduce execution time during model simulation and code generation. To enable this functionality, select the model configuration parameter Block reduction. For more information, see Block reduction.
You can now add State Reader, State Writer, and Parameter Writer blocks to your model directly from the Simulink toolstrip.
To add a State Reader or State Writer block, highlight by
clicking on a block that has a state that the State Reader or State
Writer block can read or write to. On the current block tab of the toolstrip,
click Reader-Writer and select State Reader
Block or State Writer Block from the list. A
State Reader or State Writer block appears on the canvas
with the State owner block parameter set to the block that was
highlighted. The method of adding a State Reader or State
Writer block by right-clicking and dragging a state owner block is no longer
supported starting in R2022a.
Note
Depending on the type of block you highlight, the current block tab of the toolstrip might be labeled with the name of the highlighted block, for example, Constant, or it might be labeled Block.
Similarly, to add a Parameter Writer block, highlight by clicking on a block with a parameter that the Parameter Writer block can write to. Then, on the current block tab of the toolstrip, click Parameter Writer. A Parameter Writer block appears on the canvas with the Parameter owner block parameter set to the block that was highlighted.
If you highlight a block that has both a state that the State Reader or
State Writer block can read or write to and a parameter that the
Parameter Writer block can write to, on the current block tab of the
toolstrip, click Reader-Writer. Select Parameter Writer
Block, State Reader Block, or
State Writer Block from the list.
After you add a State Reader, State Writer, or Parameter Writer block, cut and paste it to move it to the desired location within the model hierarchy.
Starting in R2022a, selecting a primary Variant Connector block, a Parameter Writer block, or a block related to either of them, highlights all blocks that are related to the selected block.
A primary Variant Connector block and all nonprimary Variant Connector blocks with the same Connector Tag as that primary block constitute a set of related blocks.
A Parameter Writer block and the parameter owner block of the value that it writes constitute a set of related blocks.
When a related block is highlighted, blocks in the current model that contain the related block are also highlighted. For example, an Initialize Function block is highlighted when it contains a Parameter Writer block that is related to the selected block.
A custom toolbar menu in the Simulink Editor can now be converted into a toolstrip tab using the slConvertCustomMenus command.
Converting a custom toolbar menu creates a toolstrip tab with a single section, which is populated by the converted menu items from the toolbar menu. List items from the menu are converted into push buttons, and list items with pop-up lists are converted into drop-down buttons.
The toolbar menu is not automatically deleted during the conversion. You can remove it by
commenting out or deleting the corresponding addCustomMenuFcn call in the
sl_customization file.
Any functionality that custom tabs do not support is ignored during the conversion. However, you can edit the generated tab. For more information, see Create Custom Simulink Toolstrip Tabs.
The Model Advisor user interface now includes simplified toolstrip with new features.
Filter Checks - Filters the checks based on their respective result statuses, such as
Failed,Passed,Justified.Justify - Justify the violations. Justifications allow you to add a rationale for violations observed during Model Advisor analysis. For more information, see Justify Violated Blocks from the Model Advisor Check Analysis (Simulink Check).
Fix - Fixes the violations by setting the violated parameter values to recommended values.
Reports - Export Model Advisor analysis reports in HTML, PDF, and DOCX formats.
Manage Configurations - Create, load, restore, and associate configurations in simple workflows.
This table describes the changes to the menu items in the Model Advisor:
| Previous UI Element | New UI Element | Description of the Change |
|---|---|---|
| Run Selected Checks | Run Checks | No change in functionality. Use this button to run selected checks. |
| Settings > (options) | Open > (options) | Some older options are no longer available. Use this button to open or customize Model Advisor Configuration Editor. |
| Generate Report… | Report > (options) | No change in functionality. Use this button to generate the Model Advisor analysis report in HTML format. Use the drop-down option to selectPDF or WORD. |
| Configure Hidden input parameters | Configure input parameters in Model Advisor Configuration Editor | Configure hidden input parameters was
a hyperlink in the check window. In R2022a, you can now click the
Configure input parameters in Model Advisor Configuration
Editor icon ( ). |
| Edit > Send Check IDs to Workspace | Right-click on any check, and select Send Check IDs to Workspace. | Use this option to send check IDs to workspace. |
| Edit > Send Instance IDs to Workspace | Right-click on any check, and select Send Instance IDs to Workspace. | Use this option to send instance IDs to workspace. |
This table describes the navigation options removed from Model Advisor:
| Navigation Options Removed |
|---|
| Settings > Treat as referenced model |
| Settings > Preferences |
| Edit > Reset |
| Switch to Model Advisor Dashboard |
| Run Checks in Background |
| Highlighting check results |
| Highlight exclusion results |
| Highlighting |
For more information, see Run Model Advisor Checks and Review Results (Simulink Check).
Simulation Analysis and Performance
Starting in R2022a, the subplot menu and the context menu for subplots in the Simulation Data Inspector include an option to change the visualization for that subplot. Previously, to change the visualization for a subplot, you could only use the Visualization Gallery in the Simulation Data Inspector.
Changing the visualization for several subplots in the Simulation Data Inspector is also easier. The Visualization Gallery now remains open until you close it, and you can freely position the window within the plot area.
Several visualizations you can use in the Record block and Simulation Data Inspector have enhancements in R2022a:
When you add a trend line to an XY plot, the trend line now has a tooltip that shows:
The series and signals to which the trend line was fitted.
The x- and y-coordinates for the point nearest the pointer.
The trend line equation and R-squared value.
The legend for the XY plot has a tooltip that indicates which run contains the plotted signal data.
Sparklines plots now show tick labels for the time axis only on the last sparkline with a visible time axis. You can control whether tick labels are shown for all sparklines or only the last sparkline using the Visualization Settings.
Maps now show a legend that indicates which signals provide the latitude and longitude data for the plotted route. The legend has a tooltip that indicates which run contains the plotted data.
You can now debug your custom C/C++ code from within Simulink by launching an external debugger and setting breakpoints in your custom code. The following debuggers are supported:
On Windows®, Microsoft® Visual Studio® debugger
On Linux®, GNU® Data Display Debugger (DDD)
On macOS, LLDB Debugger (LLDB)
To launch the external debugger, on the Debug tab of the Simulink toolstrip, in the Breakpoints section, click the arrow to
the right of the Add Breakpoint button. From the menu, select
Set Breakpoints in Custom Code.
For more information, see Debug Custom C/C++ Code.
Component-Based Modeling
In R2022a, the Mask Editor has new capabilities that enable you to perform masking
operations with fewer clicks.
This table lists the new and improved capabilities in Mask Editor.
New and Improved Mask Editor Features
| Feature | Improved or New? |
|---|---|
| Context-based tool strip for easy navigation – The menu options appear based on context. For example, the options for Parameter Constraint, Cross Parameter Constraint, and Port Constraint appear only when you select the Constraint tab. | New |
| Integrated view of initialization code and callback code – You can view the mask initialization code and callback code in a single integrated MATLAB Editor. Previously, the initialization code and callback code were in different locations. The Mask Editor code functionalities are like those in the MATLAB Editor, with some limitations. For example, the autocomplete functionality is supported, but you cannot set a breakpoint in your code. | New |
| Upload image within Mask Editor – You can set an image for the masked block icon within the Mask Editor. | New |
Icon drawing commands – The skeleton for drawing commands appears when you click the commands.
| New |
New Constraint Manager with support for port constraints – Constraint Manager is integrated inside the Mask Editor.
| New |
Copy mask definitions from Simulink library blocks – Search for the desired block and click Copy Mask to import the mask definition from an existing block.
| New |
Enhanced Property Editor for parameters – The new Property Editor allows you to set values for parameters such as Tree, LUT Widget, Tunable Popup, Custom Table, and Text Area. For example, you can use the Property Editor to specify the column properties of a custom table. Previously, you had to set values in text form using delimiters.
| Improved |
Enhanced Parameter Promotion workflow – You can now promote parameters in fewer steps. An integrated view allows you to see all promotable parameters of a block. You can select multiple parameters to promote in the case of many-to-one parameter promotion. For more information, see Promote Block Parameters on a Mask
| Improved |
The Bus Editor loads faster and has an updated interface for creating, modifying, and managing bus objects.
A toolstrip provides easy access to actions.
A Sources pane provides the available object sources.
An interactive table displays editable information about the objects, such as hierarchy and properties.
A Property Inspector pane lets you focus on one object at a time and edit its properties.
For more information, see Bus Editor.
The new Message Triggered Subsystem and Message Polling Subsystem blocks are each a type of conditionally executed subsystem that uses messages as the control signal. The information contained in the messages is accessible inside the subsystem.
A Message Triggered Subsystem block executes whenever a message is available at the control port, independent of block sample time.
A Message Polling Subsystem block pulls messages from a queue periodically based on its sample time and executes only when a message is available.
A Message Triggered Subsystem block can be used to define an independent function at the root level of an export-function model. See Export-Function Models Overview.
For more information about the Message Triggered Subsystem and Message Polling Subsystem blocks, see Message Triggered Subsystem and Using Message Polling and Message Triggered Subsystems.
Starting in R2022a, you can reinitialize the states of the blocks inside a referenced model or subsystem at any time during model simulation. Sending a function-call signal to a reinitialize port of the Model block or the Subsystem block creates a reinitialize event that implicitly initializes the states of all blocks within the Model or Subsystem block.
To add a reinitialize port to a referenced model or a subsystem, place a Reinitialize
Function block inside the referenced model or subsystem. Then, select the
Show model reinitialize ports check box in the Model
block parameters dialog or the Show subsystem reinitialize ports check
box in the Subsystem block parameters dialog. The Model or
Subsystem block displays a reinitialize port, indicated by the 
icon.
By customizing the contents of a Reinitialize Function block, for instance by using State Writer and Parameter Writer blocks, you can configure a reinitialize event to explicitly override specified states in a referenced model or subsystem in addition to implicitly initializing all states in the referenced model or subsystem. See Reinitialize States of Blocks in Subsystem.
A reinitialize event can be used to initialize states of blocks inside nested subsystems or referenced models and to initialize certain types of blocks that are not affected by an Enabled Subsystem block reset.
You can place multiple Reinitialize Function blocks inside a referenced model or subsystem. In this case, Simulink creates a reinitialize port for each Reinitialize Function block, with each port name corresponding to the Event name of the reinitialize event as specified in the Event Listener block inside the Reinitialize Function block.
You can generate code for active and inactive values of variant parameters that have different dimensions. All other attributes, such as data type and complexity, must be the same across all choices of a variant parameter.
When you generate code for variant parameters with different dimensions, with the
activation time of the associated variant control variable object to code compile, Embedded Coder® generates code for active and inactive values of variant parameters.
The code contains variant parameter definitions and an autogenerated dimension
identifier in C preprocessor conditionals #if and
#elif. The C preprocessor conditionals enable you to
conditionally compile the code for a given active value of a variant parameter. You
do not need to regenerate the code every time you change the value of the variant
control variables that are associated with variant parameters. For more information
on conditionally compiling code, see Compile Code Conditionally for all Values of Variant Parameters with Same and Different Dimensions.
Previously, if a variant parameter had values with different dimensions, you could generate code only for the active values. You had to regenerate the code every time you changed the value of the variant control variable before compiling the code.
Consider this model.
In this model, the Gain parameters of the Gain
blocks are set to the variant parameter kv1.
In the MATLAB Command Window, define
kv1as follows.kv1has values with different dimensions, and the variant activation time of the associated variant control variable objectVis set tocode compile. Set the storage class ofkv1with exported data scope to generate a code that reuses the variant parameter values that you specified in the model. You can choose to generate a code that imports variant parameter values and its dimensions from external code prior to code compilation by setting the storage class with imported data scope. For more information, see described in Choose Storage Class for Controlling Data Representation in Generated Code (Embedded Coder). In this example, the storage class of the variant parameters is set toExportedGlobal(Embedded Coder).% exported parameters spec = Simulink.Parameter(); spec.CoderInfo.StorageClass = 'ExportedGlobal'; % variant parameters choice1 = 'V == 1'; choice2 = 'V == 2'; choice3 = 'V == 3'; kv1 = Simulink.VariantVariable('Choices', {choice1, [1, 2, 3, 4], choice2, [1, 2, 3, 4, 5], choice3, [1, 2, 3, 4, 5, 6]},'Specification', 'spec'); % variant control variable V = Simulink.VariantControl('Value', 1, 'ActivationTime', 'code compile');
Generate the code using Embedded Coder. The code that you generate contains the variant parameter definition section that has active and inactive values of
kv1that you specified in the model. The code also contains the dimension identifierkv1_dim0to store the dimensions of variant parameter values across the model.//mVPrmVariableDim.c #if V == 1 real_T kv1[kv1_dim0] = { 1.0, 2.0, 3.0, 4.0 }; #elif V == 2 real_T kv1[kv1_dim0] = { 1.0, 2.0, 3.0, 4.0, 5.0 }; #elif V == 3 real_T kv1[kv1_dim0] = { 1.0, 2.0, 3.0, 4.0, 5.0, 6.0 }; #endif //rtw_variant_dims.h /* Definition for custom storage class: Define */ #if V == 1 #define kv1_dim0 4 #elif V == 2 #define kv1_dim0 5 #elif V == 3 #define kv1_dim0 6 #endifWhen you compile this code, the compiler evaluates the
#ifand#elifconditions to determine the active values and dimension of variant parameters based on the value of the variant control variableVthat you provide as an input to the compiler. If you specify the value ofVas1, the conditionV == 1evaluates totrue, and the values enclosed inV == 1becomes active during code compilation. You can then specify a different value forVand recompile the same code for any other active value ofkv1.
You can specify Simulink.Parameter variables as
values in variant parameters. Using Simulink.Parameter variables
allows you to share values among multiple variant parameters, separate values from
their data types and other properties, and control the appearance, placement,
definition, and declaration of variant parameters values in the generated code.
Simulink.Parameter variables help you to import variant
parameter values from external code at the beginning of code compile,
simulation-loop, and model startup phases of simulation and code generation
workflows based on the activation time you specify. For more information, see Stages to Set Active Choices in Variant Blocks and Variant Parameters. When you
use Simulink.Parameter variables as values in a variant
parameter, corresponding properties of all the Simulink.Parameter
variables must be the same. Only the values of Simulink.Parameter
variables can vary.
Previously, you could specify only numeric values in variant parameters.
Consider this model.
In this model, the Gain parameter of the Gain
block is set to the variant parameter kv.
In the MATLAB Command Window, define
kvas follows.kvhas the two valueskv_hatchbackandkv_sedanofSimulink.Parametertype, and the storage class is set toImportedExtern.% imported parameters kv_hatchback = Simulink.Parameter(3); kv_sedan = Simulink.Parameter(6); kv_hatchback.CoderInfo.StorageClass = 'ImportedExtern'; kv_sedan.CoderInfo.StorageClass = 'ImportedExtern'; % variant parameters kv = Simulink.VariantVariable('Choices', {'V == 1', 'kv_hatchback', 'V == 2', 'kv_sedan'});
Define a variant control variable object
Vwith the value set to1and the activation time setstartup.V = Simulink.VariantControl('Value', 1, 'ActivationTime', 'startup');
Generate the code using Embedded Coder or Simulink Coder™. The code is generated as follows.
//vPrmImported_private.h extern real_T kv_hatchback; extern real_T kv_sedan; //vPrmImported.c void vPrmImported_initialize(void) { if (V == 1) { mVPrmImported_P.kv = kv_hatchback; } else if (V == 2) { mVPrmImported_P.kv = kv_sedan; } }
The initialize function of the generated code is executed at the model startup phase to determine the active value of
kvbased on the variant condition that evaluates totrue. If the conditionV == 1evaluates totrue,kv_hatchbackis active. IfV == 2evaluates totrue,kv_sedanis active. The generated code imports active values from external code at model startup.
For more information, see Reuse Variant Parameter Values from Handwritten Code Using Simulink.Parameter Variables.
The Constraint Manager is now integrated inside the Mask Editor. The workflow for sharing constraints is simplified, and you can specify constraints for the input and output ports of blocks.
In the current shared constraint workflow, the Constraint Manager is opened in a separate window, and you must create a constraint, save it in a MAT file, and associate the file name with the parameter. Now, you can create or load a MAT file, define constraints or modify existing ones, and associate constraints with parameters within the Mask Editor. The Constraint Browser allows you to manage shared constraints.
You can use port constraints to specify constraints on the input and output ports of a masked block. The port attributes are checked against the constraints when you compile the model.
Starting in R2022a, Simulink allows you to explicitly designate a model as an export-function model. See Export-Function Models Overview. Previously, Simulink attempted to determine whether or not a model was an export-function model by analyzing the contents of the model.
After you designate a model as an export-function model, Simulink performs compile-time checks to warn you if the model does not meet export-function model requirements.
Simulink displays a 
badge in the lower-left corner of the canvas to indicate
that a model is designated as an export-function model.
If you load a model that was created and saved in a prior release, Simulink designates the model as an export-function model if the model meets the requirements to be an export-function model. In some cases, you may need to manually designate such a model as an export-function model.
For more information, see Designating an Export-Function Model.
The Simulation Target pane of the Model Configuration Parameters dialog is changed for R2022a. The parameters that pertain to custom code are now together in one section of the dialog, which is organized into three tabs: Code information, Additional source code, and Import settings. Clicking on a tab shows the parameters that are listed under that tab and hides the contents of the other two tabs.
Some of the parameters have new names, and two parameters, Compiler flags and Linker flags, both found on the Code information tab, are new for R2022a.
In the Compiler flags field, you can enter any additional compiler flags to be added to the compiler command line when your custom code is compiled.
In the Linker flags field, you can enter any additional linker flags to be added to the linker command line when your custom code is linked.
The following table lists the parameters in the new Simulation Target pane dialog that have different names or are in different locations as a result of this change.
| Parameter name prior to R2022a | New name in R2022a | New location in R2022a |
|---|---|---|
| Insert custom C code in generated > Header file | Include headers | Code information tab |
| Insert custom C code in generated > Source file | Additional code | Additional source code tab |
| Insert custom C code in generated > Initialize function | Initialize code | Additional source code tab |
| Insert custom C code in generated > Terminate function | Terminate code | Additional source code |
| Additional build information > Source files | Source files | Code information tab |
| Additional build information > Include directories | Include directories | Code information tab |
| Additional build information > Libraries | Libraries | Code information tab |
| Additional build information > Defines | Defines | Code information tab |
| Import custom code | Advanced parameters | |
| Simulate custom code in a separate process | Import settings tab | |
| Enable custom code analysis | Import settings tab | |
| Enable global variables as function interfaces | Import settings tab | |
| Undefined function handling | Import settings tab | |
| Deterministic functions and Specify by function | Import settings tab | |
| Default function array layout and Exception by function | Import settings tab | |
| Reserved names | Advanced parameters |
In R2022a, the numerical compensation user interface has these enhancements:
Right-click access in the menu of the co-simulated component under
Configure Cosimulation Signal CompensationSettings for
Auto,Always, orOffNew user interface to see options and conditions for each port
Numerical Compensation User Interface
For more information, see Numerical Compensation.
In previous releases, these settings were in separate interfaces and you could only programmatically set the numerical compensation.
Project and File Management
Data Management
Block Enhancements
The Lookup Table Editor has a new look and feel.
This graphic is a view of the Lookup Table Editor for the Throttle
Estimation lookup table block in the sldemo_fuelsys
model.
Highlights of the new interface include:
Multiple ways to access the Lookup Table Editor, including from the Simulink Editor toolstrip, MATLAB command line, and lookup table block dialogs.
From within the Lookup Table Editor, the ability to view lookup tables from models loaded in the current MATLAB session.
Visualization and editing of lookup table data in a consistent way similar to Microsoft Excel®, regardless of the data source.
A navigation field that lets you enter the path to models and subsystems that contain lookup table blocks, and lookup table blocks themselves.
Report generation containing lookup table data and surface plots.
For 1-D data, the report generates line plots.
For more than 1-D data, the report generates surface plots, one plot for each 2-D slice of data.
In the tabular area, the Lookup Table Editor contains the same lookup table spreadsheet as is available through the
Simulink.LookupTableproperty dialog box (Edit Lookup Table Data with Lookup Table Spreadsheet).Easy registration of custom lookup table blocks.
Generation of different plots for the data, including line, plot, surface, and contour plots.
Heatmap views for data.
For more information, see Use the Lookup Table Editor.
You can now use the new subplot menu for the Dashboard Scope to:
Show or hide data cursors.
Zoom out by a fixed amount.
Configure the mouse interaction to pan and select or to zoom in time, in y, or in both time and y.
Perform a fit-to-view in time, in y, or in both time and y.
To open the subplot menu on the Dashboard Scope block, select the block then click the three dots that appear when you pause on the plot area.
In previous releases, you accessed these options using the context menu for the Dashboard Scope block.
You can specify an origin on the scale for several blocks in the Customizable Blocks library:
The origin specifies the value on the scale from which the needle moves and the value bar
grows. For example, the origin for this gauge with a scale range from –100 to 100 is set to
0, such that the value bar indicates the value of the connected
signal relative to zero.
By default, the origin is specified as auto, and the value for the
origin is the minimum value for the scale.
The blocks in the Customizable Blocks library have an option to add a foreground image as part of the design for a block. Starting in R2022a, you can rotate, resize, and reposition the foreground image within the block design.
For example, if the foreground image has the wrong orientation when you add it to the
block, click the rotation button 
to rotate the image to the correct orientation in 90
degree increments.
Starting in R2022a, you can view and edit each state for the customizable Lamp block in design mode, and you can modify more aspects of the block appearance for each state. For example, you can now design a lamp that uses a different icon for each state.
By default, the Discrete PID Controller and Discrete PID Controller (2DOF) blocks take the integral gain as input and multiply it by the sample time internally as a part of performing the integration. You can now configure the blocks to accept the integral gain premultiplied with the sample time as an input. Doing so improves the execution time of the generated code. Therefore, when you have limited processing power, enable the Use I*Ts parameter and specify the Integral parameter value as the integral gain multiplied by the controller sample time.
Additionally, if your controller uses an anti-windup mechanism, enhancements to the
clamping method also reduce the execution time of the generated
code.
The floating signal selection feature (
) in the Floating Scope block will be removed in a future release. To connect signals to
your floating scope, use the existing signal selector (
) instead. For more details, see Add Floating Scope Block to Model and Connect Signals.
Connection to Hardware
MATLAB Function Blocks
In R2022a, the Ports and Data Manager has been removed. To manage variables, function call outputs, and input triggers in MATLAB Function blocks, use the Symbols pane and the Property Inspector.
For more information on managing variables, function call outputs, and input triggers with the Symbols pane and Property Inspector, see Create and Define MATLAB Function Block Variables, Manage Function Call Outputs of a MATLAB Function Block, and Manage the Input Trigger of a MATLAB Function Block.
In R2022a, the Code Generation Readiness Tool has a new user interface, more information, additional functionality, and improved navigation. In addition, you can now use the Code Generation Readiness Tool in MATLAB Online™.
In addition to the existing functionalities, you can now:
View your MATLAB code inside the Code Generation Readiness Tool. When you select an issue, the part of your MATLAB code that caused this issue gets highlighted.
Group the readiness results either by issue or by file.
Select the language that the code generation readiness analysis uses.
Refresh the code generation readiness analysis if you updated your MATLAB code.
See Check Code Using the Code Generation Readiness Tool and coder.screener.