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

[Help Request] Problems encountered in SMARTS simulation using ROS #2103

Closed
piqiuni opened this issue Nov 4, 2023 · 2 comments · Fixed by #2106
Closed

[Help Request] Problems encountered in SMARTS simulation using ROS #2103

piqiuni opened this issue Nov 4, 2023 · 2 comments · Fixed by #2106
Labels
help wanted Extra attention is needed

Comments

@piqiuni
Copy link

piqiuni commented Nov 4, 2023

High Level Description

Hello,
I want to use ROS for testing, but I get an error in "rosrun smarts_ros ros_driver.py":

smarts.core.smarts.SMARTSDestroyedError: ('ERROR: A SMARTS instance may have been deleted by gc before a call to destroy. Please explicitly call del obj or SMARTS.destroy() to make this error go away.', AttributeError("'SMARTS' object has no attribute '_agent_manager'"))

I didn't see any introduction to the ROS interface in the document. Does the new version of SMARTS still support the use of ROS?
Thanks!

Version

1.4.0

Operating System

ubuntu 20.04

Problems

No response

@piqiuni piqiuni added the help wanted Extra attention is needed label Nov 4, 2023
@piqiuni piqiuni closed this as completed Nov 4, 2023
@Gamenot
Copy link
Collaborator

Gamenot commented Nov 7, 2023

Generally we have not kept up support for use of ROS for recent versions of SMARTS. It may be broken at this time.

I have made a small patch for the error you ran into.

@Gamenot Gamenot linked a pull request Nov 7, 2023 that will close this issue
@piqiuni
Copy link
Author

piqiuni commented Nov 7, 2023

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants