State -> Message, GoalState -> Goal

Monty Code
1

We merged a large rename today to more closely match our latest terminology of how we refer to cortical messages. refactor!: rename state to cortical messages by tristanls-tbp · Pull Request #884 · thousandbrainsproject/tbp.monty · GitHub

In short:

  • tbp.monty.frameworks.models.states → tbp.monty.cmp
  • GoalState → Goal
  • State → Message
  • and associated module, method, and variable renames; for example
    • tbp.monty.frameworks.models.goal_state_generation → tbp.monty.frameworks.models.goal_generation
    • use_goal_state_driven_actions → use_goal_driven_actions
    • etc.

You’ll see variable names like goal, message, percept, and vote. A message is a general name for a cortical message. A goal is the cortical message output of a learning module or a sensor module intended for the motor system. A vote is the cortical message vote between learning modules.

A percept is the cortical message output of a sensor module in the sense that a sensor module accepts an observation (in any format) and outputs a percept (a cortical message). You’ll notice some variable names that used to be observation(s) are now percept(s). This is intended to clarify the naming as described above, being more precise as to what goes into a sensor module and what comes out of it.

2 Likes