Create a diagram of current software architecture

[micahwoodard]

Right now, there is no diagram of how the dynamic-foraging-task gui is structured. Creating a flow chart would help provide clarity for new users and pin point where refactors need to happen. Will also help define scope of adopting the behavior curriculum refactor

Acceptance Criteria

• A diagram that shows what functions the GUI currently manages, and how they will be replaced by adopting the AIND Behavior Curriculum, and Aind.Behavior.Services

[micahwoodard]

Here is a very basic flow chart of how the session logic works. I'm struggling to create a diagram that accurately reflects the complexity of the code because it is so interconnected and far reaching. Here is a starting point that we can iterate on as well as a link to a powerpoint that outlines the structures of the AIND Behavior Curriculum, and Aind.Behavior.Services

[alexpiet]

Feedback on Current Session Structure

• there are lots of ways for "initial trial" to switch from "yes" to "no. It would be good to diagram how that choice is made
• Load mouse also loads the behavior JSON file from the hard-drive
• The session loop also communicates with Bonsai