Difference between revisions of "Cornell Rocketry Team"

From Cornell Rocketry Wiki
Jump to: navigation, search
Line 1: Line 1:
 
{{crt-sidebar}}
 
{{crt-sidebar}}
Cornell Rocketry Team (CRT) is a student-led engineering project team at [https://en.wikipedia.org/wiki/Cornell_University Cornell University]. Consisting of students from four different colleges within the university, CRT strives to push the limits on [[high-power rocketry]] and build innovative payloads. The team is currently preparing to compete in the 2019 [http://www.soundingrocket.org/sa-cup-home.html Spaceport America Cup].
+
Cornell Rocketry Team (CRT) is a student-led engineering project team at [https://en.wikipedia.org/wiki/Cornell_University Cornell University]. Consisting of students from four different colleges within the university, CRT strives to push the limits on [[high-power rocketry]] and build innovative payloads. The team is currently preparing to compete in the 2019 [https://www.spaceportamericacup.com/ Spaceport America Cup].
  
 
As part of the team's educational series on high-power rocketry, members build and launch [[L1 Certification|Level 1]], [[L2 Certification|Level 2]], and Level 3 high-power rockets. Most local launches occur as part of [http://urrg.us Upstate Research Rocketry Group (URRG)], sanctioned as [[Tripoli Rocketry Association (TRA)]] Prefecture #139 and [[National Association of Rocketry (NAR)]] Section #765.
 
As part of the team's educational series on high-power rocketry, members build and launch [[L1 Certification|Level 1]], [[L2 Certification|Level 2]], and Level 3 high-power rockets. Most local launches occur as part of [http://urrg.us Upstate Research Rocketry Group (URRG)], sanctioned as [[Tripoli Rocketry Association (TRA)]] Prefecture #139 and [[National Association of Rocketry (NAR)]] Section #765.
Line 24: Line 24:
 
* [https://drive.google.com/open?id=0BwwZjqwPMhI7eTRhbEJWS0hERjA All team slides]
 
* [https://drive.google.com/open?id=0BwwZjqwPMhI7eTRhbEJWS0hERjA All team slides]
 
* [https://calendar.google.com/calendar?cid=Y29ybmVsbC5lZHVfdTZuZ2tiNjI4amYwZ2k0NnBicTFiN3BhZHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Google Calendar]
 
* [https://calendar.google.com/calendar?cid=Y29ybmVsbC5lZHVfdTZuZ2tiNjI4amYwZ2k0NnBicTFiN3BhZHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Google Calendar]
 
= Previous Competitions =
 
In the past, CRT has competed in the [https://en.wikipedia.org/wiki/NASA NASA] [https://www.nasa.gov/audience/forstudents/studentlaunch/home/index.html University Student Launch competition].  The team has transitioned to the SA Cup due to it's greater focus on creative freedom and results.
 
 
For information on previous years, follow the links below.
 
*[[NASA SL 2017-2018]]
 
*[[NASA SL 2016-2017]]
 
*[[NASA SL 2015-2016]]
 
*[[NASA SL 2014-2015]]
 
  
 
= Team Structure =
 
= Team Structure =
Line 42: Line 33:
 
*[[Independent Testing and Validation Subteam (INTEV)|Independent Testing and Validation (INTEV)]]
 
*[[Independent Testing and Validation Subteam (INTEV)|Independent Testing and Validation (INTEV)]]
 
*[[Payload Subteam|Payload]]
 
*[[Payload Subteam|Payload]]
 +
 +
= Competitions =
 +
 +
For information on the current competition and systems, go to [[SA Cup 2018-2019]].
 +
 +
== NASA Student Launch ==
 +
 +
In the past, CRT has competed in the [https://en.wikipedia.org/wiki/NASA NASA] [https://www.nasa.gov/audience/forstudents/studentlaunch/home/index.html University Student Launch competition].  The team has transitioned to the SA Cup due to it's greater focus on creative freedom and results.
 +
 +
For information on previous years, follow the links below.
 +
*[[NASA SL 2017-2018]]
 +
*[[NASA SL 2016-2017]]
 +
*[[NASA SL 2015-2016]]
 +
*[[NASA SL 2014-2015]]
  
 
=Order Form=
 
=Order Form=
  
 +
OUT OF DATE
 
https://docs.google.com/spreadsheets/d/1PO4vpfnXfCDquNCaI2nS8D_GhVYYGfD2rnUzOQ2xb-4/edit?ts=5ae8ce55
 
https://docs.google.com/spreadsheets/d/1PO4vpfnXfCDquNCaI2nS8D_GhVYYGfD2rnUzOQ2xb-4/edit?ts=5ae8ce55
  
 
= Documentation =
 
= Documentation =
  
== New Documentation ==
+
Documentation, while not a very glamorous task, is nonetheless a critical aspect of engineering.  It guides the design process, helps ensure that everyone is on the same page, and provides a reference for the future.  As such, every system that CRT develops is extensively documented throughout its production cycle.  The documentation is split between this wiki and external documents written using ShareLaTeX.
  
With the transition to SA Cup/IREC, CRT's documentation has been drastically revamped to reflect the needs of the team and the competition.  For more details on the new documentation structure, see [[Documentation]].
+
With the transition to SA Cup, CRT's documentation has been drastically revamped to reflect the needs of the team and the competition.  For more details on the new documentation structure, see [[Documentation]].
  
 
== Documentation from Previous Years ==
 
== Documentation from Previous Years ==
  
Documenting our progress throughout the life cycle of each project is a very important part of the engineering process. Every system that CRT develops has been extensively documented in our documentation that we submitted to NASA every year. We used ShareLaTeX for writing our technical reports.  
+
The NASA SL required that a number of reports be submitted throughout the year leading up to the competition.  The size of these reports and the effort they required was one of the primary motivators for switching to SA Cup.
  
One of the best ways to learn how we do documentation is to read some of it!
+
Nonetheless, they provide a comprehensive look at previous systems, as well as a good reference for what technical documentation should look like.  To read them, follow the links below.
 
*[[NASA SL 2017-2018#Documentation | NASA SL 2017-2018]]
 
*[[NASA SL 2017-2018#Documentation | NASA SL 2017-2018]]
 
*[[NASA SL 2016-2017#Documentation | NASA SL 2016-2017]]
 
*[[NASA SL 2016-2017#Documentation | NASA SL 2016-2017]]

Revision as of 19:11, 21 July 2018

Cornell Rocketry Team
Part of the CRT series
Getting Started
EnrollmentExpectationsFacilitiesFiles & CommunicationGrading
NASA USLI Seasons
2017-20182016-20172015-20162014-2015
People
Professor Douglas MacMartin (Team Advisor)Daniel Sheerer (Team Mentor) Yash Sahota (Co-Team Lead) Matt Schneider (Co-Team Lead)
Subteams
AirframeBusinessCommunications (Comms)Electrical and Software (E&S)Independent Testing and Validation (INTEV)Payload Propulsion
High-Power Rocketry Certification
Level 1 Level 2 • Level 3
How to & Guides
WikiDocumentationWriting about Safety and HazardsStyle GuideShareLaTeX GuideTechnical Writing GuideSolidworks TrainingGitHubControls BasicsAltium3D PrintingDesign CatalogAcronym DictionaryANSYS Guide
Reference
Branding and Standards* Useful Calculations*Launch Database*
Miscellaneous
FAQsLibrary of Useful Sources
*login required
VE

Cornell Rocketry Team (CRT) is a student-led engineering project team at Cornell University. Consisting of students from four different colleges within the university, CRT strives to push the limits on high-power rocketry and build innovative payloads. The team is currently preparing to compete in the 2019 Spaceport America Cup.

As part of the team's educational series on high-power rocketry, members build and launch Level 1, Level 2, and Level 3 high-power rockets. Most local launches occur as part of Upstate Research Rocketry Group (URRG), sanctioned as Tripoli Rocketry Association (TRA) Prefecture #139 and National Association of Rocketry (NAR) Section #765.

CRT's faculty advisor is Dr. Daniel Selva and the team's faculty mentor is Daniel Sheerer. The current team leads are Bryan Zheng (AEP '19), Chris Fedors (ECE '18), and Stephanie Chang (CS '20).

Expectations of Team Members

As a competitive project team, CRT holds its members to high standards. Below are some of the basic expectations of being a CRT member.

General Expectations

All team members must:

  • maintain a positive working environment
  • meet deadlines assigned to them
  • not be on another project team while they are an active member of CRT
  • attend the weekly all team meeting unless exempted by the team leads
  • work in accordance to the amount of credit hours they have signed up for
  • fill out a weekly progress report form
  • write about their contributions to the team on the wiki

Communication

  • All team members should check their email regularly
  • All team members check slack regularly
    • Be sure to turn on notifications
  • All team slides
  • Google Calendar

Team Structure

CRT maintains a functional team structure, consisting of six subteams in addition to the team leads. For more information on each subteam, follow the links below.

Competitions

For information on the current competition and systems, go to SA Cup 2018-2019.

NASA Student Launch

In the past, CRT has competed in the NASA University Student Launch competition. The team has transitioned to the SA Cup due to it's greater focus on creative freedom and results.

For information on previous years, follow the links below.

Order Form

OUT OF DATE https://docs.google.com/spreadsheets/d/1PO4vpfnXfCDquNCaI2nS8D_GhVYYGfD2rnUzOQ2xb-4/edit?ts=5ae8ce55

Documentation

Documentation, while not a very glamorous task, is nonetheless a critical aspect of engineering. It guides the design process, helps ensure that everyone is on the same page, and provides a reference for the future. As such, every system that CRT develops is extensively documented throughout its production cycle. The documentation is split between this wiki and external documents written using ShareLaTeX.

With the transition to SA Cup, CRT's documentation has been drastically revamped to reflect the needs of the team and the competition. For more details on the new documentation structure, see Documentation.

Documentation from Previous Years

The NASA SL required that a number of reports be submitted throughout the year leading up to the competition. The size of these reports and the effort they required was one of the primary motivators for switching to SA Cup.

Nonetheless, they provide a comprehensive look at previous systems, as well as a good reference for what technical documentation should look like. To read them, follow the links below.

Guides

Material For Leads