The Thousand Brains Project being open-source means not only that we open-source our code, but also that, as much as we can, we open-source our processes and planning.
Previously, I shared with you the Platform Current Reality Tree, where I described how I viewed the Monty platform and the Undesirable Effects at the time.
Today, I share with you the Platform Future Reality Tree. The Platform Future Reality Tree is similar to the Platform Current Reality Tree; the primary difference is that it includes Injections. An Injection is an action we take to change the current reality into a desired future reality. Aside from that, instead of leading to Undesirable Effects, most of the tree leads to Desired Effects, which is the future we want.
The entire Platform Future Reality Tree is quite large to take in all at once. To find items of interest in it, press CTRL+F (or CMD+F) to open the search menu, and search for the entity text. You can then click on the search result to be taken to that portion of the tree.
How can you contribute?
The Injections listed on the Future Reality Tree are projects that we’ll need to complete to achieve the desired effects. Some of them may be single pull requests, while others may be large, multi-month efforts. It depends on the nature of the Injection.
If you are interested in implementing an Injection, let us know here or on GitHub if you need additional context or advice on how to proceed. Or surprise us with a Pull Request without saying a word 
.
What’s next?
We are working on listing all Injections in our Future Work section in the documentation for easier discovery. There’s a lot to write, so it may take some time to update. The Platform Future Reality Tree is likely to be the most up-to-date artifact.
6 Likes
I think my favorite part is the open source of the process and planning.
4 Likes
After a year of work, we achieved the Desired Effect (105 Platform’s motor system and policies are decoupled from EnvironmentInterfaces.)
It is one of the big three for fully decoupling Experiment, Platform, and Environment from each other.
3 Likes
Future Reality Tree Update - Coordinate Transforms might partially address Platform quaternion convention.
At our engineering meeting today, we added a possible relationship between (DESIRED EFFECT 260 Coordinate system transforms are easy to use.) and (DESIRED EFFECT 314 Platform only uses the WXYZ quaternion convention.)
1 Like
Future Reality Tree Update - Coordinate Transforms unlikely to address Platform quaternion convention
Over time we highlighted other uses of quaternions that are outside the context of reference frame transforms. For example, when motor policies compute where to look, quaternions are used in the context pose transforms directly, outside of reference frame context.
1 Like
Future Reality Tree Update - (339 MontyForGraphMatching is decoupled from a specific motor policy implementation.)
When reviewing the Current and Future Reality Trees during today’s engineering meeting, we noticed that we achieved the Desired Effect (339 MontyForGraphMatching is decoupled from a specific motor policy implementation.) in scope of other work on decoupling the motor system from the environment.
2 Likes
Future Reality Tree Update - (367 It is unclear how to run tbp.monty experiment from outside the tbp.monty repository (e.g., as a conda dependency))
The Undesired Effect (367 It is unclear how to run tbp.monty experiment from outside the tbp.monty repository (e.g., as a conda dependency)) is now resolved.
We figured out how to do this. The template repository for using tbp.monty in your project, prototype, or paper is the best example: GitHub - thousandbrainsproject/tbp.monty_project_template: Quickly use Monty for your project, prototype, or paper. · GitHub. Additionally, we are updating our tutorial documentation to include similar instructions: docs: update tutorial to run experiment from a different repository by tristanls-tbp · Pull Request #968 · thousandbrainsproject/tbp.monty · GitHub.
2 Likes
