-
Notifications
You must be signed in to change notification settings - Fork 34
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
Discussion about new system structure #618
Comments
Transition to ROS2
ToDo
|
I am just curious about what "Nervous system" stands for in the about figure. |
I referred https://www.jstage.jst.go.jp/article/jssst/17/6/17_6_560/_pdf/-char/ja , and according ot this, "Nervous system" represents the processes that should be autonomously executed in high frequency and independently from the high-level process such as controller, estimator, and so on. In my understanding, in the case of RTOS, functions themselves that are called directly by timers correspond to "Nervous sytems". |
Thx for sharing the article. I also learnt the similar design philosophy from ros_control and gazebo: |
Thx, these two are pretty useful examples. |
For developers,
In order to refine this aerial robot system into a more sophisticated OSS, I suggest the following reforms:
I would like to discuss the architecture of the system we should aim for and the specific tasks required to achieve it.
The text was updated successfully, but these errors were encountered: