Well, it’s week 4, and the code is in the most fantastic position it has ever been in. Ever. Previous years, the software team was limited to one or two people, furiously trying to code all of the motors and few sensors we had. They struggled to implement a fully functional PID control system to smooth out the drive train during autonomous. The main reason they struggled is because they had about 2 days to test everything.
This year, things are severely different.
HAPPY NEW YEAR!
It’s a new year, Kickoff is just around the corner, and the Crusaderbots are ready to set the ball rolling.
Especially, the Software team.
My name is Shivani, and I am the leader of the Software Department for this FRC season. My role involves well, precisely what the title insinuates, Software; I am responsible for overseeing the training of rookies in the Software Department and the successful programming of the team’s robot.
During training season, we attempted to try something different, and encourage rookies interested in Software by conducting a series of Java workshops. The workshops involved a rigorous curriculum of object-oriented programming concepts and basic Java syntax. I was delighted to see the sizable number of workshop attendees and substantial amount of interest in learning how to programming.
As the competition season begins, I am excited to begin working with my new Software team. Alongside the Mechanical and Electrical Departments, we are greatly anticipating kickoff this Saturday. In the mean time, we are preoccupied with the reform of our code revision control system. Currently, we are using a web-based file hosting service known as Dropbox to store our code, but although we can archive code, we only have access to the latest copy; any information on who made certain changes or when a file was accessed are all irreclaimable. However, with the largest software team in the history of Crusaderbots, it is of utmost importance that our Software team be able to identify logical errors at individual access points. Installation of a Git hub or central repository, and individual clients on the robotics shop machines will soon be underway.
Our team’s new organization, outreach, and training efforts display prospect for an efficiently paced, well managed, and FUN build season. I can’t wait for it all to begin!
See you all at kickoff!
Shivani Negi
