You set your mesh octree depth to 18. Why? You should probably never set that above 13. That would absolutely cause it to crash. We probably need some guardrails for this.
But, summary: if you are testing to see if ODM works on a typical dataset, I recommend not using exotic settings. Use some defaults, some pre-baked settings. Then slowly vary from defaults. And I wouldn’t mess with settings you don’t know the effects of and conclude ODM doesn’t work. That’s going to waste a lot of your time and not be much fun for anyone.
I always use default first. As you see, all my muti-bands datasets failed. Then I try one of my DJI 3D dataset, it works in webODM anytime.
Then I try other dataset from others including OdM samples and pix4D. The result is frustrated.
At the same time, I fly some small datasets special for webODM to check whether my previous dataset s are to big for webODM under my laptop. At the sametime, I processed them in pix4D field all successes and finished in under 1 hour.
That is why the different make me thinking maybe there are something wrong with my vc setting or webODM setting. I try to find out some mistakes I properly made but I am not aware.
Yup: we’ll help you out with any learning curve, and your dataset that failed in multispectral was a new one for us and should be fixed in WebODM in a few weeks now that it’s been fixed in OpenSfM.
It’s strange that the default for 3D was set so high: that should never happen on its own. But, once you reduce that value, this dataset should run to completion.
The reason that I try to use webODM is the opportunity of the further process using FIELDimageR.
I found FIELDimageR can count trees and other customer setting. This is Pix4D can’t do.
File “/code/opendm/types.py”, line 338, in run
self.next_stage.run(outputs)
File “/code/opendm/types.py”, line 338, in run
self.next_stage.run(outputs)
[Previous line repeated 3 more times]
File “/code/opendm/types.py”, line 319, in run
self.process(self.args, outputs)
File “/code/stages/odm_meshing.py”, line 24, in process
mesh.screened_poisson_reconstruction(tree.filtered_point_cloud,
File “/code/opendm/mesh.py”, line 162, in screened_poisson_reconstruction
system.run(’{bin} --in {infile} ’
File “/code/opendm/system.py”, line 79, in run
raise Exception(“Child returned {}”.format(retcode))
Exception: Child returned 137
Since ODM doesn’t support my data yet, can it do RGB only now?
Other RGB data: yes. Other multispectral data: Yes. Your RGB or multispectral data from that sensor: no.
Run under default. Failed again.
That is a different dataset. Can you run the original dataset with default settings? Otherwise, we are comparing apples and oranges and chasing what may be several different issues.
Regarding VM setup, I don’t run on Windows, but @saijin_naib can point you to how to optimize your VM settings. You surely won’t be able to do much if you only have 3GB of RAM allocated.
That’s going to waste a lot of your time and not be much fun for anyone.
