My near 10000 image set keeps failing after about an hour and a half, the last 2 times with this:
ValueError: invalid stoi argument (previous time was: invalid stod argument)
[ERROR] The program could not process this dataset using the current settings. Check that the images have enough overlap, that there are enough recognizable features and that the images are in focus. You could also try to increase the --min-num-features parameter.The program will now exit.
The images do have enough overlap, are in focus, have tons of features, and I’ve been increasing the min num features, this time: Options: dsm: true, min-num-features: 15000, optimize-disk-space: true
but it doesn’t help.
Less than 5GB of the available 96GB is being used, but the processor is being utilised at up to near 100%.
WebODM on Win 10 Pro. M2Pro drone images scaled to 0.25, so dimensions only 1372 X 912 pixels for processing.
I managed 5000 of these images in 15 hours, but every time I try to do 10000, it fails, and not through lack of memory.
Unfortunately it appears to be gone from when I cleared out all the failed attempts last night. All I have is the console logs.
I’m trying a smaller subset of 6894 images currently, and it has made it past the 1.5 hour mark.
I’m using Options: dem-resolution: 2.0, dsm: true, dtm: true, mesh-size: 220000, min-num-features: 10000, orthophoto-resolution: 2.0, pc-quality: high
and have only reduced by 0.5 this time. I have also turned off the disk space saver, which maybe removing required files?
Currently 2h15 min in:
2021-10-14 14:26:29,251 DEBUG: No segmentation for DJI_0407_5.JPG, no features masked.
2021-10-14 14:26:29,302 DEBUG: Matching DJI_0515_4.JPG and DJI_0513_4.JPG. Matcher: FLANN (symmetric) T-desc: 29.967 T-robust: 0.016 T-total: 29.987 Matches: 2066 Robust: 2044 Success: True
only using 13%CPU and 3.3GB RAM, but I see there are 3 instances of WebODM running, is that normal?
Do you have an antivirus or some other security software running on your machine @Gordon? Just trying to narrow the cause of the issue. It looks as if the tracks.csv file got truncated at some point during reconstruction.