-
Notifications
You must be signed in to change notification settings - Fork 78
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
Could not initialize NNPACK! Reason: Unsupported hardware #98
Comments
Hi I think this will not affect the result if your running can go well |
VGGSFM works for small scenes (the largest I managed to reconstruct had 125 images), but fails all the time when I try the sequential method: it reconstructs fain the first bunch of images, but always fails to reconstruct the second; I tried various image sizes for the first and next batch, always the same behavior; the above message is the closes to an error that I see printed |
Usually it would be due to the runner cannot find enough correspondences between the first bunch and the second bunch. Can you share the full log here? |
|
Hi, It seems the root is, the model cannot init the reconstruction well. The first bunch (init) looks have very few inliers. I would suggest to reduce the init window size from 128 to 32 or 64, and increase max_query_pts to higher number like 4096 |
I did try multiple combinations before, and none helps. Here are the results with the parameters you suggested:
|
Hi, It seems to work better than before but meeting an out-of-memory error. Such an error can be easily solved as introduced in FAQ: "We may encounter an out-of-memory error when the number of input frames or query points is too high. In v2.0, we address this by splitting the points into several chunks and running the prediction separately. This involves two hardcoded hyperparameters: max_points_num=163840 in predict_tracks and max_tri_points_num=819200 in triangulate_tracks. These values are set for a 32GB GPU. If your GPU has less or more memory, reduce or increase these values accordingly." If it still does not work well, feel free to share the images to me here or by email. I can have a try on it. |
my GPU is of the same size as in the settings 40GB:
now i reduced those numbers as you suggested, and i get a different error:
|
Good. Now it shows the model has successfully built the first reconstruction but fails for find the second, as shown by:
Can I try to reduce this number from vggsfm/vggsfm/runners/video_runner.py Line 1060 in 2ea29c2
It will reduce the threshold about if a point is viewed as valid. For debugging purpose, you can even set it as |
lowering that the results in OOM in CUDA, and I can not make it work by reducing those numbers, pls find the images attached, maybe it works for you |
hey I see the problem here, it looks like the images are rotated, which will reduce the accuracy and confidence of tracker a lot. I wil rotate them back and do reconstruction when I have time. |
Not sure if this affects the reconstruction but I see this in the logs:
The text was updated successfully, but these errors were encountered: