|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#31
|
|||
|
|||
|
Re: Robot in 3 Days : Feedback
Quote:
Last edited by Akash Rastogi : 03-12-2013 at 14:14. |
|
#32
|
|||||
|
|||||
|
Re: Robot in 3 Days : Feedback
Quote:
-Mike EDIT: Keep doing what you're doing RI3D! One suggestion, maybe use the kit-bot DT this year? Might encourage more teams, especially veterans, to consider using the kit-bot rather than building their own failing DT. Last edited by Michael Corsetto : 03-12-2013 at 14:31. |
|
#33
|
|||
|
|||
|
Re: Robot in 3 Days : Feedback
Quote:
Edit - I do like Michael's idea of using the Kitbot on Steroids, but it is understandable if you guys would prefer using IR3 Creative products to make a drivetrain instead. Using a Kitbot would also require purchasing one beforehand, but since the new Kitbot from AndyMark won't be available until after Kickoff, that won't be an option. Last edited by Akash Rastogi : 03-12-2013 at 14:48. |
|
#34
|
||||||
|
||||||
|
Re: Robot in 3 Days : Feedback
Can you build it during the 3 days before kickoff this year?
![]() |
|
#35
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
The upside of the RI3D build is that you can get a feel for any surprises with the game components without having to expend that energy yourself.
I can certainly see how teams might not have tunnel vision as much as limited resources to mess around and find their own way. There's a saying among hackers: code wins arguments If your team is hyper-focusing on the RI3D design then your team should take a good review of how that happens internally. There are many reasons why any team will just accept a solution. This is not to say that the RI3D design is flawed in any way but part of being an engineer is to be able to speak up against detractors and also to be able to accept that there may be problems with what you advocate as well. How one does that is often an art and a significant effort. Wrap that up in some politics and sometimes the best idea is just not the one everyone agrees on. Whatever the reason for the design choices one should not hold accountable the people that give their ideas away for basically free. The right way to work out a design is not by censoring potentially valuable information from the design process. That's a political fix that covers a fault somewhere in the process. Last edited by techhelpbb : 03-12-2013 at 15:21. |
|
#36
|
|||
|
|||
|
Re: Robot in 3 Days : Feedback
This is a very wise design philosophy.
Tunnel vision is bad, sure. Reinventing the wheel is worse. |
|
#37
|
|||||
|
|||||
|
Re: Robot in 3 Days : Feedback
I think Ri3D was the biggest factor in raising last season's competitiveness among all teams. I would say don't change a thing, unless you want to put out even more awesome video updates.
It'd be great to see more teams being as open about their build season as Ri3D is. Just think how much everyone could learn if there were hundreds of open build seasons being documented even half as well as Ri3D's is documented. |
|
#38
|
|||
|
|||
|
Re: Robot in 3 Days : Feedback
Quote:
I also think it's an extremely helpful tool for Veterans. It's being produced at a critical time when many teams are still going over rules, discussing strategy and identifying goals. I think seeing refined prototypes and concepts interact with the game pieces is something that everyone can benefit from. Last year, I felt it was really helpful to see how size and storage space would play a factor in the game. I'll definitely tune in again. My only feedback would be to have an overlay on the stream. Often the view is of people working, without any talking. I understand they are pressed for time, but if somebody tunes in, it would be nice to know what component(s) they are currently working on. Or where they are in the overall process. It wouldn't have to be much, something simple like "Working on Collector Parts" or "Assembling Lifter Assembly". Thanks for doing what you do! |
|
#39
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
Robot in 3 days provided us a baseline of where everyone would be. It also gave us confidence that when a particular mechanism didn't work, we'd have a fallback that was already proven. You guys were the prototypers for all of FIRST.
I'd like to see you live-stream the whole thing with audio. Most streaming sites allow replays so people could watch the entire thing at their leisure. |
|
#40
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
Quote:
I agree that broader access would be the biggest way to improve impact. Everything else last year was great (not that some suggestions here aren't also good), and I think it really is the biggest widespread competitive boost since the kitbot. Absolutely awesome job guys. You're really doing a huge service to the community. |
|
#41
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
Could you possibly set up a Vine account for this? I know many tests that we do rarely last 7 seconds. You could post one showing wheels moving, a frisbee being fired, the lift working, etc... It would be a quick and easy way to release information in between the actual video updates that you guys do.
|
|
#42
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
How is that possible?
|
|
#43
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
Magic is one option
![]() FRC gave them the game early is another option ![]() Typo. That is another option ![]() |
|
#44
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
Quote:
RI3D I appreciate the passion you have for pushing first to a higher level I'm just concerned that too much of this in week one will lead to incredibly uniform robots and strategies. |
|
#45
|
||||
|
||||
|
Re: Robot in 3 Days : Feedback
You guys helped out SO many teams this past year, including ours and I look forward to seeing it happen again.
I would definitely like to second the notion(s) of showing more of the design/brainstorming process. I know that when we were rookies, design was something we didn't exactly know how to effectively do and I think watching you guys do it would give other rookies an idea of how it's supposed to go and how to rule out options that would take away from the overall quality of their bot. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|