KeyboardInterrupt issue occurs during 'Calculating footprint polygon and actual data corner'

[LiamDiane]

arosics version: arosics-1.12.1
Python version: py311
Operating System: Windows

The terminal outputs:

"Calculating footprint polygon and actual data corner for reference images...
Polygonize progress============-27. 0% Complete = 0:00:14Traceback (most recent call last) :
File "py_tools _ds\processing\progress_mon.py", line 161, in call 
File "py_tools_ds\processing\progress_mon.py", line 118, in print_progress 
-KeyboardInterrupt
Bounding box of calculated footprint for reference image:
(121. 1010989450509, 31. 02289291424106, 121. 98487778334754,31. 75967951179482)
Calculating footprint polygon and actual data corner coordinates for image to be shifted...
#Polygonize progress============ 27. 0% Complete => 0:00:14Traceback (most recent call last) :
File "py_tools _ds\processing\progress_mon.py", line 161, in call 
File "py_tools_ds\processing\progress_mon.py", line 118, in print_progress 
-KeyboardInterrupt
Bounding box of
calculated footprint for image to be shifted:
(121. 19296858128983,30. 915373177387618,122. 05438500484392,31. 633114412071077)" 

Every time the program reaches the 14-second mark, the KeyboardInterrupt error pops up, causing the program to freeze. However, despite the error, the corrected output is eventually produced. Why is this happening? Thanks!

[danschef]

Might be related to the footprint complexity of the input images. Could you post a screenshot of the input images? Please also post how exactly you call AROSICS.

[LiamDiane]

coreg = COREG(
                    reference_image,
                    target_image,
                    max_shift=max_shift,
                    ws=(search_window, search_window),
                    path_out=output_path
                )
coreg.correct_shifts()

[LiamDiane]

[danschef]

As stated above, the KeyboardInterrupt might a consequence of the footprint complexity of the input images + the underlying implementation of the progress bars. The footprint could be more complex than expected in case there are pixels inside the actual image footprint which have the same value like the no-data value of the image. With gdalinfo <path/to/dataset>, you can check which no-data value is set. To workaround the KeyboardInterrupt, you can simply turn off the progress bars with (COREG(..., progress=False).