No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.0.0
License Apache License, Version 2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/nasa/astrobee.git
VCS Type git
VCS Version master
Last Updated 2021-10-01
Dev Status UNMAINTAINED
CI status No Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Cache for global and local transforms.

Additional Links

No additional links.

Maintainers

  • Astrobee Flight Software

Authors

  • Astrobee Flight Software

\page framestore Framestore

We can broadly divide all static transforms into global and local types based on its highest rigid ancestor. Intuitively, if an entity is fixed with respect to the world, then it's a global static transform. Conversely, if the entity is fixed with respect to a robot, then it's a local static transform. For example, the IMU and dock poses are local and global respectively.

In a real experiment an Astrobee is launched without a simulator or any other external computer, so we cannot rely on the simulation (or some other computer) to broadcast the global transforms. Similarly, we can launch a simulation without a Free Flyer, and we should expect rviz to position the ISS and dock correctly. So, we also cannot rely on the presence of a Free Flyer to obtain global transforms. The solution is to duplicate our global transforms -- this keeps simplicity at the cost of increasing the number of messages.

The framestore nodelet is responsible for reading all transforms from the LUA transforms.config and broadcasting them as static transforms on TF2, where they may be picked up by other ROS nodes including the Gazebo simulator plugins, which use the transforms to reposition sensors and simulated entities.

The global_transform node performs a similar function, but only broadcasts the global transforms, so that in the absence of a Free Flyer the graphical user interfaces and simulator show the ISS and dock in the correct location.

CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

  • launch/framestore.launch
    • Copyright (c) 2017, United States Government, as represented by the
      • name [default: framestore]
      • manager [default: ]

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged framestore at answers.ros.org

Package Summary

Tags No category tags.
Version 0.0.0
License Apache License, Version 2.0
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/nasa/astrobee.git
VCS Type git
VCS Version master
Last Updated 2021-10-01
Dev Status UNMAINTAINED
CI status No Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Cache for global and local transforms.

Additional Links

No additional links.

Maintainers

  • Astrobee Flight Software

Authors

  • Astrobee Flight Software

\page framestore Framestore

We can broadly divide all static transforms into global and local types based on its highest rigid ancestor. Intuitively, if an entity is fixed with respect to the world, then it's a global static transform. Conversely, if the entity is fixed with respect to a robot, then it's a local static transform. For example, the IMU and dock poses are local and global respectively.

In a real experiment an Astrobee is launched without a simulator or any other external computer, so we cannot rely on the simulation (or some other computer) to broadcast the global transforms. Similarly, we can launch a simulation without a Free Flyer, and we should expect rviz to position the ISS and dock correctly. So, we also cannot rely on the presence of a Free Flyer to obtain global transforms. The solution is to duplicate our global transforms -- this keeps simplicity at the cost of increasing the number of messages.

The framestore nodelet is responsible for reading all transforms from the LUA transforms.config and broadcasting them as static transforms on TF2, where they may be picked up by other ROS nodes including the Gazebo simulator plugins, which use the transforms to reposition sensors and simulated entities.

The global_transform node performs a similar function, but only broadcasts the global transforms, so that in the absence of a Free Flyer the graphical user interfaces and simulator show the ISS and dock in the correct location.

CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

  • launch/framestore.launch
    • Copyright (c) 2017, United States Government, as represented by the
      • name [default: framestore]
      • manager [default: ]

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged framestore at answers.ros.org

No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.
No version for distro kinetic. Known supported distros are highlighted in the buttons above.