You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the tudat tests through ctest, 5 of them fail (apparently due to differences in floating-point precision for different architectures).
I am using a MacBook Pro with M1 Apple Silicon processor. Failing test are:
Copying and pasting from internal discussion (@DominicDirkx):
Test back and forth TCG<->TT at t=0, and expected value of TCG at TT=0..
long double testTime = 0.0L;
testTcg = convertTtToTcg< long double >( testTime);
testTt = convertTcgToTt< long double >( testTcg );
long double expectedTcg = -secondsSinceJ2000Synchronization * LG_TIME_RATE_TERM_LONG /
( 1.0L - LG_TIME_RATE_TERM_LONG);
BOOST_CHECK_CLOSE_FRACTION( testTcg, expectedTcg, 2.0 * std::numeric_limits< long double >::epsilon( ) );
BOOST_CHECK_CLOSE_FRACTION( testTt, testTime, 2.0 * std::numeric_limits< long double >::epsilon( ) );
are using the wrong test, I think (should be CHECK_SMALL, not CHECK_CLOSE_FRACTION).
Looking at this, I think that the long double is implemented as 64 bit, not 80 bits. Not a big problem, but good to be aware of
When running the tudat tests through
ctest
, 5 of them fail (apparently due to differences in floating-point precision for different architectures).I am using a MacBook Pro with M1 Apple Silicon processor. Failing test are:
Copying and pasting from internal discussion (@DominicDirkx):
Full test output is attached here.
The text was updated successfully, but these errors were encountered: