To give a bit of perspective:
When running the systemtests we execute the coupled participants in the given configuration and then compare exported coupling meshes to a known "good solution" for that participant combination.
Since we compile with a lot of potential hardware specific optimizations turned on, having different CPU capabilities might lead to floating point differences in the execution.
Now to stop the systemtests from failing i just guesstimated a number out of thin air which was a relative tolerance of 3e-7.
I think is a rather high value, but i also dont have any better estimation.
This issue is mainly here to discuss how to tackle the problem.
To give a bit of perspective:
When running the systemtests we execute the coupled participants in the given configuration and then compare exported coupling meshes to a known "good solution" for that participant combination.
Since we compile with a lot of potential hardware specific optimizations turned on, having different CPU capabilities might lead to floating point differences in the execution.
Now to stop the systemtests from failing i just guesstimated a number out of thin air which was a relative tolerance of
3e-7.I think is a rather high value, but i also dont have any better estimation.
This issue is mainly here to discuss how to tackle the problem.