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

Updates to Behaviour Tree RDF #43

Closed
anjanaw opened this issue Jan 10, 2023 · 4 comments
Closed

Updates to Behaviour Tree RDF #43

anjanaw opened this issue Jan 10, 2023 · 4 comments
Assignees

Comments

@anjanaw
Copy link
Member

anjanaw commented Jan 10, 2023

We need to add a few new nodes to the ontology from D3.3.

@dcorsar
Copy link
Member

dcorsar commented Jan 13, 2023 via email

@anjanaw
Copy link
Member Author

anjanaw commented Jan 15, 2023

yes please!, also current rdf might have nodes we need to remove.

@dcorsar
Copy link
Member

dcorsar commented Jan 17, 2023

ok, I've added the nodes types in the d3_3-bt-nodes branch.
Couple of points to discuss:

  • The definitions in D3.3 indicate two or more children; for example Varient is referred to as a type of "sequence node with two or more children" but the definition states "Right sibling(s) generate explanations that clarify explanations generated by the left sibling(s)". So do should instances of Varient nodes be limited to only two children, or is it the case that the definition should be more general like "sibling at index n+1 generates explanations that clarify explanations generated by the sibling at index n".
  • The custom node is reffered to as either a Sequence or Priority node. If we define a single Custom node class as a subclass of Sequence Node and Priority Node then any instance of Custom node will also be an instance of Sequence Node and Priority Node. To avoid this, are we happy to defined a Custom Sequence Node class that is a subclass of Sequence Node and a Custom Priority Node class that is a subclass of Priority Node (we may also want to explicitly state that Sequence Node is distinct from Priority Node but thats a different question).

@anjanaw
Copy link
Member Author

anjanaw commented Mar 16, 2023

From the meeting, conclusions were,

  1. a parent can have more than 2 children and this "sibling at index n+1 generates explanations that clarify explanations generated by the sibling at index n"
  2. For now, we will not use custom nodes.
  3. Please add a new "User Question" Node of type Action Node.

@anjanaw anjanaw closed this as completed Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants