FIX-IT WINDOW Proposal
 

FIRST allows teams to work on spare, replacement and upgrade parts for robots after shipment and between events via FIX-IT WINDOW rules. In 2005, FIX-IT WINDOWs opened at the end of the regional competition events (Sat 5pm) and ended the following Monday at 5pm. That window created a serious hardship for teams that travelled many hours to/from the events. In the past two years, the maximum number and duration of FIX-IT WINDOW sessions were prescribed: no more than 2 sessions, each with a 5-hour maximum duration. This much-improved, yet somewhat arbitrary, allocation of FIX-IT WINDOW sessions can still create difficult situations for teams due to conflicts arising from school use policies, scheduled mentor "day-job" hours, etc.

A lot more flexibility for teams would be gained by allowing no more than three sessions with a cumulative total of 10 hours in a given week. If the twice weekly 5-hour session works better for your team, you could still do this.

Any opinions on alternative FIX-IT WINDOW schedules?

NOTE: The 4th choice is ambiguous!!
A vote here could imply either UNRESTRICTED work is allowed, or NO work is allowed except at competitions.
If you select this choice, please post a reply indicating your intent.
You should state your case for your choice as well, since these are about a different as can be.

Re: FIX-IT WINDOW Proposal
 

Man-hours. X number of man hours to use however you want between ship date and your regional(s). For example: Say FIRST allows each team 100 man hours. The team can allow 10 people to work 10 hours, or 25 people 4 hours each, or 2 people 50 hours each, or even 5 people 10 hours each and another 2 people 25 hours each, etc. Sure it isn't enforcable but neither are the current fix-it windows. The number of man hours is debatable.

Re: FIX-IT WINDOW Proposal
 

Hmmmmm I think that might be a bad idea. Teams with CNCs could have 2 people work for 50 man hours and get a lot done.

Re: FIX-IT WINDOW Proposal
 

Though, to be fair, that's true of the current fix-it window rules as well. As with all things, resources dictate how much we can accomplish in six weeks, ten hours or at a regional.

Re: FIX-IT WINDOW Proposal
 

David,

I like your idea. I just still have a problem with the 10 hour limit for software work. I believe, as many of you probably also figured out, that the two 5 hour sessions are meant to simulate roughly 5 hours that teams get to work on their robots on Thursday and Friday. But in reallity, I know that many teams, including us, work well more than 10 hours on the robot at a competition. This is even more pronounced for SW since you do not need access to the actual robot to write SW. You only need occasional access to the robot to test the SW. You could theoretically work about 30+ hours on SW during the competition (equal to the hours that the pits are open).

Re: FIX-IT WINDOW Proposal
 

Very true but how is that any different in the regular build season? This is exactly my point. What is the purpose of 1 or 2 or 3 or whatever 5 hour or 10 hour or whatever fix-it windows. Teams with limited resources (fewer members, only hand tools, etc) are placed at a disadvantage to those with more resources (100 team membersm zillion dollar CNC shops, etc.). By FIRST limiting the fix-it windows by clock time it in no way levels the field. At least with man hours you can't just have more people working in the time period to get more done.

Re: FIX-IT WINDOW Proposal
 

My vote is "other" -
10 hrs accumulated total - allocated any way you'd like.

For example,
1 team might choose to use all 10 at one time, and be done with it,
while some may choose to allocate equal portions over X days,
and others may choose to split it up in unequal time allotments

So, depending on each teams dynamics (size of team, available equipment, and workspace, time availability of mentors and students) it would best allow all teams the capability of using the fix-it window as they wish to.

Mike

Re: FIX-IT WINDOW Proposal
 

Eliminate the fix it window.... Are we about education or not? Why should learning stop at any time during the competition and for that matter, before or after.

In OCCRA (Oakland County Competitive Robotics Association League) we have no restrictions and the education, and improvements in the robots are fantastic. Students are often heard saying "this experience is much better than FIRST... by far more fun".

Not popular I am sure, but my 2 cents.....

Re: FIX-IT WINDOW Proposal
 

just wondering if it would be better to drop the fix-it-window and go to something like ,"you can't change more then 25 percent of your robot ". better minds could figure out how to divide robot and/or percentage based on game. would it be for each event or whole season? maybe one official picture at first event uncrating.
the only reason i bring this up, it seemed that i saw a few teams carrying in alot of the robot at the comps. mainly ramps.it seemed to me that should be in crate already.
or would this to be a rule that you couldn't enforce? i do believe that writing code should be unrestricted and not part of the above idea.

Re: FIX-IT WINDOW Proposal
 

The problem that I have, personally, with the fix-it window is that the programming is supposed to be done simultaneously with the manufacturing of parts, and the coordination of that is sometimes near impossible, and quite frankly, unrealistic. Noting that the coding of specific features of the machine and the autonomous testing cannot be done until after specific components of the machine are built, I would propose that FIRST do something along the spirit of these two ideas:

1) Make separate fix-it windows for programming
2) Make the "put the computer down" deadline X amount of days after the ship deadline in order to compensate for not being realistic in coding until after the design of the robot is laid out.

As it stands, those teams who build separate identical robot bases or full robots stand to benefit from the fix-it windows because they have a full machine to work on coding with while the manufacturing crew has the ability to work on assembling the spare parts. Additionally, if a prototype base is designed before build, teams can learn to work with sensors on this prototype base so that code is already written BEFORE build starts.

When teams don't have these resources, during build, the programming crew often gets pushed by the wayside when it comes to testing because, after all, if you don't have a finished robot, you can't test it.

I believe that building and coding are two separate beasts that COULD have rules created around them that are separate (but don't necessarily have to if you have strong enough project management skills).

I'm not really... convinced that we would have to do either of these things, but i'm just throwing it out.

Re: FIX-IT WINDOW Proposal
 

+1

Re: FIX-IT WINDOW Proposal
 

Eliminate the fix-it window. I presume we have it because some teams were not playing by the existing rules so FIRST bent them a little to satisfy everyone.

I presume that those teams will still do what they want. Allow the teams to decide what message they give their students. Play within the rules or win at all costs.

I don't think this is something FIRST can solve.

Re: FIX-IT WINDOW Proposal
 

I agree.

1. It can't be and isn't enforced.
2. As Mike said, "Why stop the learning."
3. "The students are most energetic at ship date, and we want them to stop because of a fix-it-window." Paul Capioli
4. Teams that build a second robot have an advantage. NOT. We have done it and we waste all our time building the second robot and end up worse in the end, but the students are still learning.
5. Teams make large changes to fix problems. We are all learning from our mistakes. Note: Most teams are worse off because they can't get the new change working at the event.
6. As long as we all have the same amount of time, who cares.
7. All businesses are in this same type of competition with each other, and they don't have fix-it-windows.
8. May the best team win. We are all still learning.

These are my experiences after being in this for 7 years and still learning. We have yet to win anything, but we have fun. FIRST has done a great job every year designing a game that has many ways to win, simple to complex, but we always have too many rules. It is allot better then back in the day when we had to count screws and buy parts from certain companies. Let’s all state our views and help make this decision. The competition has come a long way for the good.

Re: FIX-IT WINDOW Proposal
 

I've never really been thrilled with the concept of the Fix-It Window, for similar reasons to the above. As written for the past few years, they've just been too inflexible to allow for a lot of otherwise-valid methods of getting things done.

That said, I can see the need for some kind of regulation to keep teams from shipping the RC and a kit frame, then prototyping during the regionals and bringing the whole upper half of the robot to the event with them. I propose the following:

-Teams may bring up to 25 pounds of fabricated items (as defined in the 2007 manual) to the event.
-Fabricated items brought to the event must have similar functionality to a component or mechanism shipped in the crate. (The tube gripper may look completely different, but it must still be a tube gripper.)
-COTS and KOP items are still allowed in unlimited amounts.

Re: FIX-IT WINDOW Proposal
 

I take it that you mean there is no fix-it "window" - one can do whatever they need, whenever. *

I disagree, in that there needs to be limits on how much teams can do during the competition season - otherwise teams going to the NJ regional (1st week) have a disadvantage over teams going to, say Manhattan (5th? week) - specifically, 5 extra weeks on which to perfect a mechanism that was only conceived after the team actually got to see the Game being played.

The argument that learning never ceases is, in this case, eclipsed by the need for a level playing field.

Not a fact, just my opinion.

Don

* And if I totally misinterpreted it, then, never mind...:D