What do you guys do with your younger members once the code is mostly finished but there’s still a few weeks until there’s hardware to test on? We always end up having too much time in programming because mechanical runs late, and with no bag day this year, we have 5-6 weeks until mechanical is even supposed to be done manufacturing, so I’m trying to figure out what to do with the younger members in the department.
Work with a prior year’s robot to test drive code and experiment with newer wpilib features on mechanisms.
If more experienced/skilled, look into more advanced tools (vision, trajectory generation, motion profiling, machine learning, etc). If more novice, look into generic programming tutorials or wpilib docs.
3 Likes
I’m extremely biased as I developed it, but have them check out the machine learning tools if they’re interested! Extremely limited programming skill is required for good results. Learn more about it here: https://docs.wpilib.org/en/latest/docs/software/examples-tutorials/machine-learning/index.html
1 Like
This does not happen.
1 Like
I’m extremely biased as I developed it, but have them check out the machine learning tools if they’re interested! Extremely limited programming skill is required for good results. Learn more about it here: https://docs.wpilib.org/en/latest/docs/software/examples-tutorials/machine-learning/index.html
Wow, this is really cool!
Yes and no. What happens is we take our old/practice drive base to clip and reconnect wires to attach to prototype motors. Our problem is less mechanical hardware and more having an electrical board to connect software and mechanisms. However, it is true that programming has anxiety until about Week 4, when the robot is finally built and we can see the fullness of our code in action.
Create paths for autonomous, review each other’s code, write unit tests.
They could research and build a device to interface an arduino with the roborio
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.