{"id":11380,"date":"2022-02-04T15:24:04","date_gmt":"2022-02-04T20:24:04","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=11380"},"modified":"2022-02-25T14:25:04","modified_gmt":"2022-02-25T19:25:04","slug":"leveraging-the-simulink-diagnostics-viewer","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2022\/02\/04\/leveraging-the-simulink-diagnostics-viewer\/","title":{"rendered":"Leveraging The Simulink Diagnostics Viewer"},"content":{"rendered":"
I am sure most Simulink users will agree that viewing and analyzing warnings and errors is an important part of working with Simulink models. When simulating models interactively using the play button, all diagnostics are easily noticeable since they appear in the Diagnostics Viewer as they occur.<\/span><\/div>
On the other hand, many users need to run multiple simulations overnight using the <\/span>sim<\/span><\/a> command, storing the results to MAT-files for future analysis. When doing so, there is no Diagnostics Viewer automatically popping up to inform you that a simulation triggered warnings. This does not mean that you should be ignoring those, even if a warning does not stop a simulation, this is often sign of an actual problem that should be addressed.<\/span><\/div>
In this blog post, I will illustrate how to review warnings from a simulation executed through the sim command, both programmatically and interactively using the <\/span>Diagnostics Viewer<\/span><\/a>.<\/span><\/div>

Accessing Diagnostics Programmatically<\/span><\/h3>
In case you were not aware, all diagnostics are saved in the <\/span>Simulink.SimulationOutput<\/span><\/a> object, as part of the <\/span>simulation metadata<\/span><\/a>. Here is an example of how to access this diagnostic information. First, let's load a SimulationOutput object from a MAT-file:<\/span><\/div>
data = load(<\/span>'mySavedData.mat'<\/span>)<\/span><\/span><\/div>
data = struct with fields:<\/span><\/span><\/div>
out: [1\u00d71 Simulink.SimulationOutput]\r\n<\/div><\/div><\/div><\/div><\/div><\/div>
and check if it contains any warnings:<\/span><\/div>
data.out.SimulationMetadata.ExecutionInfo.WarningDiagnostics<\/span><\/span><\/div>
ans = <\/span>4\u00d71 struct <\/span><\/div>
Fields<\/span><\/th>Diagnostic<\/span><\/th>SimulationPhase<\/span><\/th>SimulationTime<\/span><\/th><\/tr><\/thead>
1<\/span><\/th>1\u00d71 MSLDiagnostic<\/span><\/td>'Execution'<\/span><\/td>0<\/span><\/td><\/tr>
2<\/span><\/th>1\u00d71 MSLDiagnostic<\/span><\/td>'Execution'<\/span><\/td>0<\/span><\/td><\/tr>
3<\/span><\/th>1\u00d71 MSLDiagnostic<\/span><\/td>'Execution'<\/span><\/td>0.4000<\/span><\/td><\/tr>
4<\/span><\/th>1\u00d71 MSLDiagnostic<\/span><\/td>'Execution'<\/span><\/td>0.4000<\/span><\/td><\/tr><\/tbody><\/table><\/div><\/div><\/div><\/div><\/div><\/div>
In this case, we can see that it contains 4 warnings. We can look at the first warning with this line:<\/span><\/div>
data.out.SimulationMetadata.ExecutionInfo.WarningDiagnostics(1).Diagnostic<\/span><\/span><\/div>
ans = <\/span><\/div>
MSLDiagnostic with properties:\r\n\r\n identifier: 'Simulink:DataStores:DSReadBeforeWrite'\r\n message: 'The block 'testMdl\/Data Store Read' is reading from the data store 'testMdl\/Data Store Memory' before any blocks have written to this entire region of memory at time 0.0. For performance reasons, occurrences of this diagnostic for this memory at other simulation time steps will be suppressed.'\r\n paths: {'testMdl\/Data Store Read' 'testMdl\/Data Store Memory'}\r\n cause: {0\u00d71 cell}\r\n stack: [0\u00d71 struct]\r\n<\/div><\/div><\/div><\/div><\/div><\/div>
While this API gives access to all the needed information and allows you to build tooling around it, it can be tedious to type all that to see each warning one by one. <\/span><\/div>

Visualizing Diagnostics in the Diagnostics Viewer<\/span><\/h3>
To help with that, a few releases ago (in R2020b) we added a function to display all the diagnostics stored in a SimulationOutput object in the Simulink Diagnostics Viewer, exactly like if you had clicked play in the canvas: <\/span>sldiagviewer.reportSimulationMetadataDiagnostics<\/span><\/a>.<\/span><\/div>
If the model is closed, the Diagnostics Viewer will launch standalone:<\/span><\/div>
sldiagviewer.reportSimulationMetadataDiagnostics(data.out);<\/span><\/span><\/div><\/div><\/div>
\"\"<\/img><\/div>
If the model is opened, the Diagnostics Viewer will open docked in the model, as if you had simulated the model using the play button from the toolstrip:<\/span><\/div>
open_system(data.out.SimulationMetadata.ModelInfo.ModelName);<\/span><\/span><\/div><\/div>
sldiagviewer.reportSimulationMetadataDiagnostics(data.out);<\/span><\/span><\/div><\/div><\/div>
\"\"<\/img><\/div>

More on the Simulink Diagnostics Viewer<\/span><\/h3>
If you are using the latest version of MATLAB (R2021b), you may have noticed that the Diagnostics Viewer is now docked in the Simulink canvas by default. If you prefer to keep it undocked, there is an option that controls this in the Simulink preferences, or under Diagnostics in the Debug tab:<\/span><\/div>
\"\"<\/img><\/div>
Also, in case you had not noticed, like most panels in the Simulink canvas, the docked Diagnostics Viewer can be moved to the top, bottom, left or right side of the canvas. For example, I often prefer seeing it on the right:<\/span><\/div>
\"\"<\/img><\/div>

Now it's your turn<\/span><\/h3>
I recommend going through the <\/span>Diagnostics<\/span><\/a> section of the documentation for more info on this topic.<\/span><\/div>
In the comments below, I would be curious to hear if you prefer the Diagnostics Viewer docked or undocked, and if docked, where in the canvas you prefer it.<\/span><\/div>\r\n<\/div>