unexpected program state during alignment 'processing'

Hi There,

I have a fairly good machine and a CLI license, however after 2 weeks I am still not able to produce components reliably with more than 4000 pics (10MP). I will add a number of Alignment Setting Screen shots from phases when again and again I got an ‘Unexpected Program state’ during Alignment, usually during processing after 30%. I am trying to align Aerial Images taken with a gopro Hero5session on a fixed wing UAV (I know its a cheap set up).  I have played with the Images a Little bit: temperature,sharpness… but not with the distortion)

On a Win 7 Professional, this is the Hardware set up:

8 cores Intel(R) Xeon(R) CPU E5-1660 v4 @ 3.20GHz

128 GB RAM

NVIDIA TITAN Xp

ca. 3 TB SSD:

System: ATA MTFDDAK512TBN-1A SCSI Disk Device

Processing Project: ATA ST3000DM001-1ER1 SCSI Disk Device

with 700GB Pagefile on the Project-processing disk 

Here Comes the Settings when it failed:

 

 

Some times I get some good alignments with c. 3500 pics and after a while of trying to increase that number by adding additional Pictures from the adjacent Survey squares to a total of around 5000 pics I get unexpected program states. Its always the same failure (0x13010\0x10001)´during the same Point in the process. What is Happening there ? How can I prevent this?

 

Thanks for any hint!

Max

Hello Maxion,

please take a look at these threads, there are some tips that might help you find the problem:

https://support.capturingreality.com/hc/en-us/community/posts/115000771491–SOLVED-Unexpected-program-state

https://support.capturingreality.com/hc/en-us/community/posts/115000772851–SOLVED-Unexpected-program-state-on-orientation-change

Have you tried to align those images with the default alignment settings? 

Also it would be helpful if you could send us the smallest possible dataset that is causing your problems along with the exact reprosteps (especially the settings you have changed) so we can reproduce it and find the reason. 

Hi maxion,

since the Gopros have quite a small focal length, that might be an issue. Which Lens Distortion Model do you use?.

If nothing else helps, I think it might be worth a shot and do some prior undistortion. Even if this is not recommended, I manage to get results on a regularly basis, the differences to undistorted images (the same ones) is visible, but might be negligible, depending on your needs.

Did you add Control Points? If yes, deactivate them and try again - I have a difficult project atm where I did not manage to get an alignment with CPs present, but it worked without them. After the preliminar (successful) alignment (with only small errors left), you can switch them on again and it should work.

Hi Götz Hi Zuzana,

 

thanks for the replies, they are pointing into various directions for possible Solutions. However I seriously want to understand the Problem - RC is an expensive Program and it MUST be possible to be controlled by the customers.

  1. First of all I want to know what is Happening in the Code during this 30-40% processing stage  of Image Alignement - I am not the only one reporting this, but Solutions are not straight Forward see:

https://support.capturingreality.com/hc/en-us/community/posts/115000771491–SOLVED-Unexpected-program-state

 

  1. Second Point: The Fail is not consequent! Sometimes I get components of c. 3000 Images and then with THE SAME SETTINGS I get an unexpected program state. 

 

  1. The fail does not occur with small amounts of Images up till c. 1000 . Zuzana, how can I send you 5000 Images c. 8GB ?

 

  1. Bad Camera. I know Gopro is terrible for Photogrammetry, and I will redo the area with a much better camera. However I am scared to find the same Fail again, as Manuel in this post:

https://support.capturingreality.com/hc/en-us/community/posts/115000771491–SOLVED-Unexpected-program-state

uses proper Hardware and gets the same Fail.

 

  1. For Distortion Model I have tried many: Division, Brown 3, Brown3 + Tang, Brown4, Brown4 + Tang +K - pretty much everything. It did not solve the Problem.

 

  1. I did not use any CPs , but I have come GCPs on the pics.

 

 

Could it be that really the CPU is overheating :

Dmytro

  • 1 year ago

 

Found this could happen due to CPU overheating, in my case, just opened a pc case door, and alignment went with out an error.

 

 

Thanks to everyone who can help to shed light on RCs behaviour. 

Hello Maxion,

would it be possible to upload the images for example on Google drive or Dropbox and send us the link to donwload the data?