Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid value when calling getTimestamp() or getDouble("timestamp") on EulerAngles messages #2

Open
rasmartins opened this issue Aug 4, 2015 · 2 comments

Comments

@rasmartins
Copy link
Contributor

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".

@zepinto
Copy link
Member

zepinto commented Aug 4, 2015

You will need to add more context, I am not able to reproduce the problem with the following code:

EulerAngles angles = new EulerAngles();
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"

@rasmartins
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants