Update #19

[Beth Sweet]

Yay! An update that is pretty likely not to be controversial!

[Lil' Lavery]

Originally Posted by Beth Sweet

Yay! An update that is pretty likely not to be controversial!

Someone will find a way to flame FIRST.

Originally Posted by Lil' Lavery

Someone will find a way to flame FIRST.

But that wouldn't be cool... Because they are doing their best. Many times people don't give them enough credit. (I used to be one of them, then I volunteered for field crew at SVR... it takes a lot more than people think to run something like this, so cut them some slack!)

[Billfred]

Originally Posted by Lil' Lavery

Someone will find a way to flame FIRST.

Since someone extended the challenge...

[sarcasm][argument="Colbertian"]Why wasn't this part of the practice schedule from day one in 2005? For fifteen weeks of competition now, we've been forced to take guesses at the exact values on the field--and now, only two weeks of regional competitions will get a benefit from it. Now there's going to be a HUGE advantage for teams that have this extra hour of testing time when they get to Atlanta! The sky is, in fact, falling![/argument][/sarcasm]

I'm glad FIRST has seen the light about helping us to see the light.

[StephLee]

That's an excellent idea, I'm glad they've made it available. It'll help out a lot of teams in the next two weeks, I'm sure.

[chrisstruttmann]

This is good. Team Voltage never had trouble seeing the green light, we just saw the ceiling spot lights every once and a while. The software team had to scramble to do some code changes, but hey, that's what we're used to.

--Chris

[Corey Balint]

Originally Posted by Billfred

Since someone extended the challenge...

[sarcasm][argument="Colbertian"]Why wasn't this part of the practice schedule from day one in 2005? For fifteen weeks of competition now, we've been forced to take guesses at the exact values on the field--and now, only two weeks of regional competitions will get a benefit from it. Now there's going to be a HUGE advantage for teams that have this extra hour of testing time when they get to Atlanta! The sky is, in fact, falling![/argument][/sarcasm]

I'm glad FIRST has seen the light about helping us to see the light.

Actually, you can make a legit arguement here. While I dont care really, I just feel like playing Devil's Advocate. This could have been very important to teams heavily reliant on cameras in the first three weeks, and ultimately cost a team a trip to Atlanta because their guidance system wasn't working as fluidly as hoped, and therefore lost, instead of winning the Championship. We all know one ring could be huge in Finals this year...

[StephLee]

Originally Posted by Corey Balint

Actually, you can make a legit arguement here. While I dont care really, I just feel like playing Devil's Advocate. This could have been very important to teams heavily reliant on cameras in the first three weeks, and ultimately cost a team a trip to Atlanta because their guidance system wasn't working as fluidly as hoped, and therefore lost, instead of winning the Championship. We all know one ring could be huge in Finals this year...

One tube can also be important when you score five in teleoperated mode and only needed that sixth to turn the match around and beat the two ramp lifts your opponents had...

[Nawaid Ladak]

if u want us to work on our autonomous, why not just let us stack. (reference back to Update 18)

[Billfred]

Originally Posted by FreedomForce

if u want us to work on our autonomous, why not just let us stack. (reference back to Update 18)

Perhaps I'm missing something here--what does stacking have to do with autonomous? Unless, of course, you're thinking about having stacked robots function as one unit in autonomous...but I would classify such a strategy as highly unlikely.

As I see it, it's an hour. Furthermore, it's an hour that you can't use for working on the robot in other areas--like everything else, it's a tradeoff. It won't in and of itself get any teams scoring ringers, unless they've got some magic fingers on the keyboard.

[Taylor]

For those making the argument (mostly satirically so) that week 4,5,6 regionals have an advantage over 1,2,3, remember this. All robots in 1,2,3 had the same (dis)advantage of not having that hour for calibration. All robots in 4,5,6 have the same (dis)advantage of having that hour. Each regional was fair in and of itself; the winning alliances are true. No robot in a regional had an advantage over another robot in that same regional due to the hour of calibrations.

Likewise, no 4,5,6 team will have an advantage over a 1,2,3 team because the Atlanta field lighting will be different from all regionals. Teams will still have to calibrate to Atlanta conditions, no matter what or how many regionals they attended.
Similarly, I don't think rules imposed by head ref(s) at any particular regional had an adverse effect on the outcome of the event. All teams in a regional had to play by the same rules (misguided as though they may be). Only when one team experiences intentional favortism over another due to intentional inconsistency of judging calls does one team profit while another suffers.

[for what it's worth] I think FIRST has done a great job of showing they acknowledge they can make mistakes, and they are willing to analyze and possibly fix those mistakes if possible. Let's just hope we don't get Update #26 during the championships.

[marccenter]

I just wish this rule was in effect at the Detroit Regional. I specifically went up to the head judge and asked if I could get on the practice field after Thursday 5 pm matches were completed to calibrate the camera and he said no, because of FIRST rules. I am glad that FIRST has allowed this change for all of us folks working hard on trying to make the camera work. Unfortunately, that was my last tournament to work on the camera. Maybe, next Year!

[JohnBoucher]

Did this testing period help anyone?

Who went onto the field and tested values and how different were they from what you had?

Any idea how this will play out in Atlanta?

[heydowns]

Originally Posted by JohnBoucher

Did this testing period help anyone?

Who went onto the field and tested values and how different were they from what you had?

Any idea how this will play out in Atlanta?

We had no luck locking onto the vision target on Thursday of Boston regional. We were using the default values from Kevin Watson's camera code, which had worked fine for us last year and during build season this year.

Within a few minutes of being on the field, we rapidly realized the source of the problem.... The venue for Boston regional is an ice hockey arena, with electronic banners around the arena. The banners are at a height such that when you project the vision of the camera beyond the green vision target, the banners are in direct view.

They were running the banners with FIRST-related messages, most of which had a bright white background. This background had the same green component as the vision target (much like you get with florescent lights commonly found in, say, high school hallways )

Most of the time this resulted in really big bounding areas for the "tracked" object, but low pixel counts, resulting in very low confidence values. This causes the camera servo handling code to continue to look around the venue for a better match, which it never finds since it is bombarded with large-area matches.

One match, though, we actually locked completely on the banner and the robot drove down along the side of the rack, trying to get "close enough" to score

We corrected the problem by clamping down the tolerance of our YCbCr values (R, G, B min/max) for the green light to +/- 10 I believe. This resulted in less pixel matches over the actual vision target, but we had far less false positives than before. Once this was in place, the servo tracking code had good enough confidence to follow the actual green vision target.

This was possible only because we had the on-field time.

After getting it working, we helped out 2 other teams having similar problems. AFAIK, lowering the tolerance worked for them, too. We saw at least 4 other teams also taking advantage of this on-field opportunity.

For those who have trouble using the LabView app for camera calibration, or simply don't have LabView available, we use the CMUCam2GUI application from the creators of the CMUCam (google it) with good results.

[Mike Betts]

Originally Posted by heydowns

...This was possible only because we had the on-field time...

Please be sure that you feed this info back to FIRST via your Regional Committee Chair. FIRST needs to know that it was useful...

Regards,

Mike