... | ... | @@ -5,11 +5,12 @@ This is the core of the app. It provides an interface for the user to create and |
|
|
1. Give unique name to the action. If the action already exists, we can add it to the sequence choosing it from the dropdown menu on the top left corner of the window without performing additional demonstrations.
|
|
|
2. The objects and postions (if necessary) will be filled when we come from the [Record Demonstration](Record Demonstration). Rename them to make the learned PDDL model more readable. BE CAREFUL not to give multiple names for a single object.
|
|
|
3. Specify the type of objects. The order should be the same as the order of objects that we entered in step 2.
|
|
|
4. Give additional information about necessary states the the objects should be for the demonstrated action to be performed. (Optional).
|
|
|
The figure below shows all the fields of the dialogue window filled. <br />
|
|
|
4. Give additional information about necessary states the the objects should be for the demonstrated action to be performed. (Optional). Press OK when finished.
|
|
|
The figure below shows all the fields of the dialogue window filled. <br /> <br />
|
|
|
|
|
|
![Screenshot_from_1-0.webm_-_1](uploads/160caca0614889dcba5fcfbf25c40746/Screenshot_from_1-0.webm_-_1.png) <br />
|
|
|
5.
|
|
|
5. The action is now added to the end of the sequence. We can remove, modify, add an action/sequence at any position in the sequence. However, be sure to keep the validity of the sequence.
|
|
|
|
|
|
|
|
|
|
|
|
|