Run the exact same code, data, and parameters on AWS and my laptop lead to different results

[lionlai1989]

Hi:
I run s2p with pleiades images on my laptop and AWS server separately. However, I got error from AWS while the exact same code and configuration can run on my laptop smoothly.
I dive into the code, and the following is where the code starts breaking.
In ransac_cases.c, the following lines will fail when running on AWS server, but it won't fail on my laptop.

if (!isfinite(a[i][k]))  
	fail("mprod A not finite %d %d", i, k);  
if (!isfinite(b[k][j]))
	fail("mprod B not finite %d %d", k, j);

Here are my questions.
1.
What is the root cause of this failing? Can I replace non-finite value with zero?
2.
If I can't solve the problem directly, how could I "bypass" this problem? Is there a parameter which I can modify to avoid this fail? Or does it make sense if I just comment out the if statements.
3.
I still don't understand why running the exact same code, data, and parameters on AWS and my laptop will lead to different results .
My laptop:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8

AWS:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4

Any comment or feedback will be appreciated. Thank you.

[gfacciol]

Hi, this issue is most probably solved in the current version of s2p.
You can find it here: https://github.com/cmla/s2p

[lionlai1989]

I use the s2p code you gave, but it still outputs the same error message.
FAIL("/usr/bin/python3 /home/ubuntu/.local/bin/s2p tmp.json"): mprod B not finite 2 2
I will open a new issue at a new s2p github.