2D CUDA-based bilinear interpolation

While I do agree with Scott, I'll add a few comments to what he said.

It should not be necessary to have a file with the name cudainterp2_help. Instead, just rename that help file cudainterp2.m. Matlab is smart enough that it looks for help in an m-file with the same name, even if the m-file ONLY has help in it. When running the code, it uses the mexed file instead.

One thing that I do like is the author's comment about the limits of this code. I'll conjecture that the problem of crashing on very large problems is due to memory limitations in the GPU (or something like that.) As such, its probably not a bug in this code. But warning the user of known issues is a nice thing to do.

The one thing that I can say about this code is the H1 line, i.e., the first line of help. It should be a simple, concise line, that includes important key words that lookfor will find. In this code, the first line of the help was a long winded thing that went on to tell the user about installation requirements, compilation particulars, etc. Split up that line.

Finally, I see that the zip file contains some unnecessary files. These should be cleaned up before zipping the directory. The gipper utility is a nice one (found on the file exchange, written by Tim Davis) to zip directories while dropping out those files you don't want to include.

John -- Thanks for the tips, I've submitted a version with corrected help and a better zipped version (OS X's archiver .. ).

Hi all!
I did something similar with some improvements.
I also included a test to compare my solution (bilininterp) with cudainterp2 and as you can see here
http://www.mathworks.co.uk/matlabcentral/fileexchange/23795
it is much faster than cudainterp2.