Robotics Projects
Past Material
For the Consent Form
Program: VRC Team Number: Check with student. These are the teams registered this year: 2990D, 2990E, 2990K, 2990U, 2990V, 2990X |
College Credit Now (CCN) Application Instructions for MT105
Questions about this course:
When can a student drop without it penalizing them?: Students need to drop the class by April 11th in order for it to NOT show up on their transcripts AT ALL. After April 11th, students will have until MAY 12th to withdraw from the class. The class will show up on their transcript with a W as a grade. The W DOES NOT impact GPA. Anything after the May 12th date will result in a penalized GPA Where can we go to see if a course transfers?: After research, I found that the easiest way is to google : Transfer Equivalency System (Insert name of the Oregon school here) and it should pop up. They can search up how Chemeketa courses transfer into other Oregon institutions. MT105 seems to be an elective credit at most places which is great! If they are looking to go out of state, ex Transfer Equivalency System USC, it will take the student to the schools transfer website and have their specific directions. |
High School : West Salem High School
Instructor: Smith, Greg Course: MT105 CRN Lecture:81200 CRN Lab: 81201 |
Tentative Robotics Competition Calendar 2022-2023
10/28 Salem VEX League at West (Optional, all teams registered)
10/29 Sandy Tournament (2990E, 2990K, 2990U)
11/5 Lost River HS Tournament
11/19 North Marion Tournament (2990E, 2990K, 2990U)
12/2 West Salem Tournament Setup (All West Teams) + Salem VEX League at West (Optional, all teams registered)
12/3 West Salem Tournament (All West Salem Teams)
1/6 Salem VEX League at South Salem High School (Optional, all teams registered)
1/7 South Salem VEX Tournament (2990K, 2990V)
1/14 Sandy Tournament (2990E, 2990K, 2990U)
1/20 Salem VEX League at North Salem (Optional, all teams registered)
1/21 Willamette Tournament (2990E, 2990K, 2990U)
1/27-1/28 Mazama HS Tournament
1/28 iTech Prep Rookie Tournament
2/3 West Salem Tournament (All West teams either compete or help)
2/4 West Salem Tournament (All West teams either compete or help)
Semester Break
2/10 Vale HS Tournament
2/17 Salem VEX League Finals at North Salem (Optional, all teams registered)
2/18 North Marion Tournament
2/25 Skills Only at West Salem (All West Teams not competing at iTech)
2/25 iTech Prep Tournament
3/10-3/11 Oregon VEX State Championship (Qualified West Teams)
4/7-4/8 SkillsUSA State Leadership and Skills Conference: Camp Withycombe. Clackamas, OR
4/25-4/27 Vex Robotics Competition World Championship. Dallas, TX
6/19-6/23 SkillsUSA National Leadership and Skills Conference: Atlanta, GA
10/28 Salem VEX League at West (Optional, all teams registered)
10/29 Sandy Tournament (2990E, 2990K, 2990U)
11/5 Lost River HS Tournament
11/19 North Marion Tournament (2990E, 2990K, 2990U)
12/2 West Salem Tournament Setup (All West Teams) + Salem VEX League at West (Optional, all teams registered)
12/3 West Salem Tournament (All West Salem Teams)
1/6 Salem VEX League at South Salem High School (Optional, all teams registered)
1/7 South Salem VEX Tournament (2990K, 2990V)
1/14 Sandy Tournament (2990E, 2990K, 2990U)
1/20 Salem VEX League at North Salem (Optional, all teams registered)
1/21 Willamette Tournament (2990E, 2990K, 2990U)
1/27-1/28 Mazama HS Tournament
1/28 iTech Prep Rookie Tournament
2/3 West Salem Tournament (All West teams either compete or help)
2/4 West Salem Tournament (All West teams either compete or help)
Semester Break
2/10 Vale HS Tournament
2/17 Salem VEX League Finals at North Salem (Optional, all teams registered)
2/18 North Marion Tournament
2/25 Skills Only at West Salem (All West Teams not competing at iTech)
2/25 iTech Prep Tournament
3/10-3/11 Oregon VEX State Championship (Qualified West Teams)
4/7-4/8 SkillsUSA State Leadership and Skills Conference: Camp Withycombe. Clackamas, OR
4/25-4/27 Vex Robotics Competition World Championship. Dallas, TX
6/19-6/23 SkillsUSA National Leadership and Skills Conference: Atlanta, GA
|
|
|
Drive train
Second Semester
Engineering Notebook Basics
Engineering Notebooks should contain these elements:
Team number on the cover/beginning of document Errors crossed out using a single line (so errors can be seen) Unedited entries All pages intact; no pages or parts of pages removed Each page/entry chronologically numbered and dated Each page/entry signed or initialed by a student author Team meeting notes as they relate to the design process Permanently affixed pictures, CAD drawings, documents, examples of code, or other material relevant to the design process (in the case of physical notebooks, tape is acceptable, but glue is preferred) Outstanding Engineering Notebooks should contain these additional elements: Table of contents Entries are dated with the names of contributing students included Notebook begins with the first team meeting Descriptions, sketches, and pictures of design concepts and the design process Observations and thoughts of team members about their design and their design process Records of tests, test results, and evaluations of specific designs or design concepts Project management practices including their use of personnel, financial, and time resources Notes and observations from competitions to consider in the next design iteration Descriptions of programming concepts, programming improvements, or significant programming modifications Enough detail that a person unfamiliar with the team’s work would be able to follow the logic used by the team to develop their design, and recreate the robot design using only the Engineering Notebook Fully Developed Engineering Notebooks contain great detail, and will include detailed drawings, tests and test results, solutions to problems the team encountered, and will be a complete record of the design process. Notebook attributes for Fully Developed notebooks will be scored as Emerging, Proficient, and Expert on the Engineering Notebook Rubric. Only Fully Developed Notebooks should be considered for any awards requiring a notebook. The absolute minimum for a notebook to be considered “Fully Developed” would be the first four criteria of the rubric, outlining the initial design process of a single iteration. |
Resources found at students.vex.com
- Interviews with VEX Students Engineering Engineering Notebooks Code Participating in VEX Competitions Engineering - Notebooking - Coding - Competing - Code of Conduct - VEX Library - REC Library for Teams - More Student Resources - Parent and Guardian Resources Scholarships |