Skip to content

Goals

Jump to bottom
Eric Steen edited this page Jun 26, 2020 · 40 revisions

High Level Goal Algorithm

While version < 2.0 && "exploring generality between types is not overly complex"
  EVOLVE Behavior Tree (BT) subsystem to get to version 1.0
  EVOLVE Neuroevolution subsystem to get to version 2.0
else
  MOVE each automaton type into an umbrella as individual mix projects

EVOLVE Optimal Sequential Decisions (DEC-POMDP)
EVOLVE Novelty assisted interative evolutionary computation (NA-IEC)

BT Goals (things to focus on to finish Behavior Tree (BT) )

Design Goals for Behavior Tree

  1. Handling Timeouts: user-configurable at composite and/or component level. It seems both would be useful.

  2. Reactive tree:

    1. update tree asynchronously (using cast where call is now, e.g. ticking composite children)
      • provides reactivity since if/when conditions for a previously processed node change it can be re-activated
      • we achieve reactivity via monitoring nodes: Create a new decorator called a “Monitor”. This decorator had an interesting behavior in that when encountering a Monitor decorator, we would evaluate its child node and store the result of that evaluation (just as before) but the monitor would also register itself to a “monitored nodes list”. During async updates after we registered the monitor nodes, we would evaluate all registered monitor nodes in the tree before the tree evaluation step. This simple mechanism allows us to maintain the reactivity of the tree but also prevents us from doing a lot of redundant work.

  3. Processed subtrees: when a composite node fails/succeeds, what all needs to happen?

    1. sequence: stop previously scheduled ticks

  4. currently, the whole tree is started on initial app startup, but what about starting "on-demand", where we start each successive child after running its predecessor.

Testing Goals

  1. Formulate Testing Strategy & Document

Goal Backlog

Short Term Goals

  • monitors: do we need to monitor the Automata.AgentServer and Automaton.CompositeServer so that when a consumer process crashes, the worker processes should have exits handled appropriately?
  • Define protocols / data flows amongst control processes with a contract checker between all (cc is also an anti-corruption layer? A.K.A. embedded schema).
Clone this wiki locally