-
Notifications
You must be signed in to change notification settings - Fork 99
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
[Urban Feature] Camera coordinate frame changed from gazebo9 to ignition #184
Comments
Original comment by Ian Chen (Bitbucket: Ian Chen). I looked into a couple of camera urdfs that were used in gazebo9 and confirmed that the optical frame is indeed different from ignition. Like you said, we probably don’t want to change things now but it’s something to consider after the tunnel circuit. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original comment by Angela Maio (Bitbucket: Angela Maio). Recommend noting this in the Migration Guide if it will not be changed soon or ever |
Optical frames have been added. |
Original report (archived issue) by Neil Johnson (Bitbucket: realdealneil1980).
It appears that the orientation of the camera coordinate frame is different in the ignition simulator than in the gazebo 9 simulator. This has had undesirable consequences with some of our object localization math and visual odometry methods.
In gazebo 9, the camera frame (according to tf) was oriented with x right, y down, z out the optical axis of the camera. This lined up with our expectations. In ignition, the camera frame is oriented x out the optical axis, y left, and z up. So, it is basically the same as the body frame axes translated to the base of the camera.
I don’t particularly want things to change at this point, but I’d like it if someone could confirm that indeed the coordinate frame changed during the migration to ignition, and to make the teams aware of this change in case it affects them too.
The text was updated successfully, but these errors were encountered: