py_trees icon indicating copy to clipboard operation
py_trees copied to clipboard

What are your viz requirements?

Open stonier opened this issue 2 years ago • 1 comments

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 avatar Feb 23 '23 04:02 stonier