New user: Process exited with code 1

WebODM
#1

I just purchased the Windows/Mac bundle - and I was getting an uneasy feeling it was a wrong decision.

Have tried a about 10 times with different settings, but each time, I get a “Process ended with code 1” error.

I then realized, that I was on Windows (Normally use a Mac) and did a reboot.

Problem solved - at least for a mini test with 2 images.

I did not notice any warnings in the installer about doing a reboot - but perhaps it would be a good idea to include one and save a lot of headace for new users in the same situation.

Now for the big Q: Anyone have success generating GeoTiff files using images from an Autel EVO II ?

Regards
Mike

1 Like
#2

Welcome! I don’t think purchasing ODM could generally be a wrong decision :thinking:

That warning might be best served by Docker, since that’s likely what needed the restart, though I’ve not needed to in the past… perhaps because I have the required virtualization features enabled regardless of docker’s presence.

No! I only have access to a 3DR Solo.

If you have a dataset that stitches nicely and you’d like to share, we’d love contributions to our Public Datasets repository.

Stich some stuff and share it with us so we know how it goes!

1 Like
#3

Thanks Naib

I see may people do have success with WebODM, so expect I will have too.

But much to learn, first attempt at stitching with no image resizing did not go well, will give it a few more tries and upload a couple of images if I can not make it work - hopefully someone can give them a try and tell if they contain the required information.

2 Likes
#4

Mhm! Also, please don’t forget to include all the processing parameters that you change from default. It’ll be in the WebODM UI when you expand the Task under the Options menu. Same goes for the processing log.

See this post of mine for an idea of what that would look like:

Having all of that makes it way more reproducible for other people, as they know what the actual error message(s) are, and what exact settings you used.

That being said, if you’re using all defaults, you should get a proper stitch, and that’s not a bad place to start.

1 Like
#5

First attempt at a high-resolution processing job did not go quite as planned.
I selected 5 out of about 140 images - all sequentially and overlapping about 80% along the flight path.

The red box marked is the total survey area - the processed images are a small rectangle a over the buildings visible along the treeline in the middle left of the Google Maps image.

The processing result has spread the data randomly (or so it appears) over a much larger area.

I did a new job, selected Fast Orthophoto - and result was much better as seen on the third image - but scaling is off with the generated image larger than the reference Google Map - and I see entirely missing patches in this image.

HiRes
Model_Generated.PNG
(Had to delete two images, as I can only attach one…_

Have purchased the ‘Missing manual’

1 Like
#6

Replying to myself - and asking:

Found this statement on autelpilots.com:

“Remember to set your photos to 4:3. Using 16:9 will ruing the end results.”

I was shooting 16:9 - anyone can confirm the above

Regards
Mike

#7

You might need more images, maybe around 15 or so, and not only sequential. Think more like a box or so of coverage (so might be images from multiple flight lines, instead of just sequentially one by one).

Shouldn’t matter if they are coming out of camera that way… I’ve processed 16:9 4K video using Pix4D before, so I know that it is certainly possible in general.

I’ve yet to specifically try 16:9 in ODM, but I suppose I could try something.

#8

Thanks, will load all 143 images an let it run overnight :slight_smile:
This is an I7-7700 2.8 Ghz processor with 16 GB RAM - and still working hard.

1 Like
#9

16GB on an I7 will do just fine with 143. Good luck!

1 Like
#10

Moved to my MacBook Pro, gave WebODM 48 GB of memory - and I now have both a 3D and a 2D model. Need to study the parameters in the 3D browser a bit, but looks promising.

Doing another one this evening with 4x3 images shot at 4K - the Evo 2 camera is really only 12 Mpixel anyway.

Thanks all for your help

3 Likes
#11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.