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

Permanent knowledge base #37

Open
alex-mitrevski opened this issue Jul 27, 2020 · 0 comments
Open

Permanent knowledge base #37

alex-mitrevski opened this issue Jul 27, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@alex-mitrevski
Copy link
Member

Problem description

The ROSPlan knowledge base, which we are interfacing with, is kept in memory, which means that knowledge is lost when the planning system is not running. In some scenarios, however, we should be able to preserve the available knowledge even if a robot is temporarily shut down (for example in the lab manager scenario introduced by b-it-bots/mas_domestic_robotics#233, where the robot should preserve the occupancy of lab sitting spots during the day).

Suggested solution

Adapt the knowledge base interface in ROPOD's task planner, which saves knowledge items to a MongoDB database instead of keeping them in memory.

Caveats

If the knowledge base is permanently kept, we will need a strategy for verifying the correctness of the stored knowledge, otherwise the robot might be acting on outdated information.

@alex-mitrevski alex-mitrevski added the enhancement New feature or request label Apr 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant