Anyone know how to roll back to an earlier version of WebODM? I would like to get back to Build 47 of WebODM which was the last version that I was successful in processing a particular dataset of mine. With the upgrade to Builds 49 and 51 the process in the Matching Images stage takes hours and hours to process when the same dataset with identical settings would only take an hour and a half for the same matching process.
2 Likes
For some reason they made it so ORB can only be used with BruteForce, might be that.
I’m using Sift with Flann. Worked ok in Build 47 but not in 49 of 51.
1 Like
ORB (and AKAZE) have to be used with a binary features compatible matching algorithm, which BRUTEFORCE is. It should still be faster than normal SIFT+FLANN or HAHOG+BOW.
We don’t support older versions at the moment, so we don’t archive prior releases of the WebODM suite. We do keep prior releases of components like ODM, however, on GitHub.
1 Like
That’s too bad for my situation. I guess I am wondering what possibly changed between releases that changes my image matching processing times on the same data set from an hour and a half in Build 47 using Sift/Flann to over 40 plus hours (and still processing by the way) for the exact same data set also using Sift/Flann?
3 Likes
We apologize for any regressions, and obviously are not looking to create them with upgrades.
It might be related to changing a bit of our pipeline in response to OpenSFM updates that should have improved the speed/robustness of our pipeline (dropping things like --matcher-distance).
I’m trying to replicate this and other issues and track them down, so hopefully we can get things sorted for everyone shortly.
3 Likes
I miss matcher distance!
1 Like
If we get things tightened up enough you won’t even know it is gone 
That’s the goal!
Sorry for the growing pains on that one!
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.