List of Killer Bee Bot Bottoms

[Racer26]

If 2337 has verticals (2 of them) on for Kettering, I suspect we might see Breakaway's only ELEVATION + 2x SUSPENSION BONUS ever there.

[Karibou]

Originally Posted by hektormagee

We at Team RUSH like to keep everyone on their feet and having fun It's nice for us scouters, too, as we get to stretch our legs. Remember Dave's way of shaking his thing? I laughed so hard. Glad people enjoy our cheers Now we need to get the rest of the championship teams to do the cheer with us!

Dave, the judges, and the other volunteers had the best ways to shake their things. It's always great to the volunteers spirited and dancing!

I loved the signs. I wish the video crews had showed them at the end of all of the matches (they did for a lot of them, but not all)

[Carolyn_Grace]

Originally Posted by Gary Dillard

I think in the division finals you had something like "On to Einstein" in the the first match, and then in the second match (after losing the first match) it was "On to Einstein?"

It just said, "Einstein?" during the division finals. We were being hopeful. hehe
We didn't change the signs inbetween matches of each round of the eliminations, as we didn't want to take away time from Pit Crew's much needed robot assessments.

[Schnabel]

I found an error in your code, let's debug:

If (33=Team) WIN();

In this setting, 33 is your variable (assuming you defined it earlier). Let's assume 33 is currently set to null. In your example above, you are saying "If set 33 to Team then call Win" However Team is not a valid variable, instead it should be 'Team'. So that would kill you first. THEN you are setting 33 to Team, I think you would rather do a Binary test now wouldn't you? You would rather it be "If 33 is Team then call Win" which would require double =. So for this statement to function properly, you should have wrote:
If (33 == 'Team') WIN();
.
.
.
.
.
.
.
.
.
.
.
.
.
.

[apalrd]

Originally Posted by Schnabel

I found an error in your code, let's debug:


In this setting, 33 is your variable (assuming you defined it earlier). Let's assume 33 is currently set to null. In your example above, you are saying "If set 33 to Team then call Win" However Team is not a valid variable, instead it should be 'Team'. So that would kill you first. THEN you are setting 33 to Team, I think you would rather do a Binary test now wouldn't you? You would rather it be "If 33 is Team then call Win" which would require double =. So for this statement to function properly, you should have wrote:
If (33 == 'Team') WIN();
.
.
.
.
.
.
.
.
.
.
.
.
.
.

I disagree. == is not =.
= sets one variable to another. == checks for a comparison. so I am checking that team is equal to 33, if it is, then win. The order does not matter.
Actually, in C (or C++), it is better to put the constant before the variable, in case you forget the second =, so the compiler will give you an error for setting a constant instead of getting some crazy error at runtime.

EDIT: I see that BJC forgot the second =. The actual one says "if (33==team) win();"

[GaryVoshol]

Originally Posted by Carolyn_Grace

It just said, "Einstein?" during the division finals. We were being hopeful. hehe
We didn't change the signs inbetween matches of each round of the eliminations, as we didn't want to take away time from Pit Crew's much needed robot assessments.

Yes, I remember coming over to your mini-pit at Troy during elims, wondering if you were needing a time-out, only to see the robot was upended to tape on a new sign.

[delsaner]

Originally Posted by BJC

It's a Michigan thing

Originally Posted by Basel A

You haven't been to Michigan have you?

Oh how I would LOVE to volunteer at MSC. It appears that Michigan knows how to have some fun (and of course how to build good robots too).

Originally Posted by hektormagee

We at Team RUSH like to keep everyone on their feet and having fun. It's nice for us scouters, too, as we get to stretch our legs. Remember Dave's way of shaking his thing? I laughed so hard. Glad people enjoy our cheers, Now we need to get the rest of the championship teams to do the cheer with us!

Hey Rush! Hey Pi! Hey Rush! Hey Pi!

[Andrew Schreiber]

Originally Posted by Schnabel

I found an error in your code, let's debug:


In this setting, 33 is your variable (assuming you defined it earlier). Let's assume 33 is currently set to null. In your example above, you are saying "If set 33 to Team then call Win" However Team is not a valid variable, instead it should be 'Team'. So that would kill you first. THEN you are setting 33 to Team, I think you would rather do a Binary test now wouldn't you? You would rather it be "If 33 is Team then call Win" which would require double =. So for this statement to function properly, you should have wrote:
If (33 == 'Team') WIN();

Originally Posted by apalrd

I disagree. == is not =.
= sets one variable to another. == checks for a comparison. so I am checking that team is equal to 33, if it is, then win. The order does not matter.
Actually, in C (or C++), it is better to put the constant before the variable, in case you forget the second =, so the compiler will give you an error for setting a constant instead of getting some crazy error at runtime.

EDIT: I see that BJC forgot the second =. The actual one says "if (33==team) win();"

Language dependent. For example, in one of the languages I use for "fun" development checking for equality between numbers is done with the syntax: (= 33 Team).

But Andrew does make a good point, writing it Constant == variable is a great way of making the compiler check for your typos in C/C++. Why do more work when you can make a computer do it for ya?


33, will there bee more unique ones for offseason events?

[BJC]

Originally Posted by Andrew Schreiber

33, will there bee more unique ones for offseason events?

I'm sure there will be!

[Schnabel]

Originally Posted by apalrd

I disagree. == is not =.
= sets one variable to another. == checks for a comparison. so I am checking that team is equal to 33, if it is, then win. The order does not matter.
Actually, in C (or C++), it is better to put the constant before the variable, in case you forget the second =, so the compiler will give you an error for setting a constant instead of getting some crazy error at runtime.

EDIT: I see that BJC forgot the second =. The actual one says "if (33==team) win();"

JAVA developer here. That's actually the point I was trying to make, you need the == to compare. I've never played with C or C++, so I have no clue yet.

[allyourbaseFRC]

Originally Posted by BJC

I'm sure there will be!

YAY! I look forward to it! we love you, bees