-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
texturing_orthophoto_spotscale_additions branch odm_texturing issue #33
Comments
Same problem here. Here is the output of my log file which is fairly similar to @mtrl but obviously different version # for opencv: Bundle path was set to: /home/ubuntu/caliterra/reconstruction-with-image-size-1200/pmvs/bundle.rd.out |
I haven't seen this. Are you both running 32-bit machines? |
I'm running Ubuntu 14.04 64 bit. I've been looking into this some more and here is the line of code where the error occurs: https://github.com/Itseez/opencv/blob/2.4.8.x-prep/modules/imgproc/src/imgwarp.cpp#L1824 Am trying to see if I can isolate the problem. |
I'm running Ubuntu 12.04.5 32 bit against this data set https://www.dropbox.com/sh/1rt1qdh7tw2mybi/AAAv7zukDC7fszyJMXfc5x8wa?dl=0 the geotaghed folder |
I may have found the issue here. It has to do with the pmvs output file. For example, the job I just ran had a list file at this location: /mnt/odm_data/benchmark/reconstruction-with-image-size-1200/pmvs/list.rd.txt I ran it on the odm_data benchmark folder: https://github.com/OpenDroneMap/odm_data/tree/master/benchmark Notice how those images all have caps .JPG file extensions? Well the list.rd.txt output looks like this: ./DSC05510.jpg This causes the OpenCV error mentioned above since Linux is case sensitive and can't find the file. I went and lowercased all the file extension in my benchmark folder to match the list.rd.txt file and everything finished processing. |
Sounds like a regression. I think earlier versions auto renamed such cases.
|
Bah, I should have read more carefully this thread, sorry I see you already had it figured out with the file names being case sensitive sorry for the bother. |
Confirm issue. All works fine after renaming file extensions to lowercase |
FWIW here is a simple bash command to rename the files from the bash shell. It must be run from within the data directory: for file in *.JPG ; do echo $file; mv $file |
It's interesting. I haven't been able to confirm this issue -- I've run it on directories with files named with JPG extension in caps without event. Is this an artifact of file system, e.g. running in a shared NTFS directory on a Linux VM with a Windows host? |
Interesting that you can't reproduce. I've run into this multiple times on On Fri, Feb 6, 2015 at 11:27 AM, Stephen Mather notifications@github.com
|
Have you tried on a local vm? |
No, but I'll see if I can setup Vagrant on my Mac and give it a run there. On Fri, Feb 6, 2015 at 4:50 PM, Stephen Mather notifications@github.com
|
Thanks @dbaldwin. |
Hi, I was running into a problem with the texturing as well, when I found this open issue. I am running Virtualbox on windows8 64, virtualmachine is ubuntu 64 14.04. Originally I ran a subset of @dbaldwin caliterra images with the upper .JPG as the file extension and got this error message:
** Notice the incorrect path with double '/' as well as the lower .jpg. I re-ran the same imagery with lower .jpg extension with a successful output. |
Finally replicated myself. I'm not sure why I wasn't seeing this before, but it needs a patch, perhaps a little rename for upper case extensions at the start of the script. Anyone want to take a crack at it? |
@smathermather I'm currently running a job with vagrant_odm using Ubuntu 12.04 32 bit. I'll see what happens there. Then I'll try the same with 64 bit. I'll see if I can give the extension rename a try in the next day or two. @glw thanks for confirming. FWIW the double slash isn't a deal breaker, but would be nice to clean up. Linux will still be able to find the path. |
@jmwhite, I haven't gotten your script to change to lower case .jpg to run, but I think I do not understand how to use the highlighted section in the middle. Can you give an example of how that line is used? |
@w0rcy I don't know if it is on every system, but on my deb/ubuntu VMs I just do this:
It just makes everything in the filename lowercase, but that is fine for my needs. |
Thanks, @bgirardot. All lower case is fine with me. Thanks also to all who are working on this software. I have been running tests on your odm_data and on my own and it is getting better all the time. |
I like that @bgirardot -- my approach is more crude: |
Fixed the datasets as a work around until we have a patch for automatically handling this in the codebase: OpenDroneMap/odm_data_apt@0ece0bf |
As we see here...
...the error message occurs in the odm texturing program. The main error message is // Read image to get full resolution size
cv::Mat image = cv::imread(cam.texture_file);
if (image.empty())
{
throw OdmTexturingException("Failed to read image:\n'" + cam.texture_file + "'\n");
} So the problem seems to come from the fact that |
I'm getting the following error when running the texturing branch against a data set at the "running texturing" stage. Is there a recommended virtual environment for development/testing? I'm testing on an Ubuntu 12.04.5 x32 machine on Digital Ocean's cloud. Log output here
Images attached
The text was updated successfully, but these errors were encountered: