- changed status to resolved
Dynamic tree should be an independent entity in the database
Issue #115
resolved
For now, it is stored inside the controller. This sucks because accessing it is annoying. Moreover, one has to manually create a dynamic tree while running a simulation with no controller. Wasted time and potential code bugs.
Downside is that each robot might have multiple dynamics trees.. So the database should have a two-level identifier. "robot_name_dyn_module_name". Where each module requiring a dynamic tree should have its own unique "dyn_module_name"
Comments (1)
-
reporter - Log in to comment
We'll close this for now; the database is gradually being factored into different apps and so this monolithic bug is losing relevance.