-
Updated
Jan 20, 2022 - C++
control-systems
Here are 696 public repositories matching this topic...
-
Updated
Jul 5, 2021 - C++
-
Updated
Feb 24, 2020 - Java
-
Updated
Dec 23, 2021 - Shell
-
Updated
Jan 12, 2022 - Julia
-
Updated
Jan 25, 2022 - Julia
-
Updated
Oct 8, 2021 - C++
-
Updated
Dec 13, 2018 - Jupyter Notebook
-
Updated
Mar 5, 2021
-
Updated
Jun 11, 2021
-
Updated
Sep 10, 2021 - Python
-
Updated
Dec 30, 2021 - Roff
-
Updated
Feb 11, 2021 - Python
-
Updated
Jan 21, 2022 - QML
-
Updated
Jan 21, 2022 - Julia
class_name is the nomenclature of pluginlib which in this case doesn't really help people understand what this is supposed to be. We already use plugin_name elsewhere to refer to the same thing, let's rename this field in hardware_interface_info
Originally posted by @destogl in ros-controls/ros2_control#589 (comment)
Current docstring contents are not sufficient. Every function, regardless of trivialness, require at least one usage example.
-
Updated
Dec 21, 2021 - Julia
-
Updated
Aug 20, 2018 - C++
-
Updated
Feb 13, 2021 - Julia
-
Updated
Jan 5, 2022 - Python
-
Updated
Jan 12, 2022 - C
-
Updated
Aug 2, 2021 - C#
-
Updated
Jan 14, 2022 - Julia
-
Updated
Sep 2, 2021 - Jupyter Notebook
-
Updated
Sep 14, 2021 - Rust
-
Updated
Jan 17, 2022 - MATLAB
-
Updated
Jan 23, 2022 - C
-
Updated
Nov 28, 2019 - C++
Improve this page
Add a description, image, and links to the control-systems topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the control-systems topic, visit your repo's landing page and select "manage topics."
While converting the developer docs docuemnt to markdown I stumbled
upon the
envvardirective. I think it would be nice to use that generally,but it needs some work. For one all variables from
environment.rstshowup as second level TOC entries in the main navigation now. Which is something
we do not want. The developer docs should also use the referencing mechanism
and maybe we want to add a