Max Spahn

Hi, That is a correct observation. In order to be able to terminate, it is necessary to have access to a forward kinematics function, which is hard to have. The...

If you want to address this issue, I suggest to first address it in the planar environments, see https://github.com/maxspahn/gym_envs_planar There is already an implementation for the point robot, see https://github.com/maxspahn/gym_envs_planar/blob/354288a67b7185843dcb2c917ade86974ac18607/planarenvs/point_robot/envs/point_robot_env.py#L44-L64...

It looks like it is related to your hardware. Maybe, you can follow this: https://discourse.vtk.org/t/error-glsl-1-50-is-not-supported/1444/5.

This should probably be solved inside the simulation environments. Then, a function (or option) is exposed to the application, like in this case the localPlannerBench.

@c-salmi Im working on that, we can discuss that tomorrow. No need to take action from you at the moment

Currently, if a new metric needs to be added, the name of the metric must be added at various places in the code. This process can be made simpler. https://github.com/maxspahn/localPlannerBench/blob/d2e5f47acd8ddcb2bdca362f04c3258991510d31/plannerbenchmark/exec/postProcessor#L30...

This could be done with the registry pattern. Similar to #25 for planners.

This has been done for planners in #25

Set default to `--no-open`.

might be `apt install freeglut3`