You can log simulation data to the workspace, or to a temporary file on disk, for debugging and verification. Data logging lets you analyze how internal block variables change with time during simulation. For example, you might want to see that the pressure in a hydraulic cylinder is above some minimum value or compare it against the pump pressure. If you log simulation data, you can later query, plot, and analyze it without rerunning the simulation.
Simscape™ Results Explorer is an interactive tool that lets you navigate and plot the simulation data logging results. You can use data logging and the Simscape Results Explorer to view simulation results, instead of adding sensors and scopes to your model.
|Save logged simulation data in MLDATX file|
|Create simulation log variable to access data in MLDATX file|
|Plot logged simulation data for Node or Series|
|Plot logged simulation data for one node or series against another|
|(To be removed) Find |
|Find path to node in logged simulation data tree|
|(To be removed) Find path to node in logged simulation data tree|
|Determine whether simulation log is current or stale|
|Open Simscape Results Explorer to interact with logged simulation data|
|Print zero crossing information for logged simulation data|
You can log simulation data to the workspace, or to a temporary file on disk, for debugging and verification.
Using data logging for the whole model is a best practice.
Instead of logging the simulation data for the whole model, you can log data just for the selected blocks.
Additional options for logging and displaying the simulation data.
When you log simulation data, you can stream the data to a temporary file on disk and have the workspace variable point to that temporary file.
Methods of storing logged simulation data for future use and retrieving it at a later time.
Simscape Results Explorer is an interactive tool that lets you navigate and plot the simulation data logging results.
This example shows the basic workflow for logging simulation data for the whole model and then navigating and plotting the logged data using Simscape Results Explorer.
This example shows how you can log and plot simulation data instead of adding sensors to your model.
This example shows how you can access and analyze information on zero crossings during simulation.
This example shows how you can set your model to log simulation data for selected blocks only and how to view simulation data using Simscape Results Explorer.
When you display logged simulation data in Simscape Results Explorer, you can change the
directly on the plot.
This example shows how you can change to a custom unit display of logged simulation data.
This example shows the basic workflow for viewing sparkline plots of logged simulation data for selected blocks and variables directly on the model canvas.
You can use command-line interface to index into an array of components, for example, to get or set operating point targets for a particular array member, or to plot simulation data.