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. Developers can integrate this function into their scripts to quickly verify that users have the required toolboxes to run their scripts and if not, warn users. This question was prompted by trying to test a co-workers script early. MATLAB function to check whether native toolboxes have licenses available and are installed. 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. 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). Within my code, Id like to check if the end-users have fsolve in their installation and if not, use fzero. Another way to get that information is depfun - this will give you the files your function depends on. As you can see in the link I've posted, the required toolboxes are listed towards the end. Tf = all(ismember(requiredToolboxes,installedToolboxes)) īy the way, if you need to check for versions, verLessThan is your friend. I am writings some code that I wish to distribute open source. 1 Answer Sorted by: 7 I see two questions What toolboxes are required for the function I want to send You need to generate a Dependency Report. 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 |