You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is a static environment of the simulation. E.g. for EV3 only one object is available. Here is a list of ideas that could be modeled in a "Simulation Configuration" tab next to the "Robot Configuration" tab:
obstacles
size, to adopt to the size of the overall scene (background image)
weight, to allow "movable" obstacles
color, to mark it
determine initial position
walls, to create mazes
simple coloring of the background image (paint like)
determine initial pose of the robot
Each model of the simulation environment belongs to the program, but can also be stored separately like a configuration. It should be still possible to upload background pictures in the simulation execution view.
Modelling of the robot itself, e.g. determine position of the sensor, should happen in the "Robot Configuration" by annotating the configuration blocks. For this we first have to update the related robot to work with the new configuration like arduinos do.
This feature is related to a project idea, #610 and #821
It will only work for "robots" like EV3 and NXT, and later mBot
The text was updated successfully, but these errors were encountered:
Currently there is a static environment of the simulation. E.g. for EV3 only one object is available. Here is a list of ideas that could be modeled in a "Simulation Configuration" tab next to the "Robot Configuration" tab:
Each model of the simulation environment belongs to the program, but can also be stored separately like a configuration. It should be still possible to upload background pictures in the simulation execution view.
Modelling of the robot itself, e.g. determine position of the sensor, should happen in the "Robot Configuration" by annotating the configuration blocks. For this we first have to update the related robot to work with the new configuration like arduinos do.
This feature is related to a project idea, #610 and #821
It will only work for "robots" like EV3 and NXT, and later mBot
The text was updated successfully, but these errors were encountered: