Summary
This paper presents "introspective planning" as a method to enhance the reliability and safety of robotic task planning using large language models. The proposed method uses introspective reasoning to address uncertainty through a knowledge base consisting of sets of tasks, observations, and candidate plans, along with a rationale for plans to better align with user intent. Additionally, the authors introduce the Safe Mobile Manipulation benchmark with safety-critical scenarios and new evaluation metrics.
Strengths
1. The ability to generate uncertainty over robot tasks, especially in cases of unsafe operations, is particularly important.
2. The paper is well motivated in aligning LLM-generated tasks with the true user intent, given possibly ambiguous inputs.
3. The knowledge base includes a rationale for each task which expands on the KnowNo framework for generating confidence scores.
4. The new additional safety benchmark adds important safety scenarios to existing datasets to better evaluate planning under uncertainty systems.
5. The method is described well, and the availability of the code gives the opportunity for the broader community to build on this work.
Weaknesses
1. The core components of the work are well established. In the proposed direct method, the incremental improvements to existing work are primarily the introspective approach where the LLM is used to generate a rationale for the plan. The conformal prediction method additionally uses a knowledge base to produce statistical guarantees about the prediction which is very important for safe operation. However, the results show significant performance gaps between the direct and conformal prediction. Given this, it would be good to provide a robust analysis of this tradeoff in a general setting.
2. The paper focuses primarily on manipulation tasks that involve somewhat ambiguous items in a kitchen setting such as disambiguating between two sodas in the scene or having the knowledge that a plastic object shouldn’t go into an oven. It would be helpful to include other domains to better show the generalizability of the method.
3. The knowledge base is a key component of the conformal prediction. The authors compare different sizes of knowledge bases, but little is given towards how these should be constructed for a given task and domain. More details on the variations that a user needs to generate should be given. It seems the user needs to be well aware of the failure mode of the tasks to generate an appropriate knowledge base.
4. There may be bias in the user-generated knowledge base, especially for multiple users. It would be good to show how these affect the performance of the system. Perhaps evaluating a system with multiple users without sharing the intended goals would show how well the system aligns across multiple users and a single knowledge base.
Questions
1. It wasn’t initially clear to me whether the knowledge base contains the explanation. Are these stored after construction - they are not in the data files in the code repo.
2. The experimental exploration of the knowledge-base size contained in the appendix is appreciated. Is there a reason that the other metrics were not included in this evaluation? Do you have insights into why the performance drops with the largest knowledge base and what was the variation in tasks contained in the knowledge base?
3. What is the result when the user provides an ambiguous answer when the system seeks clarification?
Limitations
1. As the authors point out, one limitation is that the conformal prediction seems to perform significantly worse than direct prediction. Particularly interesting is that the Unsafe Rate is worse for conformal prediction than direct, which might raise the question as to how much the uncertainty measurement is contributing to safer outcomes.
2. The method is evaluated on a limited diverse set of tasks in a kitchen manipulation setting.
3. The authors make a good observation about multi-label prediction and more investigation is needed to understand the limits around truly ambiguous tasks.