Native WebODM 1.9.14 Build 61 on Windows 10 Pro. 64GB memory. 2TB SSD
I have about 400 images. The photos are all taken handheld with a GoPro 5 in a 30x30’ area (GPS data is useless). There is sky in many of the images (can’t be avoided). I processed something similar with ~120 images successfully.
Options: auto-boundary: true, debug: true, mesh-size: 300000, min-num-features: 30000, verbose: true
After approximately 9 hours, Task Output stopped updating. That was almost 4 hours ago. Downloading the log file shows the same thing. Here are the last few lines:
2022-05-24 19:38:25,470 DEBUG: Matching G0017061.JPG and G0017193.JPG. Matcher: FLANN (symmetric) T-desc: 274.920 T-robust: 0.022 T-total: 274.947 Matches: 66 Robust: 11 Success: False
2022-05-24 19:38:40,150 DEBUG: Matching G0017103.JPG and G0017053.JPG. Matcher: FLANN (symmetric) T-desc: 263.768 T-robust: 0.026 T-total: 263.827 Matches: 53 Robust: 11 Success: False
2022-05-24 19:39:33,604 DEBUG: Matching G0016991.JPG and G0017036.JPG. Matcher: FLANN (symmetric) T-desc: 279.608 T-robust: 0.020 T-total: 279.637 Matches: 53 Robust: 10 Success: False
2022-05-24 19:39:54,833 DEBUG: Matching G0016990.JPG and G0016940.JPG. Matcher: FLANN (symmetric) T-desc: 268.316 T-robust: 0.049 T-total: 268.380 Matches: 51 Robust: 10 Success: False
(How do I insert text that will scroll left/right instead of wrapping?)
The system shows a little CPU (7% on an 8-core/16 thread system) used by python.exe, a little disk activity by WebODM and a couple of postgres tasks, and a little network activity by WebODM, a postgres and couple python tasks.
Any idea what may have happened?
For now, I’m going to cancel the task, reboot my computer, restart WebODM and try again. I hate to lose the 12+ hours of processing