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 the mentioned methods are called on EulerAngles messages, the returned value is always -1 even though the actual value is different (checked with DUNE). Might be related with the fact that this message (and others) have a field called "time".
The text was updated successfully, but these errors were encountered:
You will need to add more context, I am not able to reproduce the problem with the following code:
EulerAnglesangles = newEulerAngles();
System.out.println(angles.getDouble("time")); // prints "0"System.out.println(angles.getTimestamp()); // prints "1.438701476012E9"System.out.println(angles.getDouble("timestamp")); // prints "1.438701476012E9"
It probably only happens when processing LSF files. If you open a log in MRA you will see the issue in the EulerAngles message, the same thing happens when converting to LLF.
When the mentioned methods are called on EulerAngles messages, the returned value is always -1 even though the actual value is different (checked with DUNE). Might be related with the fact that this message (and others) have a field called "time".
The text was updated successfully, but these errors were encountered: