Starting in R2022b, you can no longer load data stored in the
ModelDataLogs format, including data stored in
Simulink.Timeseries, Simulink.TSArray, and
Simulink.SubsysDataLogs objects.
For scripts that simulate a model created in a release earlier than R2016a that uses
ModelDataLogs format for logging, you can convert data stored in the
ModelDataLogs format to the Dataset format.
Converting a model from using ModelDataLogs format to using
Dataset format can require that you modify your existing models and
code in callbacks, functions, scripts, or tests. This table identifies possible issues to
address after converting to Dataset format.
Possible Issue After Conversion to Dataset
Format | Solution |
|---|
Code in existing callbacks, functions, scripts, or tests that used the
ModelDataLogs programmatic interface to access data can
result in an error. | Check for code that uses ModelDataLogs format access
methods. Update that code to use Dataset format access
methods. For example, suppose that existing code includes this
line. Replace
that code with a Dataset access
function. |
Mux block signal names are lost. | The Dataset format treats Mux block
signals as a vector. To identify signals by signal names, replace
Mux blocks with Bus Creator blocks. |
Signal Viewer cannot be used for signal logging. | The software does not log signal logging data in the Signal Viewer.
Use the signal logging output variable to view the logged
data. |
The unpack function generates an error. | The unpack function, which is supported for
Simulink.ModelDataLogs and
Simulink.SubsysDataLogs objects, is not
supported for Simulink.SimulationData.Dataset
objects. For example, suppose the data in mlog has
three fields: x, y, and
z. For ModelDataLogs format data, the
mlog.unpack function creates three variables in the base
workspace. For Dataset format data, the get
function accesses data by name.
|
The ModelDataLogs and Dataset
formats have different naming rules for unnamed signals. | If necessary, add signal names. In
ModelDataLogs format, for an unnamed signal coming from a
block, the software assigns a name in the form
SL_BlockName+<portIndex>, for example,
SL_Gain1. In Dataset format,
elements do not need a name, so the software leaves the signal name
empty. For both ModelDataLogs and
Dataset formats, the software assigns the same name to
unnamed signals that come from Bus Selector blocks. |
Test points in referenced models are not logged. | Consider enabling signal logging for test points in a referenced
model. |
Script uses who or whos
functions. | Consider using find |
