-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extract_optical_flow using docker image #266
Comments
I have the same problem with you. |
if you run image with command |
I have the same problem.Does anyone know how to solve it? |
To run optical flow extraction you need the CUDA runtime and a NVIDIA GPU for the Docker. For the latest versions of Docker, you can use the |
hi, I see an invalid device error: OpenCV Error: Gpu API call (invalid device ordinal) in setDevice, file /app/3rd-party/opencv-2.4.13/modules/dynamicuda/include/opencv2/dynamicuda/dynamicuda.hpp, line 658 Aborted (core dumped) @tobiascz did your issue get fixed? I have this system :
So Is this the correct cuda I am installing?-- I am getting an error during cuda install-
Does anyone know how to fix this? |
@yjxiong when i did it with bash scripts/extract_optical_flow.sh ucf-101/ApplyEyeMakeup/ ,it occurs that bash scripts/extract_optical_flow.sh UCF-101/ApplyEyeMakeup/ frame_result/ApplyEyeMakeup/ 2 |
|
2019-09-11 16:51:24,712 FATAL [default] CRASH HANDLED; Application has crashed due to [SIGSEGV] signal Hi, I think mostly this problem is due to the wrong dir or folder . For me, I cannot mkdir in the disk where I put the video folder and frame folder . So I guess the problem happend because the frame folder can't be build or the dir can't be built. I solved it by remove some files. |
Have you solved this problem?I just met the same problem as you. |
when I use the provided docker image to extract the optical_flow images using extract_optical_flow.sh the images are not created.
The OUT_FOLDER gets filled with empty folders matching the structure of the SRC_FOLDER but there are no images in the folders.
in local/errors.log I get the following error messages:
Any ideas?
The text was updated successfully, but these errors were encountered: