Difference between revisions of "Cornell Rocketry Team"

From Cornell Rocketry Wiki
Jump to: navigation, search
(Expectations of Team Members)
 
(72 intermediate revisions by 7 users not shown)
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 and sustainable payloads. The team is currently competing in the 2017-2018 [https://en.wikipedia.org/wiki/NASA NASA] [https://www.nasa.gov/audience/forstudents/studentlaunch/home/index.html University Student Launch competition] with their rocket, ''[[Flammea]]'', and its payload, the ''[[Deployable Rover System (DRS)]]''.
+
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 [https://en.wikipedia.org/wiki/High-power_rocketry 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.
  
CRT's faculty advisor is [http://www.mae.cornell.edu/mae/people/profile.cfm?netid=ds925 Dr. Daniel Selva] and the team's faculty mentor is Daniel Sheerer. The current team leads are Bryan Zheng ([[Applied & Engineering Physics|AEP]] '19), [[user:Coolchris |Chris Fedors]] ([[Electrical & Computer Engineering |ECE]] '18), and Stephanie Chang ([[Computer Science |CS]] '20).  
+
CRT's faculty advisor is [https://www.mae.cornell.edu/people/profile.cfm?netid=dgm224 Professor Douglas MacMartin] and the team's faculty mentor is [[Daniel Sheerer]].  
 +
 
 +
The current team leads are Yash Sahota ([[Computer Science|CS]] '20) and Matt Schneider ([[Mechanical Engineering |MechE]] '21).
 +
 
 +
For information on the current competition and systems, go to [[SA Cup 2018-2019]].
 +
 
 +
'''A note to all wiki editors:'''  ''remember that this page is public.  Do not post links to internal CRT items on this page.''
  
 
= Expectations of Team Members =
 
= Expectations of Team Members =
*All team members must maintain a positive working environment
+
As a competitive project team, CRT holds its members to high standards. Below are some of the basic expectations of being a CRT member.
** Above all, this is an extracurricular activity
+
 
*All team members are expected meet deadlines assigned to them
+
A more detailed rundown can be found on the [[Expectations]] page.
*All team members must attend the weekly all team meeting unless exempted by the team leads
+
 
*All team members are expected to work in accordance to the amount of credit hours they have signed up for
+
== General Expectations ==
*All team members must fill out a weekly progress report form
+
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
  
 
= Team Structure =
 
= Team Structure =
Line 20: Line 38:
 
*[[Communications Subteam (Comms)|Communications (Comms)]]
 
*[[Communications Subteam (Comms)|Communications (Comms)]]
 
*[[Electrical and Software Subteam (E&S)|Electrical and Software (E&S)]]
 
*[[Electrical and Software Subteam (E&S)|Electrical and Software (E&S)]]
 +
*[[Payload Subteam|Payload]]
 +
*[[Propulsion Subteam|Propulsion]]
 +
 +
Some subteams are deprecated, but their results live on.
 
*[[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]]
 
  
= Competition Seasons =
+
= Competitions =
CRT was first founded in 2013 and after establishing our foundations, we began competing in the NASA SL ever since.  
+
 
 +
For information on the current competition and systems, go to [[SA Cup 2018-2019]].
 +
 
 +
For information on the SA Cup in general, go to [[Spaceport America Cup]].
 +
 
 +
== 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 2017-2018]]
 
*[[NASA SL 2016-2017]]
 
*[[NASA SL 2016-2017]]
Line 31: Line 61:
  
 
= Documentation =
 
= 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.
 +
*[[NASA SL 2017-2018#Documentation | NASA SL 2017-2018]]
 +
*[[NASA SL 2016-2017#Documentation | NASA SL 2016-2017]]
 +
*[[NASA SL 2015-2016#Documentation | NASA SL 2015-2016]]
 +
*[[NASA SL 2014-2015#Documentation | NASA SL 2014-2015]]
 +
 
== Guides ==  
 
== Guides ==  
 
*[[Writing about Safety and Hazards]]
 
*[[Writing about Safety and Hazards]]
Line 37: Line 82:
 
*[[Technical Writing Guide]]
 
*[[Technical Writing Guide]]
 
*[[Solidworks Training]]
 
*[[Solidworks Training]]
 +
*[[GitHub]]
 
*[[Controls Basics]]
 
*[[Controls Basics]]
 
+
*[[Altium Setup]]
== Scores ==
+
*[[Altium]]
*Environmental and Safety Hazards
+
*[[3D Printing]]
 
+
*[[Design Catalog]]
== Environmental Hazards ==
+
*[[Acronym Dictionary]]
*Include hazards to the environment posed by our manufacturing process. I.e. lead solder and fiberglass dust.
+
*[[ANSYS Guide]]
  
 
=Material For Leads=
 
=Material For Leads=
 +
*[[Recruiting]]
 +
*[[Subteam Lead Duties]]
 +
*[[All-Team Lead Duties]]

Latest revision as of 17:28, 5 September 2019

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 Professor Douglas MacMartin and the team's faculty mentor is Daniel Sheerer.

The current team leads are Yash Sahota (CS '20) and Matt Schneider (MechE '21).

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

A note to all wiki editors: remember that this page is public. Do not post links to internal CRT items on this page.

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.

A more detailed rundown can be found on the Expectations page.

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

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.

Some subteams are deprecated, but their results live on.

Competitions

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

For information on the SA Cup in general, go to Spaceport America Cup.

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.

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