Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are your viz requirements? #415

Open
stonier opened this issue Feb 23, 2023 · 1 comment
Open

What are your viz requirements? #415

stonier opened this issue Feb 23, 2023 · 1 comment
Milestone

Comments

@stonier
Copy link
Member

stonier commented Feb 23, 2023

Looking For

A description of your use case for visualizing py_trees.

  • Describe for what purpose you need it
  • Tease out some key technical requirements
  • Differentiate between MVP (the minimum of value to you) and beyond
  • Any pain points to doing so with the currently recommended approach (see below)

Context

py_trees_js exists, but the only publicly available integration is a ros one. For non-ros environments, the expectation has been that users create their own integration to suit their own particular needs, basing it off what was done for the ros integration.

Nonetheless, there's been a recurring request for viz tools in non-ros environments. This is probably due to two reasons:

  1. The path to creating your own integration is not well supported. There is no well-defined schema for the inputs to py_trees_js, nor are there mechanisms in py_trees itself for generating those inputs (or even, logging them).
  2. Many users would like a simple solution with minimal dependencies that just works with py_trees

This issue is to try and get some understanding and alignment around those needs.

@stonier stonier added this to the ToDo milestone Feb 23, 2023
@stonier stonier pinned this issue Feb 23, 2023
@gitpushoriginmaster
Copy link
Contributor

My two cents on the topic:

  • To track the run right now, I run my code with long periods between ticks, and using the provided unicode_tree() method. While the tree is clearly understandable, it is not instant to read (I have to look for tiny '*', '✕' and '-') and with every print there is that short console print jitter. I would like a less eye-straining version of that.
  • For me an 'obvius' solution is a matplotlib Animation. I think the look of the DOT visualization would be a great format for here as well.
  • I thinks an MVP is a matplotlib Animation that shows the tree and marks the currently used connection between Behaviours that lead to the current Behaviour, the borders of those Behaviours, and color of the last returned status for that Behaviour.
  • I would just really appriciate if that would be a py_trees native solution where I can configure a flag (in BehaviourTree.init()?) that pops a new window

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants