About Cameron Nakhjiri

This author has not yet filled in any details.
So far Cameron Nakhjiri has created 2 blog entries.

Build Season Week 1 Blog

By |2025-01-14T21:35:50-08:00January 11th, 2025|

             After exciting anticipation for the game reveal over winter break, we gathered to watch FIRST’s live stream. We went straight to reviewing the game manual and brainstorming robot strategies. Our first few days of the season were spent honing in on our robot’s functional requirements and strategy. We also met with the FRC teams BREAD, GravitechX, and NerdHerd to get an outside perspective as well as exchange ideas.              After deciding our initial strategy, we researched design ideas, taking inspiration from past games and open alliance teams. Before committing to any specific robot design, the team split into Design Groups, each tasked with exploring separately to avoid the entire team fixating on just one design. These teams focused on analyzing scoring potential, identifying challenges, and understanding the game's nuances to optimize gameplay efficiency., Then, we reconvened to collaborate and discuss overarching designs to decide what we would need to prototype. We decided to prototype a ground intake that picks up coral from all orientations and a climbing mechanism inspired by Rust Hounds from Ri3d.              In conjunction with the prototyping groups, a separate group focused on designing the first iteration of our Alphabot The Alphabot combines our off-season project, a two-stage cascading elevator, [...]

By |2024-12-09T19:13:35-08:00November 19th, 2024|

After every match, the most important thing our team does is debrief. We go over what went well, but more importantly, the big question is what can be improved. Data Analytics is our advanced off-season project that works to answer that question. We can track faults in our robot by logging data from its many sensors during matches. For example, if our robot stops working during a match, taking a quick look at the logs can help us understand which specific subsystem malfunctioned, giving actionable data that our pit crew can execute. A robot generates a lot of data, but not all of it is important in diagnosis. We went around and spoke to every one of our robot subteams asking what data was important to log. Additionally, by logging how each aspect of the robot performs during a match, respective subteams can address faults in their design. If something does not show up as working correctly, we can view these issues before they later affect the robot as a cascading error.  To figure out how to  create our logging system, we did research into multiple different preexisting logging libraries, including readdressing our Log Manager application from last year. We decided to adapt from Team 581’s Dog Log and integrate it into our current Log Manager. Through spikes [...]

Go to Top