{"id":12636,"date":"2025-06-30T05:51:50","date_gmt":"2025-06-30T09:51:50","guid":{"rendered":"https:\/\/blogs.mathworks.com\/student-lounge\/?p=12636"},"modified":"2025-06-30T05:51:50","modified_gmt":"2025-06-30T09:51:50","slug":"simulink-game-day-at-usach-our-experience-bringing-control-systems-to-life","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/student-lounge\/2025\/06\/30\/simulink-game-day-at-usach-our-experience-bringing-control-systems-to-life\/","title":{"rendered":"Simulink Game Day at USACH: Our Experience Bringing Control Systems to Life"},"content":{"rendered":"
\n
<\/div>\n
Today\u2019s guest bloggers are members of the Control Systems Society (CSS) Student Branch Chapter at the Universidad de Santiago de Chile (USACH), who recently organized a Simulink Game Day on campus. Let’s hear from them..<\/span><\/div>\n
<\/div>\n
We\u2019re the Control Systems Society (CSS) Student Branch Chapter at the Universidad de Santiago de Chile (USACH), and earlier this year, we hosted a Simulink Game Day on campus. Our goal? To give our fellow students a hands-on, interactive experience with control systems using tools like MATLAB and Simulink\u2014and to show that these topics can be exciting, approachable, and even fun.<\/div>\n
We were thrilled to see our efforts recognized beyond just the event itself\u2014our department even highlighted our success on their official website<\/a>, which made the experience even more meaningful for our whole team.<\/div>\n
This event was organized by four of us: Antonio Gallardo<\/span>, Paula Huichacura<\/span>, Basti\u00e1n Jasimino<\/span>, and Ralitza Mancilla<\/span>. Together, we worked to bring this idea to life from start to finish\u2014and we\u2019re excited to share what we learned along the way.<\/div>\n
\"Equipo<\/div>\n

Why We Organized It<\/span><\/h2>\n
We\u2019ve always been passionate about control systems, and we wanted to share that with others. For many of us, this field felt intimidating at first\u2014but once we started working with Simulink, we realized how powerful and accessible it really is. Organizing this competition was our way of encouraging more students to explore the possibilities and get involved.<\/div>\n
\"Foto<\/div>\n

What We Learned from Planning<\/span><\/h2>\n
One of the biggest challenges was finding the right time to hold the event. We had to work around exams and busy schedules to make sure people could actually attend and enjoy it. Planning the logistics and making sure everyone understood the challenge also pushed us to communicate better and stay flexible as a team.<\/div>\n

Favorite Moments and Takeaways<\/span><\/h2>\n
Seeing the participants dive into the challenge and come up with creative solutions was definitely a highlight. Some teams had hilarious bugs in their final presentations that made everyone laugh, but even then, they were proud of what they built. It was amazing to see students collaborating, asking questions, and getting genuinely excited about control systems.<\/div>\n
<\/div>\n
\"Foto<\/div>\n

What We\u2019d Do Differently Next Time<\/span><\/h2>\n
Next time, we\u2019d love to give participants a bit more time and offer clearer instructions from the start\u2014maybe even go over the code together before kicking things off. We also think it would be cool to integrate a real drone to show how small changes in code can make a big impact in a physical system.<\/div>\n

Our Advice to Other Chapters<\/span><\/h2>\n
Don\u2019t wait for the perfect moment\u2014just start. It\u2019s okay if things aren\u2019t flawless. What matters is creating a space where students can learn, experiment, and connect. And if you can, set aside time after the event to chat and reflect with participants (snacks help!).<\/div>\n
Hosting Simulink Game Day was such a rewarding experience for all of us. It brought us closer as a team, and it reminded us why we love sharing what we do. We\u2019re excited to keep building events like this in the future\u2014and we hope more chapters will do the same.<\/div>\n
\"Foto<\/div>\n<\/div>\n