ICB Robotics Internship Feedback Surveys

Q1: If you are in college, what school and what is your major? If not, where do you plan to apply, what major? Did your experience in the internship influence your decision on choosing that major?

Q2: If you could go back in time, would you do this internship again?

Q3: Would you recommend this program to your friends?

Q4: Please rate your experience.

Q5: Do you plan to take a control systems class in college?

Q6: What did you enjoy most about the experience? and the least?

Q7: What concept from the program did you understand the most? and the least?

Q8: What did you learn (added skills) that may help you with the rest of high school and college? Please describe.

Q9: How much and in what way did the hands on projects help you understand the concept of feedback control?

Q10: What can we do to improve the program for students next year?

  • It would be useful to notify the students ahead of time to be prepared to program in Java because I had very little prior experience in Java, which made it more difficult for me to effectively contribute early on.
  • Incorporating more students would definitely be a plus, if lab space allows. More field trips (like the RoboSimian one) would also be cool.
  • Personally, I would require some programming experience because I would expect that a group of 4 intermediate programmers would be able to move through material more quickly and efficiently.
  • I think somewhat more active vision mentoring might be helpful. We definitely appreciated the freedom we had to experiment over several days and work independently. But our instructions were usually just "see if you can do x, y, and z soon," and we weren't quite sure whether those things were possible or simply time sinks. (I recognize, though, that the vision component was new and untested this summer, so our occasional aimless wandering in the jungles of vision may not be the experience of students in future years.) We vision interns certainly had a different experience from the control interns, who worked very closely with their mentors. Overall, though, I had a great experience, and I really appreciate all the effort our mentors put into making the program a success.
  • I think that the radio project would be more interesting if students implemented more complicated and powerful algorithms, although this would not be as good preparation for robotics.
  • It would be helpful if there were a little more structure in terms of instruction before embarking on a project--not an entire lecture, but just an intro to what's going on, for those of us who are working on being experts, but aren't quite there yet.
  • You did a great job last summer. Continue to make the primary emphasis closed loop control. A good understanding of closed loop control seems very useful, especially for robotics.
  • Not sure. Maybe have the students write less code that's not as related to actual control ideas?
  • I feel that the program could be improved by having more specific tasks for each member on the team. This way the stronger programmer can't entirely take over and leave those with less experience or confidence in the dust. I also feel like it would be more fair if students could be compensated based on how much effort they put in. The summer I participated one student spent half as much time in the lab as the rest of us and had almost no understanding of what was going on yet still got the same credit as the other students who understood the projects.
  • The first real project, antenna seeking, when on far longer than I thought it needed to. Though interesting in theory, I know that this project frustrated some of my group members greatly and at least two of them spent the entire first week developing drivers that were project-specific. This was not as constructive as it could have been. Besides this, everything was really quite beneficial. I think more time could have been spent on the kinect-robot integration, though.
  • In general, I think working on a few projects in parallel is better because it's not fun if you hit a brick wall and have nothing else to do.
  • More PID control just keep doing that. There are so many uses for sensors on the FIRST robot that I would challenge a team to use an unlikely sensor for data.
  • The Roombas were pretty frustrating to work with, although perhaps that teaches an important lesson. I don't know how you would change that anyway. I think it's fine as it is!