Difference between revisions of "Cornell Rocketry Team"

From Cornell Rocketry Wiki
Jump to: navigation, search
(→‎Documentation)
 
(23 intermediate revisions by 4 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 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 =
−
As a competitive project team, CRT holds its members to high standards. Below are some of the basic expectations of being a CRT member.  
+
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 ==
 
== General Expectations ==
 
All team members must:
 
All team members must:
Line 22: Line 31:
 
* All team members check slack regularly
 
* All team members check slack regularly
 
** Be sure to turn on notifications
 
** Be sure to turn on notifications
−
* [https://drive.google.com/open?id=0BwwZjqwPMhI7eTRhbEJWS0hERjA All team slides]
 
−
* [https://calendar.google.com/calendar?cid=Y29ybmVsbC5lZHVfdTZuZ2tiNjI4amYwZ2k0NnBicTFiN3BhZHNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ Google Calendar]
 
  
 
= Team Structure =
 
= Team Structure =
Line 31: 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)]]
−
*[[Independent Testing and Validation Subteam (INTEV)|Independent Testing and Validation (INTEV)]]
 
 
*[[Payload Subteam|Payload]]
 
*[[Payload Subteam|Payload]]
 +
*[[Propulsion Subteam|Propulsion]]
  
−
=Order Form=
+
Some subteams are deprecated, but their results live on.
 +
*[[Independent Testing and Validation Subteam (INTEV)|Independent Testing and Validation (INTEV)]]
  
−
https://docs.google.com/spreadsheets/d/1PO4vpfnXfCDquNCaI2nS8D_GhVYYGfD2rnUzOQ2xb-4/edit?ts=5ae8ce55
+
= Competitions =
  
−
= Documentation =
+
For information on the current competition and systems, go to [[SA Cup 2018-2019]].
  
−
For more detail, see [[Documentation]].
+
For information on the SA Cup in general, go to [[Spaceport America Cup]].
  
−
== New Documentation ==
+
== NASA Student Launch ==
  
−
With the transition to SA Cup/IREC, CRT's documentation has been drastically revamped to reflect the needs of the team and the competition. There are very few required documents for IREC, which is both good and bad. Good, because it means less writing.  Bad, because unfortunately documentation is an extremely critical part of design, so we now need not only to come up with our own documentation, but also provide our own motivation for doing it.
+
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.
  
−
In general, the amount of necessary writing has been greatly reduced.  Most of the information is now held in (theoretically) regularly updated wiki pages.  Additionally, it is perfectly acceptable in most cases to write in bullet points or short statements, rather than tedious, verbose paragraphs (like this one).  A greater emphasis is placed on figures with lots of labels, which are a bit time consuming to make but are far more efficient at conveying information.
+
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]]
  
−
Information relevant to multiple systems/subteams, such as integration, testing, and hazards, are still held in ShareLaTeX documents. 
+
= Documentation =
−
There are several reasons for this:
 
−
* Multiple people can edit at once.
 
−
* People can easily leave comments and discuss contentious points.
 
−
* Understanding LaTeX is, in fact, a rather useful skill, so everyone on the team should learn.
 
−
* We have a sponsorship from them, so we might as well use it.
 
  
−
Additionally, PDR is entirely made through ShareLaTeX.  Aside from the reasons listed above, the fact is that PDR is so preliminary that most all of its information will inevitably become outdated.  Were it to be hosted on the wiki, these outdated parts would eventually be overwritten and never seen again.  This is a problem on multiple fronts:
+
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.
−
* Knowing where a design started is very valuable when evaluating how it turned out.
 
−
* Some of the design alternatives that were discarded might be used in the future.
 
−
* Understanding how to start a design is a rather subtle skill, so it's useful to be able to see how it was done in the past.
 
  
−
Finally, keep in mind that the development of this documentation is an ongoing process.  Feel free to give feedback and tell the leads about any ideas that might occur to you.  If the currently layout just doesn't work for the information you need to convey, let people know and you can discuss how to tweak it.
+
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 what CRT does. Every system that CRT develops is has been extensively documented in our documentation that we submit to NASA every year. We use 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]]
Line 80: Line 84:
 
*[[GitHub]]
 
*[[GitHub]]
 
*[[Controls Basics]]
 
*[[Controls Basics]]
 +
*[[Altium Setup]]
 
*[[Altium]]
 
*[[Altium]]
 
*[[3D Printing]]
 
*[[3D Printing]]
 
*[[Design Catalog]]
 
*[[Design Catalog]]
 
*[[Acronym Dictionary]]
 
*[[Acronym Dictionary]]
 +
*[[ANSYS Guide]]
  
 
=Material For Leads=
 
=Material For Leads=

Latest revision as of 17:28, 5 September 2019

Cornell Rocketry Team
Part of the CRT series
Getting Started
Enrollment • Expectations • Facilities • Files & Communication • Grading
NASA USLI Seasons
2017-2018 • 2016-2017 • 2015-2016 • 2014-2015
People
Professor Douglas MacMartin (Team Advisor) • Daniel Sheerer (Team Mentor) • Yash Sahota (Co-Team Lead) • Matt Schneider (Co-Team Lead)
Subteams
Airframe • Business • Communications (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
Wiki • Documentation • Writing about Safety and Hazards • Style Guide • ShareLaTeX Guide • Technical Writing Guide • Solidworks Training • GitHub • Controls Basics • Altium • 3D Printing • Design Catalog • Acronym Dictionary • ANSYS Guide
Reference
Branding and Standards* • Useful Calculations* • Launch Database*
Miscellaneous
FAQs • Library of Useful Sources
*login required
V • E

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

Retrieved from "http://wiki.cornellrocketry.com/wiki/index.php?title=Cornell_Rocketry_Team&oldid=2707"