-
Notifications
You must be signed in to change notification settings - Fork 250
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
Error running python imgs2poses.py data/testscene
#39
Comments
This means you don't have the images in a separate folder called 'images'. This is necessary. I have stumbled upon the same problem a lot! |
I too am facing the same problem. Can someone explain what these data structures mean? pts3d, poses in the save_poses function |
I have another traceback on the same script imgs2poses.py Traceback (most recent call last): I'm not sure why the index goes out of range.. |
@fishirenee did you solve this? one of the images hasn't registered correctly, could it be that? |
@robclouth I revisit the dataset. I just deleted the poses that are barely blank with minor features (such as an image of the white ceiling). I noticed those poses caused this type of bug.
|
Is there anyway to figure out which images are causing the problems? Colmap is dropping one, (the number of poses is 15 but there are 16 images), but I don't know how to figure out which one it is. |
It would be nice if the code just ignored images with no pose instead of failing |
anyone with the following issue? `Need to run COLMAP Features extracted Features matched Sparse map created Finished running COLMAP, see data/frame16/colmap_output.txt for logs Post-colmap Cameras 5 Images # 15 ERROR: the correct camera poses for current points cannot be accessed Done with imgs2poses` How do I solve this? The poses are not generated. |
I figured it out, see the line LLFF/llff/poses/colmap_wrapper.py Line 64 in c6e27b1
I simply changed the code from output_path to export_path and it workedI will add that I installed colmap on Ubuntu 18.04 at the time of writing this comment and the installed version was colmap 3.4 which requires the change I mentioned above. is it possible to support both versions in the wrapper code? |
@kajalsanklecha Did you solved the issue that you have mentioned above? |
@kajalsanklecha Hi, I am facing exactly the same problem as you, do you have any idea to solve it? |
I have fix the issue at #60 The issue is because some views(images) are not registered in the colmap, so we cannot use pose_boundary.npy to process all views(images) |
thanks,good done! |
Im getting this error, when trying to do manual installation
The text was updated successfully, but these errors were encountered: