Store data for any signal except mux or bus signal
Note
The Simulink.Timeseries
class is
supported for backwards compatibility. The ModelDataLogs
format
created Simulink.Timeseries
objects for
signal logging data. Starting in R2016a, you cannot log data in the ModelDataLogs
format.
Signal logging uses the Dataset
format.
In R2016a or later, when you open a model from an earlier release
that had used ModelDataLogs
format, the model simulated
in use Dataset
format.
You can convert signal logging data from ModelDataLogs
to Dataset
format.
Converting to Dataset
format makes it easier
to post-process with other logged data (for example, logged states),
which can also use Dataset
format. For
more information, see Convert Logged Data to Dataset Format.
If you have legacy code that uses the ModelDataLogs
API,
you can encounter situations that require updates to your code or
model. See Migrate Scripts That Use Legacy ModelDataLogs API.
Simulink® software creates instances of this class to store
signal data that it logs for any signal except a mux or bus signal,
which are stored in a Simulink.TsArray
.
See Export Signal Data Using Signal Logging for more
information.
Name | Access | Description |
---|---|---|
|
| Name of this signal log. |
|
| Path of the block that output the signal logged in this signal log. |
|
| Index of the output port that emitted the signal logged in this signal log. |
|
| Name of the signal logged in this signal log. |
|
| Name of the parent of the signal recorded in this log,
if the signal is an element of a mux or a virtual bus; otherwise,
the same as |
|
| An object of |
|
| An array containing the simulation times at which signal data was logged. |
|
| An array containing the signal data. |
Export Signal Data Using Signal Logging, Simulink.TimeInfo
, Simulink.SimulationData.Dataset
, Simulink.ModelDataLogs
, Simulink.SubsysDataLogs
, Simulink.TsArray
, who
, whos
, unpack