|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Robot in 3 Days 2017
I'm sure this will be an unpopular perspective....but here goes.
As a long term supporter of FIRST and as a mentor of FRC teams in the New York area I find myself reminiscing for a time when students could not just browse for an answer to the challenges set by FIRST. No disrespect meant to the engineers and mentors taking part in robot in 3 days. Just my 2 cents. |
|
#2
|
||||
|
||||
|
Re: Robot in 3 Days 2017
Quote:
|
|
#3
|
||||
|
||||
|
Re: Robot in 3 Days 2017
Quote:
Starting points are nice. |
|
#4
|
|||||
|
|||||
|
Re: Robot in 3 Days 2017
Your perspective is not so unpopular.
I think teams should browse for ideas. A three-day idea, and the thoughts that lead up to it, are worth browsing. It should be clear now (5 yrs into the RI3D era) that three-day designs require iterative improvement to become winning FRC robots. |
|
#5
|
||||
|
||||
|
Re: Robot in 3 Days 2017
Quote:
Ri3D gives a very good assessment of what you may find at a competition ... and winning 'bots will have been benchmarked to be better than them. |
|
#6
|
||||
|
||||
|
Re: Robot in 3 Days 2017
I'm so pumped for Ri3D this year! It'll be my third year participating, and it's by far the most fun thing I've done in college. The past two years I've been the captain of The GreenHorns and this year I'll be participating as well. I'm very excited to see what we can accomplish!
|
|
#7
|
|||||
|
|||||
|
Re: Robot in 3 Days 2017
Quote:
I don't really know how to feel about Ri3D. I like that is provides a very visible icon of what an effective design process looks like, with enough time for most teams to implement it themselves. I like the emphasis on prototyping. I like that it pushes teams to do better than the Ri3D teams, though it's been my perception that the community comes right back and says "actually, just be exactly like them instead please." I like that it exposes teams to ideas on how to solve the problem, but I don't like the tendency for the chosen ideas to be presented and interpreted as the correct or best ideas. Having so many teams may reduce this effect a bit, but it also runs the risk of more or less encompassing most viable/mainstream approaches to the challenge, and dramatically reducing detailed design variation when a majority of teams have a physical standard to build their robot to after only three days, whether or not they were initially inspired by the Ri3D teams. I think the design diversity experienced in a stroll through the FRC pits, on both a full robot scale and in the tiny details, is one of the most inspiring experiences the program has to offer, and I don't like Ri3D's intentional or not reduction of this. Everyone talks about how it reduces diversity on a macro scale, but I've honestly noticed it more on a micro scale (little things like COTS tricks, gripper material choice, and so on), and don't like it there either. I definitely don't like how much teams are able to shortcut their own processes using Ri3D, or are encouraged to nix pursuit of their own concepts due to the presence of Ri3D and a ticking clock. I also don't like that it very often seems to serve as glorified advertising for COTS parts, often at the expense of optimal design, and has played a large part in perceived "kit-ification" of FRC in recent years. On the other hand, all of these things have absolutely increased the average performance and average level of success a low to mid level FRC team sees. And that's a good thing, but I also worry about the things being lost to get there. Last edited by Joe G. : 12-31-2016 at 03:57 PM. |
|
#8
|
|||
|
|||
|
Re: Robot in 3 Days 2017
One way to think of/view Ri3D is as a resource. Each team uses the resources they are afforded in different ways, with there being no single perfect way to do it. As someone who drew inspiration from an Ri3D mechanism to help complete a vital mechanism in 2015 I see this as no different than looking at previous games bots to help with mechanism ideas/implementation. I am thankful for Ri3D and assume most of the FRC community is as well. They are wonderful in helping kick-start ideas.
|
|
#9
|
||||
|
||||
|
Re: Robot in 3 Days 2017
I am also thankful to Ri3D teams. It's always a great place to get inspiration and ideas. I think everyone knows to always take Ri3D robots' strategies with a grain of salt, but they are nevertheless awesome robots.
For example, last year, the inspiration for our first iteration boulder intake came from Team Indiana (thanks!). It gave us a good starting point, but our intake ended up looking nothing like their intake after several iterations and improvements. So, you see, teams don't just copy Ri3D robots, they get inspiration and ideas from them. |
|
#10
|
||||
|
||||
|
Re: Robot in 3 Days 2017
One interesting thing to consider is that the Ri3D reveal videos may be the first FRC-style robots a rookie team ever sees, barring the animated robots in the game reveal. I think that's a bigger deal than most of the people on here might realize, just because we're so used to what an FRC robot should look like. I distinctly remember watching the Ri3D reveal from 2013 and learning so much, not about the specifics or exact engineering, but just about the general scale and proportions of a robot. The KOP chassis also does a good job of giving rookies this sense of scale just off of how the chassis is made, but it's just a chassis.
[Transitioning from an anecdotal and reasonable argument to a completely contrived and unsupported argument.] I do understand the arguments about Ri3D possibly making things too easy or providing a big chunk of the design element to teams. But as mentioned above, we're still seeing a significant portion of FRC teams fielding a robot that competes at lower level than an Ri3D clone might have. So either teams are too proud to just copy Ri3D and hone their reliability and driver skill to field a competitive robot, or teams aren't able to translate the design they see in a video into an equally competitive robot. Or both, plus a whole bunch of other, more complex reasons. Now, correct me if I'm wrong, but I also think that as FRC spreads, more and more teams are being founded without: 1) a solid base of technical mentors, 2) a solid base of financial support and sponsors. Now, if this is completely incorrect and the same percentage of teams in the early to mid-2000's were started without either or both of those two things, please tell me. That's just an impression I've gotten from reading around on here. But if it is somewhat true, I think that shows why the existence of Ri3D is more important and beneficial now than it might have been in earlier years. Last edited by Cothron Theiss : 12-31-2016 at 01:56 PM. |
|
#11
|
|||||
|
|||||
|
Re: Robot in 3 Days 2017
I would be highly interested in a little challenge. I don't know if it can be pulled off, but...
Any Ri3D robots that remain functional (and give-or-take unmodified--modify to be "legal", for a given offseason's value of "legal", but without further iteration) get entered into one or more offseason events, either as pre-rookie robots or as second robots or as "house" robots. I think you can see where this is going... The challenge is to see how an Ri3D robot would end up in a competition environment. Obviously it wouldn't be a good idea to do that at an official competition event, but at an offseason you can get away with a lot of stuff. If they all end up at the bottom of the stack, then there's a pretty good argument that they're not as "upsetting the system" as anybody thinks. If they end up at the top, then the argument goes the other way. My guess is they'll end up in the middle: above the BLT-types and below the iterated robots. |
|
#12
|
||||
|
||||
|
Re: Robot in 3 Days 2017
Quote:
|
|
#13
|
||||
|
||||
|
Re: Robot in 3 Days 2017
Quote:
I would love to meet up with Snow Problem again this year, but we run into the problem of missing the first week of the semester... In fact, The GreenHorns' team members are already missing the first day of classes and most likely the second day as well (going to class after having 5 hours of sleep over a 4 day period isn't the best idea). If there was interest, perhaps we could set up a meeting the following weekend? |
|
#14
|
||||
|
||||
|
Re: Robot in 3 Days 2017
Quote:
The rookie team then competes with our Ri3D robot while learning to scout, market their team, etc. from 4607. Considering the robot is controlled by a pre-rookie team that doesn't fully understand the game, that may skew the results slightly, but our robots have been low to middle of the pack in each event. I would think if the robot were controlled by somebody with a decent amount of drive practice and an understanding of the game, it would be a late pick at most events. |
|
#15
|
||||
|
||||
|
Re: Robot in 3 Days 2017
Quote:
Here are the results from the events we competed in as 6587: TRI - https://www.thebluealliance.com/event/2015txri RoboReboot - https://www.thebluealliance.com/event/2015txrb Texas Robot Roundup - https://www.thebluealliance.com/event/2015txrr We gave them the robot and let them make modifications on their own as a means of training and teaching them the skills they would need for the upcoming FRC season. The kids enjoyed the experience and I think the robot held it's own against some really tough competition. ![]() |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|