-
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
Seg Fault in "Compute optical flow and tracks" #14
Comments
I haven't seen this happen before. What happens when you enable fault handler?
Also, what environment are you running on? |
Seems like no issue w/ importing and enabling faulthandler. wrt my environment, i setup the venv the exact same way as described in the readme:
Your help is greatly appreciated |
You'll have to add |
I also got the same error, this is the output with
|
+1 here, very similar stack trace w/ faulthandler |
This seems to be a problem with the CoTracker code from Torch Hub, but I'm not sure why it's segfaulting. Here are a few things to try:
|
I did with boths requirements files, and get the same problem, will try the second point: Directly cloning CoTracker or integrating it as a submodule to avoid using the Torch Hub version. Thanks. |
A very quick fix for me is to change this line of code to the new version of CoTracker.
|
@phongnhhn92 Be careful—we found that CoTracker v2 produces less accurate tracks than v1. This might impact performance more than you would like. |
@dcharatan Hmm, so I would need to manually download the weight of the V1 CoTracker here and load it to reproduce your results? |
Yes, to reproduce the results, you'll need CoTracker V1's weights. It might be worth trying out the steps here to avoid having to manually download the weights. |
Hello,
I successfully ran the subsampling preprocessing script, however when i run the overfit script:
python3 -m flowmap.overfit dataset=images dataset.images.root=/.../.../.../.../flowmap/frames
I get this segmentation fault, unsure how to proceed here. Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: