Stanford SSI Wiki - User contributions [en]

ValBal SHITL

2018-05-10T02:50:21Z

Johnldean: /* Running a SHITL test */

SHITL stands for Some Hardware In The Loop. SHITL testing is a method of testing things before launch, similarly other forms of testing are Hardware in the Loop (HITL) or Hardware Out Of the Loop (HOOTL). The best test is a HITL, which tests all hardware and software components, while a HOOTL is mostly just for software and is a simulation, and a SHITL is somewhere in the middle. It's like shitty version of HITL.

For Valbal, we use a Raspberry Pi to both flash new code to the valbal board, and run tests, all from the comfort of our beds.
===Connecting to the Pi===

We use SSH to connect to the pi (more info on how to setup SSH on the client side aka your laptop can be fount under section 4 [https://www.raspberrypi.org/documentation/remote-access/ssh/ of this guide]). Rather than set up a static IP address for the pi, which can be a pain to do properly, we have the pi publish it's ip address whenever it changes to slack to the channel #what-is-valbals-ip. The user name for the defaul user is pi. So an example command to get in is <code> ssh pi@10.34.195.142 </code>

In order to get in, you will need an an authorized RSA key. So, before trying to log in message either @johndean or @jcreus to add your public key. For more info on RSA key's refer to [https://git-scm.com/book/en/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key here]

After that, you should be good to go to SSH into the Pi

===Uploading Code===

Be in the platformio project folder you want to upload code for, and just run the command <code>push</code>. This calls a short script to do the necessary things.

===Running a SHITL test===

First, you have to make sure that the code is configured to actually run the test. In Avionics.h, un-comment out the line <code>#define SERIALSHITL</code>. Once reprogrammed, this will put valbal in SHITL mode.

Next, run the script shitl/shitl.py with python3 (you must used the command <code>python3</code> since the pi defaults to python2 (I think)). You'll want to do this as soon as platformio is done uploading the code to valbal.

After shitl is running, a bunch of variables will be output to a file in test <code>shitl/test-outputs</code> . The date and time is appended to each file, so find the most recent one. I think the pi is on UTC time or something so it wont match local time.

==== Notes ====
You'll want to run the shitl.py from a screen session so that you can logout and it will stay running. To do this, run the command <code>screen</code> and then do things normally as you would. Refer to the manpages of screen for more info.

===SD Card (joan cough cough)===

ValBal SHITL

2018-05-09T09:53:08Z

Johnldean: /* Uploading Code */

ValBal SHITL

2018-05-09T09:52:47Z

Johnldean:

ValBal SHITL

2018-05-09T09:52:28Z

Johnldean: /* Uploading Code */

ValBal SHITL

2018-05-09T09:50:53Z

Johnldean: /* Connecting to the Pi */

ValBal SHITL

2018-05-09T09:35:36Z

Johnldean: Created page with "SHITL stands for Some Hardware In The Loop. SHITL testing is a method of testing things before launch, similarly other forms of testing are Hardware in the Loop (HITL) or Hard..."

Spaghetti

2018-01-03T04:42:41Z

Johnldean:

== How To Use ==

=== Important implentation notes===

* The telemetered effort is not scalled by K, it's the raw effort coming out of the compensator

* The telemetered time intervals are hella descetized cause I fucked up the precision

===Layperson "how it works"===

The central idea to spaghetti is an linear compensator that computes a control effort, given the history of measured altitudes. You don't need to know how it works in order to command it. This control effort is in kg/s. It this then scaled by a gain, called k. Since ballasting and venting are discrete on/off, and the commanded effort is continuous, this needs to be converted into a series of discrete actions, separated by a time interval. This is much like PWM, but instead of changing duty cycle directly, you are changing the time interval between events such that the action time is fixed to it's minimum acceptable value, and produce the least discretization (in the future this may want to be changed to conserve power and minimize the number of valve actions).

===Constants===

freq: The frequency that the controller is called out, which will be a constant 20Hz

k: Scallar gain of the controller. High gains mean more actions, tighter control. Low gain means less actions, looser control

b_dldt: Magnitude of change in lift vs time for ballast actions IN kg/s. This can be directly measured on vb, and us usually around 0.001kg/s

v_dldt: Magnitude of Change in lift vs time for vent actions IN kg/s. This is always an estimate as can not be measured directly. It's a magnitude, and therefor always positive, even though venting decreases net lift

rate_min: minimum threshold for commanding a dl/dt

rate_max: maximum threshold for commanding a dl/dt

b_tmin: the minimum time that a discrete ballast event can be called for. This sets the time that ballast event will be for.

v_tmin: the minimum time that a vent ballast event can be called for. This sets the time that ballast event will be for.

h_cmd: the command altitude for the controller to aim for

===Flight Controller Guide===

In the dev version of spaghetti, you can't really set bounds on your altitude as you can with the legacy controller. Instead, you set a target, and a gain, and the controller attempts to hit the target, using an effort proportional to the gain. What gain will give you the altitude range you want? Who knows.

You also have other things to tune. You want a positive effort to have an equal but opposite effect on the system as a negative effort. Thing is, you don't exactly know you dl/dt for vent actions. So, you have to guess. If it looks like venting isn't having much effect, and the controller is spending much more time above the commanded altitude than below, decrease the set dl/dt for the venting, as your estimate of it is too high.

Also, you don't want to act when your effort is really low and you are close to the target. There needs to be a minimum threshold before you start acting. This is rate_min. The higher you make rate_min, the more the controller acts like a bang-bang controller, where it waits till it's pretty late and then acts a bunch. about 1 order of magnitude below your max rate is probably a decent place to start for your rate min.

== How it works ==

=== Feedback control ===
Spaghetti uses feedback to determine what actions it should take. This is pretty intuitive, as obviously it needs to feedback the current altitude in order to make calculation of the next desired action. Here is the control loop structure:

[ Diagram coming soon]

=== Compensator ===

The heart of the spaghetti controller is the linear compensator that calculates the control effort. The first thing you may wonder is: what do you mean by linear? and what do you mean by compensatory? First of, the compensator is a single input single output system. It calculates an output given a sequence of inputs. It's also what is called Linear Time Invariant (LTI). This means that for any input u1 that produces output y1, the input 2*u1 will produce an output 2*y1. In addition, and two different inputs u1 and u2, with corresponding outputs y1 and y2, the input u1 + u2 will have output y1 + y2. In math terms, this means that it's closed under addition and multiplication, and hence linear. The time invariant part means that if you shift an input in time, the output will be exactly the same, just also shifted in time.

Why is this so important? Because it allows us to analyze the system in the frequency domain. to be continued.

=== Implementation in code ===

If we switch gears into digital signal processing land, we realize that we can implement a linear system in discrete time using what's called a difference equation. This is just a simple equation of a linear combination of past inputs and outputs. The are magical things, and you can pick coefficients tons of different stuff.

The difference equation used for spaghetti is called a [https://en.wikipedia.org/wiki/Digital_biquad_filter biquad filter]. This forms a 2nd order difference equation, as it uses the last two inputs and outputs. With a biquad, we can place two poles and two zeros anywhere we want in the s-plane.

=== Fused ascent rate estimation ===

Another thing that spaghetti implements is an estimation of ascent rate to prevent overacting when it is far away from the setpoint. "Ascent rate" for valbal is actually a tricky measurement though, because at any given time, the true ascent rate is not particularly important. The reason for this being that valbal may rise and fall with turbulence, which isn't something we really care about. Instead, we want to estimate the component of the ascent rate that is due to lift.

There are numerous way's this can be achieved, but an extremely simply method is to just lowpass filter the altitude measurements and take the derivative. Averaging works as a low pass filter, but the buffer size that you would need is too way to large unless you downsample the data, which isn't ideal. Averaging also has a few other downsides. A better way to lowpass filter in this application is to create a 2nd order lowpass filter using a biquad. This smooths out the data for us, so that when we take the derivative it will be less noisy.

However, a problem arises. Any causal lowpass filter will have what is called group delay. This means that things sent through the filter will be delayed. This is intuitive, and the same thing happens with a running average as the output responds kind of slowly to the input, and is how it reduces the noise. This becomes a problem, especially when blasting or venting which will cause sudden changes in ascent rate. If our ascent rate estimate takes too long to respond, then we can't prevent overshoots.

How do we fix this? We can add in the information that we just ballasted to our filter. The optimal way to do so would be with some gaussian distribution math, through a kalman filter. However, picking variances for this can be very handwavy, and the end result may just be an over engineered lowpass filter. So instead, w do something simpler. we want to add in the equivalent ascent rate change that we would expect from our ballasting action, but then have this amount that we added in to decay over time to zero as we know our filtered ascent rate will eventually catch up. How can we do this? Well, exponential decay like this is exactly the behavior we would get from the impulse response of a first order LTI system with a single pole on the negative real axis. We can produce this with another recurrence relation, similar to the filter. The final estimate is simply the sum of these two.

As for how to actually pick values for the filter, like quality factor and cutoff frequency, we just "play" with old data and see what works well. Same goes for the rate of exponential decay for the estimate.

=== If you think controls are cool and wanna learn more ===

Relevant classes:

* EE102A Signal Processing and Linear Systems I (highly highly recommend, great intro class)
* EE102B Signal Processing and Linear Systems II
* ENGR105 Feedback Control
* CHEMENG 100 Chemical Process Modeling, Dynamics, and Control (second half controls, first half modeling systems/diff eqs)

[[Category:ValBal_Controls]]

Spaghetti

2017-12-11T00:23:58Z

Johnldean: /* Implementation in code */

Spaghetti

2017-12-11T00:23:21Z

Johnldean: /* Implementation in code */

Spaghetti

2017-12-11T00:21:10Z

Johnldean: /* Implementation in code */

Spaghetti

2017-12-11T00:19:37Z

Johnldean:

Spaghetti

2017-12-11T00:15:34Z

Johnldean:

Spaghetti

2017-12-10T00:58:03Z

Johnldean:

=== Important implentation notes===

* The telemetered effort is not scalled by K, it's the raw effort coming out of the compensator

* The telemetered time intervals are hella descetized cause I fucked up the precision

===Layperson "how it works"===

The central idea to spaghetti is an linear compensator that computes a control effort, given the history of measured altitudes. You don't need to know how it works. This control effort is in kg/s. It this then scaled by a gain, called k. Since ballasting and venting are discrete on/off, and the commanded effort is continuous, this needs to be converted into a series of discrete actions, separated by a time interval. This is much like PWM, but instead of changing duty cycle directly, you are changing the time interval between events such that the action time is fixed to it's minimum acceptable value, and produce the least discretization (in the future this may want to be changed to conserve power and minimize the number of valve actions).

===Constants===

freq: The frequency that the controller is called out, which will be a constant 20Hz

k: Scallar gain of the controller. High gains mean more actions, tighter control. Low gain means less actions, looser control

b_dldt: Magnitude of change in lift vs time for ballast actions IN kg/s. This can be directly measured on vb, and us usually around 0.001kg/s

v_dldt: Magnitude of Change in lift vs time for vent actions IN kg/s. This is always an estimate as can not be measured directly. It's a magnitude, and therefor always positive, even though venting decreases net lift

rate_min: minimum threshold for commanding a dl/dt

rate_max: maximum threshold for commanding a dl/dt

b_tmin: the minimum time that a discrete ballast event can be called for. This sets the time that ballast event will be for.

v_tmin: the minimum time that a vent ballast event can be called for. This sets the time that ballast event will be for.

h_cmd: the command altitude for the controller to aim for

===Flight Controller Guide===

In the dev version of spaghetti, you can't really set bounds on your altitude as you can with the legacy controller. Instead, you set a target, and a gain, and the controller attempts to hit the target, using an effort proportional to the gain. What gain will give you the altitude range you want? Who knows.

You also have other things to tune. You want a positive effort to have an equal but opposite effect on the system as a negative effort. Thing is, you don't exactly know you dl/dt for vent actions. So, you have to guess. If it looks like venting isn't having much effect, and the controller is spending much more time above the commanded altitude than below, decrease the set dl/dt for the venting, as your estimate of it is too high.

Also, you don't want to act when your effort is really low and you are close to the target. There needs to be a minimum threshold before you start acting. This is rate_min. The higher you make rate_min, the more the controller acts like a bang-bang controller, where it waits till it's pretty late and then acts a bunch. about 1 order of magnitude below your max rate is probably a decent place to start for your rate min.

Spaghetti

2017-12-10T00:56:51Z

Johnldean:

=== Important implentation notes==

+ The telemetered effort is not scalled by K, it's the raw effort coming out of the compensator

===Layperson "how it works"===

The central idea to spaghetti is an linear compensator that computes a control effort, given the history of measured altitudes. You don't need to know how it works. This control effort is in kg/s. It this then scaled by a gain, called k. Since ballasting and venting are discrete on/off, and the commanded effort is continuous, this needs to be converted into a series of discrete actions, separated by a time interval. This is much like PWM, but instead of changing duty cycle directly, you are changing the time interval between events such that the action time is fixed to it's minimum acceptable value, and produce the least discretization (in the future this may want to be changed to conserve power and minimize the number of valve actions).

===Constants===

freq: The frequency that the controller is called out, which will be a constant 20Hz

k: Scallar gain of the controller. High gains mean more actions, tighter control. Low gain means less actions, looser control

b_dldt: Magnitude of change in lift vs time for ballast actions IN kg/s. This can be directly measured on vb, and us usually around 0.001kg/s

v_dldt: Magnitude of Change in lift vs time for vent actions IN kg/s. This is always an estimate as can not be measured directly. It's a magnitude, and therefor always positive, even though venting decreases net lift

rate_min: minimum threshold for commanding a dl/dt

rate_max: maximum threshold for commanding a dl/dt

b_tmin: the minimum time that a discrete ballast event can be called for. This sets the time that ballast event will be for.

v_tmin: the minimum time that a vent ballast event can be called for. This sets the time that ballast event will be for.

h_cmd: the command altitude for the controller to aim for

===Flight Controller Guide===

In the dev version of spaghetti, you can't really set bounds on your altitude as you can with the legacy controller. Instead, you set a target, and a gain, and the controller attempts to hit the target, using an effort proportional to the gain. What gain will give you the altitude range you want? Who knows.

You also have other things to tune. You want a positive effort to have an equal but opposite effect on the system as a negative effort. Thing is, you don't exactly know you dl/dt for vent actions. So, you have to guess. If it looks like venting isn't having much effect, and the controller is spending much more time above the commanded altitude than below, decrease the set dl/dt for the venting, as your estimate of it is too high.

Also, you don't want to act when your effort is really low and you are close to the target. There needs to be a minimum threshold before you start acting. This is rate_min. The higher you make rate_min, the more the controller acts like a bang-bang controller, where it waits till it's pretty late and then acts a bunch. about 1 order of magnitude below your max rate is probably a decent place to start for your rate min.

Spaghetti

2017-12-10T00:23:12Z

Johnldean: Created page with "===Layperson "how it works"=== The central idea to spaghetti is an linear compensator that computes a control effort, given the history of measured altitudes. You don't need..."

===Layperson "how it works"===

The central idea to spaghetti is an linear compensator that computes a control effort, given the history of measured altitudes. You don't need to know how it works. This control effort is in kg/s. It this then scaled by a gain, called k. Since ballasting and venting are discrete on/off, and the commanded effort is continuous, this needs to be converted into a series of discrete actions, separated by a time interval. This is much like PWM, but instead of changing duty cycle directly, you are changing the time interval between events such that the action time is fixed to it's minimum acceptable value, and produce the least discretization (in the future this may want to be changed to conserve power and minimize the number of valve actions).

===Constants===

freq: The frequency that the controller is called out, which will be a constant 20Hz

k: Scallar gain of the controller. High gains mean more actions, tighter control. Low gain means less actions, looser control

b_dldt: Magnitude of change in lift vs time for ballast actions IN kg/s. This can be directly measured on vb, and us usually around 0.001kg/s

v_dldt: Magnitude of Change in lift vs time for vent actions IN kg/s. This is always an estimate as can not be measured directly. It's a magnitude, and therefor always positive, even though venting decreases net lift

rate_min: minimum threshold for commanding a dl/dt

rate_max: maximum threshold for commanding a dl/dt

b_tmin: the minimum time that a discrete ballast event can be called for. This sets the time that ballast event will be for.

v_tmin: the minimum time that a vent ballast event can be called for. This sets the time that ballast event will be for.

h_cmd: the command altitude for the controller to aim for

===Flight Controller Guide===

In the dev version of spaghetti, you can't really set bounds on your altitude as you can with the legacy controller. Instead, you set a target, and a gain, and the controller attempts to hit the target, using an effort proportional to the gain. What gain will give you the altitude range you want? Who knows.

You also have other things to tune. You want a positive effort to have an equal but opposite effect on the system as a negative effort. Thing is, you don't exactly know you dl/dt for vent actions. So, you have to guess. If it looks like venting isn't having much effect, and the controller is spending much more time above the commanded altitude than below, decrease the set dl/dt for the venting, as your estimate of it is too high.

Also, you don't want to act when your effort is really low and you are close to the target. There needs to be a minimum threshold before you start acting. This is rate_min. The higher you make rate_min, the more the controller acts like a bang-bang controller, where it waits till it's pretty late and then acts a bunch. about 1 order of magnitude below your max rate is probably a decent place to start for your rate min.

How to Join SSI

2017-10-10T06:34:25Z

Johnldean:

Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member.

=Becoming an official member=

# Pay dues ($10 in exchange for a t-shirt) to our financial officers - any leadership team member can accept these in cash, or you can Venmo our Financial Officer, Gabi Palavecino, directly. Message her on Slack for details ({{slack-user|gabipalavecino}}). If dues present a financial hardship, message {{slack-user|smaldonado}}, {{slack-user|johndean}}, or {{slack-user|gabipalavecino}}, and we'll waive them.
# Join the SSI Slack [https://ssi-teams.slack.com/signup here].
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].
# In order to allow you access to our workspace, [[End Station III]], you need to do the following things:
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top
##Using either the "All Learning" list, or the Search Catalog, complete the following three safety trainings: '''EHS-4200: General Safety, Injury Prevention (IIPP), and Emergency Preparedness, EHS-1900: Chemical Safety for Laboratories, and EHS-2200: Compressed Gas Safety.''' If you've completed any of these previously for a laboratory class or other university purpose, you don't need to repeat them.
##Some time after completion, you will receive an email for each of these (can take up to 24 hours) certifying your completion. Save each e-mail as a PDF, or, less preferably, screenshot it. This PDF or screenshot '''must''' have your name on it. Ask in {{slack-channel|welcome-to-ssi}} if you have questions about EH&S training - mentioning {{slack-user|mc-safety}} in your question will notify people who can help.
##Sign into the [http://internal.stanfordssi.org/trainings internal site] using your Stanford email and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.
##While in ES3, make sure to sign a copy of the Space Usage Agreement and leave it in the binder by the door. This is your record of completing the workspace safety tour.
##Send a message in Slack to our workspace manager {{slack-user|juleachin}} that you've completed everything!

=Resources=

== [https://ssi-teams.slack.com/ Slack] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

To see what a list of what channels there are to join, check out the [[Slack Directory]].

[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']

==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==
Home to all of our events across all our teams.

== [https://stanfordssi.org/leadership SSI Leadership] ==
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.

==The Wiki==

This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.

==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==

The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage.

== [http://stanfordssi.org/join All The Mailing Lists] ==
We use SSI General for any organization-wide announcements, but use team-specific mailing lists for most of the updates and team announcements (Slack is still by and large the primary mode of communication for most of us though)

== [[End Station III]] ==

End Station III (also known as ES3) can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. End Station III houses work sessions, team meetings, and project storage. Keycard access is required to access the building.

[[File:whereisesiii.png|thumb|left]]

== [[Find a Project]] ==

If you're ever feeling overwhelmed or lost about all the things going on in SSI, use this page to see what's what! Reach out to someone working on a project you're interested in and they'll help you get started. If you have questions or just want to chat, poke any leadership member.

[[Category:Getting started]]

Slack Directory

2017-09-26T08:43:56Z

Johnldean: /* Non-team specific Channels */

== Non-team specific Channels ==
While SSI consists of 6 distinct teams, a large number of channels are general to all SSI members. These channels are great for cross-ssi discussions.
=== General Channels ===
:* #general - typically for general SSI-wide announcements
:* #random - for things you want to share with SSI that doesn’t belong in any other channels
:* #dankmemes - pretty self explanatory. Try typing "/dank" in the channel.
:* #spacenews - to talk about the current state of space affairs
:* #ssipac - politics
:* #best-of-slack - compilation of the best moments on SSI slack
:* #welcome-to-ssi - channel to welcome new members and answer any questions
:* #diverssity - A place to speak about relavant issues
:* #women - A place for women and gender minorities to speak about relavant issues and bond and stuff
:* #new-frosh - for the new frosh to speak among each other about young people problems
=== Fun channels ===
:* #ssi-finds-a-path - DnD roleplaying
:* #ssi-does-exercise - ssi attempts to stay fit
:* #ssi-makes-stuff - a channel to discuss non ssi related personal projects
:* #ssiplacesblocks - ssi’s minecraft group
=== Non team-specific Engineering Channels ===
Interteam collaboration on a technical projects. Why is it called raccoonworks? Who knows.
:* #raccoonworks-eecs - to talk about and get help with random EE or CS related things
:* #raccoonworks-me - to talk about and get help with random ME related things
:* #prak-ssi
=== Class Channels ===
Want to collaborate on a classes with other SSI members? We make channels for classes in the format: #ssitakes[course#]. Ex:
:* #ssitakesme203
:* #ssitakescs106b

== Team Channels ==
Each team has a general announcements channel of the format: #[teamname] (ex #rockets) where general team wide discussion and announcements will be made. Sub-projects, and often subsystems of subprojects will be in their own channels. This is usually where the engineering takes place!
=== Rockets ===
:* #rockets

=== Balloons ===
:* #balloons
:* #balloons-valbal
:* #balloons-rf
:* #balloons-habees
:* #balloons-habhive
:* #habmc
=== Sats ===
:* #satellites
=== Bio ===
:* #biology
:* #biology-reading
=== Operations ===
:* #operations
:* #operations-herbs
:* #operations-community
:* #operations-diverssity
:* #operations-marketing
=== Policy ===
:* #policy

Contacts
:* {{slack-user|kai}} - operations lead. Talk to him if you want to help make SSI run!
:* {{slack-user|dragland}} and {{slack-user|paigebrown}} - balloons coleads
:* {{slack-user|chao16}} and {{slack-user|tomusiak}} - Biology Co-Leads
:* {{slack-user|johndean}} and {{slack-user|smaldonado}} - Co-Presidents

How to Join SSI

2017-09-26T08:38:44Z

Johnldean:

Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member.

=Becoming an official member=

# Pay dues ($10 in exchange for a t-shirt) to one of our financial officers - any leadership team member can accept these in cash, or you can Venmo our Co-President, John Dean, directly. Message him on Slack for details ({{slack-user|johndean}}). If dues present a financial hardship, message {{slack-user|smaldonado}}, {{slack-user|johndean}}, or {{slack-user|gabipalavecino}}, and we'll waive them.
# Join the SSI Slack [https://ssi-teams.slack.com/signup here].
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].
# In order to allow you access to our workspace, [[End Station III]], you need to do the following things:
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top
##Using either the "All Learning" list, or the Search Catalog, complete the following three safety trainings: '''EHS-4200: General Safety, Injury Prevention (IIPP), and Emergency Preparedness, EHS-1900: Chemical Safety for Laboratories, and EHS-2200: Compressed Gas Safety.''' If you've completed any of these previously for a laboratory class or other university purpose, you don't need to repeat them.
##Some time after completion, you will receive an email for each of these (can take up to 24 hours) certifying your completion. Save each e-mail as a PDF, or, less preferably, screenshot it. This PDF or screenshot '''must''' have your name on it. Ask in {{slack-channel|welcome-to-ssi}} if you have questions about EH&S training - mentioning {{slack-user|mc-safety}} in your question will notify people who can help.
##Sign into the [http://internal.stanfordssi.org/trainings internal site] using your Stanford email and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.
##While in ES3, make sure to sign a copy of the Space Usage Agreement and leave it in the binder by the door. This is your record of completing the workspace safety tour.
##Send a message in {{slack-channel|welcome-to-ssi}} that you've completed everything!

=Resources=

== [https://ssi-teams.slack.com/ Slack] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

To see what a list of what channels there are to join, check out the [[Slack Directory]].

[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']

==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==
Home to all of our events across all our teams.

== [https://stanfordssi.org/leadership SSI Leadership] ==
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.

==The Wiki==

This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.

==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==

The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage.

== [http://stanfordssi.org/join All The Mailing Lists] ==
We use SSI General for any organization-wide announcements, but use team-specific mailing lists for most of the updates and team announcements (Slack is still by and large the primary mode of communication for most of us though)

== [[End Station III]] ==

End Station III (also known as ES3) can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. End Station III houses work sessions, team meetings, and project storage. Keycard access is required to access the building.

[[File:whereisesiii.png|thumb|left]]

[[Category:Getting started]]

Words of Sasha Maldonado

2017-09-22T07:55:38Z

Johnldean:

Some people may have noticed that this kid named Sasha Maldonado uses some fancy words from time to time. In case you, like I, don't know words very well, here is a list of words he's said that are just way to smart sounding for me.

:* Vestibule
:* Federating
:* Tinney (ok I know that one's not even a big word, don't judge me)
:* Minutiae

Words of Sasha Maldonado

2017-09-22T07:55:09Z

Johnldean: Created page with "Some people may have noticed that this kid named Sasha Maldonado uses some fancy words from time to time. In case you, like I, don't know words very well, here is a list of wo..."

How to Join SSI

2017-09-21T05:09:47Z

Johnldean: /* End Station III */

Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member.

=Becoming an official member=

# Pay dues ($10 in exchange for a t-shirt) to one of our financial officers - any leadership team member can accept these in cash, or you can Venmo our financial officer, Gabi Palavecino, directly. Message her on Slack for details ({{slack-user|gabipalavecino}}). If dues present a financial hardship, message {{slack-user|smaldonado}}, {{slack-user|johndean}}, or {{slack-user|gabipalavecino}}, and we'll waive them.
# Join the SSI Slack [https://ssi-teams.slack.com/signup here].
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].
# In order to allow you access to our workspace, [[End Station III]], you need to do the following things:
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top
##Using either the "All Learning" list, or the Search Catalog, complete the following three safety trainings: '''EHS-4200: General Safety, Injury Prevention (IIPP), and Emergency Preparedness, EHS-1900: Chemical Safety for Laboratories, and EHS-2200: Compressed Gas Safety.''' If you've completed any of these previously for a laboratory class or other university purpose, you don't need to repeat them.
##Some time after completion, you will receive an email for each of these (can take up to 24 hours) certifying your completion. Save each e-mail as a PDF, or, less preferably, screenshot it. This PDF or screenshot '''must''' have your name on it. Ask in {{slack-channel|welcome-to-ssi}} if you have questions about EH&S training - mentioning {{slack-user|mc-safety}} in your question will notify people who can help.
##Sign into the [http://internal.stanfordssi.org/trainings internal site] using your Stanford email and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.
##While in ES3, make sure to sign a copy of the Space Usage Agreement and leave it in the binder by the door. This is your record of completing the workspace safety tour.
##Send a message in {{slack-channel|welcome-to-ssi}} that you've completed everything!

=Resources=

== [https://ssi-teams.slack.com/ Slack] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

To see what a list of what channels there are to join, check out the [[Slack Directory]].

[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']

==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==
Home to all of our events across all our teams.

== [https://stanfordssi.org/leadership SSI Leadership] ==
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.

==The Wiki==

This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.

==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==

The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage.

== [http://stanfordssi.org/join All The Mailing Lists] ==
We use SSI General for any organization-wide announcements, but use team-specific mailing lists for most of the updates and team announcements (Slack is still by and large the primary mode of communication for most of us though)

== [[End Station III]] ==

End Station III (also known as ES3) can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. End Station III houses work sessions, team meetings, and project storage. Keycard access is required to access the building.

[[File:whereisesiii.png|thumb|left]]

[[Category:Getting started]]

File:Whereisesiii.png

2017-09-21T05:00:32Z

Johnldean:

How to Join SSI

2017-09-21T04:50:36Z

Johnldean: /* Slack */

Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member.

=Becoming an official member=

# Pay dues ($10 in exchange for a t-shirt) to one of our financial officers - any leadership team member can accept these in cash, or you can Venmo our financial officer, Gabi Palavecino, directly. Message her on Slack for details ({{slack-user|gabipalavecino}}). If dues present a financial hardship, message {{slack-user|smaldonado}}, {{slack-user|johndean}}, or {{slack-user|gabipalavecino}}, and we'll waive them.
# Join the SSI Slack [https://ssi-teams.slack.com/signup here].
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].
# In order to allow you access to our workspace, [[End Station III]], you need to do the following things:
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top
##Using either the "All Learning" list, or the Search Catalog, complete the following three safety trainings: '''EHS-4200: General Safety, Injury Prevention (IIPP), and Emergency Preparedness, EHS-1900: Chemical Safety for Laboratories, and EHS-2200: Compressed Gas Safety.''' If you've completed any of these previously for a laboratory class or other university purpose, you don't need to repeat them.
##Some time after completion, you will receive an email for each of these (can take up to 24 hours) certifying your completion. Save each e-mail as a PDF, or, less preferably, screenshot it. This PDF or screenshot '''must''' have your name on it. Ask in {{slack-channel|welcome-to-ssi}} if you have questions about EH&S training - mentioning {{slack-user|mc-safety}} in your question will notify people who can help.
##Sign into the [http://internal.stanfordssi.org/trainings internal site] using your Stanford email and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.
##While in ES3, make sure to sign a copy of the Space Usage Agreement and leave it in the binder by the door. This is your record of completing the workspace safety tour.
##Send a message in {{slack-channel|welcome-to-ssi}} that you've completed everything!

=Resources=

== [https://ssi-teams.slack.com/ Slack] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

To see what a list of what channels there are to join, check out the [[Slack Directory]].

[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']

==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==
Home to all of our events across all our teams.

== [https://stanfordssi.org/leadership SSI Leadership] ==
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.

==The Wiki==

This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.

==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==

The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage.

== [http://stanfordssi.org/join All The Mailing Lists] ==
We use SSI General for any organization-wide announcements, but use team-specific mailing lists for most of the updates and team announcements (Slack is still by and large the primary mode of communication for most of us though)

== [[End Station III]] ==

End Station III (also known as ES3) can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. End Station III houses work sessions, team meetings, and project storage. Keycard access is required to access the building.

[[Category:Getting started]]

Slack Directory

2017-09-21T04:46:48Z

Johnldean: Created page with "== Non-team specific Channels == While SSI consists of 6 distinct teams, a large number of channels are general to all SSI members. These channels are great for cross-ssi disc..."

== Non-team specific Channels ==
While SSI consists of 6 distinct teams, a large number of channels are general to all SSI members. These channels are great for cross-ssi discussions.
=== General Channels ===
:* #general - typically for general SSI-wide announcements
:* #random - for things you want to share with SSI that doesn’t belong in any other channels
:* #dankmemes - mandatory channel for all members!!!!!
:* #spacenews - to talk about the current state of space affairs
:* #ssipac - politics
:* #best-of-slack - compilation of the best moments on SSI slack
:* #welcome-to-ssi - channel to welcome new members and answer any questions
:* #diverssity - A place to speak about relavant issues
:* #women - A place for women and gender minorities to speak about relavant issues and bond and stuff
:* #new-frosh - for the new frosh to speak among each other about young people problems
=== Fun channels ===
:* #ssi-finds-a-path - DnD roleplaying
:* #ssi-does-exercise - ssi attempts to stay fit
:* #ssi-makes-stuff - a channel to discuss non ssi related personal projects
:* #ssiplacesblocks - ssi’s minecraft group
=== Non team-specific Engineering Channels ===
Interteam collaboration on a technical projects. Why is it called raccoonworks? Who knows.
:* #raccoonworks-eecs - to talk about and get help with random EE or CS related things
:* #raccoonworks-me - to talk about and get help with random ME related things
:* #prak-ssi
=== Class Channels ===
Want to collaborate on a classes with other SSI members? We make channels for classes in the format: #ssitakes[course#]. Ex:
:* #ssitakesme203
:* #ssitakescs106b

== Team Channels ==
Each team has a general announcements channel of the format: #[teamname] (ex #rockets) where general team wide discussion and announcements will be made. Sub-projects, and often subsystems of subprojects will be in their own channels. This is usually where the engineering takes place!
=== Rockets ===
:* #rockets

=== Balloons ===
:* #balloons
:* #balloons-valbal
:* #balloons-rf
:* #balloons-habees
:* #balloons-habhive
:* #habmc
=== Sats ===
:* #satellites
=== Bio ===
:* #biology
:* #biology-reading
=== Operations ===
:* #operations
:* #operations-herbs
:* #operations-community
:* #operations-diverssity
:* #operations-marketing
=== Policy ===
:* #policy

Contacts
:* {{slack-user|kai}} - operations lead. Talk to him if you want to help make SSI run!
:* {{slack-user|dragland}} and {{slack-user|paigebrown}} - balloons coleads
:* {{slack-user|chao16}} and {{slack-user|tomusiak}} - Biology Co-Leads
:* {{slack-user|johndean}} and {{slack-user|smaldonado}} - Co-Presidents

So You Want To...

2017-01-12T19:37:40Z

Johnldean: /* Learn About Kalman Filtering & Sensor Fusion */

==Build An Awesome Foundation of Knowledge==

[https://www.grc.nasa.gov/www/k-12/rocket/shortr.html NASA Beginner's Guide to Rockets]

[https://www.grc.nasa.gov/www/k-12/airplane/short.html NASA Beginner’s Guide to Aerodynamics]

[https://www.grc.nasa.gov/www/k-12/airplane/shortc.html NASA Beginner’s Guide to Compressible Aerodynamics]

[https://www.grc.nasa.gov/www/k-12/airplane/shortp.html NASA Beginner’s Guide to Propulsion]

==Learn About Space Shuttles/NASA Projects==

[http://spaceflight.nasa.gov/shuttle/reference/shutref/index.html Space Shuttle Reference]

[http://history.nasa.gov/SP-4221/sp4221.htm The Space Shuttle Decision]

[http://history.nasa.gov/SP-407/sp407.htm Space Shuttle]

[http://history.nasa.gov/SP-436/sp436.htm Project Orion]

[http://history.nasa.gov/SP-4001/cover.htm Project Mercury]

[http://history.nasa.gov/SP-4002/cover.htm Project Gemini]

==Learn About Rockets/HPR In General==

[https://drive.google.com/drive/u/0/folders/0B_uGMv8pu2KgNnpTbUpMajlCMjg OpenRocket Tech Documentation]

[https://drive.google.com/open?id=0B0L2asxf9DSOOXBld19neENoVkU Modern High Power Rocketry 2]

[https://drive.google.com/drive/u/0/folders/0B_uGMv8pu2KgNnpTbUpMajlCMjg HPR Basics by NAR]

[http://wiki.stanfordssi.org/L1_Certification Get your L1 Cert]

==Learn About Controls==

[https://www.site.uottawa.ca/~rhabash/ELG4152LN01.pdf A Brief Introduction]

[https://www.facstaff.bucknell.edu/mastascu/eControlHTML/Intro/Intro1.html Another Brief Introduction ft. Comic Sans]

[http://machinedesign.com/sensors/introduction-pid-control A Non Math-y Introduction to PID Control]

[https://www.youtube.com/watch?v=oBc_BHxw78s&list=PLUMWjy5jgHK1NC52DXXrriwihVrYZKqjk An Awesome playlist of YouTube videos]

==Learn About Kalman Filtering & Sensor Fusion==

[https://en.wikipedia.org/wiki/Kalman_filter Wikipedia]

[http://www.bzarg.com/p/how-a-kalman-filter-works-in-pictures/ Kalman Filtering Explained with Pictures]

[https://www.overleaf.com/3972499sxgwkz Read about Joan & Rebecca killing brain cells learning (or attempting to learn) this stuff]

[http://blog.tkjelectronics.dk/2012/09/a-practical-approach-to-kalman-filter-and-how-to-implement-it/ More info on how it works]

[http://ozzmaker.com/2015/01/27/guide-interfacing-gyro-accelerometer-raspberry-pi-kalman-filter/ Using a RasPi]

[http://forum.arduino.cc/index.php?topic=58048.0 Using an Arduino]

[http://digitalcommons.calpoly.edu/cgi/viewcontent.cgi?article=1114&context=aerosp CalPoly paper, using Arduinos]

[http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.69.880&rep=rep1&type=pdf Multi-sensor fusion with asynchronous readings] (provides a generic and powerful solution)

[http://liu.diva-portal.org/smash/get/diva2:648377/FULLTEXT01.pdf Paper on Integration of IMUs & GPS]

[http://www.acfr.usyd.edu.au/pdfs/training/multiSensorDataFusion/dataFusionNotes.pdf Long, but well written intro to multi sensor fusion and Kalman filtering]

[http://home.earthlink.net/~david.schultz/rnd/2004/KalmanApogeeII.pdf relatively simple filter used for altitude determination of high powered rockets, made to be computationally simple for dumb processors]

===Notes===

The Kalman filter is linear quadratic estimator. We assume the system is linear, which should be good enough for our purposes. For non linear systems, do an extended Kalman filter. However, this takes much more computational resources and is much more unstable.

A basic diagram of how this estimator works:

[[File:Kalman_Filter_Estimator.png|center|400px]]

===Other Resources===

*[http://www.tech-ex.com/article_images3/9/440249/1-11.pdf More papers]
*[https://agrosy.informatik.uni-kl.de/fileadmin/Literatur/Blank10.pdf “Welp Kalman filtering sometimes sucks but I think we should use it anyway"]
*[http://gentlenav.googlecode.com/files/DCMDraft2.pdf Filtering with accelerometers and gyros and more fun stuff]
*[https://www.xsens.com/images/stories/PDF/drift-free%20dynamic%20height%20sensor%20using%20mems%20imu%20aided%20by%20mems%20pressure%20sensor.pdf Mayhaps for balloons valbal]
*[http://tid.uio.no/~jankbe/Filer/PhD_JKB_200207.pdf Really cool, but way too OP]
*[http://gamepipe.usc.edu/~zyda/resources/pubs/IROS2001.pdf More gyro stuff]

==Learn About Aero/Wings==

[https://docs.google.com/a/stanford.edu/presentation/d/1xMbuJJt6TpkfMDQj7j8fbLxHWFOP7kkEhmNzFy-G7JA/ Chris’s slides]

[https://drive.google.com/open?id=0B_uGMv8pu2KgS3BuNGtiNkUwWU0 Textbook]

==Learn About Physics==

[http://web.mit.edu/16.unified/www/FALL/systems/Lab_Notes/traj.pdf Trajectory Calculations]

[https://www.grc.nasa.gov/www/k-12/rocket/rktfor.html Forces on a Rocket]

==Learn About Solid Mechanics==

[https://docs.google.com/a/stanford.edu/presentation/d/1CZW9eUfra6TJbUV_fETYeGjo4aBgbjnJfozvG6ljoY8/ Chris’s slides]

[https://drive.google.com/a/stanford.edu/file/d/0B-5MRX1wVAAdZ2xDMW1rX0t4OE0/ ME80 textbook]

==Learn About Thermodynamics/Heat Transfer==

[https://docs.google.com/a/stanford.edu/presentation/d/1pOug5fcGkt76gsBKJVQ3arGqYzyL0WgubFvMI3wZkkw/ Chris’s slides]

[https://drive.google.com/open?id=0B_uGMv8pu2KgMDY1OGtlOXBKWjQ ME131A texbook]

==Learn About Fluid Dynamics==

[http://www.engineeringtoolbox.com/bernouilli-equation-d_183.html Simple Bernoulli] (low speed)

[https://www.grc.nasa.gov/www/k-12/airplane/isentrop.html Compressible Flow] (high speed)

[https://drive.google.com/open?id=0B-5MRX1wVAAdYlpDUHoyV2taeVk ME70/131B textbook]

[http://history.nasa.gov/SP-367/chapt5.htm Transonic Flight]

==Learn About Stability==

[https://www.apogeerockets.com/downloads/PDFs/barrowman_report.pdf Barrowman Report]

[https://www.apogeerockets.com/Tech/Rocket_Stability?pg=education&zenid=e8dadefb74ed8ef9521c42a1ea8112ff Compilation of Links on Stability]

==Learn About Orbital Mechanics==

[http://www.braeunig.us/space/orbmech.htm Intro to Orbital Mechanics]

[https://drive.google.com/open?id=0B1NYU3-6sOTIa3RDMVFwYmpVWWs AA279A Lecture Notes]

==Learn About Fins==
[http://www.nakka-rocketry.net/fins.html Fins & Stability]

[https://www.apogeerockets.com/technical_publication_16 Easy to Digest Info From Apogee Rocketry]

[https://www.apogeerockets.com/education/downloads/Newsletter420.pdf Design & Construction Specifically for Low Power]

==Learn About Reefing==

[http://www.thefintels.com/aer/reef.htm People making their own reefing system]

[http://www.rocketryforum.com/showthread.php?17067-Chute-Reef-Line-Cutter People discussing cable cutters]

[http://aeroconsystems.com/cart/launch-and-recovery-accessories/cable-cutter-by-archetype-rocketry/ Aerocon Cable Cutters]

==Learn About Radio Tracking==

[http://rocstock.org/advanced/advanced-rocket-tracking-using-onboard-radio-transmitters/ Overview of Different Forms of Trackers]

[https://docs.google.com/a/stanford.edu/spreadsheets/d/1oiBWdkrCbc3TfJFp_HMPpK0ARKysxRUMq5qcPeT1HbA/ Spreadsheet Comparison of Radio Trackers (see the Radio Tracking tab)]

==Cram for An Amateur Ham Radio License==

[http://www.kb6nu.com/wp-content/uploads/2015/03/2014-no-nonsense-tech-study-guide-v20.pdf No Nonsense Guide to Earning Your Technician License] (read this if you have the time)

[https://hamstudy.org/tech2014 Flashcards to Cram The Night Before] (use these if you don’t have the time)

[http://www.arrl.org/find-an-amateur-radio-license-exam-session ARRL Lookup When/Where Exams Are Held]

==Use OpenRocket==

[https://docs.google.com/a/stanford.edu/document/d/1G1YK35jDQAkZQerhjCX9vjJEk9FbQDSkZdqDFWjk5ec/edit?usp=sharing Guide to Getting Started with OpenRocket]

==Use ''LaTeX''==

[http://ricardo.ecn.wfu.edu/~cottrell/ecn297/latex_tut.pdf A Brief Introduction]

[https://tobi.oetiker.ch/lshort/lshort.pdf A Not So Short Introduction]

[https://latex-project.org/ftp.html LaTeX For Your Computer If You're So Inclined] (but really you should be using OverLeaf)

[https://wch.github.io/latexsheet/ LaTeX Reference Sheet If Your Memory Sucks] (not perfect, but good for basic things)

[https://www.sharelatex.com/learn/ Learn How To Do Pretty Much Anything You’d Like In LaTeX]

[https://en.wikibooks.org/wiki/LaTeX Learn How To Do Pretty Much Anything You’d Like In LaTeX #2]

==Convert ''LaTeX'' to Mediawiki==

[http://pandoc.org/ Pandoc] is a wonderful tool that can convert a file to a different markup format. We use it to convert rocket PDRs from ''LaTeX'' to wiki articles.

==Run CFD Simulations==

[[CFD Workflow|Learn more about SSI's CFD Workflow]]

[[Solidworks|How to install Solidworks on your computer]]

[[Pointwise | More about our (potential) sponsor]]

[[SU2 | How to install SU2 on Corn]]

[[Category:Rockets]]

PlatformIO

2017-01-07T04:36:00Z

Johnldean:

{{guide| authors=John Dean ({{slack-user|johndean}})}}

==Background==

[http://platformio.org/ PlatformIO] is an open source Integrated Development Environment (IDE) for programming microcontrollers (like arduino) and embedded systems. For our purposes, we mainly use it to write software for the [https://www.pjrc.com/store/teensy32.html Teensy 3.2 Microcontoller]. In the past, we previously had used the easy to set up [https://www.arduino.cc/en/Guide/Environment Arduino IDE], however it has many drawbacks and lacks many of the features of a full IDE.

==Instalation==

To install the PlatformIO IDE, follow the installation steps on [http://docs.platformio.org/en/latest/ide/atom.html#installation the PlatformIO website]

There are a fair number of steps to follow if you do not have any of the software that PlatformIO incorporates, but it should be fairly straightforward.

'''OS X Users:''' due to a a problem with the program that loads your compiled code to the teensy on OS X, you will need to used a custom executable file in place of the original.
''there will be more added here later''

==Usage Guide==

To get started in PlatformIO, follow the [http://docs.platformio.org/en/latest/ide/atom.html#quick-start PlatformIO Quickstart tutorial]

===Library Dependencies===

If you used the Ardiuno IDE, you will be used to having an folder on your computers where you install libraries. If you downloaded a project from the internet that needed a bunch of new libraries, you would have to install all of them manually. Thankfully, with PlatformIO, you no longer have to worry about this. Dependencies for libraries are added to the <code>platformio.ini</code> file with a github link, so that they are automatically downloaded if you do not already have them on your computer.

For information on exactly how to set it up, follow [http://docs.platformio.org/en/latest/librarymanager/index.html?highlight=libraries this guide]

PlatformIO

2017-01-07T04:34:13Z

Johnldean:

{{guide| authors=John Dean ({{slack-user|johndean}})}}

==Background==

[http://platformio.org/ PlatformIO] is an open source Integrated Development Environment (IDE) for programming microcontrollers (like arduino) and embedded systems. For our purposes, we mainly use it to write software for the [https://www.pjrc.com/store/teensy32.html Teensy 3.2 Microcontoller]. In the past, we previously had used the easy to set up [https://www.arduino.cc/en/Guide/Environment Arduino IDE], however it has many drawbacks and lacks many of the features of a full IDE.

==Instalation==

To install the PlatformIO IDE, follow the installation steps on [http://docs.platformio.org/en/latest/ide/atom.html#installation the PlatformIO website]

There are a fair number of steps to follow if you do not have any of the software that PlatformIO incorporates, but it should be fairly straightforward.

'''OSX Users:''' due to a a problem with the program that loads your compiled code to the teensy on OSX, you will need to used a custom executable file in place of the original.
''there will be more added here later''

==Usage Guide==

To get started in PlatformIO, follow the [http://docs.platformio.org/en/latest/ide/atom.html#quick-start PlatformIO Quickstart tutorial]

===Library Dependencies===

If you used the Ardiuno IDE, you will be used to having an folder on your computers where you install libraries. If you downloaded a project from the internet that needed a bunch of new libraries, you would have to install all of them manually. Thankfully, with PlatformIO, you no longer have to worry about this. Dependencies for libraries are added to the <code>platformio.ini</code> file with a github link, so that they are automatically downloaded if you do not already have them on your computer.

For information on exactly how to set it up, follow [http://docs.platformio.org/en/latest/librarymanager/index.html?highlight=libraries this guide]

PlatformIO

2017-01-07T04:33:39Z

Johnldean:

{{guide| authors=John Dean ({{slack-user|johndean}})}}

==Background==

[http://platformio.org/ PlatformIO] is an open source Integrated Development Environment (IDE) for programming microcontrollers (like arduino) and embedded systems. For our purposes, we mainly use it to write software for the [https://www.pjrc.com/store/teensy32.html Teensy 3.2 Microcontoller]. In the past, we previously had used the easy to set up [https://www.arduino.cc/en/Guide/Environment Arduino IDE], however it has many drawbacks and lacks many of the features of a full IDE.

==Instalation==

To install the PlatformIO IDE, follow the installation steps on [http://docs.platformio.org/en/latest/ide/atom.html#installation the PlatformIO website]

There are a fair number of steps to follow if you do not have any of the software that PlatformIO incorporates, but it should be fairly straightforward.

'''OSX Users:''' due to a a problem with the program that loads your compiled code to the teensy on OSX, you will need to used a custom executable file in place of the original.
''there will be more added here later''

==Usage Guide==

To get started in PlatformIO, follow the [http://docs.platformio.org/en/latest/ide/atom.html#quick-start PlatformIO Quickstart tutorial]

===Library Dependencies===

If you used the Ardiuno IDE, you will be used to having an folder on your computers where you install libraries. If you downloaded a project from the internet that needed a bunch of new libraries, you would have to install all of them manually. Thankfully, with PlatformIO, you no longer have to worry about this. Dependencies for libraries are added to the <code>platformio.ini<\code> file with a github link, so that they are automatically downloaded if you do not already have them on your computer.

For information on exactly how to set it up, follow [http://docs.platformio.org/en/latest/librarymanager/index.html?highlight=libraries this guide]

PlatformIO

2017-01-07T04:00:43Z

Johnldean:

{{guide| authors=John Dean ({{slack-user|johndean}})}}

==Background==

[http://platformio.org/ PlatformIO] is an open source Integrated Development Environment (IDE) for programming microcontrollers (like arduino) and embedded systems. For our purposes, we mainly use it to write software for the [https://www.pjrc.com/store/teensy32.html Teensy 3.2 Microcontoller]. In the past, we previously had used the easy to set up [https://www.arduino.cc/en/Guide/Environment Arduino IDE], however it has many drawbacks and lacks many of the features of a full IDE.

==Instalation==

To install the PlatformIO IDE, follow the installation steps on [http://docs.platformio.org/en/latest/ide/atom.html#installation the PlatformIO website]

There are a fair number of steps to follow if you do not have any of the software that PlatformIO incorporates, but it should be fairly straightforward.

'''OSX Users:''' due to a a problem with the program that loads your compiled code to the teensy on OSX, you will need to used a custom executable file in place of the original.
''there will be more added here later''

==Usage Guide==

===Starting a new project===

To start a new project, select <code>PlatformIO → Initialize or Update PlatformIO Project</code> from the top bar. From this menu, simple select the board that you are programming for (Usually will be Teensy 3.2), navigate to the directory that you want to generate the project in. You should create a new directory that is the name of your project, as you want nothing but the project's contents to be in the directory that you are working in.

===Project Setup===

===Library Dependencies===

If you used the Ardiuno IDE, you will be used to having an folder on your computers where you install libraries. If you downloaded a project from the internet that needed a bunch of new libraries, you would have to install all of them manually. Thankfully, with PlatformIO, you no longer have to worry about this.

PlatformIO

2017-01-07T03:51:22Z

Johnldean:

{{guide| authors=John Dean ({{slack-user|johndean}})}}

==Background==

[http://platformio.org/ PlatformIO] is an open source Integrated Development Environment (IDE) for programming microcontrollers (like arduino) and embedded systems. For our purposes, we mainly use it to write software for the [https://www.pjrc.com/store/teensy32.html Teensy 3.2 Microcontoller]. In the past, we previously had used the easy to set up [https://www.arduino.cc/en/Guide/Environment Arduino IDE], however it has many drawbacks and lacks many of the features of a full IDE.

==Instalation==

To install the PlatformIO IDE, follow the installation steps on [http://docs.platformio.org/en/latest/ide/atom.html#installation the PlatformIO website]

There are a fair number of steps to follow if you do not have any of the software that PlatformIO incorporates, but it should be fairly straightforward.

'''OSX Users:''' due to a a problem with the program that loads your compiled code to the teensy on OSX, you will need to used a custom executable file in place of the original.
''there will be more added here later''

==Usage Guide==

=Starting a new project=

To start a new project, select <code> PlatformIO → Initialize or Update PlatformIO Project </code> from the top bar. From this menu, simple select the board that you are programming for (Usually will be Teensy 3.2), navigate to the directory that you want to generate the project in. You should create a new directory that is the name of your project, as you want nothing but the project's contents to be in the directory that you are working in.

=Project Setup=

=Library Dependencies=

If you used the Ardiuno IDE, you will be used to having an folder on your computers where you install libraries. If you downloaded a project from the internet that needed a bunch of new libraries, you would have to install all of them manually. Thankfully, with PlatformIO, you no longer have to worry about this.

PlatformIO

2017-01-07T03:26:01Z

Johnldean: Created page with "{{guide| authors=John Dean ({{slack-user|johndean}})}} ==Background== [http://platformio.org/ PlatformIO] is an open source Integrated Development Environment (IDE) for prog..."

Hugh G. Mistake

2016-06-03T04:02:59Z

Johnldean: /* Chapter 1: Hugh is Born */

== Chapter 1: Hugh is Born ==

Hugh was born one lonely night in a small room in the Durand building. His mother, Ms. Mistake, was a 3D printer who dreamed of space. She was working on printing a Falcon 9 model that fateful night, concentrating especially hard on making the layers consistent so it might have a chance at an aerodynamic glide when something perturbed her circuits and her software went haywire. She didn't remember a thing from that night, but rather awoke to find, not a Falcon 9, but a tangled nest of black plastic filament. So disappointed in not having created her Falcon 9, Ms. Mistake wrote the large ball of black plastic off in disgust. She named him Hugh G. Mistake and left him to fumble in the dark.

Lonely, blind, and disoriented in this strange new universe, Hugh cried softly to himself until he was exhausted and fell asleep. He was awoken by the sound of loud voices. Clearly human, they shouted, "Oh no, we've made a HUGE MISTAKE." Recognizing his name, Hugh's ear filament perked up, and he shuffled around to face the source of the noise. Suddenly, Hugh felt large hands lifting him through space; he could feel the air rushing through him, a this vastly new and not quite pleasant experience. He was plopped down on a hard surface and second later, he felt a scorching heat on the front of his face, starting to melt him a little, even. No sooner had he begun to think about the potential damage to his nervous system, which he could feel softening, however, than he rose to new levels of shock for the morning: he could see! His mind was overloaded with sensory input: he was in a small room with bright lights, and at least 3 humans, one of whom was brandishing the source of the scorching heat: a plastic implement with a metal tip and plastic drooling from it. He could only assume this was some sort of torture or interrogation, but he had no idea what the humans wanted from him. The one with the hot gun brought it close to his face, and once again Hugh could feel his very filament beginning to melt, as another human brought a plastic eyeball near...

Hugh was about ready to give up on being surprised for the morning. He could now see out of what he realized must be two plastic googly eyes that the humans had affixed to his face. The addition of this new and exciting sense was so mind-boggling that Hugh was tempted to write it off as a realm not bounded by logic. He didn't have long to appreciate this sense, however, because, as quickly as they had come, the humans stuffed him under a table, muttering something about "Scaring the sh*t out of Elizabeth," turned off the lights, and left the room.

Hugh was once again alone.

...to be continued

[[Category: Satire]]

L2 Post-Flight Analyses

2016-04-17T21:16:43Z

Johnldean:

= Cardinal II =
== Flight Summary ==
{|class="wikitable"
|'''Date of Flight'''
|Feb. 6, 2016
|-
|'''Launch Location'''
|LUNAR
|-
|'''L2 Certification Attempt?'''
|Yes
|-
|'''Launcher'''
|Ian Gomez
|-
|'''Recovery Status'''
|Recovered
|}

== Rocket Specs ==
{|class = "wikitable"
|'''Manufacturer'''
|Giant Leap Rocketry Firestorm 54
|-
|'''Length'''
|
|-
|'''Weight'''
|
|-
|'''Motor'''
|
|-
|'''On-Board Avionics'''
|Featherweight Raven 3
|-
|'''Payload'''
|18" drogue, 36" main parachutes
|-
|}

== Analysis ==

The data from the Raven can be found on the Google Drive [https://drive.google.com/open?id=0B_7MoD64h5LoWFVfQW4wYWhaYVE here]

= JARVIS I =
== Flight Summary ==
{|class="wikitable"
|'''Date of Flight'''
|Feb. 20, 2016
|-
|'''Launch Location'''
|TCC
|-
|'''L2 Certification Attempt?'''
|Yes
|-
|'''Launcher'''
|Rebecca Wong
|-
|'''Recovery Status'''
|Recovered, minimal damage to airframe
|}

== Rocket Specs ==
{|class = "wikitable"
|'''Manufacturer'''
|Giant Leap Rocketry Firestorm 54
|-
|'''Length'''
|69"
|-
|'''Weight'''
|5.1 lbs
|-
|'''Motor'''
|Aerotech J425
|-
|'''On-Board Avionics'''
|Featherweight Raven 3
|-
|'''Payload'''
|18" drogue, 36" main parachutes
|-
|}

The rocket was configured with the drogue chute located in the aft airframe and the forward chute located in the forward airframe with the aft airframe friction fitted onto the avionics bay. The Raven was programmed to fire a charge for the drogue chute at apogee (barometric), a redundant charge at apogee + 2.5 seconds (the time determined by OpenRocket that the rocket would have fallen 100 feet), the main charge at 600 ft, and a redundant charge at 500 ft. Each charge well contained 1.5 g of Pyrodex.

== Analysis ==
JARVIS I marked the 2nd attempted rocket flight with on-board electronics for the 2015-2016 year. Flight takeoff was nominal, however, at apogee, the drogue parachute did not deploy, nor did the main chute deploy at any lower altitude. Upon recovery, it was determined that the nose cone was ejected, which helped to increase drag substantially so the rocket did not lawn dart but fell laterally instead. The Raven was operational even after recovery, and the data retrieved from the altimeter concurred with the physical evidence that all ejection chargers successfully fired. The most reasonable hypothesis for the parachute ejection failure was that the size of the ejection charges was simply undersized.

The data from the Raven can be found on the Google Drive [https://drive.google.com/open?id=0B_7MoD64h5LobGxBaVJxcU8zTUk here]

= FLAMOS I =
== Flight Summary ==
{|class="wikitable"
|'''Date of Flight'''
|Feb. 20, 2016
|-
|'''Launch Location'''
|TCC
|-
|'''L2 Certification Attempt?'''
|Yes
|-
|'''Launcher'''
|Cameron Ramos
|-
|'''Recovery Status'''
|MIA
|}

== Rocket Specs ==
{|class = "wikitable"
|'''Manufacturer'''
|Giant Leap Rocketry Firestorm 54
|-
|'''Length'''
|69"
|-
|'''Weight'''
|5.1 lbs
|-
|'''Motor'''
|Aerotech J425
|-
|'''On-Board Avionics'''
|Featherweight Raven 3
|-
|'''Payload'''
|18" drogue, 36" main parachutes
|-
|}

The rocket was configured with the drogue chute located in the aft airframe and the forward chute located in the forward airframe with the aft airframe friction fitted onto the avionics bay. The Raven was programmed to fire a charge for the drogue chute at apogee (barometric), a redundant charge at apogee + 2.5 seconds (the time determined by OpenRocket that the rocket would have fallen 100 feet), the main charge at 600 ft, and a redundant charge at 500 ft. Each charge well contained 1.5 g of Pyrodex.

== Analysis ==
FLAMOS's avionics coupler was installed upside down causing the main chute to be deployed at apogee. The rocket successfully executed two events which would have qualified the user for Level 2 certification had he been able to recover the rocket after it drifted upwards of 1 mile from the launch site. Cameron did not have a pair of binoculars handy and took his eyes off the rocket approximately 100ft before touchdown to take a bite of his pizza and thus the rocket's landing location could only be approximated to within a quarter mile square area. After approximately 45 minutes of searching for the rocket, the search party decided to give up on the recovery. In the future, all level 2 attempts should be tracked by binoculars and the recovery team should be inside a vehicle ready to begin driving towards the rocket should it start to drift. All rockets should have an audible alarm installed that activated upon liftoff.

= MERRILL LYNCH I =
== Flight Summary ==
{|class="wikitable"
|'''Date of Flight'''
|Apr. 16, 2016
|-
|'''Launch Location'''
|TCC
|-
|'''L2 Certification Attempt?'''
|Yes
|-
|'''Launcher'''
|John Dean
|-
|'''Recovery Status'''
|Successful, No Damage
|}

== Rocket Specs ==
{|class = "wikitable"
|'''Manufacturer'''
|Giant Leap Rocketry Firestorm 54
|-
|'''Length'''
|69"
|-
|'''Weight'''
|5.2 lbs
|-
|'''Motor'''
|Aerotech J270
|-
|'''On-Board Avionics'''
|Featherweight Raven 3, Buzzer
|-
|'''Recovery'''
|Duel deploy 18" drogue, 36" main parachutes
|-
|'''Payload'''
|Airframe-Mounted Camera
|}

The rocket was configured with the drogue chute located in the aft airframe and the forward chute located in the forward airframe with the aft airframe friction fitted onto the avionics bay. The Raven was programmed to fire a charge for the drogue chute at apogee (barometric), a redundant charge at apogee + 2.5 seconds (the time determined by OpenRocket that the rocket would have fallen 100 feet), the main charge at 600 ft, and a redundant charge at 500 ft. Each charge well contained 1.5 g of Pyrodex.

== Analysis ==
The flight was fairly nominal. Due to a loose friction fit of the nose cone, there was an inertial deployment of the main chute with the drogue at apogee. However, due to low win the drift of the rocket was minimal. In the future, shear pin(s) should be used for a more controlled attachment method.
[[Category:Rockets]]

Firestorm AV Bay

2016-04-05T06:20:00Z

Johnldean:

{{problems}}

{{rocket-stub}}

[[Category: Rockets]]
[[Category: Avionics]]

The Avionics Bay in a rocket provides a place to mount all electronic equipment while protecting it from any pyrotechnics used during the flight of the rocket. The most basic AV bay used by SSI is the firestorm AV bay, which is primarily used to house an altimeter for duel-deploy for an L2 certification flight. (Need to add a nice picture of an AV bay here)

=Structure=

The picture to the left shows the general structure of an AV bay. The mounting rack provide the surfaces for mounting hardware. The bulkheads (also called end caps) protect the equipment from ejection charges and provide a surface for mounting charge wells and connection points to the shock cord. The all threads clamp the AV bay together and provide the rigid elements that prevent to AV bay from being ripped apart during ejection. The coupler encapsulates the AV bay while providing a structural element to connect the two halves of the rocket's air frame.

===Bulkheads and mounting rack===

The solid works files of the AV bay, and an already made SLDDRW file for exporting the parts to be laser cut can be found here: [https://workbench.grabcad.com/workbench/projects/gc_EDWRalY4J7crz16PdmSYkSs-3GFHSB6B2Aix13CTMa8#/space/gcTokGZ9oUjQ-YkQ5yyFbxrsyW5Cwm67B_WzILmZotkSz4 GrabCad Files]

The bulkheads and mounting racks are typically made of laser cut duron. This is for easy of manufacturing, low cost, strength, and resistance to cracking. Each bulkhead consists of an inner and an outer piece to ensure that so that the securely fit into the coupler. The inner and outer pieces for each bulkhead are epoxied together, as shown in the images to the left. The pegs of the mounting rack fit into the slots on the inner bulkhead. On one side, the bulkhead should be epoxied to the bulkhead (this is typically the end of the AV that is facing the ground when it is mounted in the rocket). Also attached to each bulkhead is a an eye bolt, for attaching to the shock cord on either side, and a charge well. Two more holes should be drilled through each bulkhead for igniter wires to be routed through.

'''NOTE:''' Completely assemble the structural components of the of the AV bay, with the mounting rack, bulkheads, and coupler put clamped together, and all of the holes on the bulkheads lined up ''before'' epoxying anything, to make sure that every piece is oreiented correctly, then disassemble and epoxy. This is easier than you might think to mess up.

===Coupler and All threads===

=Mounting Avionics=

'''NOTE:''' The specific electronics used in an AV bay often differ, so there is no single best way to mount everything. Before drilling holes or permanently attaching anything, lay out all of the components and make sure that you have enough room. '''Remember that there are all threads running on each side of the mounting rack, so make sure there is space for them when mounting electronics.''' Also, remember that wires are actually a thing, so plan space for them. Think about how you will close up the AV bay with wires attached to the top and bottom bulk head. ''Think everything through before mounting stuff.''

===Altimeter===

While each type of Altimeter are mounted slightly differently, they should all be mounted with screws and spacers, or standoffs. To get the correct hole pattern on the mounting rack, place the altimeter on the mounting rack in the correct position, mark where the screw holes in the altimeter PCB are, and drill them out. The holes should be sized such that the screws you are using can thread into the duron. Make sure that you use spacers, as shown in the diagram, between the altimeter and the mounting rack. Otherwise, the barometer may be pressed against the duron and not take accurate readings.

===Batteries===

Mounting the 9 volt batteries is relatively simple. Use snap on connectors to connect wires to the batteries. Both batteries are typically mounted on the same side. Use double sided foam type or PCB mounting tape to attach the battery to the mounting rack, then clamp the batteries in place using zip ties that run through the horizontal slots in the mounting racks.

===Pin Switch===

The pin switch is used to keep all avionics in the rocket powered down until the rocket is on the pad an ready for launch.

Firestorm AV Bay

2016-04-05T06:19:43Z

Johnldean:

Firestorm AV Bay

2016-04-05T06:16:38Z

Johnldean:

Launch Day

2016-04-02T01:43:03Z

Johnldean: /* Rocket Fuel */

= Who You Will Meet =

== Range Safety Officer (RSO) ==

The RSO is responsible for pre-flight inspection and approval of hobby rocket vehicles within a specified motor impulse range. They give the final word on whether your rocket will launch. Jump to [[#Range Safety Check | Range Safety Check ]] to read about what you need to prepare for inspection or read this document [https://www.nar.org/wp-content/uploads/2014/05/RSO-Operations-Manual-Blue-Mtn-Rktrs.pdf] if you're interested in the nuts and bolts of what an RSO does.

== Launch Control Officer (LCO) ==

The LCO is responsible for control of the range and the actual launching of the rocket vehicles themselves.

= What You Need To Bring =

== Rocket Fuel ==
Note: these lists have two columns.

<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
*Ziploc bags to store the things below in.
*Epoxy
*Tools to apply epoxy (i.e. popsicle sticks and paper plates)
*Power Drill and Impact Driver
*Correct drill bits and heads
*Dremel
*Igniters
*Bolts (what kind?)
*Screwdrivers
*Adjustable spanner
*Masking and duct tape
*Sandpaper (120 grit)
*Measuring tape
*Calipers
*Paper Towels
*Plastic bags
*Clamps
*Scale
*Gloves
*Trash bags
*Rockets
*Motors
*Spare rocket components
</div>
If doing L2 also bring these things along:
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
*Wire strippers
*Wire
*Small needlenose pliers
*Pyrodex
*Centrifuge tubes
*Extra igniters and ematches
*Soldering iron
*Power supply
*Rosin solder
*Altimeters
*Altimeter USB cables
*Batteries
*Battery connectors
*Multimeter
*Precision Screwdriver
*Laptops with altimeter programming software
*Ziptie gun & zipties
</div>

== People Fuel ==

[[File:TCCRebeccasLaunch.jpg|thumb|right|300px|Rebecca Wong at a November launch at TCC]]

*Cases of water
*Cooler for drinks
*Snacks (bring your own food)
*Cash for launch fees and purchasing miscellaneous parts
*Nice cameras
*Inverters and power strips for power from car
*Sharpies and pens
*Pre-filled out documentation
*First aid kits
*Tent
*Chairs
*Folding tables
*Trash bags
*Table cloth

== Appropriate Clothing ==

These requirements obviously change per season, but the running theme is that you will be exposed to the elements all day.
*Sunglasses
*Hats
*Scarves
*Pants
*Walking boots or sneakers
*Rain boots (for walking in muddy farmland)
*Jacket

= Vendors =

[http://bayarearocketry.com/ Bay Area Rocketry] is a local supplier of rocket parts and motors, and will often travel to launches, allowing us to pick up our motors at the site. Since SSI does not store motors on campus, this is a very nice perk.

[https://www.apogeerockets.com/ Apogee Rockets] is a website selling everything from guides to motors to fiberglass tubing, and are a very good starting point for any rocket-related parts.

[https://giantleaprocketry.com/ Giant Leap Rocketry] has a large selection of components, and tends to stock parts for larger rockets. They also sell the Firestorm 54 kit, which we have used extensively.

[https://www.publicmissiles.com Public Missiles] sells very large components - think rockets with diameters >6in.

= Range Layout =

Depending on which launch site you go to, this will be different. However, there are some basic themes.

The main areas of a launching range are the launch pad and control tent, and the parking area. Most high powered rocketry ranges have at least one launch pad that is set up 100ft away from the control tent, a distance specified by the NFPA, section 1127, as the "Minimum Personnel Distance" for any non-complex motor under 1,280 Ns (J motor). However, quite a few ranges also have a second pad, 300ft away, to be able to launch an L motor rocket, or any complex motor combinations up to J motors.

The control tent is where you check in your rocket with the RSO, and get your pad assignment from the LCO. This is also where you can take your L2 exam, if you have not done so already, and also where you bring your rocket back to get your certification.

[[File:Snow_Ranch_Launch_Site.jpg|thumb|frame|center|1000px|Snow Ranch launch site (LUNAR)]]

[[File:Del_Norte_Launch_Site.jpg|thumb|frame|center|1000px|Del Norte launch site (TCC)]]

= Packing Your Parachute =

When packing your parachute it should not fit too tightly within your airframe. You can test this yourself by giving a quick pull on the shock cord attached to the parachute. For the L1s, and most of the L2s, the parachutes are small enough that you should be able to have the entire parachute pop out of the airframe by doing this. If you find yourself having trouble either inserting your parachute into your airframe, removing it, or simply have no idea where to start there are a couple of styles of folding that may help.

'''''Half Fold:''''' This style is recommended if you have a relatively skinny airframe and are not concerned about airframe space.

'''''Triple Fold:''''' This style of folding results in a slightly thicker packed 'chute but it has a shorter length than the half fold.

Diagrams*

Here is a video.*

Some other techniques you may want to try:
*folding your lines in with your 'chute rather than wrapping them around the 'chute
*taping the folded lines with a bit of masking tape to act as a way of creating a "slider" to help slow the opening of the parachute. This essentially creates a faux dual deploy to help reduce recovery drift.

Don't forget to wrap the bottom end of your parachute in a heat resistant cloth like Nomex or Kevlar to prevent the ejection charge from burning holes into your parachute.

Re-do the parachute tied to the screw on metal loop 12 inches below the nose cone. Unscrew the loop, remove the cords and loop the parachute in a simple knot around the loop by passing the parachute through the loops of the cord lines.

Lay the parachute on the ground and arrange it so where all the cords come off the parachute are in the same spot. Accordian fold the parachute like a shirt. It should end with a width of about the diameter of the rocket.

Make a z-fold the long way on the parachute, if it looks like it will be too long for the chute protector, make 2 or 3 z-folds. Lay the cord lines along the chute the long ways and then fold the chute over once along the line of the cords. The cords should not go down the entire way, pull them out through the fold about half an inch from the bottom. Now wrap the cord lines around the chute, taking care to not cross the lines with each other.

Once that is done, take the chute protector and burrito wrap it around the chute. Make sure the slit that the shock cord goes through is at the spot furthest away from where the fire will be.

Fire + Parachute = Very Bad

The parachute+kevlar should act as a plug in the airframe. If the motor ejection does not push the parachute and kevlar out of the airframe, the pressure will push the nose cone out, which will pull the parachute and kevlar out. Both cases are fine.

This folding technique is courtesy of Stue, who learned it from a guy that makes parachutes for the military. We will assume that if it is good enough for the military, it is good enough for us.

Shock cord should be 5 body lengths, rather than 3 body lengths.

= Prepping Your Motor =

If using a single use motor or Disposable Motor System, make sure to check that the delay on the ejection charge is correct using a simulation software (i.e. OpenRocket). If needed adjust the length of the delay grain. Then place the correct quantity of ejection propellant in the correct location. Cap it.

Here is a great video to watch.

= Filling Out Your Flight Card =

You must fill out a flight card before launching any rockets on launch day. You must know and indicate:

[[File:NARLaunchCard.png|thumb|right|200px|NAR Flight Card]]

*Your name
*Model's name as well as whether it is a kit, plan, or original
*What type of recovery is on-board (i.e. parachute, helicopter, streamer, etc.)
*How many stages and engines are on-board
*What the payload is
*What type of rod is needed
*The motor specs: manufacturer, type, impulse, how many, total impulse if multiple

= Range Safety Check =

Before you get cleared for launch, the RSO will inspect your rocket structures, motor certification, and dynamic properties. You should be prepared to answer any and all questions the RSO may have about your rocket. Remember -- the RSO has the final say on whether your rocket gets to launch or not, so it is in your best interest to prepare beforehand all the necessary paperwork, calculations, safety procedures, and proper assembly and convince the RSO you know what you are doing and your launch is unlikely to fail. A full documentation of what the RSO does (or doesn't) do can be found under [[#Range Safety Officer | Range Safety Officer]].

== Administrative ==
*'''Is the flier over 18 years of age?''' If you are not over 18, you legally cannot launch mid or high power rockets. Sorry.

*'''Is the flier certified to the power level being flown?''' Not really an issue for L1's since you have no certification (yet) and will not be attempting to use any motors that require a certification, but if you are flying a motor that requires a high power certification later on, you '''must bring your NAR/TRA membership card''' indicating your current membership and certification level.

*'''Will the flight of the model rocket vehicle “bust” the launch site's FAA waiver?''' This is very important. You must be able to anticipate the altitude your rocket will fly to and be prepared to show simulation data if asked for it. For a single motor, you may be denied a launch if you expect to reach within 15% of the waiver height (15,000' for LUNAR and 16,800' for TCC). This won't be an issue for L1's, but you will certainly be asked what your rocket's expected apogee is, and you better be prepared to answer with an accurate model to back your number.

*'''Will the rocket penetrate cloud cover?''' In accordance with Federal Aviation Regulations (FAR) (the FAA regulations pertaining to who can or can't use airspace), high power rockets cannot be launched into cloud cover greater than 50% or visibility less than 5 miles.

== Motors ==

*'''Is the motor certified?''' NAR, TRA, and NFPA Safety Codes require that only certified motors be used. Motors are certified by undergoing testing as set forth by the NFPA. TRA and NAR have a reciprocity agreement so that motors that are certified with one organization are upheld by the other. Main takeaway: make sure your motor is certified (it will be) and would be good to know which organization did the certification [http://www.thrustcurve.org/searchpage.jsp (easily looked up online)].

*'''What is the motor type, average thrust, and rocket weight? Is the delay time approximate for rocket?''' Motors may be single-use or reloadable, and can be solid, liquid, or hybrids. SSI currently only uses solid motors. Your L1 motor will likely be a single-use motor as these are less prone to errors in assembly that can occur with reloadable casings. The rule of thumb regarding motor selection is a 5-to-1 thrust-to-weight ratio. The motor delay should be set appropriately for the rocket configuration and weather conditions. Motors with longer delays have lower weight recommendations so be sure to run simulations and have a good idea of what delay you need on launch day.

*'''Is the igniter a low-current igniter?''' '''''DO NOT USE LOW-CURRENT IGNITERS FOR YOUR MOTOR IGNITION.''''' I repeat. '''''DO NOT USE LOW-CURRENT IGNITERS FOR YOUR MOTOR IGNITION.''''' Low-current igniters, as their name suggest, ignite with very little current -- so little in fact that the continuity test can set them off. This means that if you do not follow this ''very important warning'', you could end up in a situation where you put your rocket on the rails, connect up the leads, go to press the button for continuity and '''''BAMMMMM''''' YOUR ROCKET GOES FLYING OFF IN FRONT OF YOUR FACE. '''''DO NOT USE LOW-CURRENT IGNITERS FOR YOUR MOTOR IGNITION''''' AKA '''NO Electric Matches'''. E-matches are ok for ejection charges in avionics bays (for L2s+), but they should '''NOT''' be used for motor ignition.

*'''Does your rocket motor have the ejection charge installed?''' This involves pouring a small amount of ejection charge into the top of your motor and putting a cap on it. Do not forget to do this. People have forgotten before (apparently) so don't let that be you, otherwise you'll find your rocket will go up quickly, and then proceed to come down ''very'' quickly. And dangerously. And you won't get certified. So don't forget.

*'''Is sufficient wadding/Kevlar installed?''' Wadding, sometimes referred to as dog barf, is fire-retardant, blown-cellulose insulation (used in home insulation) that protects your rocket/shock cord/parachute protector from getting blown to smithereens by your ejection charge. The Kevlar pads in the Firestorm kits serve an equivalent purpose of protector your parachutes from getting fried. Be sure the Kevlar pad fully wraps around the area of your parachute that is facing the ejection charge. Use your head on this one -- what good is a Kevlar covering, if it isn't covering the part of your parachute that is going to get blasted with BP/Pyrodex?

*'''What kind of motor retention system is installed?''' Motors can be retained with either a friction fit (not recommended) or a positive retention system such as motor clips or retaining rings (what you'll be using for Firestorms). Examine the motor retainer and retaining rings carefully and make sure the smaller ring is sitting inside the groove of the retainer, not just pressed into the retainer anywhere. Give your motor a good pull (the RSO may do this also) and make sure the motor cannot fall out in anyway.

*'''What prevents the motor from flying-through the rocket?''' Give your motor a good push (the RSO may do this also) and make sure neither the motor nor the motor tube move inside the airframe.

== Rocket Construction & Inspection==

*'''Is the rocket stable? Is the CG in front of the CP? Be able to identify both.''' You can find the CG of the rocket with the motor installed by finding its balancing point. Mark this point on the outside of your rocket. Use a simulation program to determine where your CP is and mark this on the outside also. The CG must be at least 1 caliber in front of the CP.

*'''Is the nose cone fitted correctly?''' Check the fit of your nose cone by yourself first. Does the nose cone separate from the rocket under its own weight? It shouldn't. Add a little bit of tape around the shoulder. The right fit is such that the nose cone will not detach if you simply pick up your rocket by the nose cone, but not so tight that you need to exert excessive effort to remove it. A few strong shakes should do the trick. Also check that paint is not inside the body tube or on the shoulder, which can cause the issues with sliding the nose cone off -- sand things down carefully as needed.

*'''Launch lugs and/or rail guides properly installed, positioned, and aligned?''' Verify your rail guides are attached securely and are in good condition (no cracks, deformations, etc). Check for any paint build up that could interfere with the launch rails -- sand as needed.

*'''Are the fins in good condition and mounted parallel to the roll axis?''' Verify you epoxied your fins on straight. Wiggle the fins at the tip. Do your fins move or flex a lot? They shouldn't. Examine the fins for any cracks or warpage.

*'''Is an appropriately-sized recovery system installed and attached?''' Verify that your shock cord is not frayed, burnt, or cut and that all knots are secure and will not slip out. Pull on the shock cord several times to check it is secured to your airframe properly. Check all your quick links and any other hardware are tightened completely and will not separate under load. Check that your parachute is in good condition and is not loose, burnt, or cut. Double check your Kevlar wrapping.

*'''Are there vent holes?''' Vent holes are used to vent the rocket's internal pressure and avoid premature separation. You should have two vent holes, one in the aft section of your rocket and one in the forward, near the nose cone.

== Launch Pad Procedure ==

The rocket should slide freely on the rail. The pad angle should be within 20 degrees of the vertical axis (normal to the surface of the earth). Flight critical electronics (if there are any) should be armed before putting in igniters. Any radio control equipment should also be nominally operating before arming the igniters.

== How to install an igniter ==

Place in the nozzle of rocket, and tape the igniter to the rocket so it does not slide out. '''Make sure not to short the leads of the igniters. '''

Here is a great video to watch.

= Checklist of What to Know =

'''If you do not know the answer to any part of this, look it up. Either in the above sections, or on the internet.'''

- How to answer questions about the bolts attaching the coupler

- How high will your rocket go? Use your own measurements of the rocket and plug them into openRocket. Don't use other peoples calculations.

- How fast will your rocket go? Same as above.

- Where is your CP?

- Where is the CG?

- How fast the rocket is going off the launch pad?

- Model of motor?

- Impulse of motor?

- Thrust of motor?

- Burn time of motor?

- Stability margin?

- What epoxy was used in construction? Ans - 30 min epoxy for the tube fins and JB Weld for hardpoint and motor retainer.

= Quick G Calculation =

Quick way to calculate g’s on liftoff:
Take the average thrust of motor in N, divide by 5 to get lbs, divide by the weight of your rocket, you want to aim for around 5 - 6 g’s.

The H550 motor puts us at an initial launch acceleration of 30g’s, approximately 90 ft/s off the launch rod, so anything inside the tube will shake uncontrollably and possibly break. It will also cause the parachutes and other stuff in the rocket to be shoved down the tube. Be careful about how you attach the coupler as screws can catch the parachute and make it fail. Ask Ian on how to explain this to the safety officer!

=Final Check!=
Are you ready to launch? Run through this quick checklist!

==L1==
*Is your parachute packed correctly? Kevlar wrapped around? Is it attached to your rocket?
*Is your airframe bolted together nice and tight?
*Did you buy the correct motor? (H or I Motor - MUST BE 38mm)
*Did you pack in black powder for motor delay ejections? Check the delay time.
*Does your nose cone slide off with vigorous vertical shaking (with the motor assembled)
*Is there any epoxy that has not dried? (Wait if there is)
*Is your certification form and flight card filled out with rocket info? Do you know your NAR/TRA membership #?
*Did you pay your launch fee?
*Are your rail guides properly mounted on your rocket?
*Is there a pressure ventilation hole so your recovery system doesn't prematurely deploy?

==L2==
In addition to the last 6 items listed under the L1 check,

*Are your parachutes correctly packed and attached to the avionics bay (and nose cone)?
*Did you buy the correct motor? (J or K -- if you're not using motor ejection, don't fill with black powder)
*Are all electronics functioning? Fresh batteries? Easy switch access?
*If using a barometric-based altimeter, have you drilled a pressure-access hole for it?
*Have you loaded up your charge wells?
*Have you checked the position and attachment of your igniters?
*'''Are your apogee and main charges facing the correct direction?'''

All good? Great! Get a photo of you and your rocket on the launch pad and good luck!

[[Category:Rockets]]

Firestorm AV Bay

2016-03-31T21:23:51Z

Johnldean:

{{rocket-stub}}

[[Category: Rockets]]
[[Category: Avionics]]

The Avionics Bay in a rocket provides a place to mount all electronic equipment while protecting it from any pyrotechnics used during the flight of the rocket. The most basic AV bay used by SSI is the firestorm AV bay, which is primarily used to house an altimeter for duel-deploy for an L2 certification flight. (Need to add a nice picture of an AV bay here)

=Structure=

The picture to the left shows the general structure of an AV bay. The mounting rack provide the surfaces for mounting hardware. The bulkheads (also called end caps) protect the equipment from ejection charges and provide a surface for mounting charge wells and connection points to the shock cord. The all threads clamp the AV bay together and provide the rigid elements that prevent to AV bay from being ripped apart during ejection. The coupler encapsulates the AV bay while providing a structural element to connect the two halves of the rocket's air frame.

===Bulkheads and mounting rack===

The solid works files of the AV bay, and an already made SLDDRW file for exporting the parts to be laser cut can be found here: [https://workbench.grabcad.com/workbench/projects/gc_EDWRalY4J7crz16PdmSYkSs-3GFHSB6B2Aix13CTMa8#/space/gcTokGZ9oUjQ-YkQ5yyFbxrsyW5Cwm67B_WzILmZotkSz4 GrabCad Files]

The bulkheads and mounting racks are typically made of laser cut duron. This is for easy of manufacturing, low cost, strength, and resistance to cracking. Each bulkhead consists of an inner and an outer piece to ensure that so that the securely fit into the coupler. The inner and outer pieces for each bulkhead are epoxied together, as shown in the images to the left. The pegs of the mounting rack fit into the slots on the inner bulkhead. On one side, the bulkhead should be epoxied to the bulkhead (this is typically the end of the AV that is facing the ground when it is mounted in the rocket). Also attached to each bulkhead is a an eye bolt, for attaching to the shock cord on either side, and a charge well. Two more holes should be drilled through each bulkhead for igniter wires to be routed through.

'''NOTE:''' Completely assemble the structural components of the of the AV bay, with the mounting rack, bulkheads, and coupler put clamped together, and all of the holes on the bulkheads lined up ''before'' epoxying anything, to make sure that every piece is oreiented correctly, then disassemble and epoxy. This is easier than you might think to mess up.

===Couple and All threads===

=Mounting Avionics=

'''NOTE:''' The specific electronics used in an AV bay often differ, so there is no single best way to mount everything. Before drilling holes or permanently attaching anything, lay out all of the components and make sure that you have enough room. '''Remember that there are all threads running on each side of the mounting rack, so make sure there is space for them when mounting electronics.''' Also, remember that wires are actually a thing, so plan space for them. Think about how you will close up the AV bay with wires attached to the top and bottom bulk head. ''Think everything through before mounting stuff.''

===Altimeter===

While each type of Altemeter are mounted slightly differently, they should all be mounted with screws and spaces, or standoffs. Place the altimeter on the mounting rack where it will be mounted, and mark where the

===Batteries===

===Pin Switch===

Firestorm AV Bay

2016-03-31T21:08:28Z

Johnldean:

Firestorm AV Bay

2016-03-31T20:59:58Z

Johnldean: /* Structure */

Firestorm AV Bay

2016-03-29T19:25:03Z

Johnldean:

Firestorm AV Bay

2016-03-29T19:24:43Z

Johnldean:

Firestorm AV Bay

2016-03-29T19:12:19Z

Johnldean:

Firestorm AV Bay

2016-03-29T18:50:56Z

Johnldean:

How to Join Rockets

2016-03-28T00:58:51Z

Johnldean:

{{rocket-sidebar}}

[[File: CardinalIILaunch.jpg | right| 250px | thumb | Cardinal II lifting off the pad on a J class motor.]]

Welcome to rockets! This page is intended to lay out the organization of the group, and let everyone know exactly what they need to do to get started! First of all, the current rockets co-leads are Christopher May and Ian Gomez - let us know if you have any questions about the group or about what you are supposed to do.

SSI tries to introduce new members to High Power Rocketry by guiding them through building a simple rocket, flying it, and earning a Level 1 certification. While not all members have to go through this, it will introduce you to designing, analyzing, building, and then flying a rocket (and you will go to a launch, which are always fun).

The main rockets page has a lot of information about High Power Rocketry, as well as how we approach it. Reading through the page before attending a meeting is recommended, but certainly not required. This one focuses more on what you have to do to join, which is less about rockets and more about logistics.

= Basic Info =

== Meetings ==

The Rockets Team has general meetings every week; during Spring Quarter of 2015-2016, these meetings are held on Thursdays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as work sessions where all of the Rockets Team members are in the same place at once.

Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.

'''If you cannot make a project meeting, let your project lead know ahead of time.'''

== Previous Knowledge ==

We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.

Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:

<ul>
<li><blockquote>Heat Transfer</blockquote></li>
<li><blockquote>Thermodynamics</blockquote></li>
<li><blockquote>Fluid Mechanics (incompressible and compressible flow)</blockquote></li>
<li><blockquote>Physics</blockquote></li>
<li><blockquote>Material Sciences</blockquote></li>
<li><blockquote>Statics and Dynamics</blockquote></li>
<li><blockquote>Controls</blockquote></li>
<li><blockquote>Circuits</blockquote></li>
<li><blockquote>Amatuer Radio</blockquote></li>
<li><blockquote>Manufacturing</blockquote></li></ul>

Introductions to many of these are available on [[So You Want To...]]

== Safety Training ==

In order to get access to MC (our room), all members must have completed basic safety training. INSERT DETAILS HERE, IM GOING TO DINNER.

== Time Commitment ==

Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. Building a basic L1 and L2 rocket should not require more than 10 hours combined if done correctly (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.

== Budget ==

Rockets has [https://docs.google.com/spreadsheets/d/11LfZaV59FnFJyt4DnnCq2Vj7DgzM_2XfgwEPw27zTdI/edit#gid=0 ''a running budget''] in the Drive (Stanford Student Space Initiative > Teams > Rockets). Please add your purchases to the correct tab so we can have a running tally of what we’re spending.

== TRA and NAR ==

[http://www.tripoli.org/ ''Tripoli Rocketry Association (TRA)''] and [http://www.nar.org/ ''National Association of Rocketry (NAR)''] are the two major organizations that organize launches, certify members, and maintain specific standards that govern high power rocketry.

In order to launch high power rockets, you are required to be a member of either organization ([http://www.tripoli.org/Membership ''Tripoli Membership''] / [http://www.nar.org/join-nar/ ''NAR Membership''])

The closest Tripoli launch site to Stanford is [http://www.tccrockets.com/ ''Tripoli Central CA''] (near Fresno) and the closest NAR launch site is [http://www.lunar.org/ ''LUNAR''] (somewhat near Stockton). TCC holds HPR launches (max height 16,800’) on the 3rd Saturday of each month. LUNAR holds HPR launches (max height of 15,000’) on the 1st Saturday of each month in addition to low power launches (max height of 1000’) on the 3rd Saturday of each month at Moffett Field.

== Launches ==

Here is the launch procedure as lifted from the [https://docs.google.com/document/d/1ItllblKqc9oATIYz2Mf4VrZK0Fh1h3ohmwlDXR33KQM/edit ''Operating Principles and Risk Management''] document.

Once the team arrives at the launch site, the rules and regulations of the governing body sponsoring the launch will take precedence. Although procedure is likely to vary from site to site, the launch procedure usually occurs in this order:

<ol style="list-style-type: decimal;">
<li><blockquote>Those attempting to fly a rocket approach the Range Safety Officer (RSO) and officers in charge of the launch, sign in (with their member numbers) and usually pay a launch fee. If the flyer is attempting to get a certification, they will fill out relevant forms to declare their intention (these and other useful documentation pertaining to both national rocketry associations are included in the Appendix).</blockquote></li>
<li><blockquote>Depending on the skill level of the flyer, there are two variations of what may occur.</blockquote>
<ol style="list-style-type: lower-alpha;">
<li><blockquote>In the non-certification flight case, the RSO will inspect the rocket and send the flyer to set up the rocket on the launch pad. This requires placing the rocket on the launch rails, placing the igniter in the motor, and checking the launch pad electronics for errors before returning to a safe distance from the launch pad.</blockquote></li>
<li><blockquote>In the case of a certification, the RSO and someone above the flyer’s certification level will inspect the rocket and send the flyer (and another more experienced member) to set up the rocket for launch. The same setup process occurs as stated above.</blockquote></li></ol>
</li>
<li><blockquote>After the range has been cleared of spectators/flyers, the RSO announces each rocket and launches them one at a time (unless otherwise specified; an example of an exception is a drag race between two rockets).</blockquote></li>
<li><blockquote>Once the range is cleared of rockets, flyers recover their rockets.</blockquote></li>
<li><blockquote>If the flight is not a certification, the procedure ends here. Otherwise, the flyer shows his or her rocket to the RSO and has them sign off on the flyer’s paperwork if the flight is successful. The paperwork is then sent off to the headquarters of the organization and processed.</blockquote></li></ol>

== Rocket Naming Conventions ==

For mass certs:

SSI-R# will be the designation for general rocket launches (blanket certification launches).

Your rocket’s name can be whatever you would like it to be. Examples in the past are: ''Cardinal I'', ''Flamos'', ''Chris May'', etc.

For Daedalus:

SSI-[Level][three letter code denoting name][Launch number] ex. SSI-L3TAL1. These will not affect the number of SSI-R launches. They will have separate counts. The launch number will be useful if the same rocket goes flying again (which should be plausible if you don't mash it).

If the rocket is Class 3, no Level number is required.

== Rockets Leadership ==

The logistics required to run a fully operational Rockets team can be too much for just two co-leads to handle. The Rockets Leadership is a group of people who care about organizing the logistics behind launches and projects that the team is working on. If you show that you care and put in an exceptional amount of effort into your project, you can choose to be a part of this group.

[https://docs.google.com/a/stanford.edu/document/d/1-J5TS0MRgHi0HFTyPhYzzF6VZBa3dqO-WpxrCLgJIpQ/edit?usp=sharing ''Here is a document with all the roles on Rockets Leadership.'']

= Resources =

Other members are one of your best resources if you have any questions about rocketry. Other fantastic resources are laid out below.

== Rockets Drive ==

There are tons of useful things in the Rockets folder!!!!! Here are descriptions of a few of those folders.

=== [http://wiki.stanfordssi.org/Stanford_Student_Space_Initiative_(SSI) ''Wiki''] ===

Go here first for finding useful data on L1 certification procedures! You should add as much to the wiki as possible.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVUFUcEpWRGt2M00 ''Archive''] ===

This holds all the older Rockets plans/documents/etc. Usually these documents are not particularly useful (which is why they are in the archive).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgU3Rsbi1KOFpuSzA ''Daedalus''] ===

This holds all the information for Daedalus, like team folders, L3 requirements, and PDRs & CDRs. Snoop around to see what they’ve done so far and steal information for your project (citing is always a good idea when you do take information).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVkdjcGQtWTNsZU0 ''Getting Nerdy: Textbooks and Manuals''] ===

This folder holds a collection of useful texts ranging from textbooks, manuals, NASA articles and technical reports. If you need to learn things, [https://docs.google.com/a/stanford.edu/document/d/18PSjKqlVLTQzfJLG7ggiWY61W3ZcaD9kCcEePinAJw0/edit?usp=drive_web ''check out this document''].

=== [https://drive.google.com/open?id=0ByRlIAW5-8GqcUcyckNmZlFfN1U ''Launch Documentation''] ===

This holds all the launch documentation for upcoming launches and things like build slot signups, ride signups, rocket building instructions, required reading, pre-flight checklists, etc. Read through this folder and you’ll have a pretty damn good idea of launch logistics.

=== [https://drive.google.com/open?id=0B-5MRX1wVAAdNXQxUzdNVGNRRWc ''Rockets Operating Principles''] ===

This folder houses all of the operating principles, risk mitigation planning, and miscellaneous safety codes, documentation, and literally anything Stanford’s lawyers could possibly want from us. If you read the document you will have a very good understanding of how the team operates on an administrative level.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgdXo4YVJEV1duRlU ''The Design Process''] ===

This folder houses all you need to know to design, fabricate and launch a rocket from a documentation standpoint. Read it.

== [https://ssi-teams.slack.com/ ''Slack''] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like #rockets), which allow us to push out general updates to everyone interested in the rockets team and direct messages in order to communicate with one person - although Slack has recently added a group messaging feature if you don’t want to make an entire channel for a 4 person chat - at a time. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']

== Mission Control ==

Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).

<noinclude>[[Category:Rockets]]</noinclude>

How to Join Rockets

2016-03-28T00:58:34Z

Johnldean:

{{rocket-sidebar}}

[[File: CardinalIILaunch.jpg | right| 250px | thumb | Cardinal II lifting off the pad on a J class motor.]]

Welcome to rockets! This page is intended to lay out the organization of the group, and let everyone know exactly what they need to do to get started! First of all, the current rockets co-leads are Christopher May and Ian Gomez - let us know if you have any questions about the group or about what you are supposed to do.

SSI tries to introduce new members to High Power Rocketry by guiding them through building a simple rocket, flying it, and earning a Level 1 certification. While not all members have to go through this, it will introduce you to designing, analyzing, building, and then flying a rocket (and you will go to a launch, which are always fun).

The main rockets page has a lot of information about High Power Rocketry, as well as how we approach it. Reading through the page before attending a meeting is recommended, but certainly not required. This one focuses more on what you have to do to join, which is less about rockets and more about logistics.

= Basic Info =

== Meetings ==

The Rockets Team has general meetings every week; during Spring Quarter of 2015-2016, these meetings are held on Thursdays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as work sessions where all of the Rockets Team members are in the same place at once.

Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.

'''If you cannot make a project meeting, let your project lead know ahead of time.'''

== Previous Knowledge ==

We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.

Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:

<ul>
<li><blockquote>Heat Transfer</blockquote></li>
<li><blockquote>Thermodynamics</blockquote></li>
<li><blockquote>Fluid Mechanics (incompressible and compressible flow)</blockquote></li>
<li><blockquote>Physics</blockquote></li>
<li><blockquote>Material Sciences</blockquote></li>
<li><blockquote>Statics and Dynamics</blockquote></li>
<li><blockquote>Controls</blockquote></li>
<li><blockquote>Circuits</blockquote></li>
<li><blockquote>Amatuer Radio</blockquote></li>
<li><blockquote>Manufacturing</blockquote></li></ul>

Introductions to many of these are available on [[So You Want To...]]

== Safety ==

In order to get access to MC (our room), all members must have completed basic safety training. INSERT DETAILS HERE, IM GOING TO DINNER.

== Time Commitment ==

Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. Building a basic L1 and L2 rocket should not require more than 10 hours combined if done correctly (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.

== Budget ==

Rockets has [https://docs.google.com/spreadsheets/d/11LfZaV59FnFJyt4DnnCq2Vj7DgzM_2XfgwEPw27zTdI/edit#gid=0 ''a running budget''] in the Drive (Stanford Student Space Initiative > Teams > Rockets). Please add your purchases to the correct tab so we can have a running tally of what we’re spending.

== TRA and NAR ==

[http://www.tripoli.org/ ''Tripoli Rocketry Association (TRA)''] and [http://www.nar.org/ ''National Association of Rocketry (NAR)''] are the two major organizations that organize launches, certify members, and maintain specific standards that govern high power rocketry.

In order to launch high power rockets, you are required to be a member of either organization ([http://www.tripoli.org/Membership ''Tripoli Membership''] / [http://www.nar.org/join-nar/ ''NAR Membership''])

The closest Tripoli launch site to Stanford is [http://www.tccrockets.com/ ''Tripoli Central CA''] (near Fresno) and the closest NAR launch site is [http://www.lunar.org/ ''LUNAR''] (somewhat near Stockton). TCC holds HPR launches (max height 16,800’) on the 3rd Saturday of each month. LUNAR holds HPR launches (max height of 15,000’) on the 1st Saturday of each month in addition to low power launches (max height of 1000’) on the 3rd Saturday of each month at Moffett Field.

== Launches ==

Here is the launch procedure as lifted from the [https://docs.google.com/document/d/1ItllblKqc9oATIYz2Mf4VrZK0Fh1h3ohmwlDXR33KQM/edit ''Operating Principles and Risk Management''] document.

Once the team arrives at the launch site, the rules and regulations of the governing body sponsoring the launch will take precedence. Although procedure is likely to vary from site to site, the launch procedure usually occurs in this order:

<ol style="list-style-type: decimal;">
<li><blockquote>Those attempting to fly a rocket approach the Range Safety Officer (RSO) and officers in charge of the launch, sign in (with their member numbers) and usually pay a launch fee. If the flyer is attempting to get a certification, they will fill out relevant forms to declare their intention (these and other useful documentation pertaining to both national rocketry associations are included in the Appendix).</blockquote></li>
<li><blockquote>Depending on the skill level of the flyer, there are two variations of what may occur.</blockquote>
<ol style="list-style-type: lower-alpha;">
<li><blockquote>In the non-certification flight case, the RSO will inspect the rocket and send the flyer to set up the rocket on the launch pad. This requires placing the rocket on the launch rails, placing the igniter in the motor, and checking the launch pad electronics for errors before returning to a safe distance from the launch pad.</blockquote></li>
<li><blockquote>In the case of a certification, the RSO and someone above the flyer’s certification level will inspect the rocket and send the flyer (and another more experienced member) to set up the rocket for launch. The same setup process occurs as stated above.</blockquote></li></ol>
</li>
<li><blockquote>After the range has been cleared of spectators/flyers, the RSO announces each rocket and launches them one at a time (unless otherwise specified; an example of an exception is a drag race between two rockets).</blockquote></li>
<li><blockquote>Once the range is cleared of rockets, flyers recover their rockets.</blockquote></li>
<li><blockquote>If the flight is not a certification, the procedure ends here. Otherwise, the flyer shows his or her rocket to the RSO and has them sign off on the flyer’s paperwork if the flight is successful. The paperwork is then sent off to the headquarters of the organization and processed.</blockquote></li></ol>

== Rocket Naming Conventions ==

For mass certs:

SSI-R# will be the designation for general rocket launches (blanket certification launches).

Your rocket’s name can be whatever you would like it to be. Examples in the past are: ''Cardinal I'', ''Flamos'', ''Chris May'', etc.

For Daedalus:

SSI-[Level][three letter code denoting name][Launch number] ex. SSI-L3TAL1. These will not affect the number of SSI-R launches. They will have separate counts. The launch number will be useful if the same rocket goes flying again (which should be plausible if you don't mash it).

If the rocket is Class 3, no Level number is required.

== Rockets Leadership ==

The logistics required to run a fully operational Rockets team can be too much for just two co-leads to handle. The Rockets Leadership is a group of people who care about organizing the logistics behind launches and projects that the team is working on. If you show that you care and put in an exceptional amount of effort into your project, you can choose to be a part of this group.

[https://docs.google.com/a/stanford.edu/document/d/1-J5TS0MRgHi0HFTyPhYzzF6VZBa3dqO-WpxrCLgJIpQ/edit?usp=sharing ''Here is a document with all the roles on Rockets Leadership.'']

= Resources =

Other members are one of your best resources if you have any questions about rocketry. Other fantastic resources are laid out below.

== Rockets Drive ==

There are tons of useful things in the Rockets folder!!!!! Here are descriptions of a few of those folders.

=== [http://wiki.stanfordssi.org/Stanford_Student_Space_Initiative_(SSI) ''Wiki''] ===

Go here first for finding useful data on L1 certification procedures! You should add as much to the wiki as possible.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVUFUcEpWRGt2M00 ''Archive''] ===

This holds all the older Rockets plans/documents/etc. Usually these documents are not particularly useful (which is why they are in the archive).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgU3Rsbi1KOFpuSzA ''Daedalus''] ===

This holds all the information for Daedalus, like team folders, L3 requirements, and PDRs & CDRs. Snoop around to see what they’ve done so far and steal information for your project (citing is always a good idea when you do take information).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVkdjcGQtWTNsZU0 ''Getting Nerdy: Textbooks and Manuals''] ===

This folder holds a collection of useful texts ranging from textbooks, manuals, NASA articles and technical reports. If you need to learn things, [https://docs.google.com/a/stanford.edu/document/d/18PSjKqlVLTQzfJLG7ggiWY61W3ZcaD9kCcEePinAJw0/edit?usp=drive_web ''check out this document''].

=== [https://drive.google.com/open?id=0ByRlIAW5-8GqcUcyckNmZlFfN1U ''Launch Documentation''] ===

This holds all the launch documentation for upcoming launches and things like build slot signups, ride signups, rocket building instructions, required reading, pre-flight checklists, etc. Read through this folder and you’ll have a pretty damn good idea of launch logistics.

=== [https://drive.google.com/open?id=0B-5MRX1wVAAdNXQxUzdNVGNRRWc ''Rockets Operating Principles''] ===

This folder houses all of the operating principles, risk mitigation planning, and miscellaneous safety codes, documentation, and literally anything Stanford’s lawyers could possibly want from us. If you read the document you will have a very good understanding of how the team operates on an administrative level.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgdXo4YVJEV1duRlU ''The Design Process''] ===

This folder houses all you need to know to design, fabricate and launch a rocket from a documentation standpoint. Read it.

== [https://ssi-teams.slack.com/ ''Slack''] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like #rockets), which allow us to push out general updates to everyone interested in the rockets team and direct messages in order to communicate with one person - although Slack has recently added a group messaging feature if you don’t want to make an entire channel for a 4 person chat - at a time. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']

== Mission Control ==

Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).

<noinclude>[[Category:Rockets]]</noinclude>

How to Join Rockets

2016-03-28T00:55:30Z

Johnldean:

{{rocket-sidebar}}

[[File: CardinalIILaunch.jpg | right| 250px | thumb | Cardinal II lifting off the pad on a J class motor.]]

Welcome to rockets! This page is intended to lay out the organization of the group, and let everyone know exactly what they need to do to get started! First of all, the current rockets co-leads are Christopher May and Ian Gomez - let us know if you have any questions about the group or about what you are supposed to do.

SSI tries to introduce new members to High Power Rocketry by guiding them through building a simple rocket, flying it, and earning a Level 1 certification. While not all members have to go through this, it will introduce you to designing, analyzing, building, and then flying a rocket (and you will go to a launch, which are always fun).

The main rockets page has a lot of information about High Power Rocketry, as well as how we approach it. Reading through the page before attending a meeting is recommended, but certainly not required. This one focuses more on what you have to do to join, which is less about rockets and more about logistics.

= Basic Info =

== Meetings ==

The Rockets Team has general meetings every week; during Spring Quarter of 2015-2016, these meetings are held on Thursdays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as work sessions where all of the Rockets Team members are in the same place at once.

Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.

'''If you cannot make a project meeting, let your project lead know ahead of time.'''

== Previous Knowledge ==

We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.

Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:

<ul>
<li><blockquote>Heat Transfer</blockquote></li>
<li><blockquote>Thermodynamics</blockquote></li>
<li><blockquote>Fluid Mechanics (incompressible and compressible flow)</blockquote></li>
<li><blockquote>Physics</blockquote></li>
<li><blockquote>Material Sciences</blockquote></li>
<li><blockquote>Statics and Dynamics</blockquote></li>
<li><blockquote>Controls</blockquote></li>
<li><blockquote>Circuits</blockquote></li>
<li><blockquote>Amatuer Radio</blockquote></li>
<li><blockquote>Manufacturing</blockquote></li></ul>

Introductions to many of these are available on [[So You Want To...]]

== Time Commitment ==

Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. Building a basic L1 and L2 rocket should not require more than 10 hours combined if done correctly (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.

== Budget ==

Rockets has [https://docs.google.com/spreadsheets/d/11LfZaV59FnFJyt4DnnCq2Vj7DgzM_2XfgwEPw27zTdI/edit#gid=0 ''a running budget''] in the Drive (Stanford Student Space Initiative > Teams > Rockets). Please add your purchases to the correct tab so we can have a running tally of what we’re spending.

== TRA and NAR ==

[http://www.tripoli.org/ ''Tripoli Rocketry Association (TRA)''] and [http://www.nar.org/ ''National Association of Rocketry (NAR)''] are the two major organizations that organize launches, certify members, and maintain specific standards that govern high power rocketry.

In order to launch high power rockets, you are required to be a member of either organization ([http://www.tripoli.org/Membership ''Tripoli Membership''] / [http://www.nar.org/join-nar/ ''NAR Membership''])

The closest Tripoli launch site to Stanford is [http://www.tccrockets.com/ ''Tripoli Central CA''] (near Fresno) and the closest NAR launch site is [http://www.lunar.org/ ''LUNAR''] (somewhat near Stockton). TCC holds HPR launches (max height 16,800’) on the 3rd Saturday of each month. LUNAR holds HPR launches (max height of 15,000’) on the 1st Saturday of each month in addition to low power launches (max height of 1000’) on the 3rd Saturday of each month at Moffett Field.

== Launches ==

Here is the launch procedure as lifted from the [https://docs.google.com/document/d/1ItllblKqc9oATIYz2Mf4VrZK0Fh1h3ohmwlDXR33KQM/edit ''Operating Principles and Risk Management''] document.

Once the team arrives at the launch site, the rules and regulations of the governing body sponsoring the launch will take precedence. Although procedure is likely to vary from site to site, the launch procedure usually occurs in this order:

<ol style="list-style-type: decimal;">
<li><blockquote>Those attempting to fly a rocket approach the Range Safety Officer (RSO) and officers in charge of the launch, sign in (with their member numbers) and usually pay a launch fee. If the flyer is attempting to get a certification, they will fill out relevant forms to declare their intention (these and other useful documentation pertaining to both national rocketry associations are included in the Appendix).</blockquote></li>
<li><blockquote>Depending on the skill level of the flyer, there are two variations of what may occur.</blockquote>
<ol style="list-style-type: lower-alpha;">
<li><blockquote>In the non-certification flight case, the RSO will inspect the rocket and send the flyer to set up the rocket on the launch pad. This requires placing the rocket on the launch rails, placing the igniter in the motor, and checking the launch pad electronics for errors before returning to a safe distance from the launch pad.</blockquote></li>
<li><blockquote>In the case of a certification, the RSO and someone above the flyer’s certification level will inspect the rocket and send the flyer (and another more experienced member) to set up the rocket for launch. The same setup process occurs as stated above.</blockquote></li></ol>
</li>
<li><blockquote>After the range has been cleared of spectators/flyers, the RSO announces each rocket and launches them one at a time (unless otherwise specified; an example of an exception is a drag race between two rockets).</blockquote></li>
<li><blockquote>Once the range is cleared of rockets, flyers recover their rockets.</blockquote></li>
<li><blockquote>If the flight is not a certification, the procedure ends here. Otherwise, the flyer shows his or her rocket to the RSO and has them sign off on the flyer’s paperwork if the flight is successful. The paperwork is then sent off to the headquarters of the organization and processed.</blockquote></li></ol>

== Rocket Naming Conventions ==

For mass certs:

SSI-R# will be the designation for general rocket launches (blanket certification launches).

Your rocket’s name can be whatever you would like it to be. Examples in the past are: ''Cardinal I'', ''Flamos'', ''Chris May'', etc.

For Daedalus:

SSI-[Level][three letter code denoting name][Launch number] ex. SSI-L3TAL1. These will not affect the number of SSI-R launches. They will have separate counts. The launch number will be useful if the same rocket goes flying again (which should be plausible if you don't mash it).

If the rocket is Class 3, no Level number is required.

== Rockets Leadership ==

The logistics required to run a fully operational Rockets team can be too much for just two co-leads to handle. The Rockets Leadership is a group of people who care about organizing the logistics behind launches and projects that the team is working on. If you show that you care and put in an exceptional amount of effort into your project, you can choose to be a part of this group.

[https://docs.google.com/a/stanford.edu/document/d/1-J5TS0MRgHi0HFTyPhYzzF6VZBa3dqO-WpxrCLgJIpQ/edit?usp=sharing ''Here is a document with all the roles on Rockets Leadership.'']

= Resources =

Other members are one of your best resources if you have any questions about rocketry. Other fantastic resources are laid out below.

== Rockets Drive ==

There are tons of useful things in the Rockets folder!!!!! Here are descriptions of a few of those folders.

=== [http://wiki.stanfordssi.org/Stanford_Student_Space_Initiative_(SSI) ''Wiki''] ===

Go here first for finding useful data on L1 certification procedures! You should add as much to the wiki as possible.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVUFUcEpWRGt2M00 ''Archive''] ===

This holds all the older Rockets plans/documents/etc. Usually these documents are not particularly useful (which is why they are in the archive).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgU3Rsbi1KOFpuSzA ''Daedalus''] ===

This holds all the information for Daedalus, like team folders, L3 requirements, and PDRs & CDRs. Snoop around to see what they’ve done so far and steal information for your project (citing is always a good idea when you do take information).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVkdjcGQtWTNsZU0 ''Getting Nerdy: Textbooks and Manuals''] ===

This folder holds a collection of useful texts ranging from textbooks, manuals, NASA articles and technical reports. If you need to learn things, [https://docs.google.com/a/stanford.edu/document/d/18PSjKqlVLTQzfJLG7ggiWY61W3ZcaD9kCcEePinAJw0/edit?usp=drive_web ''check out this document''].

=== [https://drive.google.com/open?id=0ByRlIAW5-8GqcUcyckNmZlFfN1U ''Launch Documentation''] ===

This holds all the launch documentation for upcoming launches and things like build slot signups, ride signups, rocket building instructions, required reading, pre-flight checklists, etc. Read through this folder and you’ll have a pretty damn good idea of launch logistics.

=== [https://drive.google.com/open?id=0B-5MRX1wVAAdNXQxUzdNVGNRRWc ''Rockets Operating Principles''] ===

This folder houses all of the operating principles, risk mitigation planning, and miscellaneous safety codes, documentation, and literally anything Stanford’s lawyers could possibly want from us. If you read the document you will have a very good understanding of how the team operates on an administrative level.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgdXo4YVJEV1duRlU ''The Design Process''] ===

This folder houses all you need to know to design, fabricate and launch a rocket from a documentation standpoint. Read it.

== [https://ssi-teams.slack.com/ ''Slack''] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like #rockets), which allow us to push out general updates to everyone interested in the rockets team and direct messages in order to communicate with one person - although Slack has recently added a group messaging feature if you don’t want to make an entire channel for a 4 person chat - at a time. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']

== Mission Control ==

Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).

<noinclude>[[Category:Rockets]]</noinclude>

How to Join Rockets

2016-03-28T00:53:49Z

Johnldean:

{{rocket-sidebar}}

[[File: CardinalIILaunch.jpg | right| 250px | thumb | Cardinal II lifting off the pad on a J class motor.]]

Welcome to rockets! This page is intended to lay out the organization of the group, and let everyone know exactly what they need to do to get started! First of all, the current rockets co-leads are Christopher May and Ian Gomez - let us know if you have any questions about the group or about what you are supposed to do.

SSI tries to introduce new members to High Power Rocketry by guiding them through building a simple rocket, flying it, and earning a Level 1 certification. While not all members have to go through this, it will introduce you to designing, analyzing, building, and then flying a rocket (and you will go to a launch, which are always fun).

The main rockets page has a lot of information about High Power Rocketry, as well as how we approach it. Reading through the page before attending a meeting is recommended, but certainly not required. This one focuses more on what you have to do to join, which is less about rockets and more about logistics.

= Background =

All new members are highly encouraged to earn a Level 1 certification, and most dedicated members will eventually receive a Level 2 certification.

== [http://wiki.stanfordssi.org/HPR_Background_Information High Power Rocketry]==

A high powered rocket is defined as a rocket that weighs more than 1500 grams and contains a motor or motors containing more than 125 grams of propellant and/or rated at more than 160 Newton-seconds of total impulse. There are different classifications for motors and different levels of certification required to use these motors. These rockets fall in the Class 2 Rocketry category as long as their total impulse remains below 41,000 Ns. Class 3 rockets require motors that cannot be bought commercially (and are classified as [[ITAR#Defense articles | ITAR defense articles]]).

{|
! Class
! Rating
! Total Impulse (N-s)
|-
|
Class 1 (Model Rocketry)

No certifications required
|-
|
| A
| 1.26-2.5
|-
|

| B
| 2.51-5.00
|-
|

| C
| 5.01-10.0
|-
|

| D
| 10.01-20.0
|-
|

| E
| 20.01-40.0
|-
|

| F
| 40.01-80.0
|-
|

| G
| 80.01-160
|-
|

Class 2 (High Power)

L1

|-
|
| H
| 160.01-320
|-
|

| I
| 320-640
|-
|

L2
|-
|
| J
| 640-1,280
|-
|

| K
| 1,280-2,560
|-
|

L3
|-
|
| L
| 2,560-5,120
|-
|

| M
| 5,120-10,200
|-
|

| N
| 10,200-20,500
|-
|

| O
| 20,500-41,000
|}

=== Level 1: H, I ===

There is no test required to acquire a Level 1 certification. Just a successful flight and recovery using an L1-class motor is required.

=== Level 2: J, K, L ===

The holder of an L1 certification (not necessarily from the organization they are attempting to obtain L2 certification from) must pass an examination on the subject of advanced rocketry concepts and have a successful flight and recovery using an L2-class motor.

=== Level 3: M, N, O and beyond ===

There are many requirements for an L3 flight. Check the NAR and TRA websites for further information.

= Expectations =

== Meetings ==

The Rockets Team has general meetings every week; during Spring Quarter of 2015-2016, these meetings are held on Thursdays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as worksessions where all of the Rockets Team members are in the same place at once.

Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.

'''If you cannot make a project meeting, let your project lead know ahead of time.'''

== Previous Knowledge ==

We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.

Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:

<ul>
<li><blockquote>Heat Transfer</blockquote></li>
<li><blockquote>Thermodynamics</blockquote></li>
<li><blockquote>Fluid Mechanics (incompressible and compressible flow)</blockquote></li>
<li><blockquote>Physics</blockquote></li>
<li><blockquote>Material Sciences</blockquote></li>
<li><blockquote>Statics and Dynamics</blockquote></li>
<li><blockquote>Controls</blockquote></li>
<li><blockquote>Circuits</blockquote></li>
<li><blockquote>Amatuer Radio</blockquote></li>
<li><blockquote>Manufacturing</blockquote></li></ul>

Introductions to many of these are available on [[So You Want To...]]

== Time Commitment ==

Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. Building a basic L1 and L2 rocket should not require more than 10 hours combined if done correctly (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.

== Budget ==

Rockets has [https://docs.google.com/spreadsheets/d/11LfZaV59FnFJyt4DnnCq2Vj7DgzM_2XfgwEPw27zTdI/edit#gid=0 ''a running budget''] in the Drive (Stanford Student Space Initiative > Teams > Rockets). Please add your purchases to the correct tab so we can have a running tally of what we’re spending.

== TRA and NAR ==

[http://www.tripoli.org/ ''Tripoli Rocketry Association (TRA)''] and [http://www.nar.org/ ''National Association of Rocketry (NAR)''] are the two major organizations that organize launches, certify members, and maintain specific standards that govern high power rocketry.

In order to launch high power rockets, you are required to be a member of either organization ([http://www.tripoli.org/Membership ''Tripoli Membership''] / [http://www.nar.org/join-nar/ ''NAR Membership''])

The closest Tripoli launch site to Stanford is [http://www.tccrockets.com/ ''Tripoli Central CA''] (near Fresno) and the closest NAR launch site is [http://www.lunar.org/ ''LUNAR''] (somewhat near Stockton). TCC holds HPR launches (max height 16,800’) on the 3rd Saturday of each month. LUNAR holds HPR launches (max height of 15,000’) on the 1st Saturday of each month in addition to low power launches (max height of 1000’) on the 3rd Saturday of each month at Moffett Field.

== Launches ==

Here is the launch procedure as lifted from the [https://docs.google.com/document/d/1ItllblKqc9oATIYz2Mf4VrZK0Fh1h3ohmwlDXR33KQM/edit ''Operating Principles and Risk Management''] document.

Once the team arrives at the launch site, the rules and regulations of the governing body sponsoring the launch will take precedence. Although procedure is likely to vary from site to site, the launch procedure usually occurs in this order:

<ol style="list-style-type: decimal;">
<li><blockquote>Those attempting to fly a rocket approach the Range Safety Officer (RSO) and officers in charge of the launch, sign in (with their member numbers) and usually pay a launch fee. If the flyer is attempting to get a certification, they will fill out relevant forms to declare their intention (these and other useful documentation pertaining to both national rocketry associations are included in the Appendix).</blockquote></li>
<li><blockquote>Depending on the skill level of the flyer, there are two variations of what may occur.</blockquote>
<ol style="list-style-type: lower-alpha;">
<li><blockquote>In the non-certification flight case, the RSO will inspect the rocket and send the flyer to set up the rocket on the launch pad. This requires placing the rocket on the launch rails, placing the igniter in the motor, and checking the launch pad electronics for errors before returning to a safe distance from the launch pad.</blockquote></li>
<li><blockquote>In the case of a certification, the RSO and someone above the flyer’s certification level will inspect the rocket and send the flyer (and another more experienced member) to set up the rocket for launch. The same setup process occurs as stated above.</blockquote></li></ol>
</li>
<li><blockquote>After the range has been cleared of spectators/flyers, the RSO announces each rocket and launches them one at a time (unless otherwise specified; an example of an exception is a drag race between two rockets).</blockquote></li>
<li><blockquote>Once the range is cleared of rockets, flyers recover their rockets.</blockquote></li>
<li><blockquote>If the flight is not a certification, the procedure ends here. Otherwise, the flyer shows his or her rocket to the RSO and has them sign off on the flyer’s paperwork if the flight is successful. The paperwork is then sent off to the headquarters of the organization and processed.</blockquote></li></ol>

== Rocket Naming Conventions ==

For mass certs:

SSI-R# will be the designation for general rocket launches (blanket certification launches).

Your rocket’s name can be whatever you would like it to be. Examples in the past are: ''Cardinal I'', ''Flamos'', ''Chris May'', etc.

For Daedalus:

SSI-[Level][three letter code denoting name][Launch number] ex. SSI-L3TAL1. These will not affect the number of SSI-R launches. They will have separate counts. The launch number will be useful if the same rocket goes flying again (which should be plausible if you don't mash it).

If the rocket is Class 3, no Level number is required.

== Rockets Leadership ==

The logistics required to run a fully operational Rockets team can be too much for just two co-leads to handle. The Rockets Leadership is a group of people who care about organizing the logistics behind launches and projects that the team is working on. If you show that you care and put in an exceptional amount of effort into your project, you can choose to be a part of this group.

[https://docs.google.com/a/stanford.edu/document/d/1-J5TS0MRgHi0HFTyPhYzzF6VZBa3dqO-WpxrCLgJIpQ/edit?usp=sharing ''Here is a document with all the roles on Rockets Leadership.'']

= Resources =

Other members are one of your best resources if you have any questions about rocketry. Other fantastic resources are laid out below.

== Rockets Drive ==

There are tons of useful things in the Rockets folder!!!!! Here are descriptions of a few of those folders.

=== [http://wiki.stanfordssi.org/Stanford_Student_Space_Initiative_(SSI) ''Wiki''] ===

Go here first for finding useful data on L1 certification procedures! You should add as much to the wiki as possible.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVUFUcEpWRGt2M00 ''Archive''] ===

This holds all the older Rockets plans/documents/etc. Usually these documents are not particularly useful (which is why they are in the archive).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgU3Rsbi1KOFpuSzA ''Daedalus''] ===

This holds all the information for Daedalus, like team folders, L3 requirements, and PDRs & CDRs. Snoop around to see what they’ve done so far and steal information for your project (citing is always a good idea when you do take information).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVkdjcGQtWTNsZU0 ''Getting Nerdy: Textbooks and Manuals''] ===

This folder holds a collection of useful texts ranging from textbooks, manuals, NASA articles and technical reports. If you need to learn things, [https://docs.google.com/a/stanford.edu/document/d/18PSjKqlVLTQzfJLG7ggiWY61W3ZcaD9kCcEePinAJw0/edit?usp=drive_web ''check out this document''].

=== [https://drive.google.com/open?id=0ByRlIAW5-8GqcUcyckNmZlFfN1U ''Launch Documentation''] ===

This holds all the launch documentation for upcoming launches and things like build slot signups, ride signups, rocket building instructions, required reading, pre-flight checklists, etc. Read through this folder and you’ll have a pretty damn good idea of launch logistics.

=== [https://drive.google.com/open?id=0B-5MRX1wVAAdNXQxUzdNVGNRRWc ''Rockets Operating Principles''] ===

This folder houses all of the operating principles, risk mitigation planning, and miscellaneous safety codes, documentation, and literally anything Stanford’s lawyers could possibly want from us. If you read the document you will have a very good understanding of how the team operates on an administrative level.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgdXo4YVJEV1duRlU ''The Design Process''] ===

This folder houses all you need to know to design, fabricate and launch a rocket from a documentation standpoint. Read it.

== [https://ssi-teams.slack.com/ ''Slack''] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like #rockets), which allow us to push out general updates to everyone interested in the rockets team and direct messages in order to communicate with one person - although Slack has recently added a group messaging feature if you don’t want to make an entire channel for a 4 person chat - at a time. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']

== Mission Control ==

Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).

<noinclude>[[Category:Rockets]]</noinclude>

How to Join Rockets

2016-03-28T00:53:29Z

Johnldean:

{{rocket-sidebar}}

[[File: CardinalIILaunch.jpg | right| 250px | thumb | Cardinal II lifting off the pad on a J class motor.]]

Welcome to rockets! This page is intended to lay out the organization of the group, and let everyone know exactly what they need to do to get started! First of all, the current rockets co-leads are Christopher May and Ian Gomez - let us know if you have any questions about the group or about what you are supposed to do.

SSI tries to introduce new members to High Power Rocketry by guiding them through building a simple rocket, flying it, and earning a Level 1 certification. While not all members have to go through this, it will introduce you to designing, analyzing, building, and then flying a rocket (and you will go to a launch, which are always fun).

The main rockets page has a lot of information about High Power Rocketry, as well as how we approach it. Reading through the page before attending a meeting is recommended, but certainly not required. This one focuses more on what you have to do to join, which

= Background =

All new members are highly encouraged to earn a Level 1 certification, and most dedicated members will eventually receive a Level 2 certification.

== [http://wiki.stanfordssi.org/HPR_Background_Information High Power Rocketry]==

A high powered rocket is defined as a rocket that weighs more than 1500 grams and contains a motor or motors containing more than 125 grams of propellant and/or rated at more than 160 Newton-seconds of total impulse. There are different classifications for motors and different levels of certification required to use these motors. These rockets fall in the Class 2 Rocketry category as long as their total impulse remains below 41,000 Ns. Class 3 rockets require motors that cannot be bought commercially (and are classified as [[ITAR#Defense articles | ITAR defense articles]]).

{|
! Class
! Rating
! Total Impulse (N-s)
|-
|
Class 1 (Model Rocketry)

No certifications required
|-
|
| A
| 1.26-2.5
|-
|

| B
| 2.51-5.00
|-
|

| C
| 5.01-10.0
|-
|

| D
| 10.01-20.0
|-
|

| E
| 20.01-40.0
|-
|

| F
| 40.01-80.0
|-
|

| G
| 80.01-160
|-
|

Class 2 (High Power)

L1

|-
|
| H
| 160.01-320
|-
|

| I
| 320-640
|-
|

L2
|-
|
| J
| 640-1,280
|-
|

| K
| 1,280-2,560
|-
|

L3
|-
|
| L
| 2,560-5,120
|-
|

| M
| 5,120-10,200
|-
|

| N
| 10,200-20,500
|-
|

| O
| 20,500-41,000
|}

=== Level 1: H, I ===

There is no test required to acquire a Level 1 certification. Just a successful flight and recovery using an L1-class motor is required.

=== Level 2: J, K, L ===

The holder of an L1 certification (not necessarily from the organization they are attempting to obtain L2 certification from) must pass an examination on the subject of advanced rocketry concepts and have a successful flight and recovery using an L2-class motor.

=== Level 3: M, N, O and beyond ===

There are many requirements for an L3 flight. Check the NAR and TRA websites for further information.

= Expectations =

== Meetings ==

The Rockets Team has general meetings every week; during Spring Quarter of 2015-2016, these meetings are held on Thursdays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as worksessions where all of the Rockets Team members are in the same place at once.

Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.

'''If you cannot make a project meeting, let your project lead know ahead of time.'''

== Previous Knowledge ==

We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.

Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:

<ul>
<li><blockquote>Heat Transfer</blockquote></li>
<li><blockquote>Thermodynamics</blockquote></li>
<li><blockquote>Fluid Mechanics (incompressible and compressible flow)</blockquote></li>
<li><blockquote>Physics</blockquote></li>
<li><blockquote>Material Sciences</blockquote></li>
<li><blockquote>Statics and Dynamics</blockquote></li>
<li><blockquote>Controls</blockquote></li>
<li><blockquote>Circuits</blockquote></li>
<li><blockquote>Amatuer Radio</blockquote></li>
<li><blockquote>Manufacturing</blockquote></li></ul>

Introductions to many of these are available on [[So You Want To...]]

== Time Commitment ==

Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. Building a basic L1 and L2 rocket should not require more than 10 hours combined if done correctly (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.

== Budget ==

Rockets has [https://docs.google.com/spreadsheets/d/11LfZaV59FnFJyt4DnnCq2Vj7DgzM_2XfgwEPw27zTdI/edit#gid=0 ''a running budget''] in the Drive (Stanford Student Space Initiative > Teams > Rockets). Please add your purchases to the correct tab so we can have a running tally of what we’re spending.

== TRA and NAR ==

[http://www.tripoli.org/ ''Tripoli Rocketry Association (TRA)''] and [http://www.nar.org/ ''National Association of Rocketry (NAR)''] are the two major organizations that organize launches, certify members, and maintain specific standards that govern high power rocketry.

In order to launch high power rockets, you are required to be a member of either organization ([http://www.tripoli.org/Membership ''Tripoli Membership''] / [http://www.nar.org/join-nar/ ''NAR Membership''])

The closest Tripoli launch site to Stanford is [http://www.tccrockets.com/ ''Tripoli Central CA''] (near Fresno) and the closest NAR launch site is [http://www.lunar.org/ ''LUNAR''] (somewhat near Stockton). TCC holds HPR launches (max height 16,800’) on the 3rd Saturday of each month. LUNAR holds HPR launches (max height of 15,000’) on the 1st Saturday of each month in addition to low power launches (max height of 1000’) on the 3rd Saturday of each month at Moffett Field.

== Launches ==

Here is the launch procedure as lifted from the [https://docs.google.com/document/d/1ItllblKqc9oATIYz2Mf4VrZK0Fh1h3ohmwlDXR33KQM/edit ''Operating Principles and Risk Management''] document.

Once the team arrives at the launch site, the rules and regulations of the governing body sponsoring the launch will take precedence. Although procedure is likely to vary from site to site, the launch procedure usually occurs in this order:

<ol style="list-style-type: decimal;">
<li><blockquote>Those attempting to fly a rocket approach the Range Safety Officer (RSO) and officers in charge of the launch, sign in (with their member numbers) and usually pay a launch fee. If the flyer is attempting to get a certification, they will fill out relevant forms to declare their intention (these and other useful documentation pertaining to both national rocketry associations are included in the Appendix).</blockquote></li>
<li><blockquote>Depending on the skill level of the flyer, there are two variations of what may occur.</blockquote>
<ol style="list-style-type: lower-alpha;">
<li><blockquote>In the non-certification flight case, the RSO will inspect the rocket and send the flyer to set up the rocket on the launch pad. This requires placing the rocket on the launch rails, placing the igniter in the motor, and checking the launch pad electronics for errors before returning to a safe distance from the launch pad.</blockquote></li>
<li><blockquote>In the case of a certification, the RSO and someone above the flyer’s certification level will inspect the rocket and send the flyer (and another more experienced member) to set up the rocket for launch. The same setup process occurs as stated above.</blockquote></li></ol>
</li>
<li><blockquote>After the range has been cleared of spectators/flyers, the RSO announces each rocket and launches them one at a time (unless otherwise specified; an example of an exception is a drag race between two rockets).</blockquote></li>
<li><blockquote>Once the range is cleared of rockets, flyers recover their rockets.</blockquote></li>
<li><blockquote>If the flight is not a certification, the procedure ends here. Otherwise, the flyer shows his or her rocket to the RSO and has them sign off on the flyer’s paperwork if the flight is successful. The paperwork is then sent off to the headquarters of the organization and processed.</blockquote></li></ol>

== Rocket Naming Conventions ==

For mass certs:

SSI-R# will be the designation for general rocket launches (blanket certification launches).

Your rocket’s name can be whatever you would like it to be. Examples in the past are: ''Cardinal I'', ''Flamos'', ''Chris May'', etc.

For Daedalus:

SSI-[Level][three letter code denoting name][Launch number] ex. SSI-L3TAL1. These will not affect the number of SSI-R launches. They will have separate counts. The launch number will be useful if the same rocket goes flying again (which should be plausible if you don't mash it).

If the rocket is Class 3, no Level number is required.

== Rockets Leadership ==

The logistics required to run a fully operational Rockets team can be too much for just two co-leads to handle. The Rockets Leadership is a group of people who care about organizing the logistics behind launches and projects that the team is working on. If you show that you care and put in an exceptional amount of effort into your project, you can choose to be a part of this group.

[https://docs.google.com/a/stanford.edu/document/d/1-J5TS0MRgHi0HFTyPhYzzF6VZBa3dqO-WpxrCLgJIpQ/edit?usp=sharing ''Here is a document with all the roles on Rockets Leadership.'']

= Resources =

Other members are one of your best resources if you have any questions about rocketry. Other fantastic resources are laid out below.

== Rockets Drive ==

There are tons of useful things in the Rockets folder!!!!! Here are descriptions of a few of those folders.

=== [http://wiki.stanfordssi.org/Stanford_Student_Space_Initiative_(SSI) ''Wiki''] ===

Go here first for finding useful data on L1 certification procedures! You should add as much to the wiki as possible.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVUFUcEpWRGt2M00 ''Archive''] ===

This holds all the older Rockets plans/documents/etc. Usually these documents are not particularly useful (which is why they are in the archive).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgU3Rsbi1KOFpuSzA ''Daedalus''] ===

This holds all the information for Daedalus, like team folders, L3 requirements, and PDRs & CDRs. Snoop around to see what they’ve done so far and steal information for your project (citing is always a good idea when you do take information).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVkdjcGQtWTNsZU0 ''Getting Nerdy: Textbooks and Manuals''] ===

This folder holds a collection of useful texts ranging from textbooks, manuals, NASA articles and technical reports. If you need to learn things, [https://docs.google.com/a/stanford.edu/document/d/18PSjKqlVLTQzfJLG7ggiWY61W3ZcaD9kCcEePinAJw0/edit?usp=drive_web ''check out this document''].

=== [https://drive.google.com/open?id=0ByRlIAW5-8GqcUcyckNmZlFfN1U ''Launch Documentation''] ===

This holds all the launch documentation for upcoming launches and things like build slot signups, ride signups, rocket building instructions, required reading, pre-flight checklists, etc. Read through this folder and you’ll have a pretty damn good idea of launch logistics.

=== [https://drive.google.com/open?id=0B-5MRX1wVAAdNXQxUzdNVGNRRWc ''Rockets Operating Principles''] ===

This folder houses all of the operating principles, risk mitigation planning, and miscellaneous safety codes, documentation, and literally anything Stanford’s lawyers could possibly want from us. If you read the document you will have a very good understanding of how the team operates on an administrative level.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgdXo4YVJEV1duRlU ''The Design Process''] ===

This folder houses all you need to know to design, fabricate and launch a rocket from a documentation standpoint. Read it.

== [https://ssi-teams.slack.com/ ''Slack''] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like #rockets), which allow us to push out general updates to everyone interested in the rockets team and direct messages in order to communicate with one person - although Slack has recently added a group messaging feature if you don’t want to make an entire channel for a 4 person chat - at a time. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']

== Mission Control ==

Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).

<noinclude>[[Category:Rockets]]</noinclude>

Rockets Team

2016-03-28T00:43:33Z

Johnldean:

{{rocket-sidebar}}

[[File: CardinalIILaunch.jpg | right| 250px | thumb | Cardinal II lifting off the pad on a J class motor.]]

The Rockets team is a student-led group striving to push the limits of high power rocketry. The team is currently working Project Daedalus, creating and testing novel systems for an eventual larger-scale rocket project. Project Daedalus. [[Project Daedalus]] is a suite of four rockets: [[Talos]] is a launch vehicle for [[Kythera]], [[Charybdis]] is testing out passive ascent stabilization with canted fins, [[Prometheus]] is demonstrating active roll control of a payload on descent, and [[Pegasus]] is testing a parafoil recovery system.

To accomplish each of the components of Daedalus, the Rockets team builds and launches [[L1 Certification|Level 1]], [[L2 Certification|Level 2]], and Level 3 [https://en.wikipedia.org/wiki/High-power_rocketry high-power rockets]. These are launched with national rocketry clubs.

The Rockets team Faculty Advisor is [[Dr. Hai Wang]]. The current team leads are Christopher May and Ian Gomez.

The rest of this page is dedicated to explaining everything an SSI Rockets Team member needs to know.

= Background =

== [http://wiki.stanfordssi.org/HPR_Background_Information High Power Rocketry]==

A high powered rocket is defined as a rocket that weighs more than 1500 grams and contains a motor or motors containing more than 125 grams of propellant and/or rated at more than 160 Newton-seconds of total impulse. There are different classifications for motors and different levels of certification required to use these motors. These rockets fall in the Class 2 Rocketry category as long as their total impulse remains below 41,000 Ns. Class 3 rockets require motors that cannot be bought commercially (and are classified as [[ITAR#Defense articles | ITAR defense articles]]).

{|
! Class
! Rating
! Total Impulse (N-s)
|-
|
Class 1 (Model Rocketry)

No certifications required
|-
|
| A
| 1.26-2.5
|-
|

| B
| 2.51-5.00
|-
|

| C
| 5.01-10.0
|-
|

| D
| 10.01-20.0
|-
|

| E
| 20.01-40.0
|-
|

| F
| 40.01-80.0
|-
|

| G
| 80.01-160
|-
|

Class 2 (High Power)

L1

|-
|
| H
| 160.01-320
|-
|

| I
| 320-640
|-
|

L2
|-
|
| J
| 640-1,280
|-
|

| K
| 1,280-2,560
|-
|

L3
|-
|
| L
| 2,560-5,120
|-
|

| M
| 5,120-10,200
|-
|

| N
| 10,200-20,500
|-
|

| O
| 20,500-41,000
|}

=== Level 1: H, I ===

There is no test required to acquire a Level 1 certification. Just a successful flight and recovery using an L1-class motor is required.

=== Level 2: J, K, L ===

The holder of an L1 certification (not necessarily from the organization they are attempting to obtain L2 certification from) must pass an examination on the subject of advanced rocketry concepts and have a successful flight and recovery using an L2-class motor.

=== Level 3: M, N, O and beyond ===

There are many requirements for an L3 flight. Check the NAR and TRA websites for further information.

==[[Project Daedalus]]==

Daedalus teaches the major design principles of high power rocketry with hands-on experience. Teams design and launch novel rocket concepts iteratively, starting with L1, L2 and finally ending with an L3 rocket that successfully flies the thoroughly tested design. The technology coming out of this project will benefit the Rockets Team’s flagship rocketry project.

Daedalus is the overarching rockets project for the 2015-2016 year that is divided into 4 subteams as described below.

=== [[Pegasus]] ===

The purpose of Pegasus is to demonstrate the feasibility of using a parafoil recovery system to create a controlled, directed recovery for a high-powered rocket from over 10,000 ft.

=== [[Prometheus]] ===

The purpose of Prometheus is to demonstrate roll control of a payload descent using PID-controlled fins.

=== [[Talos]]/[[Kythera]] ===

Talos is the launch vehicle for Kythera, SSI’s first generation flight computer system which will feature a Raspberry Pi that reads data from sensors and communicates that data to Teensys (Arduino-based microcontroller) in addition to using radios to provide real time GPS, orientation, and video data.

=== [[Charybdis]] ===

The purpose of Charybdis is to demonstrate passive ascent stabilization using canted fins.

= Expectations =

== Meetings ==

The Rockets Team has general meetings every week; during Spring Quarter of 2015-2016, these meetings are held on Thursdays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as worksessions where all of the Rockets Team members are in the same place at once.

Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.

'''If you cannot make a project meeting, let your project lead know ahead of time.'''

== Previous Knowledge ==

We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory.

Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:

<ul>
<li><blockquote>Heat Transfer</blockquote></li>
<li><blockquote>Thermodynamics</blockquote></li>
<li><blockquote>Fluid Mechanics (incompressible and compressible flow)</blockquote></li>
<li><blockquote>Physics</blockquote></li>
<li><blockquote>Material Sciences</blockquote></li>
<li><blockquote>Statics and Dynamics</blockquote></li>
<li><blockquote>Controls</blockquote></li>
<li><blockquote>Circuits</blockquote></li>
<li><blockquote>Amatuer Radio</blockquote></li>
<li><blockquote>Manufacturing</blockquote></li></ul>

Introductions to many of these are available on [[So You Want To...]]

== Time Commitment ==

Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. L1 and L2 do not require more than 10 hours combined (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.

= The Process =

== Design Reviews ==

Note: For a much more specific documentation check out [https://docs.google.com/document/d/1c3D9EUYV-cxaDAc-bi3u-ufAYVxP0EIeB3hBln9TbUQ/edit# ''''The Process: From PDR to PLAR'''']. The document provides specific guidelines and expectations for each stage of the process.

As specified in NASA’s engineering design life cycle, multiple design reviews are used to assess the feasibility and practicality of both attempting and accomplishing a particular project. This includes a Preliminary Design Review ([https://docs.google.com/presentation/u/1/d/1DXe1mLi3W9Z8g58muUl7w96wpbG8cZbLAWL8znXPc2M/edit#slide=id.p3 ''PDR example'']) to assess mission goals, risks, and criteria and is followed by a Critical Design Review (CDR). By CDR, a project is expected to have assessed ''specific'' hardware and software configurations for viability, addressed questions raised in the PDR, and considered manufacturing and production of their final product. Both stages include extensive criticism and evaluation by other SSI members and external entities.

'''The PDR demonstrates that the overall preliminary design meets all requirements with acceptable risk and within the cost and schedule constraints.''' It shows that the correct design options have been selected, interfaces have been identified, and verification methods have been described. Full baseline cost and schedules, as well as all risk assessment, management systems, and metrics, are presented.

The CDR demonstrates that the maturity of the design is appropriate to support proceeding to full-scale fabrication, assembly, integration, and test and that the technical effort is on track to complete the flight and ground system development and mission operations in order to meet overall performance requirements within the identified cost and schedule constraints. Progress against management plans, budget, and schedule, as well as risk assessment, are presented. '''The CDR is a review of the final design of the launch vehicle and payload system'''. All analyses should be complete and some critical testing should be complete.

The FRR examines tests, demonstrations, analyses, and audits that determine the overall system (all projects working together) readiness for a safe and successful flight/launch and for subsequent flight operations of the as-built rocket and payload system. '''It ensures that all flight and ground hardware, software, personnel, and procedures are operationally ready.'''

Immediately prior to launch, SSI will conduct a Launch Readiness Review (LRR). The LRR is performed on-site to verify procedural compliance and compliance with applicable safety codes. Furthermore, please note that launch-site safety officers will also be present to approve and assess your rockets.

After launch, SSI will conduct a Post-Launch Assessment Review (PLAR). The PLAR is an assessment of system in-flight performance. The PLAR will determine if mission success criteria were met, discuss any adverse events, enumerate lessons learned, and describe any recommended changes to the SSI Rockets program.

== Budget ==

Rockets has [https://docs.google.com/spreadsheets/d/11LfZaV59FnFJyt4DnnCq2Vj7DgzM_2XfgwEPw27zTdI/edit#gid=0 ''a running budget''] in the Drive (Stanford Student Space Initiative > Teams > Rockets). Please add your purchases to the correct tab so we can have a running tally of what we’re spending.

== TRA and NAR ==

[http://www.tripoli.org/ ''Tripoli Rocketry Association (TRA)''] and [http://www.nar.org/ ''National Association of Rocketry (NAR)''] are the two major organizations that organize launches, certify members, and maintain specific standards that govern high power rocketry.

In order to launch high power rockets, you are required to be a member of either organization ([http://www.tripoli.org/Membership ''Tripoli Membership''] / [http://www.nar.org/join-nar/ ''NAR Membership''])

The closest Tripoli launch site to Stanford is [http://www.tccrockets.com/ ''Tripoli Central CA''] (near Fresno) and the closest NAR launch site is [http://www.lunar.org/ ''LUNAR''] (somewhat near Stockton). TCC holds HPR launches (max height 16,800’) on the 3rd Saturday of each month. LUNAR holds HPR launches (max height of 15,000’) on the 1st Saturday of each month in addition to low power launches (max height of 1000’) on the 3rd Saturday of each month at Moffett Field.

== Launches ==

Here is the launch procedure as lifted from the [https://docs.google.com/document/d/1ItllblKqc9oATIYz2Mf4VrZK0Fh1h3ohmwlDXR33KQM/edit ''Operating Principles and Risk Management''] document.

Once the team arrives at the launch site, the rules and regulations of the governing body sponsoring the launch will take precedence. Although procedure is likely to vary from site to site, the launch procedure usually occurs in this order:

<ol style="list-style-type: decimal;">
<li><blockquote>Those attempting to fly a rocket approach the Range Safety Officer (RSO) and officers in charge of the launch, sign in (with their member numbers) and usually pay a launch fee. If the flyer is attempting to get a certification, they will fill out relevant forms to declare their intention (these and other useful documentation pertaining to both national rocketry associations are included in the Appendix).</blockquote></li>
<li><blockquote>Depending on the skill level of the flyer, there are two variations of what may occur.</blockquote>
<ol style="list-style-type: lower-alpha;">
<li><blockquote>In the non-certification flight case, the RSO will inspect the rocket and send the flyer to set up the rocket on the launch pad. This requires placing the rocket on the launch rails, placing the igniter in the motor, and checking the launch pad electronics for errors before returning to a safe distance from the launch pad.</blockquote></li>
<li><blockquote>In the case of a certification, the RSO and someone above the flyer’s certification level will inspect the rocket and send the flyer (and another more experienced member) to set up the rocket for launch. The same setup process occurs as stated above.</blockquote></li></ol>
</li>
<li><blockquote>After the range has been cleared of spectators/flyers, the RSO announces each rocket and launches them one at a time (unless otherwise specified; an example of an exception is a drag race between two rockets).</blockquote></li>
<li><blockquote>Once the range is cleared of rockets, flyers recover their rockets.</blockquote></li>
<li><blockquote>If the flight is not a certification, the procedure ends here. Otherwise, the flyer shows his or her rocket to the RSO and has them sign off on the flyer’s paperwork if the flight is successful. The paperwork is then sent off to the headquarters of the organization and processed.</blockquote></li></ol>

== Rocket Naming Conventions ==

For mass certs:

SSI-R# will be the designation for general rocket launches (blanket certification launches).

Your rocket’s name can be whatever you would like it to be. Examples in the past are: ''Cardinal I'', ''Flamos'', ''Chris May'', etc.

For Daedalus:

SSI-[Level][three letter code denoting name][Launch number] ex. SSI-L3TAL1. These will not affect the number of SSI-R launches. They will have separate counts. The launch number will be useful if the same rocket goes flying again (which should be plausible if you don't mash it).

If the rocket is Class 3, no Level number is required.

== Rockets Leadership ==

The logistics required to run a fully operational Rockets team can be too much for just two co-leads to handle. The Rockets Leadership is a group of people who care about organizing the logistics behind launches and projects that the team is working on. If you show that you care and put in an exceptional amount of effort into your project, you can choose to be a part of this group.

[https://docs.google.com/a/stanford.edu/document/d/1-J5TS0MRgHi0HFTyPhYzzF6VZBa3dqO-WpxrCLgJIpQ/edit?usp=sharing ''Here is a document with all the roles on Rockets Leadership.'']

= Resources =

Other members are one of your best resources if you have any questions about rocketry. Other fantastic resources are laid out below.

== Rockets Drive ==

There are tons of useful things in the Rockets folder!!!!! Here are descriptions of a few of those folders.

=== [http://wiki.stanfordssi.org/Stanford_Student_Space_Initiative_(SSI) ''Wiki''] ===

Go here first for finding useful data on L1 certification procedures! You should add as much to the wiki as possible.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVUFUcEpWRGt2M00 ''Archive''] ===

This holds all the older Rockets plans/documents/etc. Usually these documents are not particularly useful (which is why they are in the archive).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgU3Rsbi1KOFpuSzA ''Daedalus''] ===

This holds all the information for Daedalus, like team folders, L3 requirements, and PDRs & CDRs. Snoop around to see what they’ve done so far and steal information for your project (citing is always a good idea when you do take information).

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVkdjcGQtWTNsZU0 ''Getting Nerdy: Textbooks and Manuals''] ===

This folder holds a collection of useful texts ranging from textbooks, manuals, NASA articles and technical reports. If you need to learn things, [https://docs.google.com/a/stanford.edu/document/d/18PSjKqlVLTQzfJLG7ggiWY61W3ZcaD9kCcEePinAJw0/edit?usp=drive_web ''check out this document''].

=== [https://drive.google.com/open?id=0ByRlIAW5-8GqcUcyckNmZlFfN1U ''Launch Documentation''] ===

This holds all the launch documentation for upcoming launches and things like build slot signups, ride signups, rocket building instructions, required reading, pre-flight checklists, etc. Read through this folder and you’ll have a pretty damn good idea of launch logistics.

=== [https://drive.google.com/open?id=0B-5MRX1wVAAdNXQxUzdNVGNRRWc ''Rockets Operating Principles''] ===

This folder houses all of the operating principles, risk mitigation planning, and miscellaneous safety codes, documentation, and literally anything Stanford’s lawyers could possibly want from us. If you read the document you will have a very good understanding of how the team operates on an administrative level.

=== [https://drive.google.com/open?id=0B_uGMv8pu2KgdXo4YVJEV1duRlU ''The Design Process''] ===

This folder houses all you need to know to design, fabricate and launch a rocket from a documentation standpoint. Read it.

== [https://ssi-teams.slack.com/ ''Slack''] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like #rockets), which allow us to push out general updates to everyone interested in the rockets team and direct messages in order to communicate with one person - although Slack has recently added a group messaging feature if you don’t want to make an entire channel for a 4 person chat - at a time. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']

== Mission Control ==

Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).

<noinclude>[[Category:Rockets]]</noinclude>