We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some observation on the code structure (in case we want to change it in this pr):
Track
envs
Renderer
I would suggest the following structure:
track
rendering
simulator
f110_env.py
action
observation
Originally posted by @luigiberducci in #118 (review)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Some observation on the code structure (in case we want to change it in this pr):
Track
entity does not depend on the gym.Env, so it could make sense to move it outsideenvs
Renderer
and all the rendering code.envs
implement the simulator. A separation between simulator and gym API might look nice.I would suggest the following structure:
track
rendering
envs
simulator
: dynamics_models, collision_models, laser_models, base_classes, etc. (all code that should not depend on the gym)f110_env.py
: the actual gym envaction
: gym implementation of action spacesobservation
: gym implementation of obs spacesOriginally posted by @luigiberducci in #118 (review)
The text was updated successfully, but these errors were encountered: