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

Separate the robot from the environment #14

Closed
diegoferigo opened this issue Apr 15, 2019 · 1 comment · Fixed by #18
Closed

Separate the robot from the environment #14

diegoferigo opened this issue Apr 15, 2019 · 1 comment · Fixed by #18

Comments

@diegoferigo
Copy link
Member

In the current architecture, environment and robot are treated as a single entity since they are described together in the sdf file. We already have two different files for the two, and the world file exploits sdf capability to import elements from another sdf file.

Referring to #12, we have few robot-related singletons in our architecture, and it affects exploiting multiple threads for parallel simulations.

Properly handling the robot and the environment separately also in gympp::IgnitionEnvironment might simplify the support of multithread. Instead of relying on sdformat to combine world and model files, gym-ignition can do it directly manipulating the individually deserialized sdf files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant