<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://www.wiki.prhsrobotics.com/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.wiki.prhsrobotics.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jane</id>
		<title>RoboWiki - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://www.wiki.prhsrobotics.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jane"/>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Special:Contributions/Jane"/>
		<updated>2026-04-27T00:02:28Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.22.13</generator>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Nabil_Khan</id>
		<title>Nabil Khan</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Nabil_Khan"/>
				<updated>2017-11-09T02:15:03Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= nabil.jpg&lt;br /&gt;
|Gender=male&lt;br /&gt;
|MemberInYear=2013,2014,2015, 2016&lt;br /&gt;
|FreshmanInYear=2013&lt;br /&gt;
|SophomoreInYear=2014&lt;br /&gt;
|JuniorInYear=2015&lt;br /&gt;
|SeniorInYear=2016&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
|College=Georgia State University&lt;br /&gt;
|OfficerPosition=[[President]] in 2016 &amp;lt;br&amp;gt; [[Treasurer]] in 2015 &lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Nabil is a vivid, fun-loving member who actively participated in team events and was not afraid to be silly. He also happens to find citrus in disposable cups hilarious.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Got You Involved in the Team?==&lt;br /&gt;
I had Ms. Rutland as a Chemistry teacher, and she told us about it and I thought it sounded like fun so I started coming to meetings, and it was a lot of fun and I made a lot of friends.&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
My dad because he came here from another country with nothing but clothes and a few dollars in hand, and has become extremely successful.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
I plan to be a hobo.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
I play guitar, basketball, and video games in my free time.&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
MAO/math team, and Science National Honor Society&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
After I graduate from college I would like to get a good job, and be able to support my self.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;Fabrice Navidad.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
When I was put into a trash can by Aakash, Andy, and Greg and Dr. Tashlein came and pulled me out.&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/Mechanical]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Nabil_Khan</id>
		<title>Nabil Khan</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Nabil_Khan"/>
				<updated>2017-11-09T02:12:58Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= nabil.jpg&lt;br /&gt;
|Gender=male&lt;br /&gt;
|MemberInYear=2013,2014,2015, 2016&lt;br /&gt;
|FreshmanInYear=2013&lt;br /&gt;
|SophomoreInYear=2014&lt;br /&gt;
|JuniorInYear=2015&lt;br /&gt;
|SeniorInYear=2016&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
|College=Georgia State University&lt;br /&gt;
|OfficerPosition=[[President]] in 2016 &amp;lt;br&amp;gt; [[Treasurer]] in 2015 &amp;lt;br&amp;gt; [[Vice-President of Communications|VP of Communications]] in 2014&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Nabil is a vivid, fun-loving member who actively participated in team events and was not afraid to be silly. He also happens to find citrus in disposable cups hilarious.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Got You Involved in the Team?==&lt;br /&gt;
I had Ms. Rutland as a Chemistry teacher, and she told us about it and I thought it sounded like fun so I started coming to meetings, and it was a lot of fun and I made a lot of friends.&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
My dad because he came here from another country with nothing but clothes and a few dollars in hand, and has become extremely successful.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
I plan to be a hobo.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
I play guitar, basketball, and video games in my free time.&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
MAO/math team, and Science National Honor Society&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
After I graduate from college I would like to get a good job, and be able to support my self.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;Fabrice Navidad.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
When I was put into a trash can by Aakash, Andy, and Greg and Dr. Tashlein came and pulled me out.&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/Mechanical]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2012</id>
		<title>2012</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2012"/>
				<updated>2017-03-10T17:29:49Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Peachtree Regional */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
In this year, the Robo Lions competed in both [[FIRST Robotics Competition|FRC]] and [[VEX Robotics Competition|VRC]].&lt;br /&gt;
&lt;br /&gt;
[[File:2012_TeamPicture.jpg|300px|thumb|right|Robo Lions team picture.]]&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
*President: [[president::Sehyun Han]]&lt;br /&gt;
*Vice-President: [[vice-president::Andrew Shaw]]&lt;br /&gt;
*Secretary: [[secretary::Bailey Bercik]]&lt;br /&gt;
*Treasurer: [[treasurer::Ryan Mar]]&lt;br /&gt;
*Historian: [[historian::Brittany Davis]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2012}}&lt;br /&gt;
&lt;br /&gt;
==Fall Activities==&lt;br /&gt;
===VEX Robotics Competition===&lt;br /&gt;
The [[2011]] - [[2012]] VEX game was [[2011 Gateway | Gateway]].&lt;br /&gt;
====Peachtree Regional VEX Qualifier====&lt;br /&gt;
&lt;br /&gt;
===Georgia Robotics Invitational Tournament and Showcase===&lt;br /&gt;
This year, the team competed in the [[Georgia Robotics Invitational Tournament and Showcase]], or GRITS, competition in the fall.&lt;br /&gt;
==FIRST Robotics Competition==&lt;br /&gt;
===Game===&lt;br /&gt;
[[2012 Rebound Rumble | Rebound Rumble]] was the FRC game of 2012.&lt;br /&gt;
&lt;br /&gt;
===Robots===&lt;br /&gt;
The team's competition robot was called Mar Madness in honor of alumni [[Ryan Mar]].&lt;br /&gt;
&lt;br /&gt;
===Field Team===&lt;br /&gt;
*Driver: [[driver::Vikram Chabbria]]&lt;br /&gt;
*Manipulator Driver: [[manipulator driver::Tyler Thornton]]&lt;br /&gt;
*Coach: [[coach::Katherine Li]]&lt;br /&gt;
*Human Player: [[human player::Fabrice Kengne]]&lt;br /&gt;
&lt;br /&gt;
===Regionals===&lt;br /&gt;
&lt;br /&gt;
====Smoky Mountain Regional====&lt;br /&gt;
The team went to the Smoky Mountain Regional in Knoxville, Tennessee as a way to test the robot before Peachtree.&lt;br /&gt;
&lt;br /&gt;
====Peachtree Regional====&lt;br /&gt;
The team then participated in the annual Peachtree Regional at the Civic Center in Suwanee, GA.&lt;br /&gt;
&lt;br /&gt;
This time, the team emerged victorious with teams {{TBA|2415}}WiredCats and {{TBA|687}}The Nerd Herd to qualify for the World Championships.&lt;br /&gt;
&lt;br /&gt;
====World Championships====&lt;br /&gt;
The team traveled to St. Louis for the FIRST World Championships.&lt;br /&gt;
&lt;br /&gt;
===Awards===&lt;br /&gt;
The Robo Lions won both the Peachtree Regional Regional Winner and the Peachtree Regional Creativity Award.&lt;br /&gt;
&lt;br /&gt;
==Off-Season Activities==&lt;br /&gt;
TBA&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2012}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2012]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2012]] [[gender::female]] | format=count}} &lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2012]] [[gender::male]] | format=count}} &lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2012]] | format=count}} &lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2012]][[member of robotics in year::2012]] | format=count}} &lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2012]][[member of robotics in year::2012]] | format=count}} &lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2012]][[member of robotics in year::2012]] | format=count}} &lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2012]][[member of robotics in year::2012]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2012}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2012|Team Members for 2012]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2012}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2016</id>
		<title>2016</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2016"/>
				<updated>2017-03-10T17:27:12Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* GirlsFIRST Event */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
[[File:2016AlbanyWin.jpg|400px|thumb|right|Team picture of the Robo Lions in 2016]]&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
*President: [[president::Nabil Khan]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Preston Shaw]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[secretary::Jane Khampha]]&lt;br /&gt;
*Treasurer: [[treasurer::Sumedh Garimella]]&lt;br /&gt;
*Historian: [[historian::Rebeca Rodila]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Rishov Sarkar]]&lt;br /&gt;
*Webmaster: [[webmaster:: Sumaer Sahney]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Fall Activities==&lt;br /&gt;
''This was the year that the [[Attendance Clock]] was first implemented to log hours to go towards membership Robotics lettering. It was initiated by [[Scott Karlins]] (mentor of the team and father to [[Bryce Karlins]]), and then is managed by the [[Vice-President of Communications]] as well as the [[Secretary]]''&lt;br /&gt;
&lt;br /&gt;
===VEX Robotics Competition===&lt;br /&gt;
The game in the [[2015]]-[[2016]] season was [[2015 Nothing but Net | Nothing but Net]].&lt;br /&gt;
&lt;br /&gt;
===Robots at the Ridge===&lt;br /&gt;
We had a blast at our Robots at the Ridge VEX competition on Saturday, November 21st, at Peachtree Ridge High School. We had one of our VEX teams make it to the quarter-finals, but sadly not any further. Of course, at the end of the day, the [[2016]] Robo Lion members had a blast, made new friends, and some of them can't wait to start year-long VEX! We would like to thank all teams that were in attendance, as well as all the volunteers who graciously supported us throughout the event.&lt;br /&gt;
We congratulate our award winners:&lt;br /&gt;
*Tournament Champion: Team Woodward (1900R) from Woodward Academy&lt;br /&gt;
*Tournament Champion: Team GMA (1900W) from Woodward Academy&lt;br /&gt;
*Tournament Champion: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
*Excellence Award: Raider Robotics (3536M) from North Forsyth High School&lt;br /&gt;
*Judges’ Award: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
Rebeca, our [[2016]] historian, made a video recap on all the activities this year's Robo Lions were involved in.&lt;br /&gt;
&lt;br /&gt;
Curious to see all the fun? Watch it [https://drive.google.com/file/d/0B3JRwrlB1bJdUzUwRHlZOVVpN1k/view?usp=sharing here]&lt;br /&gt;
&lt;br /&gt;
==Fun Facts==&lt;br /&gt;
===Robot Rock Parody Video===&lt;br /&gt;
Over Thanksgiving Break, some members of the team got together and made a video for FIRST's 2015 Song Parody Competition.&lt;br /&gt;
&lt;br /&gt;
More info about the competition [http://www.firstinspires.org/robotics/2015-first-song-parody-competition here] &lt;br /&gt;
&lt;br /&gt;
Watch Robot Rock [https://www.youtube.com/watch?v=ybaGaAJepHY here]&lt;br /&gt;
&lt;br /&gt;
===Gwinnett Daily Post Interview===&lt;br /&gt;
The team was interviewed by Gwinnett Daily Post on November 11.&lt;br /&gt;
&lt;br /&gt;
View the full article [http://www.gwinnettdailypost.com/local/cities/duluth/with-qualifer-on-tap-peachtree-ridge-stretches-its-robotics-reach/article_6899e404-d7e5-589c-b45d-801ff2788ba6.html here]&lt;br /&gt;
&lt;br /&gt;
[[File:WaltonCollab.jpg|200px|thumb|right| Walton Collab 2k16]]&lt;br /&gt;
&lt;br /&gt;
==FIRST Robotics Competition==&lt;br /&gt;
The [[2016]] [[FRC]] Game was [[2016 FIRST Stronghold | FIRST Stronghold]].&lt;br /&gt;
===Brainstorm with Walton===&lt;br /&gt;
[[File:WaltonLove.jpg|200px|thumb|right|Walton Love 2k16]]&lt;br /&gt;
On January 10, 2016, the Robo Lions invited Walton Robotics over to collaborate on game strategies. Here are some pictures of Walton spreading the love.&lt;br /&gt;
&lt;br /&gt;
===Robots===&lt;br /&gt;
This year's robot is Khanquistador. View his reveal video [https://www.youtube.com/watch?v=HsSBCBPBLJs here].&lt;br /&gt;
&lt;br /&gt;
===Field Team===&lt;br /&gt;
The [[2016]] field team consisted of:&lt;br /&gt;
*Driver: [[driver::Preston Shaw]]&lt;br /&gt;
*Manipulator Driver: [[manipulator driver::Nabil Khan]]&lt;br /&gt;
*Coach: [[coach::Mackenzie Glaser]]&lt;br /&gt;
*Human Player: [[human player::Joel Leonardo]]&lt;br /&gt;
&lt;br /&gt;
===Districts===&lt;br /&gt;
The Georgia district model was adopted first in [[2016]], and it allowed for Georgia [[FRC]] teams to compete in-state. The Robo Lions chose to compete in 3 of the 4 available competitive events in this year: Columbus, Albany, and Kennesaw.&lt;br /&gt;
====Columbus====&lt;br /&gt;
During the weekend of March 10-12, the team headed down to Columbus to compete in the week 2 Peachtree District Qualifier. Along with their alliance Captain {{TBA|5332}}and alliance partner {{TBA|4240}}, we were able to make it all the way to the semfinals!&lt;br /&gt;
&lt;br /&gt;
====Albany====&lt;br /&gt;
The team won the tournament at the Albany District Event! Allied with teams {{TBA|3329}}and {{TBA|5651}}, we were able to rise out on top ''and'' set the record for the highest score in Georgia! The team also won the District Chairman’s Award, becoming the first team in Gwinnett County to ever win the award, giving us our second Blue Banner and automatically qualifying us for the Peachtree District State Championships. The Robo Lions were also awarded the UL Industrial Safety Award. In addition, two Robo Lions’ team members, [[Caroline Means]] and [[Mackenzie Glaser]], were named Deans List Finalists.&lt;br /&gt;
&lt;br /&gt;
====Kennesaw====&lt;br /&gt;
While it may have been Spring Break, the team topped the charts with a great win at the Kennesaw District Event, competing with a total of thirty-five other in-state teams. Having been selected by  alliance captain {{TBA|1746}}OTTO Robotics from Cumming, Ga and working alongside alliance partner {{TBA|5812}}Drewbotics from Riverdale, Ga, the teams proved indestructible scoring a whopping 154 points in the final match! With the use of vision tracking that allowed for precise high goal shots and aggressive driving skills that dominated the field, the team also won the Excellence in Engineering award sponsored by Delphi. &lt;br /&gt;
&lt;br /&gt;
===Peachtree District State Championships===&lt;br /&gt;
Having faced off against competitors of the 41 best teams throughout the state of Georgia, the team was placed as the third-seed alliance captain and made it through six rigorous playoff matches with alliance partners {{TBA|2415}}Westminster Wired Cats from Atlanta, Ga and {{TBA|4516}}Hyperion Robotics from Roswell, Ga, before losing in the Finals, but not before setting an unbeatable high score of 170 points!  The team was also awarded with the Innovation in Control Awared sponsored by Rockwell Automation, and was crowned the second ranked team in Georgia. Because of this, the team was one of twelve teams in Georgia to qualify for the World Championships to be help in St. Louis, Missouri, but the only team in Gwinnett County to do so! &lt;br /&gt;
&lt;br /&gt;
===FIRST World Championships===&lt;br /&gt;
The team was able to qualify for the FIRST Robotics World Championships that took place in St. Louis, Missouri towards the end of April. We were one of just twelve Georgia FRC teams to qualify and made it farther than we have ever done before! Clawing our way through two days of qualification matches, we placed thirteenth out of seventy-five competing teams within the Curie division. From there, they were chosen to join the 5th seed alliance captain Team {{TBA|5406}}Celt-X from Hamilton, Ontario, Canada and their alliance partners Team 3641 Flying Toasters from South Lyon, Michigan. Team {{TBA|2883}}F.R.E.D from Warroad, Minnesota was chosen to be the backup 4th robot on the alliance. The determined trio fought hard only to be stopped short in the second semi-final match, losing by a small margin. However, this still marks the farthest we've ever gotten at Worlds!&lt;br /&gt;
&lt;br /&gt;
===Awards===&lt;br /&gt;
*Industrial Design Award sponsored by General Motors at Columbus&lt;br /&gt;
*Ul Industrial Safety Hard Hat Pin at Albany&lt;br /&gt;
*Chairman's Award at Albany&lt;br /&gt;
*District Winners at Albany&lt;br /&gt;
*District Winners at Kennesaw&lt;br /&gt;
*Excellence in Engineering Award sponsored by Delphi at Kennesaw&lt;br /&gt;
*Semi-Finalists at State&lt;br /&gt;
*Innovation in Control Award sponsored by Rockwell Automation at State&lt;br /&gt;
*Semi-Finalists at the [[FIRST]] World Championships&lt;br /&gt;
&lt;br /&gt;
Check out more of our awards [[Awards | here]].&lt;br /&gt;
&lt;br /&gt;
==Off-Season Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
GRITS this year was held at Walton High School on October 10th, where the Robo Lions were able to score as runner-ups, along with alliance captain {{TBA|1648}}G3 Robotics and{{TBA|4189}}Chargers. The team also took home the Outreach Award, representing with over 25 rookie attendees.&lt;br /&gt;
&lt;br /&gt;
===GirlsFIRST Event===&lt;br /&gt;
On October 17th, 2015 Walton High School (FRC Team {{TBA|2974}})hosted a GirlsFIRST workshop to bond with local robotics teams as well as anyone interested from the surrounding communities. There were engineering contests, guest speakers from women in technology, driver practice with robots from past games, and tons of big smiles! A small group of girls on our team were glad that they got to participate in such an amazing event.&lt;br /&gt;
&lt;br /&gt;
==Spring Activities==&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
&lt;br /&gt;
[[File:2016_ParsonsSTEM.jpg|200px|thumb|right|The Robo Lions at Parsons STEM Night]]&lt;br /&gt;
&lt;br /&gt;
On Thursday, February 4th, the team headed next door to Parsons Elementary school for an awesome night of robotics demonstrations! Our new outreach VEX robot made its debut, shooting balls across the cafeteria. Many of the students were eager to bring the balls back and even got to try their hand at driving the robot. Genesis, the 2014 competition robot, served us well once as we watched students jump up to catch the ball. A huge thanks to Parsons for having us and to all of the Robo Lions who helped make this night run smoothly!&lt;br /&gt;
&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
Mason STEM Night- Members of the team brought a VEX Robot and the 2014 Aerial Assist Robot to Mason Elementary to participate in a robotics showcase alongside GSMST Robotics and the Mason FLL team. Students were excited to jump up to catch the ball as the robot launched it across the room while others drove the VEX robot. It was really great to see the new members of the team connect with the elementary students, making sure all were safe around the robot and even sharing a dance or two! Prior to the night, students helped judge science fair entries which were also on display for parents that night. We had tons of kids take interest in the robot and we really loved being able to connect the kids’ experiences with robotics to our own robotics experiences!&lt;br /&gt;
&lt;br /&gt;
===Burnette Science Night===&lt;br /&gt;
[[File:2016Burnette.jpg|200px|thumb|right|The Robo Lions at Burnette Science Night]]&lt;br /&gt;
On February 11th, the team attended their first Burnette Elementary’s Science Night. It was great to drive around our 2014 FRC robot and our VEX Outreach robot, as we had lots of interest and answered tons of great questions. We spoke with Ms. Reed, the Principal, about furthering their robotics program, and are excited to continue working with the school!&lt;br /&gt;
&lt;br /&gt;
===Lawrenceville Rotary Club Meeting===&lt;br /&gt;
Seven enthusiastic members of the Peachtree Ridge High School Robotics Team presented information about their activities to the Rotary Club of Lawrenceville on April 4. [[2016]] [[Drive Team]] and [[2016]] [[Executives |Executive Officers]] described how the competitions worked and how the group went about preparing their robots for the competitions. The group is not only about engineering and business tasks; it is about building relationships, developing leadership skills, engaging in teamwork, and outreaching within the community. They displayed two of their robots and showed a video about the “Robo Lions spirit” that won a prize at a recent competition.&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2016]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2016]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2016]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2016}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2016]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2016}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2016</id>
		<title>2016</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2016"/>
				<updated>2017-03-10T17:26:53Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* GRITS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
[[File:2016AlbanyWin.jpg|400px|thumb|right|Team picture of the Robo Lions in 2016]]&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
*President: [[president::Nabil Khan]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Preston Shaw]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[secretary::Jane Khampha]]&lt;br /&gt;
*Treasurer: [[treasurer::Sumedh Garimella]]&lt;br /&gt;
*Historian: [[historian::Rebeca Rodila]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Rishov Sarkar]]&lt;br /&gt;
*Webmaster: [[webmaster:: Sumaer Sahney]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Fall Activities==&lt;br /&gt;
''This was the year that the [[Attendance Clock]] was first implemented to log hours to go towards membership Robotics lettering. It was initiated by [[Scott Karlins]] (mentor of the team and father to [[Bryce Karlins]]), and then is managed by the [[Vice-President of Communications]] as well as the [[Secretary]]''&lt;br /&gt;
&lt;br /&gt;
===VEX Robotics Competition===&lt;br /&gt;
The game in the [[2015]]-[[2016]] season was [[2015 Nothing but Net | Nothing but Net]].&lt;br /&gt;
&lt;br /&gt;
===Robots at the Ridge===&lt;br /&gt;
We had a blast at our Robots at the Ridge VEX competition on Saturday, November 21st, at Peachtree Ridge High School. We had one of our VEX teams make it to the quarter-finals, but sadly not any further. Of course, at the end of the day, the [[2016]] Robo Lion members had a blast, made new friends, and some of them can't wait to start year-long VEX! We would like to thank all teams that were in attendance, as well as all the volunteers who graciously supported us throughout the event.&lt;br /&gt;
We congratulate our award winners:&lt;br /&gt;
*Tournament Champion: Team Woodward (1900R) from Woodward Academy&lt;br /&gt;
*Tournament Champion: Team GMA (1900W) from Woodward Academy&lt;br /&gt;
*Tournament Champion: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
*Excellence Award: Raider Robotics (3536M) from North Forsyth High School&lt;br /&gt;
*Judges’ Award: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
Rebeca, our [[2016]] historian, made a video recap on all the activities this year's Robo Lions were involved in.&lt;br /&gt;
&lt;br /&gt;
Curious to see all the fun? Watch it [https://drive.google.com/file/d/0B3JRwrlB1bJdUzUwRHlZOVVpN1k/view?usp=sharing here]&lt;br /&gt;
&lt;br /&gt;
==Fun Facts==&lt;br /&gt;
===Robot Rock Parody Video===&lt;br /&gt;
Over Thanksgiving Break, some members of the team got together and made a video for FIRST's 2015 Song Parody Competition.&lt;br /&gt;
&lt;br /&gt;
More info about the competition [http://www.firstinspires.org/robotics/2015-first-song-parody-competition here] &lt;br /&gt;
&lt;br /&gt;
Watch Robot Rock [https://www.youtube.com/watch?v=ybaGaAJepHY here]&lt;br /&gt;
&lt;br /&gt;
===Gwinnett Daily Post Interview===&lt;br /&gt;
The team was interviewed by Gwinnett Daily Post on November 11.&lt;br /&gt;
&lt;br /&gt;
View the full article [http://www.gwinnettdailypost.com/local/cities/duluth/with-qualifer-on-tap-peachtree-ridge-stretches-its-robotics-reach/article_6899e404-d7e5-589c-b45d-801ff2788ba6.html here]&lt;br /&gt;
&lt;br /&gt;
[[File:WaltonCollab.jpg|200px|thumb|right| Walton Collab 2k16]]&lt;br /&gt;
&lt;br /&gt;
==FIRST Robotics Competition==&lt;br /&gt;
The [[2016]] [[FRC]] Game was [[2016 FIRST Stronghold | FIRST Stronghold]].&lt;br /&gt;
===Brainstorm with Walton===&lt;br /&gt;
[[File:WaltonLove.jpg|200px|thumb|right|Walton Love 2k16]]&lt;br /&gt;
On January 10, 2016, the Robo Lions invited Walton Robotics over to collaborate on game strategies. Here are some pictures of Walton spreading the love.&lt;br /&gt;
&lt;br /&gt;
===Robots===&lt;br /&gt;
This year's robot is Khanquistador. View his reveal video [https://www.youtube.com/watch?v=HsSBCBPBLJs here].&lt;br /&gt;
&lt;br /&gt;
===Field Team===&lt;br /&gt;
The [[2016]] field team consisted of:&lt;br /&gt;
*Driver: [[driver::Preston Shaw]]&lt;br /&gt;
*Manipulator Driver: [[manipulator driver::Nabil Khan]]&lt;br /&gt;
*Coach: [[coach::Mackenzie Glaser]]&lt;br /&gt;
*Human Player: [[human player::Joel Leonardo]]&lt;br /&gt;
&lt;br /&gt;
===Districts===&lt;br /&gt;
The Georgia district model was adopted first in [[2016]], and it allowed for Georgia [[FRC]] teams to compete in-state. The Robo Lions chose to compete in 3 of the 4 available competitive events in this year: Columbus, Albany, and Kennesaw.&lt;br /&gt;
====Columbus====&lt;br /&gt;
During the weekend of March 10-12, the team headed down to Columbus to compete in the week 2 Peachtree District Qualifier. Along with their alliance Captain {{TBA|5332}}and alliance partner {{TBA|4240}}, we were able to make it all the way to the semfinals!&lt;br /&gt;
&lt;br /&gt;
====Albany====&lt;br /&gt;
The team won the tournament at the Albany District Event! Allied with teams {{TBA|3329}}and {{TBA|5651}}, we were able to rise out on top ''and'' set the record for the highest score in Georgia! The team also won the District Chairman’s Award, becoming the first team in Gwinnett County to ever win the award, giving us our second Blue Banner and automatically qualifying us for the Peachtree District State Championships. The Robo Lions were also awarded the UL Industrial Safety Award. In addition, two Robo Lions’ team members, [[Caroline Means]] and [[Mackenzie Glaser]], were named Deans List Finalists.&lt;br /&gt;
&lt;br /&gt;
====Kennesaw====&lt;br /&gt;
While it may have been Spring Break, the team topped the charts with a great win at the Kennesaw District Event, competing with a total of thirty-five other in-state teams. Having been selected by  alliance captain {{TBA|1746}}OTTO Robotics from Cumming, Ga and working alongside alliance partner {{TBA|5812}}Drewbotics from Riverdale, Ga, the teams proved indestructible scoring a whopping 154 points in the final match! With the use of vision tracking that allowed for precise high goal shots and aggressive driving skills that dominated the field, the team also won the Excellence in Engineering award sponsored by Delphi. &lt;br /&gt;
&lt;br /&gt;
===Peachtree District State Championships===&lt;br /&gt;
Having faced off against competitors of the 41 best teams throughout the state of Georgia, the team was placed as the third-seed alliance captain and made it through six rigorous playoff matches with alliance partners {{TBA|2415}}Westminster Wired Cats from Atlanta, Ga and {{TBA|4516}}Hyperion Robotics from Roswell, Ga, before losing in the Finals, but not before setting an unbeatable high score of 170 points!  The team was also awarded with the Innovation in Control Awared sponsored by Rockwell Automation, and was crowned the second ranked team in Georgia. Because of this, the team was one of twelve teams in Georgia to qualify for the World Championships to be help in St. Louis, Missouri, but the only team in Gwinnett County to do so! &lt;br /&gt;
&lt;br /&gt;
===FIRST World Championships===&lt;br /&gt;
The team was able to qualify for the FIRST Robotics World Championships that took place in St. Louis, Missouri towards the end of April. We were one of just twelve Georgia FRC teams to qualify and made it farther than we have ever done before! Clawing our way through two days of qualification matches, we placed thirteenth out of seventy-five competing teams within the Curie division. From there, they were chosen to join the 5th seed alliance captain Team {{TBA|5406}}Celt-X from Hamilton, Ontario, Canada and their alliance partners Team 3641 Flying Toasters from South Lyon, Michigan. Team {{TBA|2883}}F.R.E.D from Warroad, Minnesota was chosen to be the backup 4th robot on the alliance. The determined trio fought hard only to be stopped short in the second semi-final match, losing by a small margin. However, this still marks the farthest we've ever gotten at Worlds!&lt;br /&gt;
&lt;br /&gt;
===Awards===&lt;br /&gt;
*Industrial Design Award sponsored by General Motors at Columbus&lt;br /&gt;
*Ul Industrial Safety Hard Hat Pin at Albany&lt;br /&gt;
*Chairman's Award at Albany&lt;br /&gt;
*District Winners at Albany&lt;br /&gt;
*District Winners at Kennesaw&lt;br /&gt;
*Excellence in Engineering Award sponsored by Delphi at Kennesaw&lt;br /&gt;
*Semi-Finalists at State&lt;br /&gt;
*Innovation in Control Award sponsored by Rockwell Automation at State&lt;br /&gt;
*Semi-Finalists at the [[FIRST]] World Championships&lt;br /&gt;
&lt;br /&gt;
Check out more of our awards [[Awards | here]].&lt;br /&gt;
&lt;br /&gt;
==Off-Season Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
GRITS this year was held at Walton High School on October 10th, where the Robo Lions were able to score as runner-ups, along with alliance captain {{TBA|1648}}G3 Robotics and{{TBA|4189}}Chargers. The team also took home the Outreach Award, representing with over 25 rookie attendees.&lt;br /&gt;
&lt;br /&gt;
===GirlsFIRST Event===&lt;br /&gt;
On October 17th, 2015 Walton High School (FRC Team 2974) hosted a GirlsFIRST workshop to bond with local robotics teams as well as anyone interested from the surrounding communities. There were engineering contests, guest speakers from women in technology, driver practice with robots from past games, and tons of big smiles! A small group of girls on our team were glad that they got to participate in such an amazing event.&lt;br /&gt;
&lt;br /&gt;
==Spring Activities==&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
&lt;br /&gt;
[[File:2016_ParsonsSTEM.jpg|200px|thumb|right|The Robo Lions at Parsons STEM Night]]&lt;br /&gt;
&lt;br /&gt;
On Thursday, February 4th, the team headed next door to Parsons Elementary school for an awesome night of robotics demonstrations! Our new outreach VEX robot made its debut, shooting balls across the cafeteria. Many of the students were eager to bring the balls back and even got to try their hand at driving the robot. Genesis, the 2014 competition robot, served us well once as we watched students jump up to catch the ball. A huge thanks to Parsons for having us and to all of the Robo Lions who helped make this night run smoothly!&lt;br /&gt;
&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
Mason STEM Night- Members of the team brought a VEX Robot and the 2014 Aerial Assist Robot to Mason Elementary to participate in a robotics showcase alongside GSMST Robotics and the Mason FLL team. Students were excited to jump up to catch the ball as the robot launched it across the room while others drove the VEX robot. It was really great to see the new members of the team connect with the elementary students, making sure all were safe around the robot and even sharing a dance or two! Prior to the night, students helped judge science fair entries which were also on display for parents that night. We had tons of kids take interest in the robot and we really loved being able to connect the kids’ experiences with robotics to our own robotics experiences!&lt;br /&gt;
&lt;br /&gt;
===Burnette Science Night===&lt;br /&gt;
[[File:2016Burnette.jpg|200px|thumb|right|The Robo Lions at Burnette Science Night]]&lt;br /&gt;
On February 11th, the team attended their first Burnette Elementary’s Science Night. It was great to drive around our 2014 FRC robot and our VEX Outreach robot, as we had lots of interest and answered tons of great questions. We spoke with Ms. Reed, the Principal, about furthering their robotics program, and are excited to continue working with the school!&lt;br /&gt;
&lt;br /&gt;
===Lawrenceville Rotary Club Meeting===&lt;br /&gt;
Seven enthusiastic members of the Peachtree Ridge High School Robotics Team presented information about their activities to the Rotary Club of Lawrenceville on April 4. [[2016]] [[Drive Team]] and [[2016]] [[Executives |Executive Officers]] described how the competitions worked and how the group went about preparing their robots for the competitions. The group is not only about engineering and business tasks; it is about building relationships, developing leadership skills, engaging in teamwork, and outreaching within the community. They displayed two of their robots and showed a video about the “Robo Lions spirit” that won a prize at a recent competition.&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2016]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2016]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2016]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2016}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2016]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2016}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2016</id>
		<title>2016</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2016"/>
				<updated>2017-03-10T17:26:22Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* FIRST World Championships */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
[[File:2016AlbanyWin.jpg|400px|thumb|right|Team picture of the Robo Lions in 2016]]&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
*President: [[president::Nabil Khan]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Preston Shaw]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[secretary::Jane Khampha]]&lt;br /&gt;
*Treasurer: [[treasurer::Sumedh Garimella]]&lt;br /&gt;
*Historian: [[historian::Rebeca Rodila]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Rishov Sarkar]]&lt;br /&gt;
*Webmaster: [[webmaster:: Sumaer Sahney]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Fall Activities==&lt;br /&gt;
''This was the year that the [[Attendance Clock]] was first implemented to log hours to go towards membership Robotics lettering. It was initiated by [[Scott Karlins]] (mentor of the team and father to [[Bryce Karlins]]), and then is managed by the [[Vice-President of Communications]] as well as the [[Secretary]]''&lt;br /&gt;
&lt;br /&gt;
===VEX Robotics Competition===&lt;br /&gt;
The game in the [[2015]]-[[2016]] season was [[2015 Nothing but Net | Nothing but Net]].&lt;br /&gt;
&lt;br /&gt;
===Robots at the Ridge===&lt;br /&gt;
We had a blast at our Robots at the Ridge VEX competition on Saturday, November 21st, at Peachtree Ridge High School. We had one of our VEX teams make it to the quarter-finals, but sadly not any further. Of course, at the end of the day, the [[2016]] Robo Lion members had a blast, made new friends, and some of them can't wait to start year-long VEX! We would like to thank all teams that were in attendance, as well as all the volunteers who graciously supported us throughout the event.&lt;br /&gt;
We congratulate our award winners:&lt;br /&gt;
*Tournament Champion: Team Woodward (1900R) from Woodward Academy&lt;br /&gt;
*Tournament Champion: Team GMA (1900W) from Woodward Academy&lt;br /&gt;
*Tournament Champion: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
*Excellence Award: Raider Robotics (3536M) from North Forsyth High School&lt;br /&gt;
*Judges’ Award: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
Rebeca, our [[2016]] historian, made a video recap on all the activities this year's Robo Lions were involved in.&lt;br /&gt;
&lt;br /&gt;
Curious to see all the fun? Watch it [https://drive.google.com/file/d/0B3JRwrlB1bJdUzUwRHlZOVVpN1k/view?usp=sharing here]&lt;br /&gt;
&lt;br /&gt;
==Fun Facts==&lt;br /&gt;
===Robot Rock Parody Video===&lt;br /&gt;
Over Thanksgiving Break, some members of the team got together and made a video for FIRST's 2015 Song Parody Competition.&lt;br /&gt;
&lt;br /&gt;
More info about the competition [http://www.firstinspires.org/robotics/2015-first-song-parody-competition here] &lt;br /&gt;
&lt;br /&gt;
Watch Robot Rock [https://www.youtube.com/watch?v=ybaGaAJepHY here]&lt;br /&gt;
&lt;br /&gt;
===Gwinnett Daily Post Interview===&lt;br /&gt;
The team was interviewed by Gwinnett Daily Post on November 11.&lt;br /&gt;
&lt;br /&gt;
View the full article [http://www.gwinnettdailypost.com/local/cities/duluth/with-qualifer-on-tap-peachtree-ridge-stretches-its-robotics-reach/article_6899e404-d7e5-589c-b45d-801ff2788ba6.html here]&lt;br /&gt;
&lt;br /&gt;
[[File:WaltonCollab.jpg|200px|thumb|right| Walton Collab 2k16]]&lt;br /&gt;
&lt;br /&gt;
==FIRST Robotics Competition==&lt;br /&gt;
The [[2016]] [[FRC]] Game was [[2016 FIRST Stronghold | FIRST Stronghold]].&lt;br /&gt;
===Brainstorm with Walton===&lt;br /&gt;
[[File:WaltonLove.jpg|200px|thumb|right|Walton Love 2k16]]&lt;br /&gt;
On January 10, 2016, the Robo Lions invited Walton Robotics over to collaborate on game strategies. Here are some pictures of Walton spreading the love.&lt;br /&gt;
&lt;br /&gt;
===Robots===&lt;br /&gt;
This year's robot is Khanquistador. View his reveal video [https://www.youtube.com/watch?v=HsSBCBPBLJs here].&lt;br /&gt;
&lt;br /&gt;
===Field Team===&lt;br /&gt;
The [[2016]] field team consisted of:&lt;br /&gt;
*Driver: [[driver::Preston Shaw]]&lt;br /&gt;
*Manipulator Driver: [[manipulator driver::Nabil Khan]]&lt;br /&gt;
*Coach: [[coach::Mackenzie Glaser]]&lt;br /&gt;
*Human Player: [[human player::Joel Leonardo]]&lt;br /&gt;
&lt;br /&gt;
===Districts===&lt;br /&gt;
The Georgia district model was adopted first in [[2016]], and it allowed for Georgia [[FRC]] teams to compete in-state. The Robo Lions chose to compete in 3 of the 4 available competitive events in this year: Columbus, Albany, and Kennesaw.&lt;br /&gt;
====Columbus====&lt;br /&gt;
During the weekend of March 10-12, the team headed down to Columbus to compete in the week 2 Peachtree District Qualifier. Along with their alliance Captain {{TBA|5332}}and alliance partner {{TBA|4240}}, we were able to make it all the way to the semfinals!&lt;br /&gt;
&lt;br /&gt;
====Albany====&lt;br /&gt;
The team won the tournament at the Albany District Event! Allied with teams {{TBA|3329}}and {{TBA|5651}}, we were able to rise out on top ''and'' set the record for the highest score in Georgia! The team also won the District Chairman’s Award, becoming the first team in Gwinnett County to ever win the award, giving us our second Blue Banner and automatically qualifying us for the Peachtree District State Championships. The Robo Lions were also awarded the UL Industrial Safety Award. In addition, two Robo Lions’ team members, [[Caroline Means]] and [[Mackenzie Glaser]], were named Deans List Finalists.&lt;br /&gt;
&lt;br /&gt;
====Kennesaw====&lt;br /&gt;
While it may have been Spring Break, the team topped the charts with a great win at the Kennesaw District Event, competing with a total of thirty-five other in-state teams. Having been selected by  alliance captain {{TBA|1746}}OTTO Robotics from Cumming, Ga and working alongside alliance partner {{TBA|5812}}Drewbotics from Riverdale, Ga, the teams proved indestructible scoring a whopping 154 points in the final match! With the use of vision tracking that allowed for precise high goal shots and aggressive driving skills that dominated the field, the team also won the Excellence in Engineering award sponsored by Delphi. &lt;br /&gt;
&lt;br /&gt;
===Peachtree District State Championships===&lt;br /&gt;
Having faced off against competitors of the 41 best teams throughout the state of Georgia, the team was placed as the third-seed alliance captain and made it through six rigorous playoff matches with alliance partners {{TBA|2415}}Westminster Wired Cats from Atlanta, Ga and {{TBA|4516}}Hyperion Robotics from Roswell, Ga, before losing in the Finals, but not before setting an unbeatable high score of 170 points!  The team was also awarded with the Innovation in Control Awared sponsored by Rockwell Automation, and was crowned the second ranked team in Georgia. Because of this, the team was one of twelve teams in Georgia to qualify for the World Championships to be help in St. Louis, Missouri, but the only team in Gwinnett County to do so! &lt;br /&gt;
&lt;br /&gt;
===FIRST World Championships===&lt;br /&gt;
The team was able to qualify for the FIRST Robotics World Championships that took place in St. Louis, Missouri towards the end of April. We were one of just twelve Georgia FRC teams to qualify and made it farther than we have ever done before! Clawing our way through two days of qualification matches, we placed thirteenth out of seventy-five competing teams within the Curie division. From there, they were chosen to join the 5th seed alliance captain Team {{TBA|5406}}Celt-X from Hamilton, Ontario, Canada and their alliance partners Team 3641 Flying Toasters from South Lyon, Michigan. Team {{TBA|2883}}F.R.E.D from Warroad, Minnesota was chosen to be the backup 4th robot on the alliance. The determined trio fought hard only to be stopped short in the second semi-final match, losing by a small margin. However, this still marks the farthest we've ever gotten at Worlds!&lt;br /&gt;
&lt;br /&gt;
===Awards===&lt;br /&gt;
*Industrial Design Award sponsored by General Motors at Columbus&lt;br /&gt;
*Ul Industrial Safety Hard Hat Pin at Albany&lt;br /&gt;
*Chairman's Award at Albany&lt;br /&gt;
*District Winners at Albany&lt;br /&gt;
*District Winners at Kennesaw&lt;br /&gt;
*Excellence in Engineering Award sponsored by Delphi at Kennesaw&lt;br /&gt;
*Semi-Finalists at State&lt;br /&gt;
*Innovation in Control Award sponsored by Rockwell Automation at State&lt;br /&gt;
*Semi-Finalists at the [[FIRST]] World Championships&lt;br /&gt;
&lt;br /&gt;
Check out more of our awards [[Awards | here]].&lt;br /&gt;
&lt;br /&gt;
==Off-Season Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
GRITS this year was held at Walton High School on October 10th, where the Robo Lions were able to score as runner-ups, along with alliance captain 1648 G3 Robotics and 4189 Chargers. The team also took home the Outreach Award, representing with over 25 rookie attendees.&lt;br /&gt;
&lt;br /&gt;
===GirlsFIRST Event===&lt;br /&gt;
On October 17th, 2015 Walton High School (FRC Team 2974) hosted a GirlsFIRST workshop to bond with local robotics teams as well as anyone interested from the surrounding communities. There were engineering contests, guest speakers from women in technology, driver practice with robots from past games, and tons of big smiles! A small group of girls on our team were glad that they got to participate in such an amazing event.&lt;br /&gt;
&lt;br /&gt;
==Spring Activities==&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
&lt;br /&gt;
[[File:2016_ParsonsSTEM.jpg|200px|thumb|right|The Robo Lions at Parsons STEM Night]]&lt;br /&gt;
&lt;br /&gt;
On Thursday, February 4th, the team headed next door to Parsons Elementary school for an awesome night of robotics demonstrations! Our new outreach VEX robot made its debut, shooting balls across the cafeteria. Many of the students were eager to bring the balls back and even got to try their hand at driving the robot. Genesis, the 2014 competition robot, served us well once as we watched students jump up to catch the ball. A huge thanks to Parsons for having us and to all of the Robo Lions who helped make this night run smoothly!&lt;br /&gt;
&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
Mason STEM Night- Members of the team brought a VEX Robot and the 2014 Aerial Assist Robot to Mason Elementary to participate in a robotics showcase alongside GSMST Robotics and the Mason FLL team. Students were excited to jump up to catch the ball as the robot launched it across the room while others drove the VEX robot. It was really great to see the new members of the team connect with the elementary students, making sure all were safe around the robot and even sharing a dance or two! Prior to the night, students helped judge science fair entries which were also on display for parents that night. We had tons of kids take interest in the robot and we really loved being able to connect the kids’ experiences with robotics to our own robotics experiences!&lt;br /&gt;
&lt;br /&gt;
===Burnette Science Night===&lt;br /&gt;
[[File:2016Burnette.jpg|200px|thumb|right|The Robo Lions at Burnette Science Night]]&lt;br /&gt;
On February 11th, the team attended their first Burnette Elementary’s Science Night. It was great to drive around our 2014 FRC robot and our VEX Outreach robot, as we had lots of interest and answered tons of great questions. We spoke with Ms. Reed, the Principal, about furthering their robotics program, and are excited to continue working with the school!&lt;br /&gt;
&lt;br /&gt;
===Lawrenceville Rotary Club Meeting===&lt;br /&gt;
Seven enthusiastic members of the Peachtree Ridge High School Robotics Team presented information about their activities to the Rotary Club of Lawrenceville on April 4. [[2016]] [[Drive Team]] and [[2016]] [[Executives |Executive Officers]] described how the competitions worked and how the group went about preparing their robots for the competitions. The group is not only about engineering and business tasks; it is about building relationships, developing leadership skills, engaging in teamwork, and outreaching within the community. They displayed two of their robots and showed a video about the “Robo Lions spirit” that won a prize at a recent competition.&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2016]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2016]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2016]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2016}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2016]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2016}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-10T17:24:17Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Off-Season FRC Activities */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Georgia Tech Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainesville District===&lt;br /&gt;
The team attended the 2017 GeorgiaFirst Gainesville District Event on March 3rd through March 5th. We finished qualification matches at rank 30, and were chosen by the 8th alliance (Captain {{TBA|5734}}RoboReign and partner {{TBA|5332}}ToasterTech). The Robo Lions put up quite a fight in the first two quarterfinal matches, but didn't quite make the cut. Despite the results of the competition, the team worked through the day with their roaring spirits and hard work! We hope to blow the competition away at our future events with all that we've learned from Gainesville!&lt;br /&gt;
&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team {{TBA|2974}}(Walton) and Team {{TBA|4188}}(Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy.&lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future.&lt;br /&gt;
&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
Closer to home, our team took a walk over to Parsons Elementary for STEAM night with an eager group of rookies. They did a great job speaking about the 2016 robot and helping to demonstrate its capabilities. Meanwhile, others supervised youngers who wanted to try their hand at driving the VEX robots. It was a great night for the team as we got to interact with future Robo Lions and look ahead towards the establishment of another FLL team at the school. &lt;br /&gt;
&lt;br /&gt;
===Jackson STEM Night===&lt;br /&gt;
The team had a wonderful time at Jackson Elementary for their STEAM night! The 2016 robot was a hit and did a great job showing students and parents how we were able to optimize the ways in which hardware and software can work together! For younger kids, VEX robots are closer to their size, so they were thrilled to have the chance to drive them around to play soccer. Thanks to Jackson Elementary for being such great hosts- we had tons of fun meeting your FLL team as well and can’t wait to work with them!&lt;br /&gt;
&lt;br /&gt;
===Assistant Principal's Son Birthday Party!===&lt;br /&gt;
The team volunteered to entertain the school's assistant principal's son at his 6th birthday party. The fun of the party was fueled by the driving of baby vex robots and the room was filled with children's laughs! It just goes to show that science and technology can be as much fun for high schoolers as it is for the kids! &lt;br /&gt;
===Duluth Library Demo===&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-10T17:23:27Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Gainesville District */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Georgia Tech Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainesville District===&lt;br /&gt;
The team attended the 2017 GeorgiaFirst Gainesville District Event on March 3rd through March 5th. We finished qualification matches at rank 30, and were chosen by the 8th alliance (Captain {{TBA|5734}}RoboReign and partner {{TBA|5332}}ToasterTech). The Robo Lions put up quite a fight in the first two quarterfinal matches, but didn't quite make the cut. Despite the results of the competition, the team worked through the day with their roaring spirits and hard work! We hope to blow the competition away at our future events with all that we've learned from Gainesville!&lt;br /&gt;
&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future.&lt;br /&gt;
&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
Closer to home, our team took a walk over to Parsons Elementary for STEAM night with an eager group of rookies. They did a great job speaking about the 2016 robot and helping to demonstrate its capabilities. Meanwhile, others supervised youngers who wanted to try their hand at driving the VEX robots. It was a great night for the team as we got to interact with future Robo Lions and look ahead towards the establishment of another FLL team at the school. &lt;br /&gt;
&lt;br /&gt;
===Jackson STEM Night===&lt;br /&gt;
The team had a wonderful time at Jackson Elementary for their STEAM night! The 2016 robot was a hit and did a great job showing students and parents how we were able to optimize the ways in which hardware and software can work together! For younger kids, VEX robots are closer to their size, so they were thrilled to have the chance to drive them around to play soccer. Thanks to Jackson Elementary for being such great hosts- we had tons of fun meeting your FLL team as well and can’t wait to work with them!&lt;br /&gt;
&lt;br /&gt;
===Assistant Principal's Son Birthday Party!===&lt;br /&gt;
The team volunteered to entertain the school's assistant principal's son at his 6th birthday party. The fun of the party was fueled by the driving of baby vex robots and the room was filled with children's laughs! It just goes to show that science and technology can be as much fun for high schoolers as it is for the kids! &lt;br /&gt;
===Duluth Library Demo===&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-10T17:23:12Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* FRC Competitions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Georgia Tech Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainesville District===&lt;br /&gt;
The team attended the 2017 GeorgiaFirst Gainesville District Event on March 3rd through March 5th. We finished qualification matches at rank 30, and were chosen by the 8th alliance (Captain {{TBA|5734}} RoboReign and partner {{TBA|5332}}ToasterTech). The Robo Lions put up quite a fight in the first two quarterfinal matches, but didn't quite make the cut. Despite the results of the competition, the team worked through the day with their roaring spirits and hard work! We hope to blow the competition away at our future events with all that we've learned from Gainesville!&lt;br /&gt;
&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future.&lt;br /&gt;
&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
Closer to home, our team took a walk over to Parsons Elementary for STEAM night with an eager group of rookies. They did a great job speaking about the 2016 robot and helping to demonstrate its capabilities. Meanwhile, others supervised youngers who wanted to try their hand at driving the VEX robots. It was a great night for the team as we got to interact with future Robo Lions and look ahead towards the establishment of another FLL team at the school. &lt;br /&gt;
&lt;br /&gt;
===Jackson STEM Night===&lt;br /&gt;
The team had a wonderful time at Jackson Elementary for their STEAM night! The 2016 robot was a hit and did a great job showing students and parents how we were able to optimize the ways in which hardware and software can work together! For younger kids, VEX robots are closer to their size, so they were thrilled to have the chance to drive them around to play soccer. Thanks to Jackson Elementary for being such great hosts- we had tons of fun meeting your FLL team as well and can’t wait to work with them!&lt;br /&gt;
&lt;br /&gt;
===Assistant Principal's Son Birthday Party!===&lt;br /&gt;
The team volunteered to entertain the school's assistant principal's son at his 6th birthday party. The fun of the party was fueled by the driving of baby vex robots and the room was filled with children's laughs! It just goes to show that science and technology can be as much fun for high schoolers as it is for the kids! &lt;br /&gt;
===Duluth Library Demo===&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-10T17:20:08Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* TE Sessions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Georgia Tech Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainesville District===&lt;br /&gt;
The team attended the 2017 GeorgiaFirst Gainesville District Event on March 3rd through March 5th. We finished qualification matches at rank 30, and were chosen by the 8th alliance (Captain 5734 RoboReign and partner 5332 ToasterTech). The Robo Lions put up quite a fight in the first two quarterfinal matches, but didn't quite make the cut. Despite the results of the competition, the team worked through the day with their roaring spirits and hard work! We hope to blow the competition away at our future events with all that we've learned from Gainesville!&lt;br /&gt;
&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future.&lt;br /&gt;
&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
Closer to home, our team took a walk over to Parsons Elementary for STEAM night with an eager group of rookies. They did a great job speaking about the 2016 robot and helping to demonstrate its capabilities. Meanwhile, others supervised youngers who wanted to try their hand at driving the VEX robots. It was a great night for the team as we got to interact with future Robo Lions and look ahead towards the establishment of another FLL team at the school. &lt;br /&gt;
&lt;br /&gt;
===Jackson STEM Night===&lt;br /&gt;
The team had a wonderful time at Jackson Elementary for their STEAM night! The 2016 robot was a hit and did a great job showing students and parents how we were able to optimize the ways in which hardware and software can work together! For younger kids, VEX robots are closer to their size, so they were thrilled to have the chance to drive them around to play soccer. Thanks to Jackson Elementary for being such great hosts- we had tons of fun meeting your FLL team as well and can’t wait to work with them!&lt;br /&gt;
&lt;br /&gt;
===Assistant Principal's Son Birthday Party!===&lt;br /&gt;
The team volunteered to entertain the school's assistant principal's son at his 6th birthday party. The fun of the party was fueled by the driving of baby vex robots and the room was filled with children's laughs! It just goes to show that science and technology can be as much fun for high schoolers as it is for the kids! &lt;br /&gt;
===Duluth Library Demo===&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-10T17:06:11Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Spring 2017: Outreach Activities */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainesville District===&lt;br /&gt;
The team attended the 2017 GeorgiaFirst Gainesville District Event on March 3rd through March 5th. We finished qualification matches at rank 30, and were chosen by the 8th alliance (Captain 5734 RoboReign and partner 5332 ToasterTech). The Robo Lions put up quite a fight in the first two quarterfinal matches, but didn't quite make the cut. Despite the results of the competition, the team worked through the day with their roaring spirits and hard work! We hope to blow the competition away at our future events with all that we've learned from Gainesville!&lt;br /&gt;
&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future.&lt;br /&gt;
&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
Closer to home, our team took a walk over to Parsons Elementary for STEAM night with an eager group of rookies. They did a great job speaking about the 2016 robot and helping to demonstrate its capabilities. Meanwhile, others supervised youngers who wanted to try their hand at driving the VEX robots. It was a great night for the team as we got to interact with future Robo Lions and look ahead towards the establishment of another FLL team at the school. &lt;br /&gt;
&lt;br /&gt;
===Jackson STEM Night===&lt;br /&gt;
The team had a wonderful time at Jackson Elementary for their STEAM night! The 2016 robot was a hit and did a great job showing students and parents how we were able to optimize the ways in which hardware and software can work together! For younger kids, VEX robots are closer to their size, so they were thrilled to have the chance to drive them around to play soccer. Thanks to Jackson Elementary for being such great hosts- we had tons of fun meeting your FLL team as well and can’t wait to work with them!&lt;br /&gt;
&lt;br /&gt;
===Assistant Principal's Son Birthday Party!===&lt;br /&gt;
The team volunteered to entertain the school's assistant principal's son at his 6th birthday party. The fun of the party was fueled by the driving of baby vex robots and the room was filled with children's laughs! It just goes to show that science and technology can be as much fun for high schoolers as it is for the kids! &lt;br /&gt;
===Duluth Library Demo===&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-10T17:01:20Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Spring 2017: Outreach Activities */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainesville District===&lt;br /&gt;
The team attended the 2017 GeorgiaFirst Gainesville District Event on March 3rd through March 5th. We finished qualification matches at rank 30, and were chosen by the 8th alliance (Captain 5734 RoboReign and partner 5332 ToasterTech). The Robo Lions put up quite a fight in the first two quarterfinal matches, but didn't quite make the cut. Despite the results of the competition, the team worked through the day with their roaring spirits and hard work! We hope to blow the competition away at our future events with all that we've learned from Gainesville!&lt;br /&gt;
&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future.&lt;br /&gt;
&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
Closer to home, our team took a walk over to Parsons Elementary for STEAM night with an eager group of rookies. They did a great job speaking about the 2016 robot and helping to demonstrate its capabilities. Meanwhile, others supervised youngers who wanted to try their hand at driving the VEX robots. It was a great night for the team as we got to interact with future Robo Lions and look ahead towards the establishment of another FLL team at the school. &lt;br /&gt;
&lt;br /&gt;
===Jackson STEM Night===&lt;br /&gt;
The team had a wonderful time at Jackson Elementary for their STEAM night! The 2016 robot was a hit and did a great job showing students and parents how we were able to optimize the ways in which hardware and software can work together! For younger kids, VEX robots are closer to their size, so they were thrilled to have the chance to drive them around to play soccer. Thanks to Jackson Elementary for being such great hosts- we had tons of fun meeting your FLL team as well and can’t wait to work with them!&lt;br /&gt;
&lt;br /&gt;
===Duluth Library Demo===&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-10T16:52:04Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Gainsville District */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainesville District===&lt;br /&gt;
The team attended the 2017 GeorgiaFirst Gainesville District Event on March 3rd through March 5th. We finished qualification matches at rank 30, and were chosen by the 8th alliance (Captain 5734 RoboReign and partner 5332 ToasterTech). The Robo Lions put up quite a fight in the first two quarterfinal matches, but didn't quite make the cut. Despite the results of the competition, the team worked through the day with their roaring spirits and hard work! We hope to blow the competition away at our future events with all that we've learned from Gainesville!&lt;br /&gt;
&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future. &lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-03-10T16:45:58Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Scouting FAQ */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do We Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How Do We Scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In [[2016]], [[Rishov Sarkar]] created a scouting app that is reusable each year; it just requires a team member to go in and create scouting questions pertaining to the year's game. You can view it [https://scouting.prhsrobotics.com/ here]. We have also opened this scouting app up to other FRC teams who have asked us about it as they are free to use it to their desire.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Activate product key on Tableau for 5 of the programming laptops. This is because the product key found in the KOP (Kit of Parts) can only be applied on up to 5 devices. Note: the head stand scout only needs to use one of these in the stands for emergency Tableau analysis. However, Tableau should be installed on all available laptops to be used for scouting training before competition. Had stand scout should confer with programmers on which laptops they will need during competition and which are free for scouts to use. &lt;br /&gt;
*Update scouting app with questions relevant to the game.&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :)&lt;br /&gt;
&lt;br /&gt;
==Tableau Training==&lt;br /&gt;
Here is a list of tasks for scouting preparations before competition: &lt;br /&gt;
*Practice tableau analysis with rookies using past year’s data&lt;br /&gt;
*Practice making different kinds of graphs&lt;br /&gt;
*Steps for different graphs &lt;br /&gt;
*First meeting - discussing graphs + review last years graphs &lt;br /&gt;
*2nd meeting - play around with tableau settings + watching tableau tutorials +blue alliance &lt;br /&gt;
*3rd meeting - brainstorm what we would need for scouting app/ what is ideal data to collect/ qualitative vs quantitative&lt;br /&gt;
Note: scouting training does not have to be broken down into three different meetings, but this is optimal so the members do not feel overwhelmed. It is also easier to retain information by soaking up a little at a time rather than all at once. Also, [[Daniel Li]] in [[2015]] started to create his own version of the Forecast option on Tableau to see Tableau predictions of match data relating to how many points a certain team will be able to score in the next match based on previous match data. This is used by looking at the average points accumulated by one team over all of the matches that they have played. However, there is a Forecast option on Tableau that should theoretically be able to pull up this kind of data, but so far the team has not delved into this project very much. This is not a necessary project to be taken up, but it is nice to have this ability :) &lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
*What do I do if my phone loses internet or freezes and I cannot access the scouting app in order to enter in data?&lt;br /&gt;
**Get out a pencil and paper and do it the old fashion way! You can re-enter the data you've collected at a later time, but it must be collected! Missing data can be huge and can skew our perceptions of a team's performance. Just make sure you communicate this problem with the head scouts so they know what to watch out for. &lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-03-02T22:34:59Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
This year, we implemented a new way to manage different build sub-teams during the [[FRC]] season. Click [http://wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management here] to view it.&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
[[File:StarstruckWinners.jpg|thumb|300px|Award winners from the Robots at the Ridge competition.]]&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
[[File:TrunkorTreat.jpg|225px|thumb|Some team members giving out candy to kids at Trunk or Treat.]]&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
*[https://www.youtube.com/watch?v=Esb-SJ0anWE '''Fall''']&lt;br /&gt;
&lt;br /&gt;
==FRC Competitions==&lt;br /&gt;
===Gainsville District===&lt;br /&gt;
===Asheville, NC===&lt;br /&gt;
===Albany District===&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
[[File:MasonSTEM.jpg|200px|thumb|Caroline Means explains the function of [[Khanquistador]] to elementary kids.]]&lt;br /&gt;
On January 24th, 2017, the team was invited to bring their robots to Mason Elementary's STEM Night. The team brought [[Khanquistador]] Robot to use as a tool and help explain vision tracking to the parents and children. At the end, Khanquistador was used to roll boulders towards the kids. We showed the kids what they can look forward to doing in high school, hopefully to gain many more members in the future. &lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-02-25T19:07:34Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* How Do We Scout? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do We Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How Do We Scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In [[2016]], [[Rishov Sarkar]] created a scouting app that is reusable each year; it just requires a team member to go in and create scouting questions pertaining to the year's game. You can view it [https://scouting.prhsrobotics.com/ here]. We have also opened this scouting app up to other FRC teams who have asked us about it as they are free to use it to their desire.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Activate product key on Tableau for 5 of the programming laptops. This is because the product key found in the KOP (Kit of Parts) can only be applied on up to 5 devices. Note: the head stand scout only needs to use one of these in the stands for emergency Tableau analysis. However, Tableau should be installed on all available laptops to be used for scouting training before competition. Had stand scout should confer with programmers on which laptops they will need during competition and which are free for scouts to use. &lt;br /&gt;
*Update scouting app with questions relevant to the game.&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :)&lt;br /&gt;
&lt;br /&gt;
==Tableau Training==&lt;br /&gt;
Here is a list of tasks for scouting preparations before competition: &lt;br /&gt;
*Practice tableau analysis with rookies using past year’s data&lt;br /&gt;
*Practice making different kinds of graphs&lt;br /&gt;
*Steps for different graphs &lt;br /&gt;
*First meeting - discussing graphs + review last years graphs &lt;br /&gt;
*2nd meeting - play around with tableau settings + watching tableau tutorials +blue alliance &lt;br /&gt;
*3rd meeting - brainstorm what we would need for scouting app/ what is ideal data to collect/ qualitative vs quantitative&lt;br /&gt;
Note: scouting training does not have to be broken down into three different meetings, but this is optimal so the members do not feel overwhelmed. It is also easier to retain information by soaking up a little at a time rather than all at once. Also, [[Daniel Li]] in [[2015]] started to create his own version of the Forecast option on Tableau to see Tableau predictions of match data relating to how many points a certain team will be able to score in the next match based on previous match data. This is used by looking at the average points accumulated by one team over all of the matches that they have played. However, there is a Forecast option on Tableau that should theoretically be able to pull up this kind of data, but so far the team has not delved into this project very much. This is not a necessary project to be taken up, but it is nice to have this ability :) &lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-02-25T19:05:45Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* How do we scout? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do We Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How Do We Scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Activate product key on Tableau for 5 of the programming laptops. This is because the product key found in the KOP (Kit of Parts) can only be applied on up to 5 devices. Note: the head stand scout only needs to use one of these in the stands for emergency Tableau analysis. However, Tableau should be installed on all available laptops to be used for scouting training before competition. Had stand scout should confer with programmers on which laptops they will need during competition and which are free for scouts to use. &lt;br /&gt;
*Update scouting app with questions relevant to the game.&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :)&lt;br /&gt;
&lt;br /&gt;
==Tableau Training==&lt;br /&gt;
Here is a list of tasks for scouting preparations before competition: &lt;br /&gt;
*Practice tableau analysis with rookies using past year’s data&lt;br /&gt;
*Practice making different kinds of graphs&lt;br /&gt;
*Steps for different graphs &lt;br /&gt;
*First meeting - discussing graphs + review last years graphs &lt;br /&gt;
*2nd meeting - play around with tableau settings + watching tableau tutorials +blue alliance &lt;br /&gt;
*3rd meeting - brainstorm what we would need for scouting app/ what is ideal data to collect/ qualitative vs quantitative&lt;br /&gt;
Note: scouting training does not have to be broken down into three different meetings, but this is optimal so the members do not feel overwhelmed. It is also easier to retain information by soaking up a little at a time rather than all at once. Also, [[Daniel Li]] in [[2015]] started to create his own version of the Forecast option on Tableau to see Tableau predictions of match data relating to how many points a certain team will be able to score in the next match based on previous match data. This is used by looking at the average points accumulated by one team over all of the matches that they have played. However, there is a Forecast option on Tableau that should theoretically be able to pull up this kind of data, but so far the team has not delved into this project very much. This is not a necessary project to be taken up, but it is nice to have this ability :) &lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-02-25T19:05:30Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Why Do we Scout */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do We Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How do we scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Activate product key on Tableau for 5 of the programming laptops. This is because the product key found in the KOP (Kit of Parts) can only be applied on up to 5 devices. Note: the head stand scout only needs to use one of these in the stands for emergency Tableau analysis. However, Tableau should be installed on all available laptops to be used for scouting training before competition. Had stand scout should confer with programmers on which laptops they will need during competition and which are free for scouts to use. &lt;br /&gt;
*Update scouting app with questions relevant to the game.&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :)&lt;br /&gt;
&lt;br /&gt;
==Tableau Training==&lt;br /&gt;
Here is a list of tasks for scouting preparations before competition: &lt;br /&gt;
*Practice tableau analysis with rookies using past year’s data&lt;br /&gt;
*Practice making different kinds of graphs&lt;br /&gt;
*Steps for different graphs &lt;br /&gt;
*First meeting - discussing graphs + review last years graphs &lt;br /&gt;
*2nd meeting - play around with tableau settings + watching tableau tutorials +blue alliance &lt;br /&gt;
*3rd meeting - brainstorm what we would need for scouting app/ what is ideal data to collect/ qualitative vs quantitative&lt;br /&gt;
Note: scouting training does not have to be broken down into three different meetings, but this is optimal so the members do not feel overwhelmed. It is also easier to retain information by soaking up a little at a time rather than all at once. Also, [[Daniel Li]] in [[2015]] started to create his own version of the Forecast option on Tableau to see Tableau predictions of match data relating to how many points a certain team will be able to score in the next match based on previous match data. This is used by looking at the average points accumulated by one team over all of the matches that they have played. However, there is a Forecast option on Tableau that should theoretically be able to pull up this kind of data, but so far the team has not delved into this project very much. This is not a necessary project to be taken up, but it is nice to have this ability :) &lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-02-25T19:04:41Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do we Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How do we scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Activate product key on Tableau for 5 of the programming laptops. This is because the product key found in the KOP (Kit of Parts) can only be applied on up to 5 devices. Note: the head stand scout only needs to use one of these in the stands for emergency Tableau analysis. However, Tableau should be installed on all available laptops to be used for scouting training before competition. Had stand scout should confer with programmers on which laptops they will need during competition and which are free for scouts to use. &lt;br /&gt;
*Update scouting app with questions relevant to the game.&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :)&lt;br /&gt;
&lt;br /&gt;
==Tableau Training==&lt;br /&gt;
Here is a list of tasks for scouting preparations before competition: &lt;br /&gt;
*Practice tableau analysis with rookies using past year’s data&lt;br /&gt;
*Practice making different kinds of graphs&lt;br /&gt;
*Steps for different graphs &lt;br /&gt;
*First meeting - discussing graphs + review last years graphs &lt;br /&gt;
*2nd meeting - play around with tableau settings + watching tableau tutorials +blue alliance &lt;br /&gt;
*3rd meeting - brainstorm what we would need for scouting app/ what is ideal data to collect/ qualitative vs quantitative&lt;br /&gt;
Note: scouting training does not have to be broken down into three different meetings, but this is optimal so the members do not feel overwhelmed. It is also easier to retain information by soaking up a little at a time rather than all at once. Also, [[Daniel Li]] in [[2015]] started to create his own version of the Forecast option on Tableau to see Tableau predictions of match data relating to how many points a certain team will be able to score in the next match based on previous match data. This is used by looking at the average points accumulated by one team over all of the matches that they have played. However, there is a Forecast option on Tableau that should theoretically be able to pull up this kind of data, but so far the team has not delved into this project very much. This is not a necessary project to be taken up, but it is nice to have this ability :) &lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-02-25T18:59:14Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Head Stand Scout Obligations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do we Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How do we scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Activate product key on Tableau for 5 of the programming laptops. This is because the product key found in the KOP (Kit of Parts) can only be applied on up to 5 devices. Note: the head stand scout only needs to use one of these in the stands for emergency Tableau analysis. However, Tableau should be installed on all available laptops to be used for scouting training before competition. Had stand scout should confer with programmers on which laptops they will need during competition and which are free for scouts to use. &lt;br /&gt;
*Update scouting app with questions relevant to the game.&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :)&lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-02-25T17:25:50Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Head Stand Scout Obligations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do we Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How do we scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Activate product key on Tableau for all of the programming laptops. Note: the head stand scout only needs to use one of these in the stands for emergency Tableau analysis. However, Tableau should be installed on all available laptops to be used for scouting training before competition. Had stand scout should confer with programmers on which laptops they will need during competition and which are free for scouts to use. &lt;br /&gt;
*Update scouting app with questions relevant to the game.&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :)&lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Khanquistador</id>
		<title>Khanquistador</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Khanquistador"/>
				<updated>2017-02-25T16:27:06Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{RobotInfoBox&lt;br /&gt;
|Name=Khanquistador&lt;br /&gt;
|Image=Khanquistador.jpg&lt;br /&gt;
|Year=2016&lt;br /&gt;
|Competition=FRC&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==='''About Khanquistador'''===&lt;br /&gt;
&lt;br /&gt;
[[Khanquistador]] was built for the 2016 FRC game [[2016 FIRST Stronghold | Stronghold]]. It was named after the president of the club at the time, [[Nabil Khan]].&lt;br /&gt;
&lt;br /&gt;
==='''Drive Train'''===&lt;br /&gt;
*6 pneumatic wheels&lt;br /&gt;
*Raised front wheel for easy defense crossing&lt;br /&gt;
&lt;br /&gt;
==='''Shooter'''===&lt;br /&gt;
*Flywheel shooter with ability to shoot from any angle in the courtyard&lt;br /&gt;
*Vision tracks high goals to make consistent shots&lt;br /&gt;
 &lt;br /&gt;
==='''Climbing'''===&lt;br /&gt;
*Though this year's game included a climbing aspect, our team was never able to climb in competition. We did, however, try several different prototypes for climbing&lt;br /&gt;
**A springloaded arm system using the tension of surgical tubing to push an arm up to the bar and hook on&lt;br /&gt;
**A hook launched by a spring that would hit the hanging bar and snap closed over it&lt;br /&gt;
**Both of the above delivery systems would bring a rope up to the top and the robot would winch itself up with the rope from a motor mounted approximately in the center of the robot. &lt;br /&gt;
 &lt;br /&gt;
==='''Capabilities'''===&lt;br /&gt;
*Can do all defenses except drawbridge without other assistance&lt;br /&gt;
*Can shoot high and low goals&lt;br /&gt;
*Vision tracks goals for accurate shots every time&lt;br /&gt;
*Several autonomous modes including crossing a defense and shooting in the high goal&lt;br /&gt;
*Climbing capabilities&lt;br /&gt;
&lt;br /&gt;
==='''Autonomous'''===&lt;br /&gt;
*Can cross all defenses except for Portcullis, Sally Door, and Drawbridge&lt;br /&gt;
*NavX attached to the robot detects when we have finished crossing a defense&lt;br /&gt;
*Laser Rangefinder stops the robot once it reaches the pre-determined distance from the wall&lt;br /&gt;
*Uses vision tracking to aim and make a high goal shot after crossing the defense&lt;br /&gt;
&lt;br /&gt;
==='''Programming'''===&lt;br /&gt;
*Main robot code written in Java&lt;br /&gt;
*Held in a Github repository to allow version control and the swapping of laptops for coding&lt;br /&gt;
*Vision Tracking written in Python&lt;br /&gt;
&lt;br /&gt;
==='''Awards'''===&lt;br /&gt;
The team won the 2016 Albany Districts Event with [[Khanquistador]], as well as winning the Industrial Design award at the Columbus District Event. &lt;br /&gt;
&lt;br /&gt;
===External Links===&lt;br /&gt;
*For more build info on Khanquistador, check the member's build blog [https://sites.google.com/a/prhsrobotics.com/members/blog here]. Members: you must be logged in to your @prhsrobotics account in order to view this site.&lt;br /&gt;
{{FRCRobotBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category: Robots]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Alvin</id>
		<title>Alvin</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Alvin"/>
				<updated>2017-02-25T16:24:43Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* External Links */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{RobotInfoBox&lt;br /&gt;
|Name=Alvin&lt;br /&gt;
|Image=Alvin.jpg&lt;br /&gt;
|Year=2015&lt;br /&gt;
|Competition=FRC&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==='''About Alvin'''===&lt;br /&gt;
&lt;br /&gt;
Alvin was built for use in the 2015 FRC game [[2015 Recycle Rush | Recycle Rush]] and was named after the Superintendent of Gwinnett County Public Schools, J. Alvin Wilbanks.&lt;br /&gt;
&lt;br /&gt;
==='''Drive Train'''===&lt;br /&gt;
&lt;br /&gt;
Alvin's Chassis was an Andy Mark AM14U2, square configuration, from the Kit of Parts. There are 2 traction wheels in the front, and 2 dual omni wheels in the back. Powertrain is pretty standard. It's a 2-CIM gearbox located in the center of each side rail. Gates belts drive all 4 wheels.&lt;br /&gt;
&lt;br /&gt;
==='''Manipulator'''===&lt;br /&gt;
&lt;br /&gt;
Alvin's manipulator is an elevator lift with 2 pneumatic arms. we used an all brass air preparation system to conserve space and make it pretty :)&lt;br /&gt;
&lt;br /&gt;
The elevator uses 2 steel-lined belts donated by Habasit. There is a [http://www.andymark.com/product-p/am-2236.htm Toughbox Mini] gearbox with a 12.75:1 gear ratio, going to a Gates belt with a _(INSERT GEAR RATIO HERE)_ reduction on the sprockets. We have a ThunderShaft hex shaft with the 2 sprockets that drive the steel-lined belts.&lt;br /&gt;
&lt;br /&gt;
On the lift itself we used a linear bearing kit from [http://www.competitionrobotparts.com/ Competition Robot Parts]. It is designed for standard 1x2 rectangular extrusion.&lt;br /&gt;
&lt;br /&gt;
Limit switches and encoders help to enhance Alvin's speed and stacking capabilities, along with positive control/dynamic breaking on the lift. This makes the lift weight resistant and increases arm strength. The lift is made functional by two high-speed CIM motors. It has also been programmed to be automatically centered, adding on to Alvin's efficiency.&lt;br /&gt;
&lt;br /&gt;
==='''Code'''===&lt;br /&gt;
&lt;br /&gt;
Alvin was programmed in Java, the team's second year using the language. A copy of the code can be found [https://github.com/RoboLions/frc2015/tree/develop/RoboLions2015/src/org/usfirst/frc1261/RoboLions2015 here]&lt;br /&gt;
&lt;br /&gt;
===External Links===&lt;br /&gt;
*View our reveal video here : [https://youtu.be/L3GFLjNwoKU 2015 Alvin Reveal] &lt;br /&gt;
*Visit Alvin's website [http://dannyzl.wix.com/alvin here]&lt;br /&gt;
*For more build info about Alvin: check out the team's build blog [https://sites.google.com/a/prhsrobotics.com/members/blog here]. Members: you must be logged in to your @prhsrobotics email in order to view this site &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{FRCRobotBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category: Robots]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Alvin</id>
		<title>Alvin</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Alvin"/>
				<updated>2017-02-25T16:24:28Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{RobotInfoBox&lt;br /&gt;
|Name=Alvin&lt;br /&gt;
|Image=Alvin.jpg&lt;br /&gt;
|Year=2015&lt;br /&gt;
|Competition=FRC&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==='''About Alvin'''===&lt;br /&gt;
&lt;br /&gt;
Alvin was built for use in the 2015 FRC game [[2015 Recycle Rush | Recycle Rush]] and was named after the Superintendent of Gwinnett County Public Schools, J. Alvin Wilbanks.&lt;br /&gt;
&lt;br /&gt;
==='''Drive Train'''===&lt;br /&gt;
&lt;br /&gt;
Alvin's Chassis was an Andy Mark AM14U2, square configuration, from the Kit of Parts. There are 2 traction wheels in the front, and 2 dual omni wheels in the back. Powertrain is pretty standard. It's a 2-CIM gearbox located in the center of each side rail. Gates belts drive all 4 wheels.&lt;br /&gt;
&lt;br /&gt;
==='''Manipulator'''===&lt;br /&gt;
&lt;br /&gt;
Alvin's manipulator is an elevator lift with 2 pneumatic arms. we used an all brass air preparation system to conserve space and make it pretty :)&lt;br /&gt;
&lt;br /&gt;
The elevator uses 2 steel-lined belts donated by Habasit. There is a [http://www.andymark.com/product-p/am-2236.htm Toughbox Mini] gearbox with a 12.75:1 gear ratio, going to a Gates belt with a _(INSERT GEAR RATIO HERE)_ reduction on the sprockets. We have a ThunderShaft hex shaft with the 2 sprockets that drive the steel-lined belts.&lt;br /&gt;
&lt;br /&gt;
On the lift itself we used a linear bearing kit from [http://www.competitionrobotparts.com/ Competition Robot Parts]. It is designed for standard 1x2 rectangular extrusion.&lt;br /&gt;
&lt;br /&gt;
Limit switches and encoders help to enhance Alvin's speed and stacking capabilities, along with positive control/dynamic breaking on the lift. This makes the lift weight resistant and increases arm strength. The lift is made functional by two high-speed CIM motors. It has also been programmed to be automatically centered, adding on to Alvin's efficiency.&lt;br /&gt;
&lt;br /&gt;
==='''Code'''===&lt;br /&gt;
&lt;br /&gt;
Alvin was programmed in Java, the team's second year using the language. A copy of the code can be found [https://github.com/RoboLions/frc2015/tree/develop/RoboLions2015/src/org/usfirst/frc1261/RoboLions2015 here]&lt;br /&gt;
&lt;br /&gt;
===External Links===&lt;br /&gt;
View our reveal video here : [https://youtu.be/L3GFLjNwoKU 2015 Alvin Reveal] &lt;br /&gt;
Visit Alvin's website [http://dannyzl.wix.com/alvin here]&lt;br /&gt;
For more build info about Alvin: check out the team's build blog [https://sites.google.com/a/prhsrobotics.com/members/blog here]. Members: you must be logged in to your @prhsrobotics email in order to view this site &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{FRCRobotBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category: Robots]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Template:History</id>
		<title>Template:History</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Template:History"/>
				<updated>2017-02-25T16:22:27Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TitleBox&lt;br /&gt;
|title = History&lt;br /&gt;
|content =&lt;br /&gt;
{{{!}}style=&amp;quot;margin:auto; text-align: center;&amp;quot;&lt;br /&gt;
{{!}} &amp;lt;big&amp;gt;'''General'''&amp;lt;/big&amp;gt; {{!}}{{!}}style=&amp;quot;padding-left: 16px;&amp;quot; {{!}}&amp;lt;big&amp;gt;'''Specific Years'''&amp;lt;/big&amp;gt;&lt;br /&gt;
{{!}}-&lt;br /&gt;
{{!}} &amp;lt;big&amp;gt;[[Robots]] - [[Sponsors]] - [[Apparel]] - [[Website]] - [https://sites.google.com/a/prhsrobotics.com/members/?pli=1 Build Blog]&amp;lt;br&amp;gt;&lt;br /&gt;
[[Buttons]] - [[Logos]] - [[End of the Year Party]]&amp;lt;/big&amp;gt;&lt;br /&gt;
{{!}}style=&amp;quot;padding-left: 25px;&amp;quot; {{!}} &amp;lt;big&amp;gt;[[2017]] - [[2016]] - [[2015]] - [[2014]] - [[2013]] - [[2012]] - [[2011]] - [[2010]]&amp;lt;br&amp;gt;&lt;br /&gt;
[[2009]] - [[2008]] - [[2007]] - [[2006]] - [[2005]] - [[2004]]&amp;lt;/big&amp;gt;&lt;br /&gt;
{{!}}}&lt;br /&gt;
&lt;br /&gt;
}}&amp;lt;noinclude&amp;gt;&lt;br /&gt;
==Usage==&lt;br /&gt;
Mainly used on the main page for the &amp;quot;History&amp;quot; section.&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Scouting</id>
		<title>Scouting</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Scouting"/>
				<updated>2017-02-23T17:34:43Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page has been adapted from [[Sunny]]'s [http://forum.prhsrobotics.com/viewtopic.php?f=6&amp;amp;t=721&amp;amp;p=4667#p4634 post] in the forum. &lt;br /&gt;
&lt;br /&gt;
==What is scouting?==&lt;br /&gt;
&lt;br /&gt;
Scouting in the process by which teams gather, interpret, and share information.&lt;br /&gt;
&lt;br /&gt;
==Gathering Information==&lt;br /&gt;
&lt;br /&gt;
We gather information for our purposes. If at the end of qualifications, we find ourselves sitting in 2nd place and we need to create an alliance, then we use all of the scouting information to build the best alliance possible.&lt;br /&gt;
&lt;br /&gt;
We want to gather everything piece of information about an opposing robot/team. We want to know if they have a strong drivetrain, a weak drive train, can they score well, do they suck at scoring, is their minibot fast, can they play good defense, etc. No information should go uncollected, whether it's notable or not.&lt;br /&gt;
&lt;br /&gt;
==Interpreting Information==&lt;br /&gt;
&lt;br /&gt;
We use this information all throughout the tournament.&lt;br /&gt;
&lt;br /&gt;
For qualifications, we use scouting information to better gauge opponents and better gauge matches. If we learn that team xxxx has a jumpy driver who doesn't respond well to pressure, then it might be a good idea for us to put a robot to defend them and totally shut them down.&lt;br /&gt;
&lt;br /&gt;
For finals, we use scouting information to help us pick teams. This part of our scouting team has never been too good, but I would like to change that. The best way to do this is to create a list of top 24 teams. Take this list, and go into finals.&lt;br /&gt;
&lt;br /&gt;
==Sharing Information==&lt;br /&gt;
&lt;br /&gt;
There are a lot of good robots this year, but like any year, it is the job of a scout to share information about our team. Paul made a step in the right direction in this. We need to spread information about our team to others so that they know what we can do.&lt;br /&gt;
&lt;br /&gt;
In some ways our team has failed at this, and as a consequence we've seen little success at nationals. I want our scouts to spread information and becomes friends with teams. EVERY TEAM should know a 1261 scout.&lt;br /&gt;
&lt;br /&gt;
==Why Do we Scout==&lt;br /&gt;
&lt;br /&gt;
This question is better answered with a story.&lt;br /&gt;
&lt;br /&gt;
In 2010, we won the Palmetto Regional. This regional was another 2010 regional where we fought the robot, but in the end we won. Our scouting team was firing on all cylinders. We were working with another team to create an online database, and we had people going around and talking to all of the teams.&lt;br /&gt;
&lt;br /&gt;
During qualifications, scouting was awesome. Our scouters had data, and about 10 minutes before each match, Tanner or Patrick would get a text laying out the upcoming match and our opponents. This text gave me all the information I needed and the entire alliance was able to operate at a higher level.&lt;br /&gt;
&lt;br /&gt;
For eliminations, everyone on the team sat down on Friday night to talk about prospective picks. We also had been close to team 343. And when 343 went up to number 1, we knew that were getting the first pick.&lt;br /&gt;
&lt;br /&gt;
In more ways than one, scouting ensures that things fall together. Scouting ensures that we know everything just so that we are not caught off guard or blind sighted by anything.&lt;br /&gt;
&lt;br /&gt;
==Who do we scout?==&lt;br /&gt;
&lt;br /&gt;
Everyone. Period. We need information on everyone. If team xxxx sucks, I want to know ahead of time instead of finding out when they pull their shopping cart into the queuing area.&lt;br /&gt;
&lt;br /&gt;
==How do we scout?==&lt;br /&gt;
Starting in [[2014]], the team built an app in order to collect scouting information. This helped us with efficiency and analysis, especially when paired with Tableau software. Basically we have a team of data analysts, or Tableau experts, who help us go through the data we have collected as we check for accuracy, special features of the robot, and consistency. We usually get together as a team and go through solid data as well as hear feedback from the scouts who have actually gone out and talked with the competitors. Not only is performance a factor we take into consideration, but also collaboration among our team. How can we help our alliance get to victory if we cannot work well together? We also make a list of possible picks ranked by any combination of factors and how much each factor weighs. Along with this pick list, we also make sure to think of teams we would join or not join, in the event that we are chosen by a higher seeded alliance captain. In the end, if you are not an alliance captain, it may be better to just accept whichever alliance captain chooses you, in order to ensure a playing position in the playoffs.&lt;br /&gt;
&lt;br /&gt;
Earlier, we used google docs. I know some teams use paper and folders, and I know some teams use excel. There are a million ways to scout but we need to find one that works.&lt;br /&gt;
&lt;br /&gt;
Also, during qualifications, the drive team received one text message. This helped a lot, but I think that a faster, larger system would be excellent. We should aim to get the drivers all the information they could want. If this means that a scouter runs the drivers through the next match, then so be it.&lt;br /&gt;
&lt;br /&gt;
As far as spreading information, teams often make fliers of their robots. The highlights and the strengths are on one sheet of paper. We're not saying that you need to shove information down people's throats, but people should know who team 1261 is.&lt;br /&gt;
&lt;br /&gt;
For eliminations, a top 24 teams list is very common. This is a fantasy list where we say, list the best 24 teams here, no matter where we stand or where they stand. During eliminations, this list can be gold.&lt;br /&gt;
&lt;br /&gt;
==Common Scouting Positions==&lt;br /&gt;
&lt;br /&gt;
'''Lead Scout''' - this person is also known as the President of Scouting, and is someone that both the Head Pit Scout and the Head Stand Scout communicates with in cases of retrieving information from certain teams or reporting match performances.&lt;br /&gt;
&lt;br /&gt;
'''Head Pit Scout''' - this person is the lead for all of the pit scouts and pairs up people who either work well together or who can learn a lot from each other when going out and talking to teams in the pit. This helps the team create friendships and bonds so teams know they can always trust and count on us. &lt;br /&gt;
&lt;br /&gt;
'''Head Stand Scout''' - this person is in charge of maintaining order in the stands and making sure that every team on the field is being scouted. This helps the team to collect info that determines the accuracy and performance of a team's robot, how well they work under pressure, and if what they claim in the pits is true on the field. &lt;br /&gt;
&lt;br /&gt;
'''Scout''' - You do what the lead scouts says, and you do it well. The scouting team is often considered to be frivolous where people play around and get free stuff. While this might be true, it's also necessary for the scouting team to gather and pass around information. It might be wise for a scout to stick to a group of teams and make friends if needed.&lt;br /&gt;
&lt;br /&gt;
==Whats the difference between Pit Scouting and Stand Scouting?==&lt;br /&gt;
&lt;br /&gt;
'''Pit Scouting''' - Pit scouts tend to be more extroverted. They go and talk to different teams searching for qualitative data. They also represent the team on a larger scale because they go and talk to every team that is competed with. Pit scouts tend to be more experienced members. They are called pit scouts because they walk around in the pits and talk to the teams there.&lt;br /&gt;
&lt;br /&gt;
'''Stand Scouting'''- These are the members that stay in the stands and collect quantitative data. These members tend to me more introverted or are rookie members learning the ropes of FRC. &lt;br /&gt;
&lt;br /&gt;
Whether a student is a pit scout or a stand scout is determined in scouting meetings that occur at the beginning of the FRC season. Students take a scouting text that is typically written by the president to determine if students know the year's rules properly. Then members that pass move on to the next step, whether it is participating in interviews to be a pit scout or tests to assess data input skills to be a stand scout. If a student does not pass their original scouting test that determines their knowledge about rules, they are not allowed to attend competition.&lt;br /&gt;
&lt;br /&gt;
==Stand Scouting Gear==&lt;br /&gt;
Here is the list of items needed to maximize stand scouting:&lt;br /&gt;
*Portable chargers (you will be scouting the ENTIRE game; you are bound to lose battery at some point)&lt;br /&gt;
*Power strip connected to nearby outlet to seating area (handy when you do not have a portable charger or you run out of battery on your portable charger)&lt;br /&gt;
*Team tablets (6 total)&lt;br /&gt;
*Team Laptop (at least 2 in case of emergencies; these are useful when using Tableau for alliance selections and your laptop decides to crash in the middle of it. Keep in mind to update tableau data REGULARLY to access accurate results!)&lt;br /&gt;
&lt;br /&gt;
==Head Stand Scout Obligations==&lt;br /&gt;
Here are a list of tasks that the Head Stand Scout should be responsible for: &lt;br /&gt;
*Keep track of who is using which team tablet/team portable battery (It's easy to lose these if you're not careful)&lt;br /&gt;
*Making sure each team in each match is being scouted for (drowsy members tend to miss data; this will lead to inaccurate data in Tableau)&lt;br /&gt;
*Know where all of your stand scouts are scouting from. They may move to different seating areas if the view is not optimal for them&lt;br /&gt;
*Make sure scouts get up and walk/eat every once in a while; you are the parent of the stand!&lt;br /&gt;
*Make sure power strips are accessible in the stands so everyone can recharge their devices, as well as themselves! &lt;br /&gt;
*Make sure the members are comfortable talking to you! It is easy to believe a misconception about playing strategies and points, so it is better to stop inaccurate data collecting early on rather than later, all because the members were too intimidated to talk to you&lt;br /&gt;
*Pep talk your scouts! They sit there all day long walking 100s of matches; so spread the team energy to wake them up and make sure they know that their job is worthwhile :) &lt;br /&gt;
&lt;br /&gt;
==Scouting FAQ==&lt;br /&gt;
&lt;br /&gt;
* We're ranked last, do we still need to scout?&lt;br /&gt;
**YES. If we're ranked last, there's a reason. Get out there and tell teams that we're ranked last, but we're working on it. Tell them some of our good traits and get us in their thoughts.&lt;br /&gt;
&lt;br /&gt;
*Team xxxx is our rivals, we don't need to talk to them/scout them, right?&lt;br /&gt;
**YES. No matter what you hear about team xxxx, if they're a FRC team, then we can work with them. Don't let past prejudices or differences play in. Becomes friends with everyone and you'll have limitless help.&lt;br /&gt;
&lt;br /&gt;
*Drivers are the representatives of the team, it's their job to go out and talk to teams about our robot, right?&lt;br /&gt;
**THIS IS WRONG. Drivers are way too busy. Between matches, fixing the robot, communicating with the mentors/pit crew, watching matches, talking strategy with teammates and alliance partners, drivers do not have time. Drivers should be worried about winning matches, not worried about whether we're getting picked for finals.&lt;br /&gt;
&lt;br /&gt;
Let me iterate, '''it is the task of the scouting team to make sure that our team is picked for finals.''' This responsibility does not fall onto the drivers, coach, or the human player. Getting people to know our team and robot is one of the cores of scouting. If the scouting team is not doing it, then it's not doing its job.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=TRS_Solutions</id>
		<title>TRS Solutions</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=TRS_Solutions"/>
				<updated>2017-02-20T02:38:03Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{stub}}&lt;br /&gt;
&lt;br /&gt;
{{SponsorInfoBox&lt;br /&gt;
|Image=TRS_Logo.gif&lt;br /&gt;
|Year=2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
TRS Solutions has been a [[Sponsors|sponsor]] of the Robo Lions since [[Tanner Smith]] joined robotics as his dad, [[Fred Smith]] is the president of the company.&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
*[http://trstoday.com/ TRS Solutions Website]&lt;br /&gt;
&lt;br /&gt;
[[Category:Sponsors]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney</id>
		<title>Sumaer Sahney</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney"/>
				<updated>2017-02-20T02:32:32Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* What Other Groups/Clubs Are You Involved In? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= Sumaer.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2015, 2016, 2017&lt;br /&gt;
|FreshmanInYear= 2015&lt;br /&gt;
|SophomoreInYear= 2016&lt;br /&gt;
|JuniorInYear= 2017&lt;br /&gt;
|SeniorInYear= 2018&lt;br /&gt;
|OfficerPosition=[[Webmaster]] in 2016 &amp;amp; 2017&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{PAGENAME}} is the biggest dum dum member of the team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Got You Involved in the Team?==&lt;br /&gt;
In middle school, I had friends who had joined the middle school FLL team. I saw what they were doing, and i found it very intriguing. I decided to join and enjoyed it a lot. I then decided to join the PRHS Robotics Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
[[Jane Khampha| Jane]] because she is the best VP of Communications anyone could ask for.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
My goal is to be an Entrepreneur and to start up a business.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
I enjoy programming and playing video games&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
I am also involved in TSA&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
*To be successful.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;There is an orange in my cup&amp;quot; -[[Nabil Khan]]&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
Palmetto and Peachtree, I really enjoyed the competition and I really learned a lot from them.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney</id>
		<title>Sumaer Sahney</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney"/>
				<updated>2017-02-20T02:32:20Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Favorite Robotics Moments */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= Sumaer.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2015, 2016, 2017&lt;br /&gt;
|FreshmanInYear= 2015&lt;br /&gt;
|SophomoreInYear= 2016&lt;br /&gt;
|JuniorInYear= 2017&lt;br /&gt;
|SeniorInYear= 2018&lt;br /&gt;
|OfficerPosition=[[Webmaster]] in 2016 &amp;amp; 2017&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{PAGENAME}} is the biggest dum dum member of the team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Got You Involved in the Team?==&lt;br /&gt;
In middle school, I had friends who had joined the middle school FLL team. I saw what they were doing, and i found it very intriguing. I decided to join and enjoyed it a lot. I then decided to join the PRHS Robotics Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
[[Jane Khampha| Jane]] because she is the best VP of Communications anyone could ask for.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
My goal is to be an Entrepreneur and to start up a business.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
I enjoy programming and playing video games&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
I am also involved in TSA&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
*To be successful.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;There is an orange in my cup&amp;quot; -[[Nabil Khan]]&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
Palmetto and Peachtree, I really enjoyed the competition and I really learned a lot from them.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney</id>
		<title>Sumaer Sahney</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney"/>
				<updated>2017-02-20T02:32:05Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Favorite Robotics Quote */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= Sumaer.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2015, 2016, 2017&lt;br /&gt;
|FreshmanInYear= 2015&lt;br /&gt;
|SophomoreInYear= 2016&lt;br /&gt;
|JuniorInYear= 2017&lt;br /&gt;
|SeniorInYear= 2018&lt;br /&gt;
|OfficerPosition=[[Webmaster]] in 2016 &amp;amp; 2017&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{PAGENAME}} is the biggest dum dum member of the team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Got You Involved in the Team?==&lt;br /&gt;
In middle school, I had friends who had joined the middle school FLL team. I saw what they were doing, and i found it very intriguing. I decided to join and enjoyed it a lot. I then decided to join the PRHS Robotics Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
[[Jane Khampha| Jane]] because she is the best VP of Communications anyone could ask for.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
My goal is to be an Entrepreneur and to start up a business.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
I enjoy programming and playing video games&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
I am also involved in TSA&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
*To be successful.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;There is an orange in my cup&amp;quot; -[[Nabil Khan]]&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
Palmetto and Peachtree, I really enjoyed the competition and I really learned a lot from them. Plus spending time with [[Jane Khampha]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney</id>
		<title>Sumaer Sahney</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Sumaer_Sahney"/>
				<updated>2017-02-20T02:30:24Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* What Are Your Dreams In Life? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= Sumaer.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2015, 2016, 2017&lt;br /&gt;
|FreshmanInYear= 2015&lt;br /&gt;
|SophomoreInYear= 2016&lt;br /&gt;
|JuniorInYear= 2017&lt;br /&gt;
|SeniorInYear= 2018&lt;br /&gt;
|OfficerPosition=[[Webmaster]] in 2016 &amp;amp; 2017&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{PAGENAME}} is the biggest dum dum member of the team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Got You Involved in the Team?==&lt;br /&gt;
In middle school, I had friends who had joined the middle school FLL team. I saw what they were doing, and i found it very intriguing. I decided to join and enjoyed it a lot. I then decided to join the PRHS Robotics Team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
[[Jane Khampha| Jane]] because she is the best VP of Communications anyone could ask for.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
My goal is to be an Entrepreneur and to start up a business.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
I enjoy programming and playing video games&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
I am also involved in TSA&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
*To be successful.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;[[Jane Khampha]] is the best VP of Communications in the history of communications.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
Palmetto and Peachtree, I really enjoyed the competition and I really learned a lot from them. Plus spending time with [[Jane Khampha]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Honeywell</id>
		<title>Honeywell</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Honeywell"/>
				<updated>2017-02-18T18:23:30Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{SponsorInfoBox&lt;br /&gt;
|Image=HoneywellLogo.jpg&lt;br /&gt;
|Year=2004&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Honeywell was a sponsor of robotics. Honeywell invents and manufactures technologies that address some of the world’s most critical challenges around energy, safety, security, productivity and global urbanization.&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
*[http://www51.honeywell.com/honeywell/ Honeywell Website]&lt;br /&gt;
&lt;br /&gt;
[[Category:Sponsors]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Jassy_Kim</id>
		<title>Jassy Kim</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Jassy_Kim"/>
				<updated>2017-02-11T17:02:21Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* What Got You Involved in the Team? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image=&lt;br /&gt;
|Gender= female&lt;br /&gt;
|MemberInYear= 2014, 2015, 2016&lt;br /&gt;
|FreshmanInYear= 2014&lt;br /&gt;
|SophomoreInYear= 2015&lt;br /&gt;
|JuniorInYear= 2016&lt;br /&gt;
|SeniorInYear=2017&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{PAGENAME}} is a member of the team. She is often spotted playing a musical device, such as her demonic-sounding giraffe keychain.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Got You Involved in the Team?==&lt;br /&gt;
I'm not really sure, but I guess it was that one time I volunteered in place of my friend [[Crystal Lee]] because she was sick.&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
Probably my dad. Maybe Hiroshi Ishiguro since the androids he's working on are the closest I've seen to lifelike.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
Become an engineer, but if that fails, I guess I can work on art.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
Drawing, researching stuff, sleeping, and playing instruments.&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
As of now, TSA. Might join more.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
Make an android as close to lifelike as possible.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
Going to worlds in [[2014]] was pretty fun.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management</id>
		<title>Implementation of New Management</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management"/>
				<updated>2017-01-31T19:22:30Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Implementation of New Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Implementation of New Management==&lt;br /&gt;
===Implementation of basecamp: ===&lt;br /&gt;
:o	Programmers have been using it for the best year&lt;br /&gt;
::♣	Original goal was who was working on what, what does it take to get that done, it then developed into an archive for past codes&lt;br /&gt;
::♣	[[Natalie Luong]] put all of the build blog docs on Google Drive&lt;br /&gt;
:::•	Build blog is an area that students can use to check info of they weren’t here&lt;br /&gt;
:::•	We are planning to not completely abandon the build blog this year because it would be a craze&lt;br /&gt;
:::•	Archive our engineering docs into our Google Drive&lt;br /&gt;
::♣	We want to use basecamp as away to monitor our subteams to ensure that they achieve their goals&lt;br /&gt;
:::•	We should put to-do lists in our basecamp&lt;br /&gt;
:::•	Put engineering notes into basecamp&lt;br /&gt;
:::•	Rationale: Reasoning why we made an engineering decision&lt;br /&gt;
:::•	Potentially act as our build blog not now, but one day&lt;br /&gt;
:o	All communication outlets (build blog, discord, etc) should be documented somewhere&lt;br /&gt;
::♣	Maybe some find way to make build blog links easier&lt;br /&gt;
:o	There is a video (Google Drive) folder that is shared w/all mentors and officers&lt;br /&gt;
:o	Email seems to be the most effective because motivation issues w/students&lt;br /&gt;
::♣	Checklists must be created in order to maintain motivation&lt;br /&gt;
•	Tips on how to make people be held accountable&lt;br /&gt;
:o	Charts seem to be effective (but do what’s best for you [i.e. spreadsheet w/each subteams name is labeled])&lt;br /&gt;
:o	Need to list what needs to be completed, when it needs to be completed, and what it means to be completed&lt;br /&gt;
::♣	There should be checkpoints every period to measure how close people are to your definition completion&lt;br /&gt;
:o	Subteam leaders need to “pull” their subgroup, but the subteam needs to push themselves&lt;br /&gt;
::♣	May break subteams into 2-3 subgroups giving them a role in responsibility, which gives them the desire to “push” and be held accountable &lt;br /&gt;
:::•	Similar to elected officers to appointed officers&lt;br /&gt;
:::•	May get too complicated&lt;br /&gt;
:::•	May want to only divide up small tasks &lt;br /&gt;
::::o	This would cause a “fail fast, fail cheaply” mindset&lt;br /&gt;
::♣	We may want to convey the importance of members doing their general assignment more effectively&lt;br /&gt;
:::•	Our 3 subleaders will be gone next semester, so we need to start make our students understand their responsibility&lt;br /&gt;
:::•	Gives a purpose to students, may give them a drive to work&lt;br /&gt;
::♣	Don’t know our rookies well enough to know if their want to maintain their responsibility&lt;br /&gt;
:::•	May want to deal small tasks to rookies to determine their affinity&lt;br /&gt;
•	Expectations from &lt;br /&gt;
:o	Taking lots of notes (each group should have an engineering notebook filled in w/dates, times, etc) &lt;br /&gt;
::♣	Write what works, what doesn’t&lt;br /&gt;
::♣	May include pictures (i.e. shooter designs) &lt;br /&gt;
::♣	This is basically the build blog&lt;br /&gt;
:::•	Build blogs can’t be tweaked, so engineering notebooks can be used to add new colors, new notes to older designs&lt;br /&gt;
:::•	For videos in build blog, we need to label what each video contains, how it is used, and what the results were&lt;br /&gt;
::♣	We should buckle down, and get things working now&lt;br /&gt;
:o	Subteams need to incorporate measurements in docs sent to programmers to make it easier for them to code&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management</id>
		<title>Implementation of New Management</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Implementation_of_New_Management"/>
				<updated>2017-01-31T19:20:38Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Implementation of New Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Implementation of New Management====&lt;br /&gt;
•	Implementation of basecamp: &lt;br /&gt;
:o	Programmers have been using it for the best year&lt;br /&gt;
::♣	Original goal was who was working on what, what does it take to get that done, it then developed into an archive for past codes&lt;br /&gt;
::♣	[[Natalie Luong]] put all of the build blog docs on Google Drive&lt;br /&gt;
:::•	Build blog is an area that students can use to check info of they weren’t here&lt;br /&gt;
:::•	We are planning to not completely abandon the build blog this year because it would be a craze&lt;br /&gt;
:::•	Archive our engineering docs into our Google Drive&lt;br /&gt;
::♣	We want to use basecamp as away to monitor our subteams to ensure that they achieve their goals&lt;br /&gt;
:::•	We should put to-do lists in our basecamp&lt;br /&gt;
:::•	Put engineering notes into basecamp&lt;br /&gt;
:::•	Rationale: Reasoning why we made an engineering decision&lt;br /&gt;
:::•	Potentially act as our build blog not now, but one day&lt;br /&gt;
:o	All communication outlets (build blog, discord, etc) should be documented somewhere&lt;br /&gt;
::♣	Maybe some find way to make build blog links easier&lt;br /&gt;
:o	There is a video (Google Drive) folder that is shared w/all mentors and officers&lt;br /&gt;
:o	Email seems to be the most effective because motivation issues w/students&lt;br /&gt;
::♣	Checklists must be created in order to maintain motivation&lt;br /&gt;
•	Tips on how to make people be held accountable&lt;br /&gt;
:o	Charts seem to be effective (but do what’s best for you [i.e. spreadsheet w/each subteams name is labeled])&lt;br /&gt;
:o	Need to list what needs to be completed, when it needs to be completed, and what it means to be completed&lt;br /&gt;
::♣	There should be checkpoints every period to measure how close people are to your definition completion&lt;br /&gt;
:o	Subteam leaders need to “pull” their subgroup, but the subteam needs to push themselves&lt;br /&gt;
::♣	May break subteams into 2-3 subgroups giving them a role in responsibility, which gives them the desire to “push” and be held accountable &lt;br /&gt;
:::•	Similar to elected officers to appointed officers&lt;br /&gt;
:::•	May get too complicated&lt;br /&gt;
:::•	May want to only divide up small tasks &lt;br /&gt;
::::o	This would cause a “fail fast, fail cheaply” mindset&lt;br /&gt;
::♣	We may want to convey the importance of members doing their general assignment more effectively&lt;br /&gt;
:::•	Our 3 subleaders will be gone next semester, so we need to start make our students understand their responsibility&lt;br /&gt;
:::•	Gives a purpose to students, may give them a drive to work&lt;br /&gt;
::♣	Don’t know our rookies well enough to know if their want to maintain their responsibility&lt;br /&gt;
:::•	May want to deal small tasks to rookies to determine their affinity&lt;br /&gt;
•	Expectations from &lt;br /&gt;
:o	Taking lots of notes (each group should have an engineering notebook filled in w/dates, times, etc) &lt;br /&gt;
::♣	Write what works, what doesn’t&lt;br /&gt;
::♣	May include pictures (i.e. shooter designs) &lt;br /&gt;
::♣	This is basically the build blog&lt;br /&gt;
:::•	Build blogs can’t be tweaked, so engineering notebooks can be used to add new colors, new notes to older designs&lt;br /&gt;
:::•	For videos in build blog, we need to label what each video contains, how it is used, and what the results were&lt;br /&gt;
::♣	We should buckle down, and get things working now&lt;br /&gt;
:o	Subteams need to incorporate measurements in docs sent to programmers to make it easier for them to code&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2016</id>
		<title>2016</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2016"/>
				<updated>2017-01-21T15:59:49Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Fall Activities */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
[[File:2016AlbanyWin.jpg|400px|thumb|right|Team picture of the Robo Lions in 2016]]&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
*President: [[president::Nabil Khan]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Preston Shaw]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[secretary::Jane Khampha]]&lt;br /&gt;
*Treasurer: [[treasurer::Sumedh Garimella]]&lt;br /&gt;
*Historian: [[historian::Rebeca Rodila]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Rishov Sarkar]]&lt;br /&gt;
*Webmaster: [[webmaster:: Sumaer Sahney]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Fall Activities==&lt;br /&gt;
''This was the year that the [[Attendance Clock]] was first implemented to log hours to go towards membership Robotics lettering. It was initiated by [[Scott Karlins]] (mentor of the team and father to [[Bryce Karlins]]), and then is managed by the [[Vice-President of Communications]] as well as the [[Secretary]]''&lt;br /&gt;
&lt;br /&gt;
===VEX Robotics Competition===&lt;br /&gt;
The game in the [[2015]]-[[2016]] season was [[2015 Nothing but Net | Nothing but Net]].&lt;br /&gt;
&lt;br /&gt;
===Robots at the Ridge===&lt;br /&gt;
We had a blast at our Robots at the Ridge VEX competition on Saturday, November 21st, at Peachtree Ridge High School. We had one of our VEX teams make it to the quarter-finals, but sadly not any further. Of course, at the end of the day, the [[2016]] Robo Lion members had a blast, made new friends, and some of them can't wait to start year-long VEX! We would like to thank all teams that were in attendance, as well as all the volunteers who graciously supported us throughout the event.&lt;br /&gt;
We congratulate our award winners:&lt;br /&gt;
*Tournament Champion: Team Woodward (1900R) from Woodward Academy&lt;br /&gt;
*Tournament Champion: Team GMA (1900W) from Woodward Academy&lt;br /&gt;
*Tournament Champion: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
*Excellence Award: Raider Robotics (3536M) from North Forsyth High School&lt;br /&gt;
*Judges’ Award: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
Rebeca, our [[2016]] historian, made a video recap on all the activities this year's Robo Lions were involved in.&lt;br /&gt;
&lt;br /&gt;
Curious to see all the fun? Watch it [https://drive.google.com/file/d/0B3JRwrlB1bJdUzUwRHlZOVVpN1k/view?usp=sharing here]&lt;br /&gt;
&lt;br /&gt;
==Fun Facts==&lt;br /&gt;
===Robot Rock Parody Video===&lt;br /&gt;
Over Thanksgiving Break, some members of the team got together and made a video for FIRST's 2015 Song Parody Competition.&lt;br /&gt;
&lt;br /&gt;
More info about the competition [http://www.firstinspires.org/robotics/2015-first-song-parody-competition here] &lt;br /&gt;
&lt;br /&gt;
Watch Robot Rock [https://www.youtube.com/watch?v=ybaGaAJepHY here]&lt;br /&gt;
&lt;br /&gt;
===Gwinnett Daily Post Interview===&lt;br /&gt;
The team was interviewed by Gwinnett Daily Post on November 11.&lt;br /&gt;
&lt;br /&gt;
View the full article [http://www.gwinnettdailypost.com/local/cities/duluth/with-qualifer-on-tap-peachtree-ridge-stretches-its-robotics-reach/article_6899e404-d7e5-589c-b45d-801ff2788ba6.html here]&lt;br /&gt;
&lt;br /&gt;
[[File:WaltonCollab.jpg|200px|thumb|right| Walton Collab 2k16]]&lt;br /&gt;
&lt;br /&gt;
==FIRST Robotics Competition==&lt;br /&gt;
The [[2016]] [[FRC]] Game was [[2016 FIRST Stronghold | FIRST Stronghold]].&lt;br /&gt;
===Brainstorm with Walton===&lt;br /&gt;
[[File:WaltonLove.jpg|200px|thumb|right|Walton Love 2k16]]&lt;br /&gt;
On January 10, 2016, the Robo Lions invited Walton Robotics over to collaborate on game strategies. Here are some pictures of Walton spreading the love.&lt;br /&gt;
&lt;br /&gt;
===Robots===&lt;br /&gt;
This year's robot is Khanquistador. View his reveal video [https://www.youtube.com/watch?v=HsSBCBPBLJs here].&lt;br /&gt;
&lt;br /&gt;
===Field Team===&lt;br /&gt;
The [[2016]] field team consisted of:&lt;br /&gt;
*Driver: [[driver::Preston Shaw]]&lt;br /&gt;
*Manipulator Driver: [[manipulator driver::Nabil Khan]]&lt;br /&gt;
*Coach: [[coach::Mackenzie Glaser]]&lt;br /&gt;
*Human Player: [[human player::Joel Leonardo]]&lt;br /&gt;
&lt;br /&gt;
===Districts===&lt;br /&gt;
The Georgia district model was adopted first in [[2016]], and it allowed for Georgia [[FRC]] teams to compete in-state. The Robo Lions chose to compete in 3 of the 4 available competitive events in this year: Columbus, Albany, and Kennesaw.&lt;br /&gt;
====Columbus====&lt;br /&gt;
During the weekend of March 10-12, the team headed down to Columbus to compete in the week 2 Peachtree District Qualifier. Along with their alliance Captain {{TBA|5332}}and alliance partner {{TBA|4240}}, we were able to make it all the way to the semfinals!&lt;br /&gt;
&lt;br /&gt;
====Albany====&lt;br /&gt;
The team won the tournament at the Albany District Event! Allied with teams {{TBA|3329}}and {{TBA|5651}}, we were able to rise out on top ''and'' set the record for the highest score in Georgia! The team also won the District Chairman’s Award, becoming the first team in Gwinnett County to ever win the award, giving us our second Blue Banner and automatically qualifying us for the Peachtree District State Championships. The Robo Lions were also awarded the UL Industrial Safety Award. In addition, two Robo Lions’ team members, [[Caroline Means]] and [[Mackenzie Glaser]], were named Deans List Finalists.&lt;br /&gt;
&lt;br /&gt;
====Kennesaw====&lt;br /&gt;
While it may have been Spring Break, the team topped the charts with a great win at the Kennesaw District Event, competing with a total of thirty-five other in-state teams. Having been selected by  alliance captain {{TBA|1746}}OTTO Robotics from Cumming, Ga and working alongside alliance partner {{TBA|5812}}Drewbotics from Riverdale, Ga, the teams proved indestructible scoring a whopping 154 points in the final match! With the use of vision tracking that allowed for precise high goal shots and aggressive driving skills that dominated the field, the team also won the Excellence in Engineering award sponsored by Delphi. &lt;br /&gt;
&lt;br /&gt;
===Peachtree District State Championships===&lt;br /&gt;
Having faced off against competitors of the 41 best teams throughout the state of Georgia, the team was placed as the third-seed alliance captain and made it through six rigorous playoff matches with alliance partners {{TBA|2415}}Westminster Wired Cats from Atlanta, Ga and {{TBA|4516}}Hyperion Robotics from Roswell, Ga, before losing in the Finals, but not before setting an unbeatable high score of 170 points!  The team was also awarded with the Innovation in Control Awared sponsored by Rockwell Automation, and was crowned the second ranked team in Georgia. Because of this, the team was one of twelve teams in Georgia to qualify for the World Championships to be help in St. Louis, Missouri, but the only team in Gwinnett County to do so! &lt;br /&gt;
&lt;br /&gt;
===FIRST World Championships===&lt;br /&gt;
The team was able to qualify for the FIRST Robotics World Championships that took place in St. Louis, Missouri towards the end of April. We were one of just twelve Georgia FRC teams to qualify and made it farther than we have ever done before! Clawing our way through two days of qualification matches, we placed thirteenth out of seventy-five competing teams within the Curie division. From there, they were chosen to join the 5th seed alliance captain Team 5406 Celt-X from Hamilton, Ontario, Canada and their alliance partners Team 3641 Flying Toasters from South Lyon, Michigan. Team 2883 F.R.E.D from Warroad, Minnesota was chosen to be the backup 4th robot on the alliance. The determined trio fought hard only to be stopped short in the second semi-final match, losing by a small margin. However, this still marks the farthest we've ever gotten at Worlds!&lt;br /&gt;
&lt;br /&gt;
===Awards===&lt;br /&gt;
*Industrial Design Award sponsored by General Motors at Columbus&lt;br /&gt;
*Ul Industrial Safety Hard Hat Pin at Albany&lt;br /&gt;
*Chairman's Award at Albany&lt;br /&gt;
*District Winners at Albany&lt;br /&gt;
*District Winners at Kennesaw&lt;br /&gt;
*Excellence in Engineering Award sponsored by Delphi at Kennesaw&lt;br /&gt;
*Semi-Finalists at State&lt;br /&gt;
*Innovation in Control Award sponsored by Rockwell Automation at State&lt;br /&gt;
*Semi-Finalists at the [[FIRST]] World Championships&lt;br /&gt;
&lt;br /&gt;
Check out more of our awards [[Awards | here]].&lt;br /&gt;
&lt;br /&gt;
==Off-Season Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
GRITS this year was held at Walton High School on October 10th, where the Robo Lions were able to score as runner-ups, along with alliance captain 1648 G3 Robotics and 4189 Chargers. The team also took home the Outreach Award, representing with over 25 rookie attendees.&lt;br /&gt;
&lt;br /&gt;
===GirlsFIRST Event===&lt;br /&gt;
On October 17th, 2015 Walton High School (FRC Team 2974) hosted a GirlsFIRST workshop to bond with local robotics teams as well as anyone interested from the surrounding communities. There were engineering contests, guest speakers from women in technology, driver practice with robots from past games, and tons of big smiles! A small group of girls on our team were glad that they got to participate in such an amazing event.&lt;br /&gt;
&lt;br /&gt;
==Spring Activities==&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
&lt;br /&gt;
[[File:2016_ParsonsSTEM.jpg|200px|thumb|right|The Robo Lions at Parsons STEM Night]]&lt;br /&gt;
&lt;br /&gt;
On Thursday, February 4th, the team headed next door to Parsons Elementary school for an awesome night of robotics demonstrations! Our new outreach VEX robot made its debut, shooting balls across the cafeteria. Many of the students were eager to bring the balls back and even got to try their hand at driving the robot. Genesis, the 2014 competition robot, served us well once as we watched students jump up to catch the ball. A huge thanks to Parsons for having us and to all of the Robo Lions who helped make this night run smoothly!&lt;br /&gt;
&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
Mason STEM Night- Members of the team brought a VEX Robot and the 2014 Aerial Assist Robot to Mason Elementary to participate in a robotics showcase alongside GSMST Robotics and the Mason FLL team. Students were excited to jump up to catch the ball as the robot launched it across the room while others drove the VEX robot. It was really great to see the new members of the team connect with the elementary students, making sure all were safe around the robot and even sharing a dance or two! Prior to the night, students helped judge science fair entries which were also on display for parents that night. We had tons of kids take interest in the robot and we really loved being able to connect the kids’ experiences with robotics to our own robotics experiences!&lt;br /&gt;
&lt;br /&gt;
===Burnette Science Night===&lt;br /&gt;
[[File:2016Burnette.jpg|200px|thumb|right|The Robo Lions at Burnette Science Night]]&lt;br /&gt;
On February 11th, the team attended their first Burnette Elementary’s Science Night. It was great to drive around our 2014 FRC robot and our VEX Outreach robot, as we had lots of interest and answered tons of great questions. We spoke with Ms. Reed, the Principal, about furthering their robotics program, and are excited to continue working with the school!&lt;br /&gt;
&lt;br /&gt;
===Lawrenceville Rotary Club Meeting===&lt;br /&gt;
Seven enthusiastic members of the Peachtree Ridge High School Robotics Team presented information about their activities to the Rotary Club of Lawrenceville on April 4. [[2016]] [[Drive Team]] and [[2016]] [[Executives |Executive Officers]] described how the competitions worked and how the group went about preparing their robots for the competitions. The group is not only about engineering and business tasks; it is about building relationships, developing leadership skills, engaging in teamwork, and outreaching within the community. They displayed two of their robots and showed a video about the “Robo Lions spirit” that won a prize at a recent competition.&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2016]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2016]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2016]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2016}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2016]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2016}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2016</id>
		<title>2016</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2016"/>
				<updated>2017-01-21T15:59:01Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Fall Activities */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
[[File:2016AlbanyWin.jpg|400px|thumb|right|Team picture of the Robo Lions in 2016]]&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
*President: [[president::Nabil Khan]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Preston Shaw]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[secretary::Jane Khampha]]&lt;br /&gt;
*Treasurer: [[treasurer::Sumedh Garimella]]&lt;br /&gt;
*Historian: [[historian::Rebeca Rodila]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Rishov Sarkar]]&lt;br /&gt;
*Webmaster: [[webmaster:: Sumaer Sahney]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Fall Activities==&lt;br /&gt;
This was the year that the [[Attendance Clock]] was first implemented to log hours to go towards membership Robotics lettering. It was initiated by [[Scott Karlins]] (mentor of the team and father to [[Bryce Karlins]]), and then is managed by the [[Vice-President of Communications]] as well as the [[Secretary]]&lt;br /&gt;
&lt;br /&gt;
===VEX Robotics Competition===&lt;br /&gt;
The game in the [[2015]]-[[2016]] season was [[2015 Nothing but Net | Nothing but Net]].&lt;br /&gt;
&lt;br /&gt;
===Robots at the Ridge===&lt;br /&gt;
We had a blast at our Robots at the Ridge VEX competition on Saturday, November 21st, at Peachtree Ridge High School. We had one of our VEX teams make it to the quarter-finals, but sadly not any further. Of course, at the end of the day, the [[2016]] Robo Lion members had a blast, made new friends, and some of them can't wait to start year-long VEX! We would like to thank all teams that were in attendance, as well as all the volunteers who graciously supported us throughout the event.&lt;br /&gt;
We congratulate our award winners:&lt;br /&gt;
*Tournament Champion: Team Woodward (1900R) from Woodward Academy&lt;br /&gt;
*Tournament Champion: Team GMA (1900W) from Woodward Academy&lt;br /&gt;
*Tournament Champion: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
*Excellence Award: Raider Robotics (3536M) from North Forsyth High School&lt;br /&gt;
*Judges’ Award: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
Rebeca, our [[2016]] historian, made a video recap on all the activities this year's Robo Lions were involved in.&lt;br /&gt;
&lt;br /&gt;
Curious to see all the fun? Watch it [https://drive.google.com/file/d/0B3JRwrlB1bJdUzUwRHlZOVVpN1k/view?usp=sharing here]&lt;br /&gt;
&lt;br /&gt;
==Fun Facts==&lt;br /&gt;
===Robot Rock Parody Video===&lt;br /&gt;
Over Thanksgiving Break, some members of the team got together and made a video for FIRST's 2015 Song Parody Competition.&lt;br /&gt;
&lt;br /&gt;
More info about the competition [http://www.firstinspires.org/robotics/2015-first-song-parody-competition here] &lt;br /&gt;
&lt;br /&gt;
Watch Robot Rock [https://www.youtube.com/watch?v=ybaGaAJepHY here]&lt;br /&gt;
&lt;br /&gt;
===Gwinnett Daily Post Interview===&lt;br /&gt;
The team was interviewed by Gwinnett Daily Post on November 11.&lt;br /&gt;
&lt;br /&gt;
View the full article [http://www.gwinnettdailypost.com/local/cities/duluth/with-qualifer-on-tap-peachtree-ridge-stretches-its-robotics-reach/article_6899e404-d7e5-589c-b45d-801ff2788ba6.html here]&lt;br /&gt;
&lt;br /&gt;
[[File:WaltonCollab.jpg|200px|thumb|right| Walton Collab 2k16]]&lt;br /&gt;
&lt;br /&gt;
==FIRST Robotics Competition==&lt;br /&gt;
The [[2016]] [[FRC]] Game was [[2016 FIRST Stronghold | FIRST Stronghold]].&lt;br /&gt;
===Brainstorm with Walton===&lt;br /&gt;
[[File:WaltonLove.jpg|200px|thumb|right|Walton Love 2k16]]&lt;br /&gt;
On January 10, 2016, the Robo Lions invited Walton Robotics over to collaborate on game strategies. Here are some pictures of Walton spreading the love.&lt;br /&gt;
&lt;br /&gt;
===Robots===&lt;br /&gt;
This year's robot is Khanquistador. View his reveal video [https://www.youtube.com/watch?v=HsSBCBPBLJs here].&lt;br /&gt;
&lt;br /&gt;
===Field Team===&lt;br /&gt;
The [[2016]] field team consisted of:&lt;br /&gt;
*Driver: [[driver::Preston Shaw]]&lt;br /&gt;
*Manipulator Driver: [[manipulator driver::Nabil Khan]]&lt;br /&gt;
*Coach: [[coach::Mackenzie Glaser]]&lt;br /&gt;
*Human Player: [[human player::Joel Leonardo]]&lt;br /&gt;
&lt;br /&gt;
===Districts===&lt;br /&gt;
The Georgia district model was adopted first in [[2016]], and it allowed for Georgia [[FRC]] teams to compete in-state. The Robo Lions chose to compete in 3 of the 4 available competitive events in this year: Columbus, Albany, and Kennesaw.&lt;br /&gt;
====Columbus====&lt;br /&gt;
During the weekend of March 10-12, the team headed down to Columbus to compete in the week 2 Peachtree District Qualifier. Along with their alliance Captain {{TBA|5332}}and alliance partner {{TBA|4240}}, we were able to make it all the way to the semfinals!&lt;br /&gt;
&lt;br /&gt;
====Albany====&lt;br /&gt;
The team won the tournament at the Albany District Event! Allied with teams {{TBA|3329}}and {{TBA|5651}}, we were able to rise out on top ''and'' set the record for the highest score in Georgia! The team also won the District Chairman’s Award, becoming the first team in Gwinnett County to ever win the award, giving us our second Blue Banner and automatically qualifying us for the Peachtree District State Championships. The Robo Lions were also awarded the UL Industrial Safety Award. In addition, two Robo Lions’ team members, [[Caroline Means]] and [[Mackenzie Glaser]], were named Deans List Finalists.&lt;br /&gt;
&lt;br /&gt;
====Kennesaw====&lt;br /&gt;
While it may have been Spring Break, the team topped the charts with a great win at the Kennesaw District Event, competing with a total of thirty-five other in-state teams. Having been selected by  alliance captain {{TBA|1746}}OTTO Robotics from Cumming, Ga and working alongside alliance partner {{TBA|5812}}Drewbotics from Riverdale, Ga, the teams proved indestructible scoring a whopping 154 points in the final match! With the use of vision tracking that allowed for precise high goal shots and aggressive driving skills that dominated the field, the team also won the Excellence in Engineering award sponsored by Delphi. &lt;br /&gt;
&lt;br /&gt;
===Peachtree District State Championships===&lt;br /&gt;
Having faced off against competitors of the 41 best teams throughout the state of Georgia, the team was placed as the third-seed alliance captain and made it through six rigorous playoff matches with alliance partners {{TBA|2415}}Westminster Wired Cats from Atlanta, Ga and {{TBA|4516}}Hyperion Robotics from Roswell, Ga, before losing in the Finals, but not before setting an unbeatable high score of 170 points!  The team was also awarded with the Innovation in Control Awared sponsored by Rockwell Automation, and was crowned the second ranked team in Georgia. Because of this, the team was one of twelve teams in Georgia to qualify for the World Championships to be help in St. Louis, Missouri, but the only team in Gwinnett County to do so! &lt;br /&gt;
&lt;br /&gt;
===FIRST World Championships===&lt;br /&gt;
The team was able to qualify for the FIRST Robotics World Championships that took place in St. Louis, Missouri towards the end of April. We were one of just twelve Georgia FRC teams to qualify and made it farther than we have ever done before! Clawing our way through two days of qualification matches, we placed thirteenth out of seventy-five competing teams within the Curie division. From there, they were chosen to join the 5th seed alliance captain Team 5406 Celt-X from Hamilton, Ontario, Canada and their alliance partners Team 3641 Flying Toasters from South Lyon, Michigan. Team 2883 F.R.E.D from Warroad, Minnesota was chosen to be the backup 4th robot on the alliance. The determined trio fought hard only to be stopped short in the second semi-final match, losing by a small margin. However, this still marks the farthest we've ever gotten at Worlds!&lt;br /&gt;
&lt;br /&gt;
===Awards===&lt;br /&gt;
*Industrial Design Award sponsored by General Motors at Columbus&lt;br /&gt;
*Ul Industrial Safety Hard Hat Pin at Albany&lt;br /&gt;
*Chairman's Award at Albany&lt;br /&gt;
*District Winners at Albany&lt;br /&gt;
*District Winners at Kennesaw&lt;br /&gt;
*Excellence in Engineering Award sponsored by Delphi at Kennesaw&lt;br /&gt;
*Semi-Finalists at State&lt;br /&gt;
*Innovation in Control Award sponsored by Rockwell Automation at State&lt;br /&gt;
*Semi-Finalists at the [[FIRST]] World Championships&lt;br /&gt;
&lt;br /&gt;
Check out more of our awards [[Awards | here]].&lt;br /&gt;
&lt;br /&gt;
==Off-Season Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
GRITS this year was held at Walton High School on October 10th, where the Robo Lions were able to score as runner-ups, along with alliance captain 1648 G3 Robotics and 4189 Chargers. The team also took home the Outreach Award, representing with over 25 rookie attendees.&lt;br /&gt;
&lt;br /&gt;
===GirlsFIRST Event===&lt;br /&gt;
On October 17th, 2015 Walton High School (FRC Team 2974) hosted a GirlsFIRST workshop to bond with local robotics teams as well as anyone interested from the surrounding communities. There were engineering contests, guest speakers from women in technology, driver practice with robots from past games, and tons of big smiles! A small group of girls on our team were glad that they got to participate in such an amazing event.&lt;br /&gt;
&lt;br /&gt;
==Spring Activities==&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
&lt;br /&gt;
[[File:2016_ParsonsSTEM.jpg|200px|thumb|right|The Robo Lions at Parsons STEM Night]]&lt;br /&gt;
&lt;br /&gt;
On Thursday, February 4th, the team headed next door to Parsons Elementary school for an awesome night of robotics demonstrations! Our new outreach VEX robot made its debut, shooting balls across the cafeteria. Many of the students were eager to bring the balls back and even got to try their hand at driving the robot. Genesis, the 2014 competition robot, served us well once as we watched students jump up to catch the ball. A huge thanks to Parsons for having us and to all of the Robo Lions who helped make this night run smoothly!&lt;br /&gt;
&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
Mason STEM Night- Members of the team brought a VEX Robot and the 2014 Aerial Assist Robot to Mason Elementary to participate in a robotics showcase alongside GSMST Robotics and the Mason FLL team. Students were excited to jump up to catch the ball as the robot launched it across the room while others drove the VEX robot. It was really great to see the new members of the team connect with the elementary students, making sure all were safe around the robot and even sharing a dance or two! Prior to the night, students helped judge science fair entries which were also on display for parents that night. We had tons of kids take interest in the robot and we really loved being able to connect the kids’ experiences with robotics to our own robotics experiences!&lt;br /&gt;
&lt;br /&gt;
===Burnette Science Night===&lt;br /&gt;
[[File:2016Burnette.jpg|200px|thumb|right|The Robo Lions at Burnette Science Night]]&lt;br /&gt;
On February 11th, the team attended their first Burnette Elementary’s Science Night. It was great to drive around our 2014 FRC robot and our VEX Outreach robot, as we had lots of interest and answered tons of great questions. We spoke with Ms. Reed, the Principal, about furthering their robotics program, and are excited to continue working with the school!&lt;br /&gt;
&lt;br /&gt;
===Lawrenceville Rotary Club Meeting===&lt;br /&gt;
Seven enthusiastic members of the Peachtree Ridge High School Robotics Team presented information about their activities to the Rotary Club of Lawrenceville on April 4. [[2016]] [[Drive Team]] and [[2016]] [[Executives |Executive Officers]] described how the competitions worked and how the group went about preparing their robots for the competitions. The group is not only about engineering and business tasks; it is about building relationships, developing leadership skills, engaging in teamwork, and outreaching within the community. They displayed two of their robots and showed a video about the “Robo Lions spirit” that won a prize at a recent competition.&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2016]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2016]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2016]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2016}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2016]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2016}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2016</id>
		<title>2016</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2016"/>
				<updated>2017-01-21T15:58:35Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Fall Activities */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
[[File:2016AlbanyWin.jpg|400px|thumb|right|Team picture of the Robo Lions in 2016]]&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
*President: [[president::Nabil Khan]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Preston Shaw]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[secretary::Jane Khampha]]&lt;br /&gt;
*Treasurer: [[treasurer::Sumedh Garimella]]&lt;br /&gt;
*Historian: [[historian::Rebeca Rodila]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Rishov Sarkar]]&lt;br /&gt;
*Webmaster: [[webmaster:: Sumaer Sahney]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Fall Activities==&lt;br /&gt;
This was the year that the [[Attendance Clock]] was first implemented to log hours to go towards membership Robotics lettering. It was initiated by [[Scott Karlins]], and then is managed by the [[Vice-President of Communications]] as well as the [[Secretary]]&lt;br /&gt;
&lt;br /&gt;
===VEX Robotics Competition===&lt;br /&gt;
The game in the [[2015]]-[[2016]] season was [[2015 Nothing but Net | Nothing but Net]].&lt;br /&gt;
&lt;br /&gt;
===Robots at the Ridge===&lt;br /&gt;
We had a blast at our Robots at the Ridge VEX competition on Saturday, November 21st, at Peachtree Ridge High School. We had one of our VEX teams make it to the quarter-finals, but sadly not any further. Of course, at the end of the day, the [[2016]] Robo Lion members had a blast, made new friends, and some of them can't wait to start year-long VEX! We would like to thank all teams that were in attendance, as well as all the volunteers who graciously supported us throughout the event.&lt;br /&gt;
We congratulate our award winners:&lt;br /&gt;
*Tournament Champion: Team Woodward (1900R) from Woodward Academy&lt;br /&gt;
*Tournament Champion: Team GMA (1900W) from Woodward Academy&lt;br /&gt;
*Tournament Champion: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
*Excellence Award: Raider Robotics (3536M) from North Forsyth High School&lt;br /&gt;
*Judges’ Award: RoboDragons E (675E) from Gwinnett School of Mathematics, Science, and Technology&lt;br /&gt;
&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
Rebeca, our [[2016]] historian, made a video recap on all the activities this year's Robo Lions were involved in.&lt;br /&gt;
&lt;br /&gt;
Curious to see all the fun? Watch it [https://drive.google.com/file/d/0B3JRwrlB1bJdUzUwRHlZOVVpN1k/view?usp=sharing here]&lt;br /&gt;
&lt;br /&gt;
==Fun Facts==&lt;br /&gt;
===Robot Rock Parody Video===&lt;br /&gt;
Over Thanksgiving Break, some members of the team got together and made a video for FIRST's 2015 Song Parody Competition.&lt;br /&gt;
&lt;br /&gt;
More info about the competition [http://www.firstinspires.org/robotics/2015-first-song-parody-competition here] &lt;br /&gt;
&lt;br /&gt;
Watch Robot Rock [https://www.youtube.com/watch?v=ybaGaAJepHY here]&lt;br /&gt;
&lt;br /&gt;
===Gwinnett Daily Post Interview===&lt;br /&gt;
The team was interviewed by Gwinnett Daily Post on November 11.&lt;br /&gt;
&lt;br /&gt;
View the full article [http://www.gwinnettdailypost.com/local/cities/duluth/with-qualifer-on-tap-peachtree-ridge-stretches-its-robotics-reach/article_6899e404-d7e5-589c-b45d-801ff2788ba6.html here]&lt;br /&gt;
&lt;br /&gt;
[[File:WaltonCollab.jpg|200px|thumb|right| Walton Collab 2k16]]&lt;br /&gt;
&lt;br /&gt;
==FIRST Robotics Competition==&lt;br /&gt;
The [[2016]] [[FRC]] Game was [[2016 FIRST Stronghold | FIRST Stronghold]].&lt;br /&gt;
===Brainstorm with Walton===&lt;br /&gt;
[[File:WaltonLove.jpg|200px|thumb|right|Walton Love 2k16]]&lt;br /&gt;
On January 10, 2016, the Robo Lions invited Walton Robotics over to collaborate on game strategies. Here are some pictures of Walton spreading the love.&lt;br /&gt;
&lt;br /&gt;
===Robots===&lt;br /&gt;
This year's robot is Khanquistador. View his reveal video [https://www.youtube.com/watch?v=HsSBCBPBLJs here].&lt;br /&gt;
&lt;br /&gt;
===Field Team===&lt;br /&gt;
The [[2016]] field team consisted of:&lt;br /&gt;
*Driver: [[driver::Preston Shaw]]&lt;br /&gt;
*Manipulator Driver: [[manipulator driver::Nabil Khan]]&lt;br /&gt;
*Coach: [[coach::Mackenzie Glaser]]&lt;br /&gt;
*Human Player: [[human player::Joel Leonardo]]&lt;br /&gt;
&lt;br /&gt;
===Districts===&lt;br /&gt;
The Georgia district model was adopted first in [[2016]], and it allowed for Georgia [[FRC]] teams to compete in-state. The Robo Lions chose to compete in 3 of the 4 available competitive events in this year: Columbus, Albany, and Kennesaw.&lt;br /&gt;
====Columbus====&lt;br /&gt;
During the weekend of March 10-12, the team headed down to Columbus to compete in the week 2 Peachtree District Qualifier. Along with their alliance Captain {{TBA|5332}}and alliance partner {{TBA|4240}}, we were able to make it all the way to the semfinals!&lt;br /&gt;
&lt;br /&gt;
====Albany====&lt;br /&gt;
The team won the tournament at the Albany District Event! Allied with teams {{TBA|3329}}and {{TBA|5651}}, we were able to rise out on top ''and'' set the record for the highest score in Georgia! The team also won the District Chairman’s Award, becoming the first team in Gwinnett County to ever win the award, giving us our second Blue Banner and automatically qualifying us for the Peachtree District State Championships. The Robo Lions were also awarded the UL Industrial Safety Award. In addition, two Robo Lions’ team members, [[Caroline Means]] and [[Mackenzie Glaser]], were named Deans List Finalists.&lt;br /&gt;
&lt;br /&gt;
====Kennesaw====&lt;br /&gt;
While it may have been Spring Break, the team topped the charts with a great win at the Kennesaw District Event, competing with a total of thirty-five other in-state teams. Having been selected by  alliance captain {{TBA|1746}}OTTO Robotics from Cumming, Ga and working alongside alliance partner {{TBA|5812}}Drewbotics from Riverdale, Ga, the teams proved indestructible scoring a whopping 154 points in the final match! With the use of vision tracking that allowed for precise high goal shots and aggressive driving skills that dominated the field, the team also won the Excellence in Engineering award sponsored by Delphi. &lt;br /&gt;
&lt;br /&gt;
===Peachtree District State Championships===&lt;br /&gt;
Having faced off against competitors of the 41 best teams throughout the state of Georgia, the team was placed as the third-seed alliance captain and made it through six rigorous playoff matches with alliance partners {{TBA|2415}}Westminster Wired Cats from Atlanta, Ga and {{TBA|4516}}Hyperion Robotics from Roswell, Ga, before losing in the Finals, but not before setting an unbeatable high score of 170 points!  The team was also awarded with the Innovation in Control Awared sponsored by Rockwell Automation, and was crowned the second ranked team in Georgia. Because of this, the team was one of twelve teams in Georgia to qualify for the World Championships to be help in St. Louis, Missouri, but the only team in Gwinnett County to do so! &lt;br /&gt;
&lt;br /&gt;
===FIRST World Championships===&lt;br /&gt;
The team was able to qualify for the FIRST Robotics World Championships that took place in St. Louis, Missouri towards the end of April. We were one of just twelve Georgia FRC teams to qualify and made it farther than we have ever done before! Clawing our way through two days of qualification matches, we placed thirteenth out of seventy-five competing teams within the Curie division. From there, they were chosen to join the 5th seed alliance captain Team 5406 Celt-X from Hamilton, Ontario, Canada and their alliance partners Team 3641 Flying Toasters from South Lyon, Michigan. Team 2883 F.R.E.D from Warroad, Minnesota was chosen to be the backup 4th robot on the alliance. The determined trio fought hard only to be stopped short in the second semi-final match, losing by a small margin. However, this still marks the farthest we've ever gotten at Worlds!&lt;br /&gt;
&lt;br /&gt;
===Awards===&lt;br /&gt;
*Industrial Design Award sponsored by General Motors at Columbus&lt;br /&gt;
*Ul Industrial Safety Hard Hat Pin at Albany&lt;br /&gt;
*Chairman's Award at Albany&lt;br /&gt;
*District Winners at Albany&lt;br /&gt;
*District Winners at Kennesaw&lt;br /&gt;
*Excellence in Engineering Award sponsored by Delphi at Kennesaw&lt;br /&gt;
*Semi-Finalists at State&lt;br /&gt;
*Innovation in Control Award sponsored by Rockwell Automation at State&lt;br /&gt;
*Semi-Finalists at the [[FIRST]] World Championships&lt;br /&gt;
&lt;br /&gt;
Check out more of our awards [[Awards | here]].&lt;br /&gt;
&lt;br /&gt;
==Off-Season Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
GRITS this year was held at Walton High School on October 10th, where the Robo Lions were able to score as runner-ups, along with alliance captain 1648 G3 Robotics and 4189 Chargers. The team also took home the Outreach Award, representing with over 25 rookie attendees.&lt;br /&gt;
&lt;br /&gt;
===GirlsFIRST Event===&lt;br /&gt;
On October 17th, 2015 Walton High School (FRC Team 2974) hosted a GirlsFIRST workshop to bond with local robotics teams as well as anyone interested from the surrounding communities. There were engineering contests, guest speakers from women in technology, driver practice with robots from past games, and tons of big smiles! A small group of girls on our team were glad that they got to participate in such an amazing event.&lt;br /&gt;
&lt;br /&gt;
==Spring Activities==&lt;br /&gt;
===Parsons STEM Night===&lt;br /&gt;
&lt;br /&gt;
[[File:2016_ParsonsSTEM.jpg|200px|thumb|right|The Robo Lions at Parsons STEM Night]]&lt;br /&gt;
&lt;br /&gt;
On Thursday, February 4th, the team headed next door to Parsons Elementary school for an awesome night of robotics demonstrations! Our new outreach VEX robot made its debut, shooting balls across the cafeteria. Many of the students were eager to bring the balls back and even got to try their hand at driving the robot. Genesis, the 2014 competition robot, served us well once as we watched students jump up to catch the ball. A huge thanks to Parsons for having us and to all of the Robo Lions who helped make this night run smoothly!&lt;br /&gt;
&lt;br /&gt;
===Mason STEM Night===&lt;br /&gt;
Mason STEM Night- Members of the team brought a VEX Robot and the 2014 Aerial Assist Robot to Mason Elementary to participate in a robotics showcase alongside GSMST Robotics and the Mason FLL team. Students were excited to jump up to catch the ball as the robot launched it across the room while others drove the VEX robot. It was really great to see the new members of the team connect with the elementary students, making sure all were safe around the robot and even sharing a dance or two! Prior to the night, students helped judge science fair entries which were also on display for parents that night. We had tons of kids take interest in the robot and we really loved being able to connect the kids’ experiences with robotics to our own robotics experiences!&lt;br /&gt;
&lt;br /&gt;
===Burnette Science Night===&lt;br /&gt;
[[File:2016Burnette.jpg|200px|thumb|right|The Robo Lions at Burnette Science Night]]&lt;br /&gt;
On February 11th, the team attended their first Burnette Elementary’s Science Night. It was great to drive around our 2014 FRC robot and our VEX Outreach robot, as we had lots of interest and answered tons of great questions. We spoke with Ms. Reed, the Principal, about furthering their robotics program, and are excited to continue working with the school!&lt;br /&gt;
&lt;br /&gt;
===Lawrenceville Rotary Club Meeting===&lt;br /&gt;
Seven enthusiastic members of the Peachtree Ridge High School Robotics Team presented information about their activities to the Rotary Club of Lawrenceville on April 4. [[2016]] [[Drive Team]] and [[2016]] [[Executives |Executive Officers]] described how the competitions worked and how the group went about preparing their robots for the competitions. The group is not only about engineering and business tasks; it is about building relationships, developing leadership skills, engaging in teamwork, and outreaching within the community. They displayed two of their robots and showed a video about the “Robo Lions spirit” that won a prize at a recent competition.&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2016]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2016]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2016]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2016]][[member of robotics in year::2016]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2016}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2016]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2016}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock</id>
		<title>Attendance Clock</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock"/>
				<updated>2017-01-21T15:56:32Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Opening the fingerprint scanner application on PC */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The attendance clock was adopted in [[2015]] when [[Scott Karlins]] introduced the device to the team. It is a fingerprint scanner that takes a member's fingerprint and logs in their hours for certain events or general team meetings. This is used to compile hours gathered by members over the year to see if they are eligible to earn a robotics varsity letter. &lt;br /&gt;
&lt;br /&gt;
=How it Works=&lt;br /&gt;
The team has a laptop dedicated for this fingerprint scanner's operations. &lt;br /&gt;
&lt;br /&gt;
==Opening the fingerprint scanner application on PC==&lt;br /&gt;
#Plug in flash drive found in fingerprint scanner package&lt;br /&gt;
#Use USB cable to connect the fingerprint scanner device onto the PC. Wait for fingerprint scanner to power up. &lt;br /&gt;
#Open files on the flash drive, and locate the folder labeled “RAMS”&lt;br /&gt;
#Open the RAS application&lt;br /&gt;
#Once opened, the RAS application should reveal a login box where you enter a password. The password is “RoboLions!” (as of 2015)&lt;br /&gt;
#Once logged in, the main screen should appear. It should have options such as creating a new user, device management, attendance management, etc&lt;br /&gt;
&lt;br /&gt;
===Logging in to the fingerprint scanner device===&lt;br /&gt;
#Make sure the fingerprint scanner is either plugged into a nearby outlet or a PC in order to power itself up &lt;br /&gt;
#Press the MENU button after the main screen has opened on the device&lt;br /&gt;
#This should prompt the device to display the word “Manager?” on the screen. Your user/ID card must be made a manager in order to manage the device.&lt;br /&gt;
#To log in as a manager, enter your user ID number. This is the number you are assigned when you are created an ID card on the fingerprint scanner device.&lt;br /&gt;
#Enter in your password. The default password for a manager is 1261.&lt;br /&gt;
#This should prompt you to a page of different options, such as User, Log data, U-Disk, Setting, and About&lt;br /&gt;
&lt;br /&gt;
====Editing an existing ID card to create a new User ID Card====&lt;br /&gt;
#This is the first step in adding a new member to the fingerprint scanner system. First, make sure you have cleared the ID cards of discontinued members of the team from the roster that can be found on the PC application. Do not delete them completely; this can be replaced with new members’ information. #Instead, delete the fingerprints and edit the name/gender/cardID.&lt;br /&gt;
#To delete fingerprints from an ID card, you must have the fingerprint scanner device open to the main page. Navigate to menu → user → delete and locate the particular ID card using the roster that can be found on the fingerprint scanner PC application. Use the arrow keys to select fingerprints to delete. Make sure to delete both fingerprint scans of the previous user. Make sure to also select “Get all Enroll” in device management of the PC application in order to sync both medias.&lt;br /&gt;
#To edit the ID card, you must use the fingerprint scanner PC application. Locate the user+ option and select the specified user. Right click on the user and select edit, and you are able to clear the name/gender/cardID as needed. Be sure to select the second tab of the ID card labeled: “Extend Info” to clear the user’s title.&lt;br /&gt;
&lt;br /&gt;
====Creating a new User ID Card from scratch====&lt;br /&gt;
#Open the fingerprint scanner PC application.&lt;br /&gt;
#Locate the user+ option. There is a plus sign at the top of the page that enables you to create a new ID card. Click this and fill in all of the necessary information found below:&lt;br /&gt;
#*Enroll ID/Card ID&lt;br /&gt;
#*Name (enter in the member’s full name)&lt;br /&gt;
#*User ID (this should be the same as the enroll/card ID number)&lt;br /&gt;
#*Gender &lt;br /&gt;
#*Default attendance should display as followed: Duty, Robotics.&lt;br /&gt;
#*Default password should be entered at the User ID&lt;br /&gt;
#There is another page that should be edited. Look at the top of the window and click the second tab labeled “Extend Info”&lt;br /&gt;
#*Un-select the boxes labeled: 1st lock, 2nd lock&lt;br /&gt;
#*Fill in the title name (first name.last initial; like the @prhsrobotics email accounts)&lt;br /&gt;
#Done! Now, you must sync the information to the device. Navigate to the fingerprint scanner application and locate the device management option. Click “Upload all enroll”&lt;br /&gt;
#Wait for the device to finish syncing. Check to make sure the sync has worked by logging in on the device and checking the roster using manager login, and selecting “user” → “Enroll” and navigate using the arrow keys or the number keys.&lt;br /&gt;
&lt;br /&gt;
====Adding in fingerprints to an existing ID card====&lt;br /&gt;
#You must have created a correlating ID card on the fingerprint scanner application and have it uploaded on the device in order to add new fingerprints. You cannot add fingerprints that won’t be going anywhere!&lt;br /&gt;
#Log in to the fingerprint scanner device.&lt;br /&gt;
#Select “user” → “enter”. Navigate the roster using the arrows/numbers key by user ID number. &lt;br /&gt;
#Ask the person to swipe the scanner 3 times each with one hand’s index finger. The page should prompt the question, “Continue”. Enter “yes” and swipe the other hand’s index finger 3 times. &lt;br /&gt;
#When complete, exit to the main page of the device. Navigate the fingerprint scanner PC application and click “Device management” &lt;br /&gt;
#Select “get all enroll” to sync fingerprints with the PC app.&lt;br /&gt;
#Wait until scanner has finished syncing and test the sync completion by having the person swipe the scanner.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock</id>
		<title>Attendance Clock</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock"/>
				<updated>2017-01-21T15:55:35Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Creating a new User ID Card from scratch */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The attendance clock was adopted in [[2015]] when [[Scott Karlins]] introduced the device to the team. It is a fingerprint scanner that takes a member's fingerprint and logs in their hours for certain events or general team meetings. This is used to compile hours gathered by members over the year to see if they are eligible to earn a robotics varsity letter. &lt;br /&gt;
&lt;br /&gt;
=How it Works=&lt;br /&gt;
The team has a laptop dedicated for this fingerprint scanner's operations. &lt;br /&gt;
&lt;br /&gt;
==Opening the fingerprint scanner application on PC==&lt;br /&gt;
#Plug in flash drive found in fingerprint scanner package&lt;br /&gt;
#Use USB cable to connect the fingerprint scanner device onto the PC. Wait for fingerprint scanner to power up. &lt;br /&gt;
#Open files on the flash drive, and locate the folder labeled “RAMS”&lt;br /&gt;
#Open the RAS application&lt;br /&gt;
#Once opened, the RAS application should reveal a login box where you enter a password. The password is “RoboLions!” (as of 2015)&lt;br /&gt;
#Once logged in, the main screen should appear. It should have options such as creating a new user, device management, attendance management, etc&lt;br /&gt;
&lt;br /&gt;
===Logging in to the fingerprint scanner device===&lt;br /&gt;
#Make sure the fingerprint scanner is either plugged into a nearby outlet or a PC in order to power itself up &lt;br /&gt;
#Press the MENU button after the main screen has opened on the device&lt;br /&gt;
#This should prompt the device to display the word “Manager?” on the screen. Your user/ID card must be made a manager in order to manage the device.&lt;br /&gt;
#To log in as a manager, enter your user ID number. This is the number you are assigned when you are created an ID card on the fingerprint scanner device.&lt;br /&gt;
#Enter in your password. The default password for a manager is 1261.&lt;br /&gt;
#This should prompt you to a page of different options, such as User, Log data, U-Disk, Setting, and About&lt;br /&gt;
&lt;br /&gt;
===Editing an existing ID card to create a new User ID Card===&lt;br /&gt;
#This is the first step in adding a new member to the fingerprint scanner system. First, make sure you have cleared the ID cards of discontinued members of the team from the roster that can be found on the PC application. Do not delete them completely; this can be replaced with new members’ information. #Instead, delete the fingerprints and edit the name/gender/cardID.&lt;br /&gt;
#To delete fingerprints from an ID card, you must have the fingerprint scanner device open to the main page. Navigate to menu → user → delete and locate the particular ID card using the roster that can be found on the fingerprint scanner PC application. Use the arrow keys to select fingerprints to delete. Make sure to delete both fingerprint scans of the previous user. Make sure to also select “Get all Enroll” in device management of the PC application in order to sync both medias.&lt;br /&gt;
#To edit the ID card, you must use the fingerprint scanner PC application. Locate the user+ option and select the specified user. Right click on the user and select edit, and you are able to clear the name/gender/cardID as needed. Be sure to select the second tab of the ID card labeled: “Extend Info” to clear the user’s title.&lt;br /&gt;
&lt;br /&gt;
===Creating a new User ID Card from scratch===&lt;br /&gt;
#Open the fingerprint scanner PC application.&lt;br /&gt;
#Locate the user+ option. There is a plus sign at the top of the page that enables you to create a new ID card. Click this and fill in all of the necessary information found below:&lt;br /&gt;
#*Enroll ID/Card ID&lt;br /&gt;
#*Name (enter in the member’s full name)&lt;br /&gt;
#*User ID (this should be the same as the enroll/card ID number)&lt;br /&gt;
#*Gender &lt;br /&gt;
#*Default attendance should display as followed: Duty, Robotics.&lt;br /&gt;
#*Default password should be entered at the User ID&lt;br /&gt;
#There is another page that should be edited. Look at the top of the window and click the second tab labeled “Extend Info”&lt;br /&gt;
#*Un-select the boxes labeled: 1st lock, 2nd lock&lt;br /&gt;
#*Fill in the title name (first name.last initial; like the @prhsrobotics email accounts)&lt;br /&gt;
#Done! Now, you must sync the information to the device. Navigate to the fingerprint scanner application and locate the device management option. Click “Upload all enroll”&lt;br /&gt;
#Wait for the device to finish syncing. Check to make sure the sync has worked by logging in on the device and checking the roster using manager login, and selecting “user” → “Enroll” and navigate using the arrow keys or the number keys.&lt;br /&gt;
&lt;br /&gt;
===Adding in fingerprints to an existing ID card===&lt;br /&gt;
#You must have created a correlating ID card on the fingerprint scanner application and have it uploaded on the device in order to add new fingerprints. You cannot add fingerprints that won’t be going anywhere!&lt;br /&gt;
#Log in to the fingerprint scanner device.&lt;br /&gt;
#Select “user” → “enter”. Navigate the roster using the arrows/numbers key by user ID number. &lt;br /&gt;
#Ask the person to swipe the scanner 3 times each with one hand’s index finger. The page should prompt the question, “Continue”. Enter “yes” and swipe the other hand’s index finger 3 times. &lt;br /&gt;
#When complete, exit to the main page of the device. Navigate the fingerprint scanner PC application and click “Device management” &lt;br /&gt;
#Select “get all enroll” to sync fingerprints with the PC app.&lt;br /&gt;
#Wait until scanner has finished syncing and test the sync completion by having the person swipe the scanner.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock</id>
		<title>Attendance Clock</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock"/>
				<updated>2017-01-21T15:55:13Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Creating a new User ID Card from scratch */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The attendance clock was adopted in [[2015]] when [[Scott Karlins]] introduced the device to the team. It is a fingerprint scanner that takes a member's fingerprint and logs in their hours for certain events or general team meetings. This is used to compile hours gathered by members over the year to see if they are eligible to earn a robotics varsity letter. &lt;br /&gt;
&lt;br /&gt;
=How it Works=&lt;br /&gt;
The team has a laptop dedicated for this fingerprint scanner's operations. &lt;br /&gt;
&lt;br /&gt;
==Opening the fingerprint scanner application on PC==&lt;br /&gt;
#Plug in flash drive found in fingerprint scanner package&lt;br /&gt;
#Use USB cable to connect the fingerprint scanner device onto the PC. Wait for fingerprint scanner to power up. &lt;br /&gt;
#Open files on the flash drive, and locate the folder labeled “RAMS”&lt;br /&gt;
#Open the RAS application&lt;br /&gt;
#Once opened, the RAS application should reveal a login box where you enter a password. The password is “RoboLions!” (as of 2015)&lt;br /&gt;
#Once logged in, the main screen should appear. It should have options such as creating a new user, device management, attendance management, etc&lt;br /&gt;
&lt;br /&gt;
===Logging in to the fingerprint scanner device===&lt;br /&gt;
#Make sure the fingerprint scanner is either plugged into a nearby outlet or a PC in order to power itself up &lt;br /&gt;
#Press the MENU button after the main screen has opened on the device&lt;br /&gt;
#This should prompt the device to display the word “Manager?” on the screen. Your user/ID card must be made a manager in order to manage the device.&lt;br /&gt;
#To log in as a manager, enter your user ID number. This is the number you are assigned when you are created an ID card on the fingerprint scanner device.&lt;br /&gt;
#Enter in your password. The default password for a manager is 1261.&lt;br /&gt;
#This should prompt you to a page of different options, such as User, Log data, U-Disk, Setting, and About&lt;br /&gt;
&lt;br /&gt;
===Editing an existing ID card to create a new User ID Card===&lt;br /&gt;
#This is the first step in adding a new member to the fingerprint scanner system. First, make sure you have cleared the ID cards of discontinued members of the team from the roster that can be found on the PC application. Do not delete them completely; this can be replaced with new members’ information. #Instead, delete the fingerprints and edit the name/gender/cardID.&lt;br /&gt;
#To delete fingerprints from an ID card, you must have the fingerprint scanner device open to the main page. Navigate to menu → user → delete and locate the particular ID card using the roster that can be found on the fingerprint scanner PC application. Use the arrow keys to select fingerprints to delete. Make sure to delete both fingerprint scans of the previous user. Make sure to also select “Get all Enroll” in device management of the PC application in order to sync both medias.&lt;br /&gt;
#To edit the ID card, you must use the fingerprint scanner PC application. Locate the user+ option and select the specified user. Right click on the user and select edit, and you are able to clear the name/gender/cardID as needed. Be sure to select the second tab of the ID card labeled: “Extend Info” to clear the user’s title.&lt;br /&gt;
&lt;br /&gt;
===Creating a new User ID Card from scratch===&lt;br /&gt;
#Open the fingerprint scanner PC application.&lt;br /&gt;
#Locate the user+ option. There is a plus sign at the top of the page that enables you to create a new ID card. Click this and fill in all of the necessary information found below:&lt;br /&gt;
#*Enroll ID/Card ID&lt;br /&gt;
#*Name (enter in the member’s full name)&lt;br /&gt;
#*User ID (this should be the same as the enroll/card ID number)&lt;br /&gt;
#*Gender &lt;br /&gt;
#Default attendance should display as followed: Duty, Robotics.&lt;br /&gt;
#Default password should be entered at the User ID&lt;br /&gt;
#There is another page that should be edited. Look at the top of the window and click the second tab labeled “Extend Info”&lt;br /&gt;
#*Un-select the boxes labeled: 1st lock, 2nd lock&lt;br /&gt;
#*Fill in the title name (first name.last initial; like the @prhsrobotics email accounts)&lt;br /&gt;
#Done! Now, you must sync the information to the device. Navigate to the fingerprint scanner application and locate the device management option. Click “Upload all enroll”&lt;br /&gt;
#Wait for the device to finish syncing. Check to make sure the sync has worked by logging in on the device and checking the roster using manager login, and selecting “user” → “Enroll” and navigate using the arrow keys or the number keys.&lt;br /&gt;
&lt;br /&gt;
===Adding in fingerprints to an existing ID card===&lt;br /&gt;
#You must have created a correlating ID card on the fingerprint scanner application and have it uploaded on the device in order to add new fingerprints. You cannot add fingerprints that won’t be going anywhere!&lt;br /&gt;
#Log in to the fingerprint scanner device.&lt;br /&gt;
#Select “user” → “enter”. Navigate the roster using the arrows/numbers key by user ID number. &lt;br /&gt;
#Ask the person to swipe the scanner 3 times each with one hand’s index finger. The page should prompt the question, “Continue”. Enter “yes” and swipe the other hand’s index finger 3 times. &lt;br /&gt;
#When complete, exit to the main page of the device. Navigate the fingerprint scanner PC application and click “Device management” &lt;br /&gt;
#Select “get all enroll” to sync fingerprints with the PC app.&lt;br /&gt;
#Wait until scanner has finished syncing and test the sync completion by having the person swipe the scanner.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock</id>
		<title>Attendance Clock</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Attendance_Clock"/>
				<updated>2017-01-21T15:54:37Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* How it Works */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The attendance clock was adopted in [[2015]] when [[Scott Karlins]] introduced the device to the team. It is a fingerprint scanner that takes a member's fingerprint and logs in their hours for certain events or general team meetings. This is used to compile hours gathered by members over the year to see if they are eligible to earn a robotics varsity letter. &lt;br /&gt;
&lt;br /&gt;
=How it Works=&lt;br /&gt;
The team has a laptop dedicated for this fingerprint scanner's operations. &lt;br /&gt;
&lt;br /&gt;
==Opening the fingerprint scanner application on PC==&lt;br /&gt;
#Plug in flash drive found in fingerprint scanner package&lt;br /&gt;
#Use USB cable to connect the fingerprint scanner device onto the PC. Wait for fingerprint scanner to power up. &lt;br /&gt;
#Open files on the flash drive, and locate the folder labeled “RAMS”&lt;br /&gt;
#Open the RAS application&lt;br /&gt;
#Once opened, the RAS application should reveal a login box where you enter a password. The password is “RoboLions!” (as of 2015)&lt;br /&gt;
#Once logged in, the main screen should appear. It should have options such as creating a new user, device management, attendance management, etc&lt;br /&gt;
&lt;br /&gt;
===Logging in to the fingerprint scanner device===&lt;br /&gt;
#Make sure the fingerprint scanner is either plugged into a nearby outlet or a PC in order to power itself up &lt;br /&gt;
#Press the MENU button after the main screen has opened on the device&lt;br /&gt;
#This should prompt the device to display the word “Manager?” on the screen. Your user/ID card must be made a manager in order to manage the device.&lt;br /&gt;
#To log in as a manager, enter your user ID number. This is the number you are assigned when you are created an ID card on the fingerprint scanner device.&lt;br /&gt;
#Enter in your password. The default password for a manager is 1261.&lt;br /&gt;
#This should prompt you to a page of different options, such as User, Log data, U-Disk, Setting, and About&lt;br /&gt;
&lt;br /&gt;
===Editing an existing ID card to create a new User ID Card===&lt;br /&gt;
#This is the first step in adding a new member to the fingerprint scanner system. First, make sure you have cleared the ID cards of discontinued members of the team from the roster that can be found on the PC application. Do not delete them completely; this can be replaced with new members’ information. #Instead, delete the fingerprints and edit the name/gender/cardID.&lt;br /&gt;
#To delete fingerprints from an ID card, you must have the fingerprint scanner device open to the main page. Navigate to menu → user → delete and locate the particular ID card using the roster that can be found on the fingerprint scanner PC application. Use the arrow keys to select fingerprints to delete. Make sure to delete both fingerprint scans of the previous user. Make sure to also select “Get all Enroll” in device management of the PC application in order to sync both medias.&lt;br /&gt;
#To edit the ID card, you must use the fingerprint scanner PC application. Locate the user+ option and select the specified user. Right click on the user and select edit, and you are able to clear the name/gender/cardID as needed. Be sure to select the second tab of the ID card labeled: “Extend Info” to clear the user’s title.&lt;br /&gt;
&lt;br /&gt;
===Creating a new User ID Card from scratch===&lt;br /&gt;
#Open the fingerprint scanner PC application.&lt;br /&gt;
#Locate the user+ option. There is a plus sign at the top of the page that enables you to create a new ID card. Click this and fill in all of the necessary information found below:&lt;br /&gt;
#*Enroll ID/Card ID&lt;br /&gt;
#*Name (enter in the member’s full name)&lt;br /&gt;
#*User ID (this should be the same as the enroll/card ID number)&lt;br /&gt;
#*Gender &lt;br /&gt;
#Default attendance should display as followed: Duty, Robotics.&lt;br /&gt;
#Default password should be entered at the User ID&lt;br /&gt;
#There is another page that should be edited. Look at the top of the window and click the second tab labeled “Extend Info”&lt;br /&gt;
#Un-select the boxes labeled: 1st lock, 2nd lock&lt;br /&gt;
#Fill in the title name (first name.last initial; like the @prhsrobotics email accounts)&lt;br /&gt;
#Done! Now, you must sync the information to the device. Navigate to the fingerprint scanner application and locate the device management option. Click “Upload all enroll”&lt;br /&gt;
#Wait for the device to finish syncing. Check to make sure the sync has worked by logging in on the device and checking the roster using manager login, and selecting “user” → “Enroll” and navigate using the arrow keys or the number keys. &lt;br /&gt;
&lt;br /&gt;
===Adding in fingerprints to an existing ID card===&lt;br /&gt;
#You must have created a correlating ID card on the fingerprint scanner application and have it uploaded on the device in order to add new fingerprints. You cannot add fingerprints that won’t be going anywhere!&lt;br /&gt;
#Log in to the fingerprint scanner device.&lt;br /&gt;
#Select “user” → “enter”. Navigate the roster using the arrows/numbers key by user ID number. &lt;br /&gt;
#Ask the person to swipe the scanner 3 times each with one hand’s index finger. The page should prompt the question, “Continue”. Enter “yes” and swipe the other hand’s index finger 3 times. &lt;br /&gt;
#When complete, exit to the main page of the device. Navigate the fingerprint scanner PC application and click “Device management” &lt;br /&gt;
#Select “get all enroll” to sync fingerprints with the PC app.&lt;br /&gt;
#Wait until scanner has finished syncing and test the sync completion by having the person swipe the scanner.&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017_FIRST_Steamworks</id>
		<title>2017 FIRST Steamworks</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017_FIRST_Steamworks"/>
				<updated>2017-01-20T00:47:29Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:SteamworksLogo.jpg|thumb|250px|right|The logo for the 2017 game.]]&lt;br /&gt;
'''FIRST Steamworks''' was the FRC game in 2017. &lt;br /&gt;
==Game Overview==&lt;br /&gt;
In FIRST Steamworks, alliances work to prepare their airships for launch at the end of the match. They do this by inserting fuel (small whiffle balls) into the boiler to build steam pressure and delivering gears to the airship to power its rotors. At the end of the match, ropes are lowered from the airships, and robots can climb up them to be ready for takeoff. Points are awarded for the amount of fuel put in the boiler, for successfully activating any airship rotors, and for climbing onto the rope at the end of the match. &lt;br /&gt;
&lt;br /&gt;
==Field Overview==&lt;br /&gt;
[[File:SteamworksField.png|800px|center]]&lt;br /&gt;
[[File:SteamworksFieldLabeled.png|800px|center]]&lt;br /&gt;
The field is divided into two red and blue launchpads (one for each alliance) demarcated by the launchpad line. In between the two launchpads is the neutral zone. Each launchpad features a retrieval zone, an area where human players can feed recycled fuel and gears into the robot, and a key, a small area in front of the boiler marked off with tape matching the alliance's color. The boiler is in the bottom two corners of the field bordering the launchpad, and the airships are located at the edge of each launchpad. &lt;br /&gt;
===Boiler===&lt;br /&gt;
The boiler is the machine that converts fuel into steam pressure. There is one for each alliance in the corner opposite to the scoring table. They have a high goal and a low goal. The high goal has a funnel shape and processes fuel at a higher efficiency, meaning less fuel must be used up to build up steam pressure. The low goal is simply a 2 ft. 1 in. opening in the boiler, and it processes fuel at a lower efficiency (see scoring section). The high efficiency goal is surrounded by a net and is made so that all missed shots will roll back onto the field. &lt;br /&gt;
===Airship===&lt;br /&gt;
The airship features the rotors and climbing rope that robots climb at the end of the match. The airship is also unique in that it requires at least 1 human player known as the pilot to be inside of it to place and spin gears, making it the first game where a person is allowed on the field during gameplay. &lt;br /&gt;
&lt;br /&gt;
There can be a max of 2 pilots per alliance. Robots deliver gears to the airship, specifically to one of the 3 lifts facing the alliance station. The pilot then pulls on a cable to bring the gears up and places the gear on the airship to activate the motors. The steam tank is also in the airship, which is the large center of it. It has LED lights of the alliance color on it indicating how much steam pressure has been built up. Each 10 kPa generated will activate one row of LEDs in a white color, while an additional 10 will turn that row the alliance's color. Lastly, the airship also features a structure known as the davit, which is where the ropes are stored. During the last 30 seconds, the pilots will deploy the ropes from the davit. The robot must climb all the way up the rope and touch the touchpad at the top of the rope to get points for climbing. &lt;br /&gt;
===Retrieval Zone and Loading Lane===&lt;br /&gt;
When fuel enters the boiler, they will eventually exit out into a return bin in the Alliance station. The human player must make sure that when a return bin or any overflow bin is full, they must go and empty it in through the retrieval zone. Robots may enter the retrieval zone, and human players can feed in balls or gears to the robot. A special area known as the loading lane is provided so that human players can easily walk from the retrieval zone to the alliance station without interrupting the robot drivers. &lt;br /&gt;
===Key===&lt;br /&gt;
The key is simply a small, taped-off area in front of the boilers. It is there so teams can input fuel into the low efficiency goal. It has no major function; however, robots cannot spend more than 5 seconds in the opposing alliance's key, or they will receive a foul. &lt;br /&gt;
==Scoring==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align:center; margin-left: auto; margin-right: auto; height:25px&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Action&lt;br /&gt;
! Match Points&lt;br /&gt;
! Ranking Points&lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; | Autonomous&lt;br /&gt;
|-&lt;br /&gt;
|| Reaching the baseline || 5 pts. ||&lt;br /&gt;
|-&lt;br /&gt;
|| 1 unit of fuel in the high efficiency goal || 1 pt. ||&lt;br /&gt;
|-&lt;br /&gt;
|| 3 units of fuel in the low efficiency goal || 1 pt. ||&lt;br /&gt;
|-&lt;br /&gt;
|| Successfully activating an airship rotor || 60 pts. || &lt;br /&gt;
|-&lt;br /&gt;
! colspan=&amp;quot;3&amp;quot; | Teleop&lt;br /&gt;
|-&lt;br /&gt;
|| 3 units of fuel in the high efficiency goal || 1 pt. ||&lt;br /&gt;
|-&lt;br /&gt;
|| 9 units of fuel in the low efficiency goal || 1 pt. ||&lt;br /&gt;
|-&lt;br /&gt;
|| Reaching steam pressure equal to or above 40 kPa || ''60 pts.'' ||  '''1 RP'''&lt;br /&gt;
|-&lt;br /&gt;
|| Successfully activating an airship rotor || 40 pts. ||&lt;br /&gt;
|-&lt;br /&gt;
|| Activating all 4 airship rotors || ''100 pts.'' || '''1 RP'''&lt;br /&gt;
|-&lt;br /&gt;
|| Climbing the rope and reaching the touchpad || 50 pts. ||&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;span style=&amp;quot;font-size:88%&amp;quot;&amp;gt;'''Bolded''' items apply only to qualification matches, while ''italicized'' items apply only to playoffs.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Robots==&lt;br /&gt;
The team is currently in the process of building a robot for this game. &lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
*[https://firstfrc.blob.core.windows.net/frc2017/Manual/2017FRCGameSeasonManual.pdf FIRST Steamworks Official Game Manual]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:FRC Games]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Ian_Yelle</id>
		<title>Ian Yelle</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Ian_Yelle"/>
				<updated>2017-01-14T18:59:24Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: Created page with &amp;quot;{{MemberInfoBox |Image= ianYelle.jpg |Gender= male |MemberInYear= 2017  |FreshmanInYear=   2017 |SophomoreInYear=   2018 |JuniorInYear=  2019 |SeniorInYear=  2020 |ForumAccoun...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= ianYelle.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2017 &lt;br /&gt;
|FreshmanInYear=   2017&lt;br /&gt;
|SophomoreInYear=   2018&lt;br /&gt;
|JuniorInYear=  2019&lt;br /&gt;
|SeniorInYear=  2020&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What got you involved in the team?==&lt;br /&gt;
I knew the Glasers and they got me involved.&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
[[Mackenzie Glaser]] because I've known her for the longest.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
To become either a biochemist or go into IT&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
Programming, reading, playing the keyboard, video games, and chemistry experiments.&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
Cross Country&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
To possibly cure cancer or create a revolutionary computer program&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;Why won't ____&amp;quot; &amp;quot;Because physics.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
First joining&lt;br /&gt;
&lt;br /&gt;
==Anything special you'd like to add about yourself?==&lt;br /&gt;
I'm Canadian.&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Members</id>
		<title>Members</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Members"/>
				<updated>2017-01-14T14:58:32Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains all past and present members of the robotics team.&lt;br /&gt;
&lt;br /&gt;
To see the category of members, click [[:Category:Members|here]].&lt;br /&gt;
&lt;br /&gt;
==Alumni==&lt;br /&gt;
Alumni are robotics members that have since left high school to move onto college or other things. Some come back and mentor, some do not.&lt;br /&gt;
&lt;br /&gt;
For a list of all current alumni, click [[Alumni|here]].&lt;br /&gt;
&lt;br /&gt;
==Sub-Teams==&lt;br /&gt;
Throughout the build season, the team is broken up into smaller sub-teams that specialize in certain tasks to expedite the build of the robot.&lt;br /&gt;
&lt;br /&gt;
The current sub-teams listed in no particular order are:&lt;br /&gt;
*[[:Category:Team/CAD|CAD]]&lt;br /&gt;
*[[:Category:Team/Electrical|Electrical]]&lt;br /&gt;
*[[:Category:Team/Mechanical|Mechanical]]&lt;br /&gt;
*[[:Category:Team/Programming|Programming]]&lt;br /&gt;
*[[:Category:Team/Scouting|Scouting]]&lt;br /&gt;
*[[:Category:Team/Website|Website]]&lt;br /&gt;
&lt;br /&gt;
==Statistics==&lt;br /&gt;
*Number of Males: {{#ask:[[gender::male]][[member of robotics in year::+]] | format=count}}&lt;br /&gt;
*Number of Females: {{#ask:[[gender::female]][[member of robotics in year::+]] | format=count}}&lt;br /&gt;
*Total Number of Members: {{#ask:[[member of robotics in year::+]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
For more statistics, click [[Members/Statistics|here]].&lt;br /&gt;
== 2017 ==&lt;br /&gt;
{{MemberList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
== 2016 ==&lt;br /&gt;
{{MemberList | year=2016}}&lt;br /&gt;
&lt;br /&gt;
== 2015 ==&lt;br /&gt;
{{MemberList | year=2015}}&lt;br /&gt;
&lt;br /&gt;
== 2014 ==&lt;br /&gt;
{{MemberList | year=2014}}&lt;br /&gt;
&lt;br /&gt;
== 2013 ==&lt;br /&gt;
{{MemberList | year=2013}}&lt;br /&gt;
&lt;br /&gt;
== 2012 ==&lt;br /&gt;
{{MemberList | year=2012}}&lt;br /&gt;
&lt;br /&gt;
== 2011 ==&lt;br /&gt;
{{MemberList | year=2011}}&lt;br /&gt;
&lt;br /&gt;
== 2010 ==&lt;br /&gt;
{{MemberList | year=2010}}&lt;br /&gt;
&lt;br /&gt;
== 2009 ==&lt;br /&gt;
{{MemberList | year=2009}}&lt;br /&gt;
&lt;br /&gt;
== 2008 ==&lt;br /&gt;
{{MemberList | year=2008}}&lt;br /&gt;
&lt;br /&gt;
== 2007 ==&lt;br /&gt;
{{MemberList | year=2007}}&lt;br /&gt;
&lt;br /&gt;
== 2006 ==&lt;br /&gt;
{{MemberList | year=2006}}&lt;br /&gt;
&lt;br /&gt;
== 2005 ==&lt;br /&gt;
{{MemberList | year=2005}}&lt;br /&gt;
&lt;br /&gt;
== 2004 ==&lt;br /&gt;
{{MemberList | year=2004}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
[[Category:Pages to be updated yearly]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=2017</id>
		<title>2017</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=2017"/>
				<updated>2017-01-09T00:28:09Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Spring 2017: FRC */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{YearBar}}&lt;br /&gt;
{{Todo|Add some images.}}&lt;br /&gt;
This is the {{PAGENAME}} year.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Officers==&lt;br /&gt;
''This is the year the [[Social Media Lead]] and the [[Historian]] roles were combined.''&lt;br /&gt;
*President: [[president::Mackenzie Glaser]]&lt;br /&gt;
*Vice-President of VEX: [[Vice-President of VEX::Joel Leonardo]]&lt;br /&gt;
*Vice-Presidents of FRC: [[Vice-President of FRC::Natalie Luong]]&lt;br /&gt;
*Vice-President of Business: [[Vice-President of Business::Nawar Khan]]&lt;br /&gt;
*Vice-President of Outreach: [[Vice-President of Outreach::Caroline Means]]&lt;br /&gt;
*Vice-President of Communications: [[Vice-President of Communications::Jane Khampha]]&lt;br /&gt;
*Secretary: [[Secretary::Nehemiah Elias]]&lt;br /&gt;
*Treasurer: [[Treasurer::Rithik Raina]]&lt;br /&gt;
*Historian: [[Historian::Poojan Raval]]&lt;br /&gt;
*Webmaster: [[Webmaster::Sumaer Sahney]]&lt;br /&gt;
*Programming Lead: [[Programming Lead::Chris Carlson]]&lt;br /&gt;
*CAD Lead: [[CAD Lead::Neil Penning]]&lt;br /&gt;
&lt;br /&gt;
==Mentors==&lt;br /&gt;
{{mentorList | year=2017}}&lt;br /&gt;
==Fall 2016: VEX Robotics==&lt;br /&gt;
As we do in the fall, the team participated in the 2016 VEX Game, [[2016 Starstruck | Starstruck]]. The club was split up into 7 subteams on August 23, and had 12 weeks to build a robot to compete in the game. This year, school was also held off on Election Day, which happened to be one of our VEX Meeting days. An optional meeting was held for teams who still needed that build day. &lt;br /&gt;
===VEX Qualifier: Robots at the Ridge===&lt;br /&gt;
The VEX Qualifier: Robots at the Ridge was held at PRHS on November 19. Over 50 teams from over Georgia, with some coming from as far as Knoxville, Tennessee. They all gathered to take place in the 2016 VEX Game, VEX Starstruck. One of the 1261 Subteams made it to quarterfinals, but sadly did not go past that. Still, it was a great event overall, and all students enjoyed their time there! We also had many people stay after and clean up, which helped us clean up the entire school commons in only an hour! &amp;lt;br&amp;gt; Congratulations to our first place winners: &lt;br /&gt;
*Captain: 3921B &amp;quot;Beta&amp;quot; from Carrollton, GA&lt;br /&gt;
*1st pick: 1961E &amp;quot;South Forsyth Eaglebots&amp;quot; from Cumming, GA&lt;br /&gt;
*2nd pick: 7201P &amp;quot;Marist Penguins&amp;quot; from Atlanta, GA&amp;lt;br&amp;gt;&lt;br /&gt;
We also congratulate the following award-winning teams: &lt;br /&gt;
*Excellence Award: 675E &amp;quot;RoboDragons E&amp;quot; from Lawrenceville, GA&lt;br /&gt;
*Judges Award: 31415R &amp;quot;Domo Arigato&amp;quot; from Cumming, GA&lt;br /&gt;
&lt;br /&gt;
==Fall 2016: Outreach Activities==&lt;br /&gt;
===Suwanee Parade===&lt;br /&gt;
[[File:2017STEMHeroes.jpg|250px|thumb|right|2017 STEM Heroes of Suwanee: the Robo Lions!]]&lt;br /&gt;
On September 17, 2016, the Robo Lions marched valiantly through Suwanee, donned with masks and heroic capes. This year's parade theme was &amp;quot;Super Suwanee, Super People!&amp;quot;. The team took home the &amp;quot;Most Entertaining Group&amp;quot; award from the judges. &lt;br /&gt;
&lt;br /&gt;
===Duluth Fall Festival===&lt;br /&gt;
On September 24, 2016, the Robo Lions attended the Duluth Fall Festival once again. They shot t-shirts and beach balls with the assistance of [[Jeff]] and [[Genesis]] from the back of their parade float. &lt;br /&gt;
The event was filled with fun, excitement, and thunderous pride as our team took to the streets cheering about our love of STEM. We made lots of new friends and connections within the community, as it stands as a memory that will never be forgotten. We used our superhero theme from the Suwannee Day Parade, and everyone fulfilled their roles of being superheroes beautifully.&lt;br /&gt;
&lt;br /&gt;
===Maker Faire===&lt;br /&gt;
On the weekend of October 1-2, some of the Robo Lions set up and maintained a booth at Maker Faire Atlanta. The team debuted an interactive display which helped us teach visitors to our booth about the sensors which make us successful on the field. We had a steady stream of visitors both days with kids driving VEX Robots and exploring our FRC Robots while we helped to connect our community to the STEM opportunities in their area. We were recognized for our set up and had a great time catching up with our fellow FRC Teams before GRITS! &lt;br /&gt;
&lt;br /&gt;
===Ridge Run 5K Color Run===&lt;br /&gt;
On October 19, 2016, the Robo Lions were invited to kickoff the Ridge Color Run by shooting colorful flour out of Jeff the t-shirt robot. See [http://wiki.prhsrobotics.com/index.php?title=How-To:_Color_Run_Preparation  How to: Color Run Preparation] to see how we succeeded in doing so.&lt;br /&gt;
&lt;br /&gt;
===TE Sessions===&lt;br /&gt;
This year, Georgia FIRST, in collaboration with the Robojackets, held various Technology Enrichment sessions where one team would teach others on some crucial aspects of Robotics. We held two of our own sessions. &lt;br /&gt;
====Raspberry Pi and Vision Tracking====&lt;br /&gt;
On October 15th, the Robo Lions hosted a TE Session focused on helping other FRC teams understanding how to effectively use raspberry pis, which are small single-boarded computers that are used for processing the code that lies within the robot. It was a great experience, and we saw many people there, both new and old. Many concepts such as HSV-based color, contour tracking, and PID control were discussed. The programming team also gave tips on how to use a vision tracking system more efficiently. There was also a Q&amp;amp;A given at the end of the session to address any of confusion. This session was recorded by the RoboJackets; [http://prhsrobotics.us12.list-manage.com/track/click?u=4dfc28ec565342f7298dc7b32&amp;amp;id=1e73f35cb1&amp;amp;e=3ff57b8829 click here] to view a recording. &lt;br /&gt;
====Effective Social Media====&lt;br /&gt;
On October 29th, we hosted a TE Session that focused on having effective social media. We presented to teams about how to manage social media effectively and how to use each form of social media to its fullest extent. Many FRC teams attended, which enabled us to meet and interact with many people we've never met. We gained insight and perspective from a wide variety of teams, so even though we were hosting the event, we got a couple of things out of it as well.&lt;br /&gt;
&lt;br /&gt;
===Trunk or Treat===&lt;br /&gt;
The team did have a trunk at PRHS's second annual Trunk or Treat, where kids go from trunk to trunk, trick or treating in a safe environment. The team's trunk was a Star Wars based trunk, showing the cockpit view of the Millennium Falcon. The team showed off the VEX outreach bot, Kobe. &lt;br /&gt;
&lt;br /&gt;
===Other School Events===&lt;br /&gt;
The Robo Lions attended many events hosted at PRHS during the fall. This includes, but isn't limited to, the home football games, the Asian American College Fair, and Ridge Run. At most of these events, the Robo Lions showcased Jeff the T-Shirt Robot. &lt;br /&gt;
&lt;br /&gt;
==Side Activities==&lt;br /&gt;
===Parody Video===&lt;br /&gt;
The team once again participated in the FIRST Parody contest. This year, the team decided to make a parody of the song &amp;quot;Don't Stop Believin'&amp;quot; by Journey. The parody was named &amp;quot;Don't Stop Buildin'&amp;quot;, and can be seen [https://www.youtube.com/watch?v=Xb5AcKW8Lwo here.]&lt;br /&gt;
===End of Season Video===&lt;br /&gt;
&lt;br /&gt;
==Spring 2017: FRC==&lt;br /&gt;
Due to chilly weather and possibility of icy roads/snow, the team opted to hold kickoff at home. Most of the veterans separated themselves by gender and held sleepovers at corresponding houses, eager to watch the game reveal the next morning. 2017 Kickoff brought the reveal of FIRST Steamworks, a steampunk-themed gamed that combines a variety of challenges for each alliance to &amp;quot;power their aircraft&amp;quot; and &amp;quot;prepare for takeoff!&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Off-Season FRC Activities==&lt;br /&gt;
===GRITS===&lt;br /&gt;
The Robo Lions attended GRITS at Riverside Military Academy on October 22, 2016. They played alongside many other Georgia teams, and they ended qualifications as the 3rd seeded alliance captain. Forming an alliance with Team 2974 (Walton) and Team 4188 (Columbus Space Program), they made it all the way to the semifinals before accepting defeat. They did not go home empty-handed, though. With over 30 rookies, the team was able to take home the Outreach award for the third year in a row and got quite a nifty Portcullis styled trophy. &lt;br /&gt;
&lt;br /&gt;
==Spring 2017: Outreach Activities==&lt;br /&gt;
&lt;br /&gt;
==Sponsors==&lt;br /&gt;
{{sponsorList | year=2017}}&lt;br /&gt;
&lt;br /&gt;
==Demographics==&lt;br /&gt;
*Number of Members: {{#ask:[[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Female Members: {{#ask:[[member of robotics in year::2017]] [[gender::female]] | format=count}}&lt;br /&gt;
*Number of Male Members: {{#ask:[[member of robotics in year::2017]] [[gender::male]] | format=count}}&lt;br /&gt;
*Number of Mentors: {{#ask:[[mentor in year::2017]] | format=count}}&lt;br /&gt;
*Number of Freshmen: {{#ask:[[Freshman in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Sophomores: {{#ask:[[Sophomore in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Juniors: {{#ask:[[Junior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
*Number of Seniors: {{#ask:[[Senior in year::2017]][[member of robotics in year::2017]] | format=count}}&lt;br /&gt;
&lt;br /&gt;
==Members==&lt;br /&gt;
{{memberList|year=2017}}&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Members#2016|Team Members for 2017]]&lt;br /&gt;
&lt;br /&gt;
==External Links==&lt;br /&gt;
&lt;br /&gt;
{{#set:Year=2017}}&lt;br /&gt;
&lt;br /&gt;
{{YearBar}}&lt;br /&gt;
&lt;br /&gt;
[[Category:History]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Competition_Preparations</id>
		<title>Competition Preparations</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Competition_Preparations"/>
				<updated>2016-12-09T14:53:48Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: /* Chairmans */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Below are some checklists made every year in preparation for the various competitions attended by the Robo Lions. &lt;br /&gt;
&lt;br /&gt;
==Organization of Members==&lt;br /&gt;
===Rooming===&lt;br /&gt;
Make a spreadsheet for students (make sure to include role, phone number, car and room arrangements, and a place to check forms and payment).&lt;br /&gt;
*If staying at a hotel during competition, team members must bring luggage and forms to the team at least 2 days prior to competition.&lt;br /&gt;
===Roles===&lt;br /&gt;
Make sure all members are fully briefed on their roles &lt;br /&gt;
*Have scouting meetings (pull from the prelim scouting meeting power points, scouting leads should modify year by year)&lt;br /&gt;
*Have a well rehearsed chairman’s team&lt;br /&gt;
*Have data analysis people practice Tableau&lt;br /&gt;
*Drive team roles should be well divided (who talks to teams, who follows the robot around fixing problems, who manages strategy)&lt;br /&gt;
*Would be preferable to have pair scouts at all times, so that no one gets lost or make it possible to switch scouting&lt;br /&gt;
*Make sure each member has a team shirt to wear at competition&lt;br /&gt;
&lt;br /&gt;
==Liability Forms==&lt;br /&gt;
*Teacher signature form&lt;br /&gt;
*Info form about competition and travel arrangements&lt;br /&gt;
*Insurance and parent form&lt;br /&gt;
*Liability waiver&lt;br /&gt;
*GA FIRST waiver (once a season)&lt;br /&gt;
&lt;br /&gt;
==Lists==&lt;br /&gt;
===Packing===&lt;br /&gt;
Edit the basic packing list to include robot replacement parts specific to that year - consult build leads and mentors&lt;br /&gt;
===Devices===&lt;br /&gt;
Make a devices list for that year: include laptops and tablets being taken and who is responsible for them &lt;br /&gt;
Make sure that on packing night the people in charge of devices take theirs and carry them to competition (divide up between scouts and programmers)&lt;br /&gt;
&lt;br /&gt;
==Handouts==&lt;br /&gt;
===Buttons===&lt;br /&gt;
Make sure that buttons are made (probably about 300 for district level competition)&lt;br /&gt;
==Robot==&lt;br /&gt;
*Make sure that robot info sheets are made and printed.&lt;br /&gt;
*Make sure that electrical diagrams are made and printed&lt;br /&gt;
*Make sure that the bill of materials (CAW) is complete (with mentor approval) and is printed and put into the rule book.&lt;br /&gt;
*A list should be compiled of what needs to be done on the robot once it is unbagged on load in night. It should be detailed and have the people responsible listed.&lt;br /&gt;
&lt;br /&gt;
==Pit==&lt;br /&gt;
Talk with safety captains on role&lt;br /&gt;
*Batteries&lt;br /&gt;
*Pit cleanliness&lt;br /&gt;
*Enforcing safety rules (number of people in pit, safety glasses)&lt;br /&gt;
To-Do&lt;br /&gt;
*Check the safety box for all necessary equipment (see safety captain manual)&lt;br /&gt;
*Set up green flash drive with any necessary pit videos (that year’s chairman’s video, etc.)&lt;br /&gt;
*Put down floor tiles&lt;br /&gt;
*Take everything that’s not boxes off of wire shelf (this includes metal, etc.)&lt;br /&gt;
*Put everything that belongs on wire shelf onto wire shelf&lt;br /&gt;
**Boxes of screws&lt;br /&gt;
**Safety box&lt;br /&gt;
**Safety glasses&lt;br /&gt;
**Monitor&lt;br /&gt;
**Toolboxes&lt;br /&gt;
**Batteries&lt;br /&gt;
*Unpack batteries and chargers and start charging immediately (batteries should go on second shelf of wire rack)&lt;br /&gt;
*Get out gray cart and set up laptops there&lt;br /&gt;
*Set up curtains and banner in the back of the pit&lt;br /&gt;
*Set up tools on back table&lt;br /&gt;
**Drill press&lt;br /&gt;
**Bandsaw&lt;br /&gt;
**Vices&lt;br /&gt;
**Belt sander&lt;br /&gt;
*Set up FRC banner thing in the front of the pit&lt;br /&gt;
*Set up monitor&lt;br /&gt;
*Put on top of wire shelf (make sure it is zip-tied securely)&lt;br /&gt;
*Load videos from flash drive&lt;br /&gt;
*Have pit crew practice judge talks about robot and team&lt;br /&gt;
&lt;br /&gt;
==Scouting==&lt;br /&gt;
===Scouting Postitions===&lt;br /&gt;
Make sure that there are appointed head scouts that are responsible for pit or stand scouts.&lt;br /&gt;
===Scouts===&lt;br /&gt;
Make sure that each scout knows which team they need to be scouting at which times and that they always have a device ready to input data.&lt;br /&gt;
====Materials====&lt;br /&gt;
Take a power strip and portable batteries up to the stands so the stand scouts don't run out of battery while scouting the entire day.&lt;br /&gt;
===Tableau===&lt;br /&gt;
Make sure Tableau is on a minimum of 3 laptops (codes can be pulled from TIMS)&lt;br /&gt;
===App===&lt;br /&gt;
*Make sure all students have accounts and have been approved by admin&lt;br /&gt;
*Input live scouting and pre-scouting forms&lt;br /&gt;
*Input team lists for pre-scouting&lt;br /&gt;
*Once match schedule has been released, the lead stand scout at competition should put them in immediately.&lt;br /&gt;
&lt;br /&gt;
==Chairmans==&lt;br /&gt;
*Make sure that all Chairman’s materials for that year are prepared - these should stay with the Chairman’s presentation team lead&lt;br /&gt;
*Make sure video is on a flash drive&lt;br /&gt;
*Have essays printed in Chairman’s packet&lt;br /&gt;
*Judge’s sheet&lt;br /&gt;
*Any other things (copy of business plan, buttons, etc.)&lt;br /&gt;
*Media waivers - make sure to print extras to give to other teams (they always forget)&lt;br /&gt;
===Assigning Tasks===&lt;br /&gt;
It has been proven useful to make a timeline visually so that tasks are completed by the desired deadline. Below is a generic template made by [[Caroline Means]] in [[2017]]. &lt;br /&gt;
&lt;br /&gt;
Assignment&lt;br /&gt;
*Actual Due Date:&lt;br /&gt;
*Team-set Due Date:&lt;br /&gt;
*Assigned to: &lt;br /&gt;
*Check in: (usually with a student organizer for the Chairman's team or a team mentor)&lt;br /&gt;
*Backup plan:&lt;br /&gt;
&lt;br /&gt;
It is also helpful to draw in language arts teachers so that they may provide more insight and advice on ensuring the essay is in optimal form.&lt;br /&gt;
&lt;br /&gt;
==Communication==&lt;br /&gt;
*Set up a Remind class for that competition team - make sure that ALL students are on it&lt;br /&gt;
*Set up the rest of in-team communication that needs to happen (scouting leads group chat, etc.)&lt;br /&gt;
*Once competition event is over, have someone write up a press release for review before a final release.&lt;br /&gt;
*Have pre-scouting form and scouting line # put on the website a few weeks in advance&lt;br /&gt;
===Media===&lt;br /&gt;
Make sure media person is briefed on what to post to IG, Twitter, and FB&lt;br /&gt;
*Match score updates&lt;br /&gt;
*Overall team progress&lt;br /&gt;
*“Excited to start and end the day”&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Sagar_Patel</id>
		<title>Sagar Patel</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Sagar_Patel"/>
				<updated>2016-12-08T15:20:42Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= sagarpatel.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2017 &lt;br /&gt;
|FreshmanInYear=   2017&lt;br /&gt;
|SophomoreInYear=   2018&lt;br /&gt;
|JuniorInYear=  2019&lt;br /&gt;
|SeniorInYear=  2020&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What got you involved in the team?==&lt;br /&gt;
I wanted to become an engineer.&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
I have no role model yet.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
I want to create anything after graduating from Georgia Tech.&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
I play Xbox one games .&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
I am not involved in any other clubs.&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
My dream is to make things or improve .&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
I have no favorite quote.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
My favorite moment was going to GRITS.&lt;br /&gt;
&lt;br /&gt;
==Anything special you'd like to add about yourself?==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Simar_Bajwa</id>
		<title>Simar Bajwa</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Simar_Bajwa"/>
				<updated>2016-12-08T15:20:26Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= simarbajwa.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2017 &lt;br /&gt;
|FreshmanInYear=   2017&lt;br /&gt;
|SophomoreInYear=   2018&lt;br /&gt;
|JuniorInYear=  2019&lt;br /&gt;
|SeniorInYear=  2020&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What got you involved in the team?==&lt;br /&gt;
Upperclassmen told me to join the team.&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
My role model is Kanye West because he has managed to achieve anything anyone could ever want and still not smile.&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
My future career is a neurosugeon&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
My interests are tennis, and football, and netflix, and video games.&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
I dream to be good&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;Trees Are Never Sad. Look At Them Every Once In a while, they're quite beautiful&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
When the robot got disassembled for no reason. &lt;br /&gt;
&lt;br /&gt;
==Anything special you'd like to add about yourself?==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Halston_Edwards</id>
		<title>Halston Edwards</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Halston_Edwards"/>
				<updated>2016-12-08T15:20:00Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= halstonedwards.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2017 &lt;br /&gt;
|FreshmanInYear=   2017&lt;br /&gt;
|SophomoreInYear=   2018&lt;br /&gt;
|JuniorInYear=  2019&lt;br /&gt;
|SeniorInYear= 2020&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What got you involved in the team?==&lt;br /&gt;
the programming and building &lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
BOB MARLEY cause he is a free spirit&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
aerospace engineer  &lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
games and building stuff&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
BEATBOX&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
To be successful &lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
&amp;quot;To be gracious in defeat &amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
See my team's idea work out&lt;br /&gt;
&lt;br /&gt;
==Anything special you'd like to add about yourself?==&lt;br /&gt;
No, but I like to chill a lot&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	<entry>
		<id>https://www.wiki.prhsrobotics.com/index.php?title=Arvind_Raza</id>
		<title>Arvind Raza</title>
		<link rel="alternate" type="text/html" href="https://www.wiki.prhsrobotics.com/index.php?title=Arvind_Raza"/>
				<updated>2016-12-08T15:19:45Z</updated>
		
		<summary type="html">&lt;p&gt;Jane: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{MemberInfoBox&lt;br /&gt;
|Image= arvindraza.jpg&lt;br /&gt;
|Gender= male&lt;br /&gt;
|MemberInYear= 2017 &lt;br /&gt;
|FreshmanInYear=   2017&lt;br /&gt;
|SophomoreInYear=   2018&lt;br /&gt;
|JuniorInYear=  2019&lt;br /&gt;
|SeniorInYear=  2020&lt;br /&gt;
|ForumAccount=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==What got you involved in the team?==&lt;br /&gt;
Previous knowledge and my personal interests&lt;br /&gt;
&lt;br /&gt;
==Who is Your Role Model?==&lt;br /&gt;
Gandhi; he's Indian&lt;br /&gt;
&lt;br /&gt;
==What are Your Future Career Plans==&lt;br /&gt;
Entrepreneur&lt;br /&gt;
&lt;br /&gt;
==Interests or Hobbies==&lt;br /&gt;
Gaming, soccer, programming&lt;br /&gt;
&lt;br /&gt;
==What Other Groups/Clubs Are You Involved In?==&lt;br /&gt;
Beta club, math team&lt;br /&gt;
&lt;br /&gt;
==What Are Your Dreams In Life?==&lt;br /&gt;
Attending Georgia Tech and entrepreneurship&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Quote==&lt;br /&gt;
You're never finished until you're done.&lt;br /&gt;
&lt;br /&gt;
==Favorite Robotics Moments==&lt;br /&gt;
Building wit my team&lt;br /&gt;
&lt;br /&gt;
==Anything special you'd like to add about yourself?==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Members]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Team/]]&lt;/div&gt;</summary>
		<author><name>Jane</name></author>	</entry>

	</feed>