![]() ![]() 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. Now I'll wait for a compiled version before testing it. A useful error message would've saved time trying to diagnose the problem. ![]() Unfortunately, it required the Image Processing Toolbox, which I currently lack. This question was prompted by trying to test a co-workers script early. I hoped for a list of the many toolboxes I have access to. Answers (1) Audio System and DSP share Some specific aspects of Fixed Point Toolbox are shared (in particular double precision and half precision) code generation is shared with a number of tools, such as deploying to Raspberry Pi and Arduino (at least from Simulink) Sign in to answer this question. 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. Backup any files you may need to another directory before performing. 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. Caution Uninstalling the toolbox deletes all files in the MATLAB/toolbox signal directory. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |