-
Notifications
You must be signed in to change notification settings - Fork 4
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
Failed to call service with turtlesim/TeleportRelative_Request message requires a float for field linear, but got a <class 'str'> #1
Comments
Hi, thank you for the feedback! The issue is that ChatGPT doesn't always follow the schema in turtlesim_api.json. I have tried to "condition" ChatGPT on the schema here Please keep in mind this is all very experimental, but maybe you can find a way to have ChatGPT create reliable responses in the expected format or to parse the generated response properly. There is now a simple chat history in this repo so with proper error handling one might also try to ask ChatGPT to correct its previous respone. Please find below some useful links: |
it would also be interesting to see how one could extend this demo to the entire ROS ecosystem in an autogpt like approach. Maybe someone could create an organization on github and work on this |
I called it again multiple times, and the majority of the time works perfectly, like you said. And my turtle moved around and spawned another one.
At some point I got this error from the ros_bridge:
And yes, this must happen because ChatGPT doesn't follow the schema sometimes. But I agree that this is experimental and also ChatGPT responses are not deterministic. After that I tweaked the prompts to not kill the first turtle, and then moved around the two turtles like this:
Thank you for the links, they are very useful. |
great you found a solution, lets keep this issue open to improve awareness of these shortcomings |
Hi, I tried to run this demo with the following prompt:
And I got this error message:
Is there another way of parsing the arguments?
Thanks
The text was updated successfully, but these errors were encountered: