yarox / morseweb Goto Github PK

Is it possible to export a single object from a Blender scene using the export tool?

1 fakerobot.extra.get_camera_position, to get the camera position.
2 fakerobot.extra.get_environment, to get the name of the environment the simulation is running on.
3 fakerobot.extra.get_start_time, to get the time the simulation started.

1 is provided in 1.3 as supervision_services.get_camarafp_position.
2 will be provided in 1.4 in supervision_services.details through the field environment.
3 will be provided in 1.4 in the multinode message through the entry __time. It is a list containing simulation_time, simulation_dt, and real_time.

Here is the pull request addressing these changes in MORSE.

When loading a custom environment, e.g.: Environment("mysim/envs/arena.blend"), morseweb can't locate its exported model inside morseweb/web/models. It seems it's trying to find a model called mysim/envs/arena.blend.json instead of just arena.json.

Add a way to show messages from the running simulation scripts into the web interface. May be useful to display simulation progress, for example.

Hi!
I just started using MORSE today, so excuse me for my total noobness. I followed the tutorial on MORSE website to get it to run in headless mode, and it seems to work, but when I try to run the multinode_server before starting the web interface I get this error:

Traceback (most recent call last):
  File "/usr/local/bin/multinode_server", line 30, in <module>
    from pymorse.stream import StreamJSON, PollThread
ImportError: cannot import name 'PollThread'

Any idea how to fix it?
Thanks!

Display a message on the client indicating the websocket status.

Make it possible to load a new simulation (update the environment and the models present on it) without having to restart the websocket service.

Automatically export the objects present in the simulation when loading the websocket server. We could check if the latest version of the models are already exported and, if not, execute the blender export tool.

In a multi-robot simulation some of the robots stay at the origin, and their positions are not updated.