2007 Default Code?

[Binome]

Anyone know where it is?

[teh_pwnerer795]

lmao... i guess its in the box with all of software

[Davx]

The 2006 code is availible at IFI Robotics, and although the 2007 RC is likely to come with a different version, the general structure will no doubt be the same. If you're just looking for a platform the start development, the 2006 user code is a good place to start. You should only have to copy over your user-created files and anything you add to User_Routines.c and User_Routines_fast.c.

[Kingofl337]

The 2007 Code for easyC will be posted on: http://www.intelitekdownloads.com/easyCPRO/

[Alexa Stott]

Kevin's code is up on his site. Scroll down a bit to find it.

[paulcd2000]

where? that's 2006 at the bottom

[Ctrl Alt Delete]

Can't seem to find default code for 2007 yet. Anyone know where I can find it or will find it eventually?

[Davx]

The default code is generally found at IFI Robotics. The 2006 code was last updated on 12/28/06, so it's likely that the 2007 code is not very (if at all) different. This is where the code would be most likely to show up if the 2007 is any different. Seeing as the controller has not changed for the 2007 season, I'd guess there is no change in the default code.

[Ctrl Alt Delete]

Thanks. I realized that after I thought about it. The controllers changed from 04 and 05 though. We figured that out the hard way last week!
I guess I'll be testing it out in FusionEdit.

EDIT: If it came out in December then they made two spelling mistakes on the site. The download file is 2-28 and it says right next to it 21-28.

[amateurrobotguy]

I believe the 2006 code IS the 2007 code. Seeing as MPLAB compiler version and IDE did not change from last year, I would assume that everything works the same. Check Kevin's site. The files were updated last year, but now say "2007 Default".

That is convenient for us proggers as we don't have to port our already running cam routines Now...to work with 2 lights at the same time *rubs chin*

[Kevin Watson]

Originally Posted by amateurrobotguy

That is convenient for us proggers as we don't have to port our already running cam routines

Yes, exactly. Last year Dave dropped the hint that the CUMcam2 would be back, and I'm hoping teams have spent some time in the off-season working with the camera.

Originally Posted by amateurrobotguy

Now...to work with 2 lights at the same time *rubs chin*

The best thing to do at this point is to spend some time thinking about what the camera will "see" from the starting area. It's important to know a few things:

1) The camera has a very wide field of view of ~60 degrees.
2) The camera will not always "see" two lights. Recent data taken on a regulation field shows that the camera will only detect a single light if it's within about +/- 25 degrees of rotation relative to the camera.
3) If two lights are detected by the camera, the camera will return a single rectangle around both lights.
4) If only one light is detected by the camera, the number of pixels reported by the camera will be small (~10).

-Kevin

[chris31]

Originally Posted by Kevin Watson

The best thing to do at this point is to spend some time thinking about what the camera will "see" from the starting area. It's important to know a few things:

I thought the rule was we are not allowed to reuse code. Ill have to check this years manual though.

[Astronouth7303]

Originally Posted by chris31

I thought the rule was we are not allowed to reuse code. Ill have to check this years manual though.

This rule has always been vague and debated. Use good judgment (and GP).

My personal policy is that: (1) You should be allowed to use any libraries you (or anyone else) have developed; (2) You can copy/paste trivial snippets that, if developed from scratch, would look nearly identical anyway.

Of course, using previous code as a guide to writing this year's code is perfectly fine, IMHO. (I haven't gotten to that section of the manual yet.)

Also, retyping should be considered the same as copy/pasting. This goes for competitions as well. If you bring print outs of code that you just type into the laptop, why not just bring a flash drive with the files? The manual is pretty clear, though, that writing code during the fix-it windows for your specific robot is off-limits. You may design, structure, outline, etc. code. See the section on the robot for details.

[Mike Copioli]

Yes, exactly. Last year Dave dropped the hint that the CUMcam2 would be back, and I'm hoping teams have spent some time in the off-season working with the camera.

Originally Posted by Kevin Watson

The best thing to do at this point is to spend some time thinking about what the camera will "see" from the starting area. It's important to know a few things:

1) The camera has a very wide field of view of ~60 degrees.
2) The camera will not always "see" two lights. Recent data taken on a regulation field shows that the camera will only detect a single light if it's within about +/- 25 degrees of rotation relative to the camera.
3) If two lights are detected by the camera, the camera will return a single rectangle around both lights.
4) If only one light is detected by the camera, the number of pixels reported by the camera will be small (~10).

-Kevin

Kevin, There seems to be some confusion about this years camera code. At the kickoff we were all told that this years camera code could support multiple targets. Is this the case? And if so. How? The code on your repository appears to be no different than last years. Does the new code independantly track multiple centroids? Or does it average the independant targets to produce one centroid? From the above statement it appears that the only way to differentiate between multiple and isolated targets is by the number of pixels. If two targets are "seen" by the camera, how do you direct the camera to select one of the targets?

[Joel J]

It seems to just average the centroids of both targets (so if it finds two lights, then following the centroid sent back would have you heading towards one of the "un lighted" columns). If the pixel count indicates the presence of two targets, you would possibly have to rotate the camera to home in on only one, then track again.

edit: I'm kinda curious how this announced feature works, as well. I shouldn't speculate based only on what I've seen.