Using image processing toolbox on other computers

조회 수: 8 (최근 30일)
Michael
Michael 2013년 10월 4일
편집: DGM 2023년 3월 24일
I have the Image Processing toolbox on my computer. If I write a code using some function in that toolbox is there anyway someone without the toolbox can run the code? Or can I make like an executable function, for someone without the toolbox or Matlab can run?

채택된 답변

Image Analyst
Image Analyst 2013년 10월 4일
Yes, if you get the (very expensive) MATLAB Compiler product you can make standalone executables. See the FAQ: http://matlab.wikia.com/wiki/FAQ#MATLAB_Compiler_Toolbox Otherwise if they want to run it from MATLAB without having the toolbox installed , they will not be able to run it. Of course a standalone executable does not require MATLAB or any toolboxes but you will need to install a large "MCR" MATLAB Component Runtime library that has all the base MATLAB functions your app needs included in it, and I believe the toolbox functions are included in your app's exe.
  댓글 수: 6
Sean de Wolski
Sean de Wolski 2017년 5월 5일
Keith, the MCR does indeed contain the Image Processing Toolbox libraries. Are you sure you had a license for IPT available when you did the compilation>
Image Analyst
Image Analyst 2017년 5월 5일
I don't see a problem with our answers. In fact your first point agrees with my answer where I said "MATLAB Component Runtime library that has all the base MATLAB functions your app needs included in it, and I believe the toolbox functions are included in your app's exe."
And for your second point, I compile image processing apps all the time and my users don't have or need "his/her own copies of the required Image Toolbox DLLs on his/her own machine." My users have nothing, no Mathworks products beforehand, and all they install is the MCR and my app and it works fine. They don't need anything else.
If you have problems with Coder, as opposed to the MATLAB Compiler, you'd have to ask the Mathworks. I don't have Coder.

댓글을 달려면 로그인하십시오.

추가 답변 (2개)

Betelhem
Betelhem 2022년 12월 26일
define what image processing toolbox in matlab
  댓글 수: 2
Image Analyst
Image Analyst 2022년 12월 26일
I have absolutely no idea what this Answer means, or how it answers the original question. If you think you have something to add that was not discussed in the other Answer, then please elaborate, because I think your Answer just leaves everyone confused.
DGM
DGM 2022년 12월 27일
This is Image Processing Toolbox:
Here is the documentation root for IPT:

댓글을 달려면 로그인하십시오.


DGM
DGM 2022년 12월 26일
편집: DGM 2023년 3월 24일
I see two questions, the latter of which is well-answered already. Aside from the prospect of compiling standalone executables, there may be things you can do to remove dependency of basic m-code on Image Processing Toolbox. Before we go that far, consider that a number of very common IPT tools have actually been included in the base toolbox since 2013. For example, imshow() and im2double were moved in R2014b; imresize() was moved sometime after R2015b. Also, maybe it's just my skewed perspective, but it seems to me that more users (especially students) have access to IPT than they did 10-15 years ago.
That said, there are a number of user-contributed implementations of basic tools on the File Exchange. It all depends what you're after, though one should be aware that many are themselves not independent of IPT and may need further work.
For the sake of addressing its own IPT dependency, MIMT includes a number of passthrough/fallback wrappers for basic IPT tools. It also includes a number of tools that aren't wrappers, but may suffice to replace some usage of various IPT tools. For example:
These MIMT tools include conditional fallback implementations which will run in the absence of IPT (or in versions prior to the introduction of the corresponding IPT function). These are not generally drop-in replacements for all use-cases, and the fallback code may be slower than the IPT passthrough. Check the documentation and take note of any differences in supported functionality or syntax.
  • adapthisteqFB uses/replaces adapthisteq
  • bwareafiltFB uses/replaces bwareafilt
  • bwdistFB uses/replaces bwdist
  • bwlabelFB uses/replaces bwlabel
  • despeckle uses/replaces bwareaopen (default does both opening and closing)
  • histeqFB uses/replaces histeq
  • hitmiss uses/replaces bwhitmiss
  • imadjustFB uses/replaces imadjust
  • imcast uses/replaces im2double, im2uint8, etc
  • imappmat uses/replaces imapplymatrix (default output class handling differs)
  • imcropFB uses/replaces imcrop
  • imfilterFB uses/replaces imfilter (default edge handling differs)
  • imhistFB uses/replaces imhist
  • imresizeFB uses/replaces imresize
  • imrotateFB uses/replaces imrotate
  • imhistmatchFB uses/replaces imhistmatch
  • imnoiseFB uses/replaces imnoise
  • imsharpenFB uses/replaces imsharpen
  • imshow2 uses/replaces imshow (defaults, view controls, and capabilities differ)
  • morphnhood uses/replaces bwmorph, bwperim, (bwlookup to some extent)
  • morphops uses/replaces imdilate, imopen, imtophat, etc
  • nhfilter uses/replaces medfilt2, stdfilt, rangefilt, (nlfilter to some extent)
  • padarrayFB uses/replaces padarray
  • stretchlimFB uses/replaces stretchlim
These tools don't passthrough to their IPT counterparts, but may fill the same role depending on your needs. For example:
  • edgemap see imgradient, edge
  • replacepixels see imoverlay
  • fkgen see fspecial
  • tonemap see tonemap
  • mono see rgb2gray, im2gray, rgb2lightness
  • imerror see immse, psnr
  • imcheckerboard see checkerboard
  • pickblobs see bwselect
  • splitchans see imsplit
  • iminv see imcomplement
  • imclassrange see getrangefromclass
  • colordiff see deltaE, imcolordiff
  • roifilter see roifilt2
  • flattenbg see imflatfield
  • unsharp see imsharpen
  • immodify see imcontrast
  • imcompare see imfuse, imshowpair
  • rgb2linear see rgb2lin
  • linear2rgb see lin2rgb
  • and other color space conversion tools
There are definitely limitations to this approach. MIMT tools are generally dependent on other MIMT tools, so isolating a subset of MIMT tools to include in your own release is a minor chore. More significantly, several very valuable tools like regionprops(), bwconncomp(), and image registration/transformation tools aren't covered by MIMT or other FEX submissions. While that means that user-submitted implementations can't answer OP's need, they might suffice for simpler cases.

카테고리

Help CenterFile Exchange에서 Image Processing Toolbox에 대해 자세히 알아보기

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by