Go to Post Mmmmmmmm. Donuts! - Sean Schuff [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 01-09-2007, 08:37 PM
amateurrobotguy's Avatar
amateurrobotguy amateurrobotguy is offline
Lead Programmer/Senior Engineer
no team
 
Join Date: Feb 2005
Rookie Year: 2000
Location: ****
Posts: 136
amateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these parts
Why should I update my 2006 code?

It seems like all of the things Kevin kindly updated, I already did myself last season:

" Altered tracking algorithm to use the t-packet confidence value to
determine whether the code should track or search.

Added Get_Tracking_State() function, which can be used to determine
if the camera is pointing at the target."

" Provided two new functions to set the pan and tilt servo position.
This was done to provide a level of indirection so that the servos
could be controlled from the robot controller or the CMUcam2."

I saw that t-packet confidence could be useful, and added it to the if() in tracking.c before it romped off tracking the "target". I also don't need a Get_Tracking_State() as I just check to see if tpackets.my = 1 before I let it go go romping off tracking. And yeah, I noticed that some of the PWM values were fuzzy as well while testing. But, I just changed tracking.h around and got it to work fine.

" Fixed bug in search initialization code where temp_pan_servo was
initialized to zero instead of Tracking_Config_Data.Pan_Min_PWM."

Hmmm, didn't really have any problems with this.

Am I missing something huge here? Is there really any need to update?
__________________
I quit FRC over 2 years ago (more if you're reading this past 2010).
  #2   Spotlight this post!  
Unread 01-09-2007, 08:43 PM
Dave Flowerday Dave Flowerday is offline
Software Engineer
VRC #0111 (Wildstang)
Team Role: Engineer
 
Join Date: Feb 2002
Rookie Year: 1995
Location: North Barrington, IL
Posts: 1,366
Dave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond repute
Re: Why should I update my 2006 code?

Quote:
Originally Posted by amateurrobotguy View Post
Is there really any need to update?
Yes - you are not allowed to reuse the code you wrote last year:

Quote:
Originally Posted by R76
Unaltered software modules developed during prior competitions can not be directly reused. Just as designs for hardware COMPONENTS may be reused from one year to the next, software algorithms and designs may be reused. However, the specific lines of code must be customized for each ROBOT each year.
  #3   Spotlight this post!  
Unread 01-09-2007, 08:53 PM
amateurrobotguy's Avatar
amateurrobotguy amateurrobotguy is offline
Lead Programmer/Senior Engineer
no team
 
Join Date: Feb 2005
Rookie Year: 2000
Location: ****
Posts: 136
amateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these parts
Re: Why should I update my 2006 code?

I think that that rule is just there to stop teams from "generic" coding their bot off-season. Just as building a bot off season is not allowed, I agree, the same should apply to the code behind the bot. However, since 95% of my code was not specific to "Aim-High", it can be reused via cut and paste. Am I correct in saying this?
__________________
I quit FRC over 2 years ago (more if you're reading this past 2010).

Last edited by amateurrobotguy : 01-09-2007 at 09:01 PM.
  #4   Spotlight this post!  
Unread 01-09-2007, 08:59 PM
jgannon's Avatar
jgannon jgannon is offline
I ᐸ3 Robots
AKA: Joey Gannon
no team
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Pittsburgh, PA
Posts: 1,467
jgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond reputejgannon has a reputation beyond repute
Re: Why should I update my 2006 code?

As Dave points out, this is rule <R76>, which is on page 24 of section 8. This rule was definitely in effect last year, too. It came part and parcel with the whole Fix-it Window revolution. As far as lawyering it, the rule is pretty clear in saying that while the design can be reused, the actual lines of code cannot.
__________________
Team 1743 - The Short Circuits
2010 Pittsburgh Excellence in Design & Team Spirit Awards
2009 Pittsburgh Regional Champions (thanks to 222 and 1218)
2007 Pittsburgh Website Award
2006 Pittsburgh Regional Champions (thanks to 395 and 1038)
2006 Pittsburgh Rookie Inspiration & Highest Rookie Seed

Team 1388 - Eagle Robotics
2005 Sacramento Engineering Inspiration
2004 Curie Division Champions (thanks to 1038 and 175)
2004 Sacramento Rookie All-Star

_
  #5   Spotlight this post!  
Unread 01-09-2007, 09:09 PM
amateurrobotguy's Avatar
amateurrobotguy amateurrobotguy is offline
Lead Programmer/Senior Engineer
no team
 
Join Date: Feb 2005
Rookie Year: 2000
Location: ****
Posts: 136
amateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these partsamateurrobotguy is infamous around these parts
Re: Why should I update my 2006 code?

It says designs AND algorithms may be reused. So as long as I take out the code for the shooter, I am not violating the rule.
__________________
I quit FRC over 2 years ago (more if you're reading this past 2010).
Closed Thread


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Why Ref’s should always throw flags BLCamp Championship Event 8 05-11-2006 08:19 AM
Master code update Eldarion Control System 1 03-09-2006 09:14 PM
Why should Andy be on Survivor? George1902 General Forum 24 06-21-2004 01:19 AM
What Features Should the Default Code REALLY include? Joe Johnson Programming 30 04-29-2004 10:39 PM
Why I think FIRST should reconsider... Joe Johnson General Forum 36 01-14-2003 03:51 PM


All times are GMT -5. The time now is 03:17 PM.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi