The next ROS Deliberation Community Group meeting will be held on 2025-10-06T15:00:00Z.
Google Meet link: https://meet.google.com/njs-ieym-dgk
Agenda:
Feel welcome to propose additional agenda items, especially if you have a quick tool spotlight for this session! As always, do stay in touch by joining the mailing list or the Discord server.
To simplify handling huge trees, what about the following kind of visualization? Is it already a thing?
It collapses child nodes in a folder-like visualization. It also cycles through a full view with all sub-nodes even in the collapsed view, and a direct-children only simplified view.
I find it easier to comprehend bigger trees this way, but maybe it’s just me: on ManyMove, I handle trees by grouping the xml snippets in C++ code, so this kind of visualization helps me make a simpler comparison at runtime.
This is implemented in my fork of Groot (v1):
https://github.com/pastoriomarco/Groot
It only works in Monitoring mode, not sure if it would help or how it should behave when editing.
To collapse nodes, click on them with mouse’s middle button.
This is really cool @pastoriomarco – but since Groot1 is deprecated / in maintenance mode, only supports BehaviorTree.CPP v3, and this is still a fork, I would be a little reluctant to have this be a tool spotlight.
Are there any paths to get this into a more actively maintained upstream tool?
Well, this weren’t really meant as an actual tool to showcase, but more as a concept.
Whenever I show a pic of the trees I generate with ManyMove there’s someone that find their size daunting, so I matured the belief that I’m using BTs in unconventional ways… 
@pastoriomarco and I messaged, and we’ll include a discussion about this in the agenda after all! I think some of the challenges I mentioned in my previous comment on this thread are good to talk about as a group. Thanks, Marco!