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

Questions About RT2 Model Output: Tuple Structure and Tensor Meaning #27

Open
Eagle17035 opened this issue Nov 18, 2024 · 0 comments
Open

Comments

@Eagle17035
Copy link

Eagle17035 commented Nov 18, 2024

Subject: Clarification on RT2 model output structure and usage

Hi [Support Team/RT2 Developers],

I’m working on integrating the RT2 model into a ROS2-based robotic arm control system. The model is being used to generate control commands based on visual input (images) and natural language instructions. However, I’m encountering some challenges in understanding the structure and purpose of the model's output.

Here’s what I observe:

  1. The model output is a tuple with two elements.
  2. The first element is a tensor with shape [1, 1023, 20000].
  3. The meaning and intended use of this tensor are unclear in my application, as the size seems too large for direct use as robotic arm joint control commands.
  4. The second element in the tuple has not been explored yet.

Could you please clarify the following:

  1. What is the meaning of each element in the model’s output tuple?
  2. Is the first tensor (shape [1, 1023, 20000]) designed for use in robotic control, or does it require additional decoding or processing? If so, what is the recommended approach?
  3. If the second element of the tuple is relevant to robotic control, could you provide guidance or examples on how to interpret and use it?

Any examples, documentation, or best practices related to using RT2 for robotic arm control would be greatly appreciated.

Thank you for your assistance!

Best regards

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
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

1 participant