The Modelify Worklist view lists conversion messages that could affect the conversion. It includes messages provided by Atlas, found during the code mapping, and messages provided by Modelify, generated during the conversion process.
Before the initial conversion, you should check whether there are messages reported by Atlas during the mapping process.
For example, suppose that a message is about references to missing code (e.g. missing function definition). You will have to add the missing definitions and then re-map with Atlas so that Modelify can reanalyze the code. To re-map the code, select Atlas from the main menu, then select Re-Map Workspace.
For details about this view refer to Modelify Worklist View.
One category for problems corresponds to Modelify limitations. These are limitations in Modelify that could prevent the user from performing a desired conversion. For example, conversion type cannot be set to Simulink for a function if it contains a loop. This occurs because Modelify does not yet perform the needed control flow and data flow analysis to create the required Simulink blocks.
Another category corresponds to MATLAB limitations. As the term indicates, these are limitations imposed by MATLAB or any of the Simulink/Stateflow toolboxes. For example, a recursive function cannot be converted to Simulink or Stateflow. Even if Modelify can successfully convert to models the functions involved in the recursion, Simulink shows an error message when it detects a model reference cycle.
Conversion limitations found in your projects will be added to the Modelify Worklist view as they are found during conversion. Refer to the Conversion Limitations section for a detailed list of known limitations.