{"id":5,"date":"2008-03-04T22:45:10","date_gmt":"2008-03-05T03:45:10","guid":{"rendered":"https:\/\/blogs.mathworks.com\/seth\/2008\/03\/04\/searching-in-simulink\/"},"modified":"2008-03-28T00:26:13","modified_gmt":"2008-03-28T05:26:13","slug":"searching-in-simulink","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2008\/03\/04\/searching-in-simulink\/","title":{"rendered":"Searching in Simulink"},"content":{"rendered":"
\r\n

Here we have an example library<\/a> consisting of masked subsystems.\r\n <\/p>

sys = 'pidLibrary'<\/span>;\r\nopen_system(sys)<\/pre> 
When you double click on a block, you get the mask dialog, and the Help<\/b> button displays the MaskHelp<\/tt> if you click on it.\r\n   <\/p>\r\n   
 <\/p>\r\n   
Some of these blocks are properly documented, but others have no MaskHelp<\/tt>.  You could click through all the blocks in this library and click on the help button, but that would be a painful manual\r\n      process. How can you audit this library and ensure that the components are properly documented?\r\n   <\/p>\r\n   
find_system<\/b><\/p>\r\n   
find_system<\/tt><\/a> is a very powerful tool for scripting in Simulink which allows you to automate tasks that might otherwise be time-consuming\r\n      to perform.  The find_system<\/tt> syntax is very specific:\r\n   <\/p>
find_system(sys, 'c1', cv1, 'c2', cv2,...'p1', v1, 'p2', v2,...)<\/pre>
find_system<\/tt> takes a set of constraints ('c1', cv1, 'c2', cv2<\/tt><\/i>)  and searches for blocks in the system (sys<\/tt><\/i>) that have the specified parameter values ('p1', v1, 'p2', v2<\/tt><\/i>).  Notice that all constraint\/value pairs are passed to find_system<\/tt> before<\/i> the parameter\/value pairs. This confused me once when I got the order wrong, so watch out for that.\r\n   <\/p>\r\n   
Here is a quick find_system<\/tt> command that returns the right answer.\r\n   <\/p>
blksNoHelp = find_system(sys,'MaskHelp'<\/span>,''<\/span>)\r\nhilite_system(blksNoHelp,'find'<\/span>)<\/pre>
blksNoHelp = \r\n    'pidLibrary\/Continuous PI \r\nController'\r\n    'pidLibrary\/Discrete PI \r\nController'\r\n<\/pre> 
It is important to be aware of the search constraint defaults.<\/p>\r\n   
\r\n      
    \r\n         
  • SearchDepth<\/tt> is set to all levels, but this can be changed to 0 for only open systems, 1 to search only the specified system, 2 for that\r\n            system and its children, etc.\r\n         <\/li>\r\n         
  • LookUnderMasks<\/tt> defaults to graphical<\/tt> only, which means find_system<\/tt> doesn’t look under functional masks (those with a dialog and workspace).\r\n         <\/li>\r\n         
  • FollowLinks<\/tt> defaults to off<\/tt>, which means linked blocks are not searched.  This is very important when the block might reside in a library linked from\r\n            your system.\r\n         <\/li>\r\n         
  • FindAll<\/tt> defaults to off<\/tt>, which means you will only get blocks back from the search.  The other option is to specify on<\/tt> and find_system<\/tt> will also return lines and annotations from the model.\r\n         <\/li>\r\n         
  • CaseSensitive<\/tt> is on<\/tt> by default, so make sure your caps lock isn’t turned on.  This constraint affects the value inputs only; parameters are not\r\n            treated as being case sensitive.\r\n         <\/li>\r\n      <\/ul>\r\n   <\/div>\r\n   
    In our example, if we were also concerned with the contents of those masked blocks, we would need to expand our search to\r\n      LookUnderMasks<\/tt>. This search would then return Simulink base blocks because they do not use MaskHelp<\/tt>.  To reduce the results to only those blocks that are masked, we can do a search where the Mask<\/tt> property is set to on<\/tt>.\r\n   <\/p>
    blksNoHelp2 = find_system(sys,'LookUnderMasks'<\/span>,'all'<\/span>,...<\/span>\r\n                             'Mask'<\/span>,'on'<\/span>,'MaskHelp'<\/span>,''<\/span>)\r\nhilite_system(setdiff(blksNoHelp2,blksNoHelp),'find'<\/span>)<\/pre>
    blksNoHelp2 = \r\n    'pidLibrary\/Continuous PI \r\nController'\r\n    'pidLibrary\/Discrete PI \r\nController'\r\n    'pidLibrary\/Discrete PID \r\nController\/Discrete Derivative'\r\n<\/pre> 
    Another reason constraints are so important is that the amount of work done by find_system<\/tt> is proportional to the number of blocks included in the search.  If you are looking under all masks, following all links\r\n      and searching the full depth of the model hierarchy, the speed of the search will be proportional to the size of your model.\r\n       find_system<\/tt> is not a Simulink Google search that skips across indexed model information. When find_system<\/tt> is called it has to resolve all block parameters as it works. This means that you will evaluate all the dialog code and parameters\r\n      required by the search. To speed up find_system<\/tt>, include the appropriate constraints to reduce the number of blocks being evaluated.\r\n   <\/p>\r\n   
    Tip:<\/b> Where ever possible include a SearchDepth<\/tt> to cast a small net.\r\n   <\/p>\r\n   
    Challenge<\/b><\/p>\r\n   
    This got me thinking about how you might perform the inverse of this search. How would you find blocks that have MaskHelp<\/tt> without specifying the value it is set to?  The first person to provide a correct answer in the comments gains fame and notoriety\r\n      as a find_system<\/tt> expert.\r\n   <\/p>\r\n   
    Did you already know how to use find_system<\/tt>?  This is my second post and I’m looking for feedback on how much experience you have with Simulink. Post a comment and tell\r\n      me what you think.\r\n   <\/p>