I was trying to run the codes i have got from codeproject http://www.codeproject.com/Articles/239849/Multiple-face-detection-and-recognition-in-real-ti .The code build fine but during runtime that it is throwing Emgu.CV.CvInvoke Error. And the code stops at the point where i initialize HaarCascade classifier.I did all configurations fine according to the tuitorials given here http://fewtutorials.bravesites.com/entries/announcements/-level-0-emgucv-installation-guide-for-64-bit-windows-users and i have tried other sample code including face detection code.They all work fine.
!C:\Users\sizusuzu\Desktop\Capture.PNG!
Can anyone help me?
I believe you problem lies as per the comments in this link http://www.emgu.com/forum/viewtopic.php?f=4&t=2910
I had same problem after compiling and building installer then running installer on different machine. You really need the OpenCV references as per the link...hope that helps
Related
I'm trying to use LabView to operate a ThorLab CS235CU camera. However, so far I haven't had any success using LabView to operate it, despite searching the provided thorlabs and national instruments documentation and google for an answer all week. I started by trying ThorLab's VIs that came with their software, but anytime I run a script it returns the following error:
Error 1386 has occurred at Invoke Node. In the provided "simple image aquisition" VI, this error occurs at 3 locations (steps 2, 3, and 4) before deleting the rest of the script, if run with execution highlighted. National Instruments has 3 suggested fixes on their website: unblocking DLLs manually, which seems unrealistic given I don't know what is causing this error; running LabView as an administrator, which I had been doing from the beginning and didn't help the issue; and creating a configuration file, which I tried but did not work. I put it in C:\ProgramFiles\National Instruments\LabView 2020 as well as C:\ProgramFiles(x86)\National Instruments\LabView 2020, but the error still occurs. I'm very new to using LabView and couldn't begin to explain why this error is occurring, so anyone that can or knows how to help, please do.
It seems that you didn't set up the ThorLabs driver properly one way or another. Often it is the manufacturer's installer that must be run first (with LabVIEW turned off) and eventually you'll find the according driver/dll wrapper VIs (also referred to as LabVIEW-Driver) in some arcane subdirectory like <Program Files>\ThorLabs\<Product>\Drivers\Labview\...
It might make sense to copy that directory to your myProject\drivers\ Folder and the simple image acquisition.vi to something like myProject\examples and work your way from there. Also make sure you're using LabVIEW 32bit since few third-party drivers come in 64bit.
I've suddenly run into an issue when trying to build and run my app - I need to use AVFoundation and suddenly it's telling me the below message
Could not build module 'AVFoundation'
This comes a long with some other issues such as:
/Library/Frameworks/CoreMIDI.framework/Headers/MIDIDriver.h:390:83: Expected ')'
Which I find odd...
If I remove the import it of course builds and runs just fine.
I have tried several things i.e. adding it to Link Binary with Libraries, clearing derived data, cleaning the project etc etc with no luck.
I'm at a loss with this so any help would be much appreciated.
I'm running Xcode 9 and using CocoaPods - I'm also embedding some swift into my objective C code - something new to me, so could it be related to that perhaps?
Thanks in advance for any help!
I am running opencv 3.0's sample code hog.cpp (from the folder \samples\gpu\hog.cpp) for people detection, using the GPU. (the CPU part crashes for me). The code compiles, but when I run it, it crashes at the line:
gpu_hog->detectMultiScale(gpu_img, found);
Unhandled exception at 0x000007FEDE717A28 (opencv_core300.dll) in
Hog3StandAlone.exe: 0xC0000005: Access violation reading location
0x000002380000013C.
I am using visual studio 2012, Windows 7 Pro 64 bit.
There are quite a few things that can cause such a problem.
The code itself seems "fine".
What I suggest is that you compile the program in Debug mode. Then, run it from Visual Studio. The IDE's debug session should stop at the exact place in which the "access violation" happened. From there, you can have a more precise idea on the origin of the problem.
For example, I got similar problem at line #341
vc >> frame;
because the VideoCapture vc object returned corrupted frames.
Your problem might be similar (or completely different. That's why you should run a debug session in Visual Studio)
I've tried the same sample before and worked without any problems as far as I remember. On the other hand, this access violation is probably due to the fact that your input "gpu_img" is empty or corrupted. Make it sure that you read the frames correctly (you can use imshow function to visually examine) and also you upload it into gpu_img as well. I don't see any other possible explanation.
Could somebody please explain what cob32api does?
I have the task of migrating a batch cobol system from 32 bit Windows to 64 bit Linux. A large number of programs call 'cob32api' which belongs to Net Express. The Linux equivalent to Net Express is Server Express, but I'm not at all clear on what this particular call actually does. There don't appear to be any parameters required. Sadly, there are also no comments explaining what it's for.
Naturally I get an error when I try to build:
Load error : file 'cob32api'
error code: 173, pc=0, call=1, seg=0 173
Called program file not found in drive/directory
Can anybody help me out here?
Thanks in advance.
OK, I tracked down a colleague who has worked on this stuff and knew what it meant. The call to cob32api is required so that the cobol program in question, as well as any sub-modules, can call Windows APIs. This explains why the corresponding library (cob32api.dll) has no Linux equivalent.
The simple solution to my problem: Remove the call altogether.
I hope this helps anybody who runs into a similar problem.
Thanks for the comments.
Additional information:
The removal of the "cob32api" call had consequences for the sub-modules I mentioned. Ther were a number of calls of the form
CALL WINAPI "windows-function-name" ...
These resulted in later compile errors and therefore needed to be replaced.
I tried to use generate unit tests for some parts of code in my project. But all I get is the same error everytime, and the messages offered are'nt very helpful to arrive at a solution. Pex says that the code is not visible to it. But if i add the required classes and their dependencies to another solution, it works fine. Has anyone else faced this issue and found an answer?
I found out the issue. There was a name mismatch between the name of the project and the name of the assembly. Once I fixed these to be the same name, It was visible by Pex. Sorry for the carelessness.