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
We started off with a quick discussion on programming's role in robotics, and how important it is. This was then followed by a in-depth discussion about the concepts behind robot code and its role in making the robot perform what it is supposed to, whether it is shooting, driving, in-taking game pieces, and climbing (as it pertains to this year's main subsystems). We learned that it does so with the help of various sensors that helps the robot understand its surroundings. We spoke about the various hardware that the robot uses to perform different tasks, what inputs it will receive either from a remote or in the case of the autonomous, sensor data. Adam posed different scenarios and examples to clarify that a robot will do whatever the user and programmer want it to do, and it will use sensors or other forms of input to receive data. The robot will process said data, and actuate whatever hardware is necessary to fulfill the task at hand. Adam shed some light on the role of a subsystem, and what process the robot experiences in order to make it do the simple task of driving forward.
The text was updated successfully, but these errors were encountered:
We started off with a quick discussion on programming's role in robotics, and how important it is. This was then followed by a in-depth discussion about the concepts behind robot code and its role in making the robot perform what it is supposed to, whether it is shooting, driving, in-taking game pieces, and climbing (as it pertains to this year's main subsystems). We learned that it does so with the help of various sensors that helps the robot understand its surroundings. We spoke about the various hardware that the robot uses to perform different tasks, what inputs it will receive either from a remote or in the case of the autonomous, sensor data. Adam posed different scenarios and examples to clarify that a robot will do whatever the user and programmer want it to do, and it will use sensors or other forms of input to receive data. The robot will process said data, and actuate whatever hardware is necessary to fulfill the task at hand. Adam shed some light on the role of a subsystem, and what process the robot experiences in order to make it do the simple task of driving forward.
The text was updated successfully, but these errors were encountered: