{"id":5520,"date":"2016-05-17T16:39:04","date_gmt":"2016-05-17T21:39:04","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=5520"},"modified":"2017-04-27T09:39:39","modified_gmt":"2017-04-27T14:39:39","slug":"simulation-data-inspector-inside-parfor","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2016\/05\/17\/simulation-data-inspector-inside-parfor\/","title":{"rendered":"Simulation Data Inspector inside parfor"},"content":{"rendered":"

Last week I presented a few tips to run simulations in parallel<\/a>, and received an interesting comment<\/a> asking how to use the Simulation Data Inspector<\/a> in that context.<\/p>\n

So let's take a look!<\/p>\n

Background<\/strong><\/p>\n

Before getting into details of parfor<\/tt><\/a>, let's first discuss an interesting feature of the Simulation Data Inspector (SDI). In case you were not aware, SDI uses a database file to store the runs it displays. That way, if you close SDI, or even shutdown MATLAB, you do not lose your data.<\/p>\n

In case you did not notice, when you open SDI in a new MATLAB session and the previous session was containing runs, you can see the following in the bottom left corner:<\/p>\n

\"Prior<\/p>\n

If you click on the hyperlink, you will be given the choice to open or discard the prior runs.<\/p>\n

\"Import<\/p>\n

Creating runs in parallel<\/strong><\/p>\n

Since parallel workers are MATLAB sessions without the graphical interface, it is possible to use this prior session data feature to import runs created by the workers.<\/p>\n

Once your model is setup to log data<\/a>, you can do the following:<\/p>\n

Before the parfor<\/tt> loop:<\/p>\n