[ale] Processing color negative scans with ALE

[Jari Juslin]

David Hilvert kirjoitti:
>>   'IMG_3437.png'*****      (96.446125% match) | Calculating 
>> post-alignment match                                       ale: 
>> ui/../d2/trans_multi.h:199: d2::trans_multi& 
>> d2::trans_multi::operator=(const d2::trans_multi&): Assertion 
>> `spatio_elem_map_r' failed.

> Does --ips 0 fix this problem?

It gets me a bit farther, thanks :-).

Here is a comparison:

zds at terra:/zds-data/digikuvat/hdr/hdr401$ ale --threads 2 --16bpc 
IMG_3963.png IMG_3964.png IMG_3965.png IMG_3966.png IMG_3967.png 
_IMG_3968.png IMG_3969.png IMG_3970.png IMG_3971.png ale_bug_test.png
Output file will be 'ale_bug_test.png'.
Original Frame:
  'IMG_3963.png'.
Supplemental Frames:
  'IMG_3964.png'***** okay (94.710798% match).
  'IMG_3965.png'***** okay (95.393201% match).
  'IMG_3966.png'***** okay (96.029818% match).
  'IMG_3967.png'*****      (84.680275% match) | Calculating 
post-alignment match                                       ale: 
ui/../d2/trans_multi.h:192: d2::trans_multi& 
d2::trans_multi::operator=(const d2::trans_multi&): Assertion 
`spatio_elem_map' failed.


zds at terra:/zds-data/digikuvat/hdr/hdr401$ ale -ips 0 --threads 2 --16bpc 
IMG_3963.png IMG_3964.png IMG_3965.png IMG_3966.png IMG_3967.png 
_IMG_3968.png IMG_3969.png IMG_3970.png IMG_3971.png ale_bug_test.png
Output file will be 'ale_bug_test.png'.
Original Frame:
  'IMG_3963.png'.
Supplemental Frames:
  'IMG_3964.png'***** okay (94.710798% match).
  'IMG_3965.png'***** okay (95.393201% match).
  'IMG_3966.png'***** okay (96.029818% match).
  'IMG_3967.png'***** okay (96.357041% match).
  '_IMG_3968.png'***** okay (96.466493% match).
  'IMG_3969.png'*****      (85.254806% match) | Calculating 
post-alignment match                                       ale: 
ui/../d2/trans_multi.h:192: d2::trans_multi& 
d2::trans_multi::operator=(const d2::trans_multi&): Assertion 
`spatio_elem_map' failed.

I'll try your patch next.

What makes me think this is a bit more complex issue than a simple 
out-of-memory error is that it happens at different points for different 
input data, sometimes with just two images, sometimes as far as seven.. 
and all of them are 14.4MP.

However, with the same data, the error strikes at exactly the same time 
(at least in the cases I've tested this far).

I have 3G of physical memory in the system running ALE and a 32-bit 
kernel. Can 32-bit kernel limit the memory available to the ALE process 
in this kind of system?


BTW, thanks a lot for your work on ALE.. I have used it a lot and it 
produces great results. It also enables me to shoot HDR handheld, if 
necessary, as with ALE I can align the images properly for HDR composition.


	-Jari