-
Notifications
You must be signed in to change notification settings - Fork 88
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
Segmentation fault when run demo and some fix #9
Comments
We just created an official docker for DPVO with instructions on how to set it up: https://github.com/princeton-vl/DPVO_Docker Hopefully this will be much easier; if you run into problems with the docker please follow up and I will try my best to help. |
Hello , thanks for the great repo! I have the same issue when using the docker file. Although i'm not sure it is the same causes because it refers to some XDG_RUNTIME_DIR.
EDIT: I change in the docker file the the repo link to the one from @dicarne and it worked. https://github.com/dicarne/DPVO Thank you very much both of you! |
Hi, I face the same issue while I use the docker env from the author. Have you solved it? |
`(dpvo) root@ubuntu:/home/code/DPVO# pip install . × python setup.py bdist_wheel did not run successfully.
note: This error originates from a subprocess, and is likely not a problem with pip. |
@dicarne I have changed the file, how can I rebuild it? |
It's been a while since I remember clearly, but I should have executed |
OS:
ubuntu 20.04LTS
Gcc and g++:
10.3.0
Conda environment: same as
environment.yml
Cudnn:
8.3.2
Driver Version:
510.47.03
CUDA Version:
11.6
After installing the dependencies and downloading the model according to the README, run the README
demo command, and it run failed. Without and error message.
I found some method to fix it:
in
DPViewer/dpviewer/viewer.cpp
and
Then I can run without error(sometimes).
And I found the following change will be helpful, before the change, there was a certain probability of segmentation fault, after the change, no more segmentation fault. Presumably this is due to pointer initialization.
Since I commented out the code to calculate the
transformMatrix
, the camera will not be updated.And I found that whenever I called the calculated code in the loop of this thread, it would definitely error out. Therefore, I create a member function specifically for calculating and updating the
transformMatrix
in main thread.New update
transformMatrix
function (Don't forget to write the function definition and mutex definition):Lock when render thread draw points and poses:
Call it in python:
Now, in the visualization view, the camera can render the pose normally.
But I observed that point cloud data was used, but my visualization view only had the camera pose and video, not any points.
I'm not very familiar with gl programming, so just a simple replace of the render point function.
Finally, I can now run the visualization interface properly on my computer and update the poses and point cloud dynamically!
Here is all changes: dicarne@5f17684 dicarne@677b056
Some unanswered questions: Why, even with the same environment configuration as the author claims, I was unable to run the code of this project until I modified some of the code? I changed several computers and operating systems, and tried in docker, but all failed. I'm curious what the environment configuration is like to run it directly.
The text was updated successfully, but these errors were encountered: