[FIRST EMAIL] Stop Build Day Survey

[AllenGregoryIV]

Originally Posted by Fusion_Clint

Are the teams going to pay for that expedited shipping or are we expecting FEDEX to pay for 800 teams to quick ship freight?

Once everyone is in districts, we are going to have to figure it out anyway. I'm just suggesting we figure it out earlier.

[indieFan]

Originally Posted by gblake

"I advocate tightening the current stop-build restrictions because I don't want to see the total FRC program slide too far down the slippery slope of over-emphasizing the competition part of an otherwise well-rounded FRC program." See the next paragraph for an explanation of why I wrote this.

In this thread about a survey about Stop Build Day, I think it would be useful and interesting if each post (even those that are part of a multi-post exchange) began with a short sentence or phrase stating why the poster opposes/supports eliminating, weakening, loosening, tightening, keeping, strengthening (or is undecided about) the current stop build rules.

I wrote something very similar to this in my survey.

The question FRC needs to ask itself is: Does it want to emphasize the engineering, including the trade-offs that are required (everything has a trade-off), or does it want to emphasize winning a competition?

[waialua359]

Originally Posted by RoboChair

1678 is not an amazing and successfully competitive team because we are talented. We got to where we are today with long hours of mostly well planned out hard work.

We could not have reached as far as we have without the practice robots we build that enable us to keep iterating our designs. In 2013 we were a unknown player to the greater FRC community, nobody knew who we were outside of California. Then we won our division after being turned down by our first 3 picks. We made it that far not because of talent, but because of working our butts off to make our robot ready to compete on the world stage every moment we were able. 2014 was much the same story for us. 2015 we had a good robot, not overly amazing, but our success was because of the time and work we put into developing our can grabbers. We finished the design of our final can grabbers the day before we left for Champs, not one team ever beat those can grabbers.

Our robots would still be good if we didn't build a practice bot, but they wouldn't be Einstein good. And a good robot is useless to a driver that can't drive it to it's potential.

Actually, it was 4.
I'd argue that we worked just as hard as you folks. I'd also argue that there are other teams that work even harder than we do but with results that are much less successful on the field. Is it because of talent?
You brought up some good points though. But let me also ask you this. Why was your can grabbers unbeatable? Everyone else in the world saw what 118 did early on during their unveil and week 1 event.
Perhaps....talent?

[AllenGregoryIV]

Originally Posted by waialua359

Is it because of talent?

I'd call it skill not talent. Talent often has a component of natural ability that can't be learned which is where i think he was making a point that be cause they worked hard they developed the ability and skill to be world champions.

[Jon Stratis]

Originally Posted by PayneTrain

They haven't been through inspection at their first district event, which allows them no more than 4-5 hours on day zero and two to three hours on day one to get inspected. It's really easy to find this information out but you seem to have trouble seeking it, so here you go:

Week 1 CHS District - Northern Virginia Event Schedule (2016)
Week 6 Chesapeake District Championship Schedule (2016)
Minnesota North Star Regional Schedule (2016)

Before you get snarky, you might want to realize that I was replying to the content of your post, which was about DCMP, not district events in general. I've been around long enough to know how they work and what their schedules are like.

You'll notice that, while districts have 4-5 hours on day 0, regionals don't. There's a couple hours for load-in, but that's just drop and go, no work or pit setup. Sure, that could change. You could increase the hours and allow teams to stay. But in my experience, you only get about 2/3 of the team loaded in the night before at regionals. All the other teams are still traveling to the event - district events are supposed to be as local as possible for teams, while regionals are hit or miss. Some teams have to travel, and getting to the regional by 5PM the day before instead of the following morning would mean different plans and possibly an additional day off school. Remember, regional teams are already missing an additional day per event compared to districts!

My point is, there are a lot of logistical concerns to consider when you talk about changing times, and those concerns are likely different for different events, based on the demographics of each event. This isn't a one-size-fits-all solution, as FIRST events are not currently one-size-fits-all.

[D.Allred]

Originally Posted by indieFan

I wrote something very similar to this in my survey.

The question FRC needs to ask itself is: Does it want to emphasize the engineering, including the trade-offs that are required (everything has a trade-off), or does it want to emphasize winning a competition?

Interesting point. FIRST's goal is to inspire students and grow to reach as many students as possible. It emphasizes Gracious Professionalism and Co-opertition. Engineering and competition are just a means to that end.

I don't have the wisdom to know if eliminating bag day will negatively or positively impact those goals. My gut feel is it will provide more opportunities for teams to interact outside of competition which is a net positive to FIRST.

The change to a district event structure actually emphasizes competition more than dropping bag day. (More matches... same money ... better use of resources is the theme presented.) Are districts overemphasizing competition?

Food for thought.

David

[jman4747]

Originally Posted by indieFan

I wrote something very similar to this in my survey.

The question FRC needs to ask itself is: Does it want to emphasize the engineering, including the trade-offs that are required (everything has a trade-off), or does it want to emphasize winning a competition?

You need excellent engineering skills to win in a competition in the first place. Yes giving teams more time with the robot would likely help people "win" more, but ask your self why. Getting more time to work directly on the subject of the team's engineering efforts I presume would give more opportunity to improve the engineering skills of the students.

Why bag up the primary teaching tool at the point when we have the most mentor, student, and sponsor engagement of any other time of the year?

[Deke]

I think these are two great points on this subject:

Originally Posted by waialua359

Here's something that no one has really elaborated on yet. What about student/mentor talent?
IMO, elite teams will always be elite teams no matter what rules you change. They are good not because they build 2 robots and continually iterate as the main reason. Its plain and simple.....talent.
I was blown away to here recently that teams could put in less than 1/2 the amount of time and build world class, Einstein ready robots.
I dont think you can do that with all the resources in the world or a change in schedule, without first and foremost the talent and experience to do so.
In Jim Zondag's white paper, he specifically names some example elite teams. Change the rules and they will STILL be elite.

Originally Posted by Andrew Schreiber

I'm for stopping bagging. But I also understand that it would have minimal real impact for low performance teams on their competitiveness [1]. More impactful would be figuring out why so many teams continue to ignore the resources placed in front of them (Ri3D, kitbot, various build days hosted by teams) and figuring out how we can develop more resources and get them used.

Example - how many teams at your events failed to reliably drive? I seem to see at least one per event that's using the kitbot but wiring or programming was too hard. How many fail to move in auto? For me, way too many teams fell into that category. So, the question becomes why? The kitbot can be put together by following instructions. The wiring can be done similarly. And for the most part driving should work fine out of the box. But why is it still so hard?

The following is just from my own observations from watching competitions over the years in a district system.

I think there are teams out there with a very low "ceiling" on their robots/teams performance that would not be solved with infinite amount of time available to them. This can be due to lack talent/resources/skill/capability/knowledge or whatever terminology you want to use.

However, I think there is a much larger subset of teams that do have the knowledge/talent/capability to have a high "ceiling" but run out of time to realize the "ceiling" that they have.

I get to watch a lot of the same teams in person at FIM districts and see a lot of the same teams from the first to second event. There are many that fall into the too little too late to make it into the DCMP. Many matches in the district system allows you to iterate and get better, with more time than regionals, but you still need to come out punching or you'll miss the DCMP boat. Believe me, been there, done that.

I'm in favor of removing bag day because I see many teams reach their "ceiling" at their second event and be competitive, when they were barely able to perform at their first event.

Also, removing should remove a level of bureaucracy with the sign in and out that is not value added IMO.

People have shown to be very adaptive to the situation they were given. I don't think there will be the extreme cases of eliminating bag day will cause all the robots to be competitive, or it will burn all the mentors and students out. I just think it will help the middle tier teams reach their potential. To me, it's not that drastic of a change.

[indieFan]

Originally Posted by D.Allred

Interesting point. FIRST's goal is to inspire students and grow to reach as many students as possible. It emphasizes Gracious Professionalism and Co-opertition. Engineering and competition are just a means to that end.

The change to a district event structure actually emphasizes competition more than dropping bag day. (More matches... same money ... better use of resources is the theme presented.) Are districts overemphasizing competition?

I can see the argument going both ways.

No: The districts can be seen as allowing for the iterative process because you test your robot, then make changes. All engineering requires an iterative process.

Yes: For the reasons you mention above, plus the goal of getting to DCMP.

Personally, not only would I like to keep SBD, but I would like to get rid of the unbag times before the districts. Unbag times defeat the purpose of SBD. (Unbag times between events makes sense to fix things.)

I've been on teams that went to regionals, champs, and districts. Districts are the same length of time as regionals (3 days), so why is there a different structure to the unbagging rules? It makes no sense to me.

[indieFan]

Originally Posted by jman4747

You need excellent engineering skills to win in a competition in the first place. Yes giving teams more time with the robot would likely help people "win" more, but ask your self why. Getting more time to work directly on the subject of the team's engineering efforts I presume would give more opportunity to improve the engineering skills of the students.

Why bag up the primary teaching tool at the point when we have the most mentor, student, and sponsor engagement of any other time of the year?

1. If you're primary teaching tool is at that time, then you're not utilizing the rest of your year well.

2. If you need to "win" because of sponsor donations, you need to reset in the sponsor's minds what this program is about.

3. Engineers have drop dead dates. When they don't meet those dates, there are stiff penalties, typically financial in nature. The lesson of a drop dead date seems to be getting lost on people these days.

[Mr V]

Originally Posted by indieFan

3. Engineers have drop dead dates. When they don't meet those dates, there are stiff penalties, typically financial in nature. The lesson of a drop dead date seems to be getting lost on people these days.

Yes FRC is supposed to at least resemble the real world of engineering and in the real world deadlines are common and in some cases there are penalties that can be financial in nature to the company and if the company has to pay up because that deadline was missed the person or persons who failed to meet that internal deadline are likely to come under the scrutiny of their boss.

[Whatever]

This is kind of minor point but I haven't seen anyone make it.

Over 20+ years as an engineer in the semiconductor industry I have learned to appreciate good marketing requirements at the beginning of a project. There is nothing is worse than working on a project with shifting requirements and projects with really poor requirements have a habit of getting a lot of good engineers laid off. In FRC the equivalent to market requirements is the robot strategy that drives the build season. I would argue that consistently good teams are the teams that do the best job of predicting how the game is going to be played early in the build season. More build time and more chances to reset the design does de-emphasize this aspect of the program.

[Andrew Schreiber]

Originally Posted by Deke

I think these are two great points on this subject:





The following is just from my own observations from watching competitions over the years in a district system.

I think there are teams out there with a very low "ceiling" on their robots/teams performance that would not be solved with infinite amount of time available to them. This can be due to lack talent/resources/skill/capability/knowledge or whatever terminology you want to use.

However, I think there is a much larger subset of teams that do have the knowledge/talent/capability to have a high "ceiling" but run out of time to realize the "ceiling" that they have.

...

I'm in favor of removing bag day because I see many teams reach their "ceiling" at their second event and be competitive, when they were barely able to perform at their first event.

I've snipped out a couple of pretty major points.

1) Yes, there are teams that, given an infinite amount of time will simply not be able to build a functional, let alone, competitive robot.

2) I'm not convinced of this. I'm convinced they run out of time because they think their ceiling is far higher than it realistically should be.

3) I think this is more an issue of teams needing to compete more.

[Siri]

Originally Posted by indieFan

Personally, not only would I like to keep SBD, but I would like to get rid of the unbag times before the districts. Unbag times defeat the purpose of SBD. (Unbag times between events makes sense to fix things.)

I've been on teams that went to regionals, champs, and districts. Districts are the same length of time as regionals (3 days), so why is there a different structure to the unbagging rules? It makes no sense to me.

Regionals and District Events are not the same lengths of time. Using your team's event schedule, PNW Glacier Peak had load-in on Friday (11 March 2016) at 5PM. Opening Ceremonies were the next day at 10:30AM, and Awards were scheduled for the following day at 4PM. Also in 2016, Robodox went to the LA Regional, which loaded in 6PM Wednesday (9 March 2016). Opening Ceremonies weren't until Friday at 8:30AM, and closing ceremonies were scheduled for Saturday 4:30PM. District unbag time is replacing the Thursday you see between load-in and Opening Ceremonies on the LA Regional schedule.

Originally Posted by Mr V

Yes FRC is supposed to at least resemble the real world of engineering and in the real world deadlines are common and in some cases there are penalties that can be financial in nature to the company and if the company has to pay up because that deadline was missed the person or persons who failed to meet that internal deadline are likely to come under the scrutiny of their boss.

This sounds essentially like what can happen if you miss a deadline for FRC, wherein deadline = event. SBD is an artificial deadline before that happens, and it isn't a hard one at that. It's just harder for some than others. Changing this would require not just banning the WH allowance but banning practice bots and other development, which, in addition to not having a clear meaning is the clearest example of holding back student inspiration and development that I can think of. My kids have learned and grown incredibly with practice bots over the years, not to mention the difference between unbag time and regional pit time.

[D.Allred]

Originally Posted by indieFan

I can see the argument going both ways.

No: The districts can be seen as allowing for the iterative process because you test your robot, then make changes. All engineering requires an iterative process.

Yes: For the reasons you mention above, plus the goal of getting to DCMP.

Personally, not only would I like to keep SBD, but I would like to get rid of the unbag times before the districts. Unbag times defeat the purpose of SBD. (Unbag times between events makes sense to fix things.)

I've been on teams that went to regionals, champs, and districts. Districts are the same length of time as regionals (3 days), so why is there a different structure to the unbagging rules? It makes no sense to me.

Thanks for the clarification. I have a better understanding of your perspective.

I'd rather extend that unbagging rule to regional teams than deny districts that option. We'll agree to disagree on that point.

It's a good debate to have. However, the survey didn't address this middle ground that already exists within the district system.

David