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
To get you started with the drone racing project, you can head over to our [documentation page](https://lsy-drone-racing.readthedocs.io/en/latest/getting_started/general.html).
Copy file name to clipboardexpand all lines: docs/getting_started/general.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,13 @@ Welcome to the LSY Drone Racing Project! This is a platform developed by the LSY
5
5
6
6
Implementing Your Own Algorithms
7
7
--------------------------------
8
-
To implement your own controller, you need to implement a ``Controller`` class in the :mod:`lsy_drone_racing.control` module. The only restriction we place on controllers is that they have to implement the interface defined by the :class:`BaseController <lsy_drone_racing.control.controller.BaseController>` class. Apart from that, you are encouraged to use the full spectrum of control algorithms, e.g., MPC, trajectory optimization, reinforcement learning, etc., to compete in the challenge. Please make sure to put your controller implementation in the :mod:`lsy_drone_racing.control` module to make sure that it is correctly recognized by our scripts.
8
+
To implement your own controller, you need to implement a ``Controller`` class in the :mod:`lsy_drone_racing.control` module. The only restriction we place on controllers is that they have to implement the interface defined by the :class:`BaseController <lsy_drone_racing.control.controller.BaseController>` class. Apart from that, you are encouraged to use the full spectrum of control algorithms, e.g., MPC, trajectory optimization, reinforcement learning, etc., to compete in the challenge. Please make sure to put your controller implementation in the :mod:`lsy_drone_racing.control` module to make sure that it is correctly recognized by our scripts.
9
9
10
10
.. note::
11
11
Make sure to inherit from the base class for your controller implementation. This ensures that your controller is compatible with our scripts. Also make sure to only create one controller class per file. Otherwise, we do not know which controller to load from the file.
12
12
13
13
.. warning::
14
-
You are not allowed to modify the interface of the :class:`BaseController <lsy_drone_racing.control.controller.BaseController>` class. Doing so will make your controller incompatible with the deployment environment and we won't be able to run your controller on our setup.
14
+
You are not allowed to modify the interface of the :class:`BaseController <lsy_drone_racing.control.controller.BaseController>` class. Doing so will make your controller incompatible with the deployment environment and we won't be able to run your controller on our setup.
15
15
16
16
.. warning::
17
17
Many students are enthusiastic about deep reinforcement learning and try to use it to solve the challenge. While you are completely free in choosing your control algorithm, we know from experience that training good agents is non-trivial, requires significant compute, and can be difficult to transfer into the real world setup. Students taking this approach should make sure they already have some experience with RL, and take their policies to the real world setup early to address potential sim2real issues.
@@ -39,7 +39,7 @@ Project Structure
39
39
-----------------
40
40
The project is organized as follows:
41
41
42
-
The `lsy_drone_racing` package contains all the code for the project. The :mod:`lsy_drone_racing.control` module contains the interface for the controllers, and the :mod:`lsy_drone_racing.envs` module contains the environments for the project.
42
+
The ``lsy_drone_racing`` package contains all the code for the project. The :mod:`lsy_drone_racing.control` module contains the interface for the controllers, and the :mod:`lsy_drone_racing.envs` module contains the environments for the project.
43
43
44
44
The levels are defined in the config files contained in the `config` folder. You can have a look at the configuration options to understand how exactly they differ from each other.
0 commit comments