![]() ![]() With the exception of the point Walter mentione in his comment (in case the code uses EVAL), this is a save method. license ('inuse') and it will return what products you have used. a trial version) and after running the code execute: Theme. Now I'll wait for a compiled version before testing it. First, you can run code on a machine that has the necessary products (e.g. A useful error message would've saved time trying to diagnose the problem. ![]() Unfortunately, it required the Image Processing Toolbox, which I currently lack. struct2table (toolboxes) ans Name Version Guid. Use struct2table to format this stored information as a readable table. toolboxes 1x2 struct array with fields: Name Version Guid. This question was prompted by trying to test a co-workers script early. Store information about these toolboxes in a variable. I hoped for a list of the many toolboxes I have access to. image_toolbox).įurthermore, when I ran license('inuse'), I only received the following: 'Image Processing Toolbox') to product names (ie. Some quick searching revealed ver product or the license function with the 'test' argument may be useful, but I could not find a mapping of toolbox names (ie. toolboxes Information about installed toolboxesstructure array. How would one check for installed MATLAB toolboxes in a script/function? (checking toolbox versions would also be good!) This could provide a quick and useful error message when someone attempts to run a script without a required toolbox.Ī quick, albeit rough, solution that comes to mind is parsing the text output of the ver command. I know this is a pretty old question, but a really simple answer is actually in the question (parse the output of ver). Tf = all(ismember(requiredToolboxes,installedToolboxes)) īy the way, if you need to check for versions, verLessThan is your friend. Here's an older list of feature strings for various toolboxes taken from a now-defunct newsgroup thread (link is now dead): featureStr = ] = deal(v.Name) A better choice is the license function, which (as you pointed out) requires a unique "feature string" for each toolbox. It's possible to have a toolbox installed and no license to use it (or all the available licenses could be checked out by other users). One drawback to the ver function is that it only tells you what's installed, not what has an available license. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |