Difference between revisions of "Cornell Rocketry Team"
(→Documentation) |
(→Documentation from Previous Years) |
||
Line 46: | Line 46: | ||
== Documentation from Previous Years == | == Documentation from Previous Years == | ||
− | Documenting our progress throughout the life cycle of each project is a very important part of | + | 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. |
One of the best ways to learn how we do documentation is to read some of it! | One of the best ways to learn how we do documentation is to read some of it! |
Revision as of 18:42, 21 July 2018
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 and sustainable payloads. The team is currently competing in the 2017-2018 NASA University Student Launch competition with their rocket, Flammea, and its payload, the Deployable Rover System (DRS).
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).
Contents
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.
- Airframe
- Business
- Communications (Comms)
- Electrical and Software (E&S)
- Independent Testing and Validation (INTEV)
- Payload
Order Form
https://docs.google.com/spreadsheets/d/1PO4vpfnXfCDquNCaI2nS8D_GhVYYGfD2rnUzOQ2xb-4/edit?ts=5ae8ce55
Documentation
New Documentation
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.
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.
One of the best ways to learn how we do documentation is to read some of it!
Guides
- Writing about Safety and Hazards
- Style Guide
- ShareLaTeX Guide
- Technical Writing Guide
- Solidworks Training
- GitHub
- Controls Basics
- Altium
- 3D Printing
- Design Catalog
- Acronym Dictionary