amcelroy

Howdy, I wrote OpenCLV (OpenCL for Labview) about a year ago and have decided to make it an Opensource project availible on GitHub. It contains all my C code to compile DLLs, all the Labview code, some pre-compiled x64 DLL code and a pre-built .vip project if you just want to download and install it. https://github.com/amcelroy/OpenCLV.git My email is in the GPL license header in the C code if you find any bugs or have any comments. Austin

Y'all are awesome! That NI white paper was perfect. Merged their solution for determining runtime, Shaun and Jacks's solution for Application Directory.vi for the runtime state and my previous solution for the dev environment state. Thanks so much!

It expects the .dll to be in the same folder as the library (see picture). Perhaps it has something to do with that? The add-on is in the vi.lib virtual folder under Dependencies. The error case displays a pop-up which says that there isn't an OpenCL.dll on the system, which isn't happening. Austin

Hey ShaunR, After adding the DLLs to the project manually and adding them as always include, the DLLs get added to the .exe under the data folder. So one step closer. The program still compiles and runs, but the behavior is the same, i.e. the program doesn't seem to recognize any OpenCL devices, though it does in the dev environment. I've also tried move all the dlls to the same folder as the .exe, no luck there either. My code that is deploying has the option to not pick an OpenCL device, which pops up an error that says no OpenCL device has been configured. This error message is 100% from the add-on, so the add-on has been compiled and is in the .exe. Fortunately the code is deploying to a dev environment where no .exe, but it would be interesting to know if other folks have had similar problems in the past. Austin

Hey ShaunR, A little embarrassing, but my own http://sine.ni.com/nips/cds/view/p/lang/en/nid/211893 Or the latest version at: www.raptorview.net Austin

Hey Jack, Nice to speak with you again! I added the library to the "Always Included" section and that did not work. The build preview definitely doesn't show the add-on library or add-on dll in the Generate Preview pane. As for the linking type, they are just being dragged/dropped from the front panel icons. Thanks for the input, Austin

Howdy, I've written a program in Labview 2012 using a 3rd party add-on and would like to deploy it as an .exe. The .exe seems to build (it even runs!) fine and includes a few custom .dlls written for the project, but the 3rd party add-on doesn't seem to have been added, either the library or the .dll. The project runs perfectly in the development environment. Any hints as to how to overcome this problem? Thanks, Austin

Howdy folks, Just wanted to announce that OpenCLV (OpenCL for LabVIEW) is available on NI's website. The toolkit installs through the VI Package Manager and adds a suite of OpenCL VIs to LabVIEW. There is a lot of documentation and example code to help get new projects started, even if you are an OpenCL rookie! Easily configure multiple OpenCL devices to run in parallel Work with 1D, 2D, and 3D memory and images with OpenCL kernels Use Global, Local, and Private memory for a fully optimized OpenCL experience Packages AMD's OpenCL fast Fourier transform algorithm into easy-to-use VIs Easily work with Intel, AMD, and NVIDIA - both CPU and GPU devices Take advantage of a comprehensive manual and examples This add-on only runs on Labview 2012 x64 and the end user needs to install device appropriate OpenCL SDKs. If you have any feedback or questions, don't hesitate to contact the RaptorView team at support@raptorview.net. http://sine.ni.com/nips/cds/view/p/lang/en/nid/211893

Hey Aristos, The error the dreaded Access Violation exception. Sometimes the VS2010 error handler points to Labview.exe, other times it is some memory address on the stack. The chain of calls is Labview->My Library->OpenCL. Either the problem is un-catchable in the OpenCL library or is exactly as you say: Labview is throwing the error. Either way, the problem doesn't appear to be solvable. I have a huge warning in the user manual and an FAQ on most common causes of this happening in OpenCL, hopefully the trade-off of using OpenCL is enough to overcome the development crashes. Everything is stable (and VERY fast) as long as the kernel is legit. Thanks for taking the time to give a good answer, Austin

Hey guys, I'm developing an OpenCL add-on for Labview and the one issue that is really causing grief are unhandled exceptions in OpenCL kernels. It is really easy for the end user to write an OpenCL kernel that goes outside the bounds of the memory that was allocated in Labview. Unfortunately, there isn't really a way to prevent the user from doing this except warning them in the manual. Accessing memory outside of what is allocated by Labview causes an Unhandled Exception in which causes Labview to just quit. I've tried all sorts of stuff in C/C++: try/catch, __try/__except, enabling SEH exception handling, and trying SetUnhandledExceptionFilter. Does anyone know any tricks that can prevent Labview crashing on an Unhandled Exception? The next option is to write everything in C# and try out the error handling there, but OpenCL doesn't have a verified C# implementation at this point. Thanks, Austin