-
Notifications
You must be signed in to change notification settings - Fork 158
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
Obtain type of an instance from the KB #203
Comments
Hi Diego! You can ask for all the types: And then iterate through the types to get the propositions of each type (empty type name returns all instances): And iterating over the responses to check whether the instance is in that type. I know that this is not the best interface to get it, and I believe this is a useful thing to provide. Therefore, I'll flag the issue as an enhancement to be implemented in future versions (soon I hope). Best regards, |
Hi Gerard, Yes, all going well thanks. You too, I hope. Thanks a lot for your help, it works!!! To apply your workaround I have only to write few lines in the KB interface... so, it is a great workaround ;-)
Due to our last talk about ROSPlan, I decided to remove the use of MongoDB inside KB interface and create a specific interface to the Scene Database. And this Scene Database is using ROS Server to store the information instead of MongoDB, as you proposed ;-). Of course, this is a preliminary version and I have to create a specific node to manage concurrent access to ROS Server parameters related to Scene Database. But if you are interested on that, you could check the code here. Kind regards, |
Glad it worked! |
I have removed [Q&A] prefix as this is now tagged as enhancement. |
Hi,
I have added an instance to the KB, for example "it1" of type "item". Later I need to get the type ("item") of an instance("it1") from the KB, would it be possible? After checking the messages and reviewing KB source code, it seems that it is not possible...
Thanks.
Kind regards,
-- Diego
The text was updated successfully, but these errors were encountered: