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

Basic modeling of the simulation environment #826

Closed
bjost2s opened this issue May 9, 2020 · 1 comment
Closed

Basic modeling of the simulation environment #826

bjost2s opened this issue May 9, 2020 · 1 comment

Comments

@bjost2s
Copy link
Contributor

bjost2s commented May 9, 2020

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

@bjost2s
Copy link
Contributor Author

bjost2s commented May 12, 2022

done

@bjost2s bjost2s closed this as completed May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant