|
|
Package Summary
| Tags | No category tags. |
| Version | 2.0.9 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/IntelligentRoboticsLabs/ros2_planning_system.git |
| VCS Type | git |
| VCS Version | humble-devel |
| Last Updated | 2022-07-10 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Francisco Martin Rico
Authors
Problem Expert
The Problem Expert module is responsible for maintaining the instances, predicates and goals of the PDDL problem.
The main class is plansys2::ProblemExpertNode, which is instantiated from ProblemExpertNode.cpp. plansys2::ProblemExpertNode is a rclcpp_lifecycle::LifecycleNode, but currently the functionality is in the active phase.
The class responsible for maintaining this problem instance is plansys2::ProblemExpert, which is independent of ROS2.
The Problem Expert is dynamic and volatile, accessing its functionality through ROS2 services. To facilitate the task of the application developer, an plansys2::ProblemExpertClient class has been implemented that hides the complexity of handling ROS2 messages and services. Its API is similar to that of plansys2::ProblemExpert, since both have to implement the plansys2::ProblemExpertInterface interface.
The Problem Expert instantiates a plansys2::DomainExpertClient, and every update query is verified against domain to check if it is valid.
Every update in the Problem, is notified publishing a std_msgs::msg::Empty in /problem_expert/update_notify. It helps other modules and applications to be aware of updates, being not necessary to do polling to check it.
Services
-
/problem_expert/add_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/add_problem_goal[plansys2_msgs::srv::AddProblemGoal] -
/problem_expert/add_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/add_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/clear_problem_knowledge[plansys2_msgs::srv::ClearProblemKnowledge] -
/problem_expert/exist_problem_function[plansys2_msgs::srv::ExistNode] -
/problem_expert/exist_problem_predicate[plansys2_msgs::srv::ExistNode] -
/problem_expert/get_problem[plansys2_msgs::srv::GetProblem] -
/problem_expert/get_problem_function[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_functions[plansys2_msgs::srv::GetStates] -
/problem_expert/get_problem_goal[plansys2_msgs::srv::GetProblemGoal] -
/problem_expert/get_problem_instance[plansys2_msgs::srv::GetProblemInstanceDetails] -
/problem_expert/get_problem_instances[plansys2_msgs::srv::GetProblemInstances] -
/problem_expert/get_problem_predicate[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_predicates[plansys2_msgs::srv::GetStates] -
/problem_expert/is_problem_goal_satisfied[plansys2_msgs::srv::IsProblemGoalSatisfied] -
/problem_expert/remove_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/remove_problem_goal[plansys2_msgs::srv::RemoveProblemGoal] -
/problem_expert/remove_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/remove_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/update_problem_function[plansys2_msgs::srv::AffectNode]
Published topics
-
/problem_expert/update_notify[std_msgs::msg::Empty]
Changelog for package plansys2_problem_expert
2.0.9 (2022-07-10)
- Humble Upgrade
- Fix possible bug https://github.com/ros2/rclcpp/issues/1968
- Contributors: Francisco Mart
Wiki Tutorials
Source Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged plansys2_problem_expert at answers.ros.org
|
|
Package Summary
| Tags | No category tags. |
| Version | 2.0.11 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/IntelligentRoboticsLabs/ros2_planning_system.git |
| VCS Type | git |
| VCS Version | iron-devel |
| Last Updated | 2023-08-02 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | UNRELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Francisco Martin Rico
Authors
Problem Expert
The Problem Expert module is responsible for maintaining the instances, predicates and goals of the PDDL problem.
The main class is plansys2::ProblemExpertNode, which is instantiated from ProblemExpertNode.cpp. plansys2::ProblemExpertNode is a rclcpp_lifecycle::LifecycleNode, but currently the functionality is in the active phase.
The class responsible for maintaining this problem instance is plansys2::ProblemExpert, which is independent of ROS2.
The Problem Expert is dynamic and volatile, accessing its functionality through ROS2 services. To facilitate the task of the application developer, an plansys2::ProblemExpertClient class has been implemented that hides the complexity of handling ROS2 messages and services. Its API is similar to that of plansys2::ProblemExpert, since both have to implement the plansys2::ProblemExpertInterface interface.
The Problem Expert instantiates a plansys2::DomainExpertClient, and every update query is verified against domain to check if it is valid.
Every update in the Problem, is notified publishing a std_msgs::msg::Empty in /problem_expert/update_notify. It helps other modules and applications to be aware of updates, being not necessary to do polling to check it.
Services
-
/problem_expert/add_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/add_problem_goal[plansys2_msgs::srv::AddProblemGoal] -
/problem_expert/add_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/add_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/clear_problem_knowledge[plansys2_msgs::srv::ClearProblemKnowledge] -
/problem_expert/exist_problem_function[plansys2_msgs::srv::ExistNode] -
/problem_expert/exist_problem_predicate[plansys2_msgs::srv::ExistNode] -
/problem_expert/get_problem[plansys2_msgs::srv::GetProblem] -
/problem_expert/get_problem_function[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_functions[plansys2_msgs::srv::GetStates] -
/problem_expert/get_problem_goal[plansys2_msgs::srv::GetProblemGoal] -
/problem_expert/get_problem_instance[plansys2_msgs::srv::GetProblemInstanceDetails] -
/problem_expert/get_problem_instances[plansys2_msgs::srv::GetProblemInstances] -
/problem_expert/get_problem_predicate[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_predicates[plansys2_msgs::srv::GetStates] -
/problem_expert/is_problem_goal_satisfied[plansys2_msgs::srv::IsProblemGoalSatisfied] -
/problem_expert/remove_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/remove_problem_goal[plansys2_msgs::srv::RemoveProblemGoal] -
/problem_expert/remove_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/remove_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/update_problem_function[plansys2_msgs::srv::AffectNode]
Published topics
-
/problem_expert/update_notify[std_msgs::msg::Empty]
Changelog for package plansys2_problem_expert
2.0.11 (2023-08-02)
2.0.10 (2023-07-17)
- Merge remote-tracking branch \'origin/humble-devel\'
- Merge pull request #238 from roveri-marco/fix_goal_structure_issue_205 Fix goal structure issue 205
- Merge remote-tracking branch \'origin/master\' into fix_goal_structure_issue_205
- Minor changes to the tests to comply with some change in the generated output
- Fixed some errors and some tests to comply with the revised output
- Merge branch \'master\' into bt-builder-plugins
- Merge pull request #242 from PlanSys2/duplicate_instances Duplicate instances
- Fix typo
- Check instance types and associated tests
- Merge pull request #235 from MostafaGomaa/problem_expert/Fix_InvalidInstance [problem_expert] AddInstance successeeds if instance already exists
- Merge remote-tracking branch \'origin/master\' into fix_goal_structure_issue_205
- Fixed support for the complex goal parsing both from the terminal and from file
- [problem_expert] AddInstance successeeds if instance already exists
- Merge remote-tracking branch \'upstream/master\'
- Contributors: Francisco Mart
Wiki Tutorials
Source Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged plansys2_problem_expert at answers.ros.org
|
plansys2_problem_expert package from ros2_planning_system repoplansys2_bringup plansys2_domain_expert plansys2_executor plansys2_lifecycle_manager plansys2_msgs plansys2_pddl_parser plansys2_planner plansys2_problem_expert plansys2_terminal |
|
|
Package Summary
| Tags | No category tags. |
| Version | 0.0.17 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/IntelligentRoboticsLabs/ros2_planning_system.git |
| VCS Type | git |
| VCS Version | eloquent-devel |
| Last Updated | 2020-08-11 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Francisco Martin Rico
Authors
Problem Expert
The Domain Expert module is responsible for maintaining the instances, predicates and goals of the PDDL problem.
The main class is plansys2::ProblemExpertNode, which is instantiated from problem_expert_node.cpp. plansys2::DomainExpertNode is a rclcpp_lifecycle::LifecycleNode, and in its configuration phase reads the model_file parameter, which contains the .pddl file from which to read the model.
The class responsible for maintaining this domain is plansys2::DomainExpert, which is independent of ROS2.
The Domain Expert does not change while active, accessing its functionality through ROS2 services. To facilitate the task of the application developer, an plansys2::DomainExpertClient class has been implemented that hides the complexity of handling ROS2 messages and services. Its API is similar to that of plansys2::DomainExpert, since both have to implement the plansys2::DomainExpertInterface interface.
Services:
-
/domain_expert/get_domain_types[plansys2_msgs::srv::GetDomainTypes] -
/domain_expert/get_domain_actions[plansys2_msgs::srv::GetDomainActions] -
/domain_expert/get_domain_action_details[plansys2_msgs::srv::GetDomainActionDetails] -
/domain_expert/get_domain_predicates[plansys2_msgs::srv::GetDomainPredicates] -
/domain_expert/get_domain_predicate_details[plansys2_msgs::srv::GetDomainPredicateDetails] -
/domain_expert/get_domain[plansys2_msgs::srv::GetDomain]
Changelog for package plansys2_problem_expert
0.0.17 (2020-08-11)
0.0.16 (2020-08-11)
0.0.15 (2020-08-09)
0.0.14 (2020-08-07)
- Merge pull request #26 from mjcarroll/reduce_deps [Eloquent] Reduce unnecessary dependencies
- Remove CMAKE_BUILD_TYPE
- Contributors: Francisco Mart
Wiki Tutorials
Source Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged plansys2_problem_expert at answers.ros.org
|
|
Package Summary
| Tags | No category tags. |
| Version | 2.0.8 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/IntelligentRoboticsLabs/ros2_planning_system.git |
| VCS Type | git |
| VCS Version | galactic-devel |
| Last Updated | 2022-05-04 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Francisco Martin Rico
Authors
Problem Expert
The Problem Expert module is responsible for maintaining the instances, predicates and goals of the PDDL problem.
The main class is plansys2::ProblemExpertNode, which is instantiated from ProblemExpertNode.cpp. plansys2::ProblemExpertNode is a rclcpp_lifecycle::LifecycleNode, but currently the functionality is in the active phase.
The class responsible for maintaining this problem instance is plansys2::ProblemExpert, which is independent of ROS2.
The Problem Expert is dynamic and volatile, accessing its functionality through ROS2 services. To facilitate the task of the application developer, an plansys2::ProblemExpertClient class has been implemented that hides the complexity of handling ROS2 messages and services. Its API is similar to that of plansys2::ProblemExpert, since both have to implement the plansys2::ProblemExpertInterface interface.
The Problem Expert instantiates a plansys2::DomainExpertClient, and every update query is verified against domain to check if it is valid.
Every update in the Problem, is notified publishing a std_msgs::msg::Empty in /problem_expert/update_notify. It helps other modules and applications to be aware of updates, being not necessary to do polling to check it.
Services
-
/problem_expert/add_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/add_problem_goal[plansys2_msgs::srv::AddProblemGoal] -
/problem_expert/add_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/add_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/clear_problem_knowledge[plansys2_msgs::srv::ClearProblemKnowledge] -
/problem_expert/exist_problem_function[plansys2_msgs::srv::ExistNode] -
/problem_expert/exist_problem_predicate[plansys2_msgs::srv::ExistNode] -
/problem_expert/get_problem[plansys2_msgs::srv::GetProblem] -
/problem_expert/get_problem_function[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_functions[plansys2_msgs::srv::GetStates] -
/problem_expert/get_problem_goal[plansys2_msgs::srv::GetProblemGoal] -
/problem_expert/get_problem_instance[plansys2_msgs::srv::GetProblemInstanceDetails] -
/problem_expert/get_problem_instances[plansys2_msgs::srv::GetProblemInstances] -
/problem_expert/get_problem_predicate[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_predicates[plansys2_msgs::srv::GetStates] -
/problem_expert/is_problem_goal_satisfied[plansys2_msgs::srv::IsProblemGoalSatisfied] -
/problem_expert/remove_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/remove_problem_goal[plansys2_msgs::srv::RemoveProblemGoal] -
/problem_expert/remove_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/remove_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/update_problem_function[plansys2_msgs::srv::AffectNode]
Published topics
-
/problem_expert/update_notify[std_msgs::msg::Empty]
Changelog for package plansys2_problem_expert
2.0.8 (2022-05-04)
2.0.7 (2022-05-04)
2.0.6 (2022-05-03)
2.0.5 (2022-05-03)
- Fix ROS2 Buildfarm error due to Threads
- Contributors: Francisco Mart
Wiki Tutorials
Source Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged plansys2_problem_expert at answers.ros.org
|
|
Package Summary
| Tags | No category tags. |
| Version | 1.0.10 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/IntelligentRoboticsLabs/ros2_planning_system.git |
| VCS Type | git |
| VCS Version | foxy-devel |
| Last Updated | 2021-07-05 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Francisco Martin Rico
Authors
Problem Expert
The Problem Expert module is responsible for maintaining the instances, predicates and goals of the PDDL problem.
The main class is plansys2::ProblemExpertNode, which is instantiated from ProblemExpertNode.cpp. plansys2::ProblemExpertNode is a rclcpp_lifecycle::LifecycleNode, but currently the functionality is in the active phase.
The class responsible for maintaining this problem instance is plansys2::ProblemExpert, which is independent of ROS2.
The Problem Expert is dynamic and volatile, accessing its functionality through ROS2 services. To facilitate the task of the application developer, an plansys2::ProblemExpertClient class has been implemented that hides the complexity of handling ROS2 messages and services. Its API is similar to that of plansys2::ProblemExpert, since both have to implement the plansys2::ProblemExpertInterface interface.
The Problem Expert instantiates a plansys2::DomainExpertClient, and every update query is verified against domain to check if it is valid.
Every update in the Problem, is notified publishing a std_msgs::msg::Empty in /problem_expert/update_notify. It helps other modules and applications to be aware of updates, being not necessary to do polling to check it.
Services
-
/problem_expert/add_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/add_problem_goal[plansys2_msgs::srv::AddProblemGoal] -
/problem_expert/add_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/add_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/clear_problem_knowledge[plansys2_msgs::srv::ClearProblemKnowledge] -
/problem_expert/exist_problem_function[plansys2_msgs::srv::ExistNode] -
/problem_expert/exist_problem_predicate[plansys2_msgs::srv::ExistNode] -
/problem_expert/get_problem[plansys2_msgs::srv::GetProblem] -
/problem_expert/get_problem_function[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_functions[plansys2_msgs::srv::GetStates] -
/problem_expert/get_problem_goal[plansys2_msgs::srv::GetProblemGoal] -
/problem_expert/get_problem_instance[plansys2_msgs::srv::GetProblemInstanceDetails] -
/problem_expert/get_problem_instances[plansys2_msgs::srv::GetProblemInstances] -
/problem_expert/get_problem_predicate[plansys2_msgs::srv::GetNodeDetails] -
/problem_expert/get_problem_predicates[plansys2_msgs::srv::GetStates] -
/problem_expert/is_problem_goal_satisfied[plansys2_msgs::srv::IsProblemGoalSatisfied] -
/problem_expert/remove_problem_function[plansys2_msgs::srv::AffectNode] -
/problem_expert/remove_problem_goal[plansys2_msgs::srv::RemoveProblemGoal] -
/problem_expert/remove_problem_instance[plansys2_msgs::srv::AffectParam] -
/problem_expert/remove_problem_predicate[plansys2_msgs::srv::AffectNode] -
/problem_expert/update_problem_function[plansys2_msgs::srv::AffectNode]
Published topics
-
/problem_expert/update_notify[std_msgs::msg::Empty]
Changelog for package plansys2_problem_expert
1.0.10 (2021-07-03)
- Remove node parameter in client constructors
- Adding comments specifying how the syntax is wrong in unexpected_syntax problem file.
- Adding unit tests for new functions in plansys2_problem_expert.
- Add ability to read in pddl problem files to plansys2 and a new AddProblem service to the plansys2_problem_expert. Adding problem_file node parameter to plansys2_problem_expert to load a single problem file at launch.
- ros2-plan-msg: Adding functions to plansys2_msgs/Knowledge message.
- pddl-tree-messages: Deleting unused function declarations. Adding explicit specifier to single param constructors in plansys2_core/Types.hpp.
- Suggestion for #118
- pddl-tree-messages: Extending action string parsing utilities in plansys2_problem_expert/Utils.cpp.
- pddl-tree-messages: Performing some minor cleanup.
- pddl-tree-messages: Using explicit specifier for single parameter constructors in plansys2_core/Types.hpp.
- pddl-tree-messages: Replacing user access function calls with shorter versions where possible.
- pddl-tree-messages: Adding user access functions to domain expert client.
- pddl-tree-messages: Adding goal user access functions to problem expert client.
- pddl-tree-messages: Adding predicate user access functions to problem expert client.
- pddl-tree-messages: Adding predicate user access functions to problem expert client.
- pddl-tree-messages: Using helper functions in problem expert client to handle user interactions.
- pddl-tree-messages: Updating getInstance and getInstances calls to use helper classes.
- pddl-tree-messages: Updating addInstance and removeInstance calls to use helper classes.
- pddl-tree-messages: Replacing hard coded node equality check with function call.
- pddl-tree-messages: Using ROS messages to define the PDDL construct trees.
- Adding support for PDDL addition and subtraction expressions. Courtesy of \@jjzapf
- Update version
- Contributors: Alexander Xydes, Francisco Mart