How to Be in SSI

2019-09-25T00:03:15Z

Thwhite:

How to Be in SSI

2019-09-25T00:00:52Z

Thwhite:

End station III

2019-09-25T00:00:10Z

Thwhite:

End Station III is our home base. It's where we do almost all of our project work, and where we keep our stuff. It's also an active laboratory doing some pretty cool work. Here are some thoughts, tips and tricks about using it!

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

=Where is ESIII=

See the picture above! Or you can type "where pizza" to any slack channel to get an address.

=How Can I Get Access to ESIII=

Follow the instructions on [[How to Join SSI]]! If you have any problems, please feel free to message the Co-Presidents!

Once you have access, you'll be required to help clean, once a quarter, for less than an hour, to maintain it.

=What are the rules in ESIII=

There are a couple things to keep in mind while you're in ESIII.

# Please swipe in when you enter, even if someone else is holding the door for you. We're required to get a sense of who's in the building in case of emergency!
# *Do not enter ESIII alone.* It's an active laboratory. If you need a buddy, hit up #random in the slack - people are always willing to head over!
# Don't park bikes inside, please; it blocks stuff.
# You can open the loading dock door - but don't open it for long (it messes up sensitive experiments), and don't leave it open (so people don't steal our stuff).
# Don't use the door near Green Earth Sciences - use the one on South Service Road instead.
# Although it's tempting, please don't actually sleep in ESIII.

=Tips and Tricks=
# Check out the #doorbell channel to see if people are in ESIII if you're unsure!
# There are some cool easter eggs and historical moments hidden all around - check things out while you're there!
# We have access to the break room - it's a lovely spot to do PSETs with people.
# ISS stands for Industrial Subterranean Space, but it's the closest we have (so far!) to our own International Space Station. Each room is named after a capsule of the ISS - Unity (Mechanical Engineering), Harmony (Electrical Engineering), Tranquility (Meeting Room), Destiny (Storage), and Zarya (General Use, 3D Printers and Desktop). The two storage spaces on the floor are named after capsules that meet the ISS - Dragon and Cygnus.

2018-09-21T19:59:17Z

2018-09-21T13:48:15Z

Thwhite: /* Step 2: Go to the SSI Internal Site */

Congratulations! You have done a great service to SSI by spending your own hard-earned money on buying something we need. Thanks for that. The reimbursement system is absolutely key to our functionality as an organization - without it, it would take months of lead time to buy anything, and what we do would become almost impossible. Now, let's get your money back, as quickly as possible.

= Step 1: Keep you receipt! =

The importance of this cannot be overstated. Without a receipt, it's very difficult to reimburse. If you're buying things at home, save your receipt and try to submit it as soon as you can; if you're traveling with SSI, take a picture of your receipt in case you forget it or accidentally lose it. And when you get your receipt, check two things:
* Is it an invoice? If so, it's not quite enough - you also need to attach a bank statement.
* Is it itemized? Restaurants are especially notorious for this, but if a place doesn't list a breakdown of what you spent, it doesn't count. If you get one of these, go back and ask for an itemized one. If you can't get an itemized one, we can try to work something out.

= Step 2: Go to the SSI Internal Site =

It's at https://internal.stanfordssi.org/. You can log on with your Stanford ID. If all goes well, you should see this page:

[[File:SSIInternalHome.JPG|thumb|left|alt=SSI Internal Site Start Page.|SSI Internal Site Start Page.]]

If not, go to #operations-website and complain.

= Step 3: Click on the reimbursements tab =

Once you're there, click on New Reimbursement

= Step 4: Fill out the fields and submit! =

Most fields here are self-explanatory. Some notes:
* If you used an SSI credit card, make sure to box that field.
* If this expense was already handled somehow (this happens rarely), hit that field.
* "Delivery Method" refers to if you want to pick the reimbursement up at Old Union or have it mailed to you. Generally pickup at Old Union is easier.
* If you're confused by a field or unsure what to put, please contact @chloe or @Peter Maldonado.

= Step 5: (Rockets Team Only) Fill Out an Expense Report =

Some teams require that you make a detailed listing of the expenses you dealt with. They'll have a budget document where you can list what money you spent. Contact your coleads to know where that is.

= Step 6: Track your process and make changes if necessary =

When you submit your reimbursement, slackbot will message you to let you know! After that, it's up to the financial officers to process it, and slackbot will update you as they do so. If there's something wrong with your reimbursement, they'll also let you know! If you get a message saying your reimbursement was rejected, don't despair. There are plenty of ways to fix it and resubmit it--check the message from either the FOs, team co-leads, or SSE (Stanford Student Enterprises, the people who make the final call on the validity of a reimbursement) and make the necessary changes. If you're unsure what the message means or want clarification, contact either @chloe or @Peter Maldonado.

= Step 7: Pick up your reimbursement =

Within a few weeks, you should get an email from ASSU saying that a payment is available! You can go pick up your check from the ASSU office on the first floor of Old Union, behind the Axe and Palm (TAP).

[[Category:Operations]]

Getting Reimbursed

2018-09-21T13:47:54Z

Thwhite:

Congratulations! You have done a great service to SSI by spending your own hard-earned money on buying something we need. Thanks for that. The reimbursement system is absolutely key to our functionality as an organization - without it, it would take months of lead time to buy anything, and what we do would become almost impossible. Now, let's get your money back, as quickly as possible.

= Step 1: Keep you receipt! =

The importance of this cannot be overstated. Without a receipt, it's very difficult to reimburse. If you're buying things at home, save your receipt and try to submit it as soon as you can; if you're traveling with SSI, take a picture of your receipt in case you forget it or accidentally lose it. And when you get your receipt, check two things:
* Is it an invoice? If so, it's not quite enough - you also need to attach a bank statement.
* Is it itemized? Restaurants are especially notorious for this, but if a place doesn't list a breakdown of what you spent, it doesn't count. If you get one of these, go back and ask for an itemized one. If you can't get an itemized one, we can try to work something out.

= Step 2: Go to the SSI Internal Site =

It's at https://internal.stanfordssi.org/. You can log on with your Stanford ID. If all goes well, you should see this page:

[[File:SSIInternalHome.JPG|thumb|left|alt=SSI Internal Site Start Page.|SSI Internal Site Start Page.]]

If not, go to #operations-website and complain.

= Step 3: Click on the reimbursements tab =

Once you're there, click on New Reimbursement

= Step 4: Fill out the fields and submit! =

Most fields here are self-explanatory. Some notes:
* If you used an SSI credit card, make sure to box that field.
* If this expense was already handled somehow (this happens rarely), hit that field.
* "Delivery Method" refers to if you want to pick the reimbursement up at Old Union or have it mailed to you. Generally pickup at Old Union is easier.
* If you're confused by a field or unsure what to put, please contact @chloe or @Peter Maldonado.

= Step 5: (Rockets Team Only) Fill Out an Expense Report =

Some teams require that you make a detailed listing of the expenses you dealt with. They'll have a budget document where you can list what money you spent. Contact your coleads to know where that is.

= Step 6: Track your process and make changes if necessary =

When you submit your reimbursement, slackbot will message you to let you know! After that, it's up to the financial officers to process it, and slackbot will update you as they do so. If there's something wrong with your reimbursement, they'll also let you know! If you get a message saying your reimbursement was rejected, don't despair. There are plenty of ways to fix it and resubmit it--check the message from either the FOs, team co-leads, or SSE (Stanford Student Enterprises, the people who make the final call on the validity of a reimbursement) and make the necessary changes. If you're unsure what the message means or want clarification, contact either @chloe or @Peter Maldonado.

= Step 7: Pick up your reimbursement =

Within a few weeks, you should get an email from ASSU saying that a payment is available! You can go pick up your check from the ASSU office on the first floor of Old Union, behind the Axe and Palm (TAP).

[[Category:Operations]]

Getting Reimbursed

2018-09-21T13:47:17Z

Thwhite:

Congratulations! You have done a great service to SSI by spending your own hard-earned money on buying something we need. Thanks for that. The reimbursement system is absolutely key to our functionality as an organization - without it, it would take months of lead time to buy anything, and what we do would become almost impossible. Now, let's get your money back, as quickly as possible.

= Step 1: Keep you receipt! =

The importance of this cannot be overstated. Without a receipt, it's very difficult to reimburse. If you're buying things at home, save your receipt and try to submit it as soon as you can; if you're traveling with SSI, take a picture of your receipt in case you forget it or accidentally lose it. And when you get your receipt, check two things:
* Is it an invoice? If so, it's not quite enough - you also need to attach a bank statement.
* Is it itemized? Restaurants are especially notorious for this, but if a place doesn't list a breakdown of what you spent, it doesn't count. If you get one of these, go back and ask for an itemized one. If you can't get an itemized one, we can try to work something out.

= Step 2: Go to the SSI Internal Site =

It's at https://internal.stanfordssi.org/. You can log on with your Stanford ID. If all goes well, you should see this page:

[[File:SSIInternalHome.JPEG|thumb|left|alt=SSI Internal Site Start Page.|SSI Internal Site Start Page.]]

If not, go to #operations-website and complain.

= Step 3: Click on the reimbursements tab =

Once you're there, click on New Reimbursement

= Step 4: Fill out the fields and submit! =

Most fields here are self-explanatory. Some notes:
* If you used an SSI credit card, make sure to box that field.
* If this expense was already handled somehow (this happens rarely), hit that field.
* "Delivery Method" refers to if you want to pick the reimbursement up at Old Union or have it mailed to you. Generally pickup at Old Union is easier.
* If you're confused by a field or unsure what to put, please contact @chloe or @Peter Maldonado.

= Step 5: (Rockets Team Only) Fill Out an Expense Report =

Some teams require that you make a detailed listing of the expenses you dealt with. They'll have a budget document where you can list what money you spent. Contact your coleads to know where that is.

= Step 6: Track your process and make changes if necessary =

When you submit your reimbursement, slackbot will message you to let you know! After that, it's up to the financial officers to process it, and slackbot will update you as they do so. If there's something wrong with your reimbursement, they'll also let you know! If you get a message saying your reimbursement was rejected, don't despair. There are plenty of ways to fix it and resubmit it--check the message from either the FOs, team co-leads, or SSE (Stanford Student Enterprises, the people who make the final call on the validity of a reimbursement) and make the necessary changes. If you're unsure what the message means or want clarification, contact either @chloe or @Peter Maldonado.

= Step 7: Pick up your reimbursement =

Within a few weeks, you should get an email from ASSU saying that a payment is available! You can go pick up your check from the ASSU office on the first floor of Old Union, behind the Axe and Palm (TAP).

[[Category:Operations]]

Getting Reimbursed

2018-07-12T05:43:15Z

Thwhite: Started new page. Edits to come.

IREC 2018

2018-07-08T23:48:20Z

Thwhite:

[[File: IREC2018pose.jpg|400px|thumb|right|frame|The team posing with the fully integrated rocket before launching it at the competition.]]

IREC 2018 was the second SSI IREC team to participate in the [[Intercollegiate Rocketry Engineering Competition]], placing second in the 30k commercial off-the-shelf motor category. The rocket was named Redshift and featured an avionics bay with a long-distance radio system, a reduced-diameter recovery system, a fiberglass airframe with a carbon fiber fin lay-up, a powered decoupling mechanism, and a software-defined GPS payload.

=Overview=

At four inches in diameter and 128 inches long, the rocket design used a minimum diameter airframe to house the Cessaroni Technology N2900 motor. With a wet mass of 58 pounds (dry mass of 27.8 lbs + 1-7 lbs lead shot ballast), the rocket was built to fly to 30,000 feet.

=Goals and Requirements=

The goal of the rocket design was to be capable of delivering an 8.8 pound payload to an altitude of 30,000 feet while employing as much student innovation as possible.

=System Design=

[[File:IREC2018cad.png|800px|thumb|center|frame|CAD model of the rocket, displaying subsystem layout.]]

The system went through a few key iterations: at first, a full staging system was considered, then a boosted dart system. After those options turned out to be relatively infeasible due to manpower and expertise issues, as well as the full system redesign that it would have required to conform to smaller airframe diameters, a move was made to a powered decoupling system.

==Avionics==

The avionics system consisted of multiple custom printed circuit board assemblies (PCBAs), which used direct board-to-board interconnects to eliminate the use of wires.

The main boards in the avionics system were:

* [[Skybass]], an altimeter developed by [[User:Johnldean|John Dean]]
* Motherboard, which was the main interface between all other boards and contained the power distribution, arming systems, and e-match firing pathways.
* Daughtership, a board for mounting the StratoLogger and Raven COTS altimeters.

==Recovery==

At apogee, the recovery system deployed a small drogue parachute for a swift, controlled descent that minimized horizontal drift. The deployment of the drogue was triggered by a CO2 canister deployment mechanism.

When the rocket reached an apogee of 1,500 feet, the main chute, which was retained in the recovered tubing by the Tender Retention System, was deployed for a soft landing.

The recover tube was selected to have a reduced diameter, smaller than that of the rocket airframe. This reduced diameter was chosen so that the parachutes would be able to deploy through the restriction in the airframe size caused by the staging ring.

==Structures==

The structure of the rocket was constructed using COTS fiberglass tubing, with a student-built carbon-fiber fin lay-up. The structures team attempted to build a custom airframe using the [[X-Winder]] filament winder, but was unable to produce a usable airframe in time using this method.

==Payload==

The payload flown on the rocket was a software-define GPS experiment. The goal was to use a COTS software defined radio USB dongle (RTL-SDR), connected to a Raspberry Pi Zero, to capture raw samples from the GPS L1 spectrum. One the rocket is recovered, the raw samples could be downloaded from the Raspberry Pi's SD card and run through tracking algorithms to solve for the rocket's position throughout the flight. The advantages of such a system were specifically for rocketry applications, namely that such a system could be more resistant to losing lock with satellites during high accelerations during flight due to high rates of doppler shift, and that it could provide a way around the GPS COCOM restrictions. The COCOM restrictions limit consumer GPS operation under high velocities and altitudes, which poses an issue for SSI's [[Spaceshot]] project.

==Staging==

The staging project was a decoupling mechanism developed for high-speed decoupling. A stepper motor drives a lead screw, on which a nut rides, lifting and lowering a set of lever arms that turn the vertical motion of the nut into horizontal motion. This horizontal motion actuates a set three clamps which affix two metal rings together. These rings are each mounted on one half of the airframe. By backing off the clamps, the rings, and consequently the airframes, are free to separate.

Issues with the staging system arose when it was near to its completion. The greatest problem was that the stepper motor would have to provide a constant holding torque in order to keep the rocket rigid during the period of time between integration and when separation was required during launch. This application of holding torque required a significant amount of power, and the original battery size resulted in a 20 minute maximum lifetime. Given the lack of adequate space to add enough batteries for a multi-hour lifetime, required in the event of launch delays, and uncertainty about the speed with which the system would drain the battery, it was decided before test launch three that the project should be cut from the final rocket design.

==Launch Operations==

Launch Operations handled all launch logistics, including food at the launch, lodging for multi-day launches, checklist organization, pre-launch packing, and transportation.

=Test Launches=

==Launch 1==

TODO: Attach launch stats and a link to the data?

==Launch 2==

==Launch 3==

=The Competition=

=Documentation=

* [https://drive.google.com/file/d/1B-4ndZNTqcyyGEI-J9Cef_EhLjfIpOm6/view?usp=sharing Project Technical Report]
* [https://drive.google.com/file/d/1JBI0Ohp3OFxwmPIfnDCpdROMip6v7sKL/view?usp=sharing Poster]
* [https://docs.google.com/drawings/d/1FZ-EO2cmcVqKG4EX4ICNpjDG-7YpyGjMEO3sUQ1J7eA/edit?usp=sharing Fast Facts Card]
* [https://drive.google.com/file/d/11V0K0Fe9YUkwESrhL8_F12ssUUUeGvvl/view?usp=sharing SRADio Podium Presentation Slides]
* [https://drive.google.com/file/d/1nuDhLZtP00u9kX1kKX7aCkomgPamfNCM/view?usp=sharing SRADio Podium Presentation Proposal]

[[Category:Rockets]]

IREC 2018

2018-07-08T17:41:29Z

Thwhite:

How to Build a Firestorm

2017-09-29T06:54:32Z

Thwhite: Created page with " � == Components == ===What’s In The Bag (or should be)=== '''External Structure\''' Bodytubes (one of each) [36”, 24”] or [34”, 26”], 54mm ID Nosecone, 54mm OD..."

�
== Components ==
===What’s In The Bag (or should be)===

'''External Structure\'''
Bodytubes (one of each) [36”, 24”] or [34”, 26”], 54mm ID
Nosecone, 54mm OD
Fin can, 54mm ID
Slimline motor retainer, 54mm ID
Rail guides (pack of two)

'''Recovery'''
4 quicklinks (2 for L1 cert)
2 KEVLAR presewn shock cords (1 for L1)
2 KEVLAR parachute coverings (1 for L1)
18” chute (not included for L1)
36” chute
Hardpoint, 54mm OD

'''Avionics Bay'''
6.25” coupler (4” coupler for L1), 54mm OD
2 bulkheads for 54mm body tube (1 for L1)
3 eyebolts ¼ x 20 (1 for L1)
5 washers ¼” (1 for L1)
8 hex nuts (1 for L1)
Brass tube ¼” ID
Fiberglass mounting board
2 charge wells
2 electric matches
altimeter
9V battery

'''Supplies Parts List'''
· Popsicle stick(s)
· Paper plate(s)
· JB Weld
· 30-minute epoxy (referred to as epoxy)
. long dowel 20-30in length, ~1cm diameter (preferably rounded)
. string (4-5ft) for threading the shock cord through u-bolt
. sandpaper (100 grit)
. thread glue
. blue masking tape (used to increase diameters of cylinders)
. drill + ¼” + ⅛” bits
. sharpie
. measuring tools (yard/meter stick, flexible measuring tape)

===Jargon ===
. DMS - disposable motor system
. RMS - reusable motor system
. Launch rails/ rail guides - ¼” aluminum extrusions to keep rocket straight on liftoff
. DD - dual deployment (two parachutes)
. SD - single deploy (one parachute)
. 54 - 54mm is the diameter of the rocket
. Forward - this way to space
. Aft - this way to land

===Personal Protective Equipment (PPE)===
. Gloves (for epoxy)
. Eye protection (for drilling)

===Designing Intelligently ===
Try to think of the design principles behind your rocket. Blindly building this will not accomplish much of anything. Question every design decision and try to improve on it – this is not set in stone. This document will ask you important questions before each section. Please try to answer and understand each one before moving on.
L1 Certifications Considerations. What is needed for an L1 cert.? No electronics, etc.
L2 Certifications Considerations. What is needed for an L2 cert.? How does this change your design?

===GrabCAD and OpenRocket ===
Ian has created a Solidworks model of the Firestorm DD and uploaded it to GrabCAD, email iangomez@stanford.edu if you would like access to it. Rebecca has created an OpenRocket model of a DD and non-DD version of the Firestorm, which should be in this folder.* [EDIT HERE]

*You should be able to do this on your own after the first workshop.

A Cross Section of an L1-Ready Rocket (not drawn to scale) [EDIT HERE]

Firestorm AV Bay

2017-09-29T02:12:22Z

Thwhite:

{{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.

See: [[How to Build a Firestorm]]

[[Category: Rockets Guides]]

Slack Directory

2017-09-26T18:55:55Z

Thwhite: /* Policy */

== 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
:* #ssi-plays-video-games - video games in general, played together.
:* #ssi-jams - ssi makes melodic noises

=== 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
:* #rockets-irec - our largest project each year
:* #rockets-argus - the Argus Daedalus Project, with RF activated cameras and so forth.
:* #rockets-charybdis - the Charybdis Daedalus Project, which is a rocket that spins like a rifle bullet.
:* #rockets-icarus - the Icarus Daedalus Project, which is a rocket that has a multi-activated reefed parachute.
:* #rockets-ksp: shooting for the Mun (playing Kerbal Space Program)

=== Balloons ===
:* #balloons
:* #balloons-valbal
:* #balloons-rf
:* #balloons-habees
:* #balloons-habhive
:* #habmc
=== Sats ===
:* #satellites
=== Bio ===
:* #biology
:* #biology-reading
:* #biology-terminator
:* #biology-backspace
:* #biology-device
=== 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|thomaswhite}} and {{slack-user|williamalvero}} - rockets coleads
:* {{slack-user|chao16}} and {{slack-user|tomusiak}} - Biology Co-Leads
:* {{slack-user|johndean}} and {{slack-user|smaldonado}} - Co-Presidents

Slack Directory

2017-09-26T18:54:45Z

Thwhite: /* Rockets */

== 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
:* #ssi-plays-video-games - video games in general, played together.
:* #ssi-jams - ssi makes melodic noises

=== 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
:* #rockets-irec - our largest project each year
:* #rockets-argus - the Argus Daedalus Project, with RF activated cameras and so forth.
:* #rockets-charybdis - the Charybdis Daedalus Project, which is a rocket that spins like a rifle bullet.
:* #rockets-icarus - the Icarus Daedalus Project, which is a rocket that has a multi-activated reefed parachute.
:* #rockets-ksp: shooting for the Mun (playing Kerbal Space Program)

=== Balloons ===
:* #balloons
:* #balloons-valbal
:* #balloons-rf
:* #balloons-habees
:* #balloons-habhive
:* #habmc
=== Sats ===
:* #satellites
=== Bio ===
:* #biology
:* #biology-reading
:* #biology-terminator
:* #biology-backspace
:* #biology-device
=== 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

Slack Directory

2017-09-26T18:52:40Z

Thwhite: /* Fun channels */

Find a Project

2017-09-21T02:44:31Z

Thwhite: /* Daedalus */

= SSI Overload =
So you've joined [https://ssi-teams.slack.com/join] Slack, maybe gone to a meeting or two, but you're not sure what you can do or what there even is to do with so many teams swirling around? Well you've come to right place! Below are all the projects each team is working on, what skills they utilize or where they're especially looking for help, and who you can contact to jump in! Think of this like a jobs listing page except that the jobs are always available and you apply by poking the person of contact and saying you want the job -- and it's probably yours.

As you can see from the length of this list, there will always be more SSI to do than you will have hours in a day, week, month, or year -- don't feel pressured to overextend yourself! If you have questions, are feeling overwhelmed, or just want to chat with someone, don't hesitate to reach out to a leadership member. ''SSI exists for, and because of, its members (that's you.) Your sanity, health, and overall well-being always come first.''

= Balloons =

== HABMC ==
HABMC has a request list a mile long, but here are a couple highlights. Feel free to slack {{slack-user|kai}} if you have ideas or questions
* 3D visualizations using Cesium or Unity
* Natural Language Processing for the commands module
* Create a mobile app using React Native
* Improved [[Balloons Radio Projects|RF integrations]]
* Overhaul security on websocket connections
* Navigation algorithms

== ValBal ==

== HABEES ==
HABEES (High Altitude Balloon Electrical Engineering Systems) is the the umbrella project for all EE & CS projects outside of ValBal (that is, largely oriented at standard profile balloon launches). Because of this, there is a nearly limitless number of possibilities and projects to pursue within HABEES -- with that said, if you're new to EE or CS, or a veteran, and just generally want some ideas of what you can make, here's a bunch! Contact {{slack-user|kirillsafin}} to discuss working on any of these!

* HONEY EE -- the primary electronics in HABEES revolve around the HONEY architecture. If you're interested in EE, you can test circuits and/or make PCB's for this architecture and have it fly with other boards. Head over to the [[Gen_2_Architecture | HONEY]] page to understand more about it. Below are some project ideas for circuits/boards you can make for HONEY!
** Motor/Servo Driver
** External/Internal Payload Heaters
** Atmospheric Gas Sensors
** Wind Sensors
** SSTV Radio Board
** WinLink Radio Email Board
** APRS Radio Board
** 12V Battery Management System
** General Purpose Radio Transceiver
** Camera Board
** CubeSat Mapping Board
** Literally anything else
* HONEY CS -- although there's a lot of electronics in HABEES, they all need some software; and, even better, that software always has room for improvement, so here's some possible projects!
** Software for tracking something (with motors/servos)
** Improving filtering/error checking for sensors
** Compression algorithms for logged & transmitted data
** Enhancing speed, quality, and throughput of CAN Bus
** Enhancing TestBench (QueenBee) test software
** Introducing/Developing radio encoding & decoding schemes
** Developing forward & reverse error correction for radio links
** Developing Point-To-Point radar link software

== BUZZ ==
BUZZ is the umbrella subteam for balloons radio projects. It operated as part of HABEES, and works to develop/try/test new radio technologies within balloons. ValBal also develops independent and system-specific radio systems. Some ideas for possible projects, as well as ongoing projects, are below: Talk to {{slack-user|kirillsafin}} and {{slack-user|ariatedjarati}} about them!
* Improved ATV link quality
* Teensy-native SSTV Transmission & Reception
* APRS development
* Native GFSK/FSK/OOK transceivers & software
* WiFi downlink/uplink (2.4GHz / 5 GHz)
* Stanford Ground Station (high gain, directional)
* Portable Field Ground Station
* Balloons National Ground Station Networ
* WinLink Global Radio E-Mail
* Digital Video/Image encoding

= Rockets =
== Onboarding ==

== Daedalus ==

Daedalus is our suite of technology development projects. The work done here pushes forwards on our long-term plan for a space shot. Each project will involve some mechanical, electrical, programming and simulations work, so feel free to join any one of them - but each focuses on a different aspect of rocketry.

Icarus - Reefed Parachute, '''Lead: Saylor'''

*Icarus is building a rocket with a reefed parachute - one which changes size during flight to adjust the rocket descent. This project will intimately involve:
** Mechanics and mechanical engineering - designing, simulating and building a deployment mechanism.
** Mechanics and aerodynamics - designing the parachute and its aerodynamic properties.
** Electrical engineering - PCB design, electrical integration and programming. Focus on high reliability and low size & power.

Charybdis - Spin Stabilization '''Contact: William'''

*Charybdis is building a rocket that spins like a rifle bullet, then stops spinning mid-air to deploy parachutes.
** Mechanical engineering - designing reliable deployment mechanism.
** Aerodynamics and simulation - designing fin system to create desired spin.

Argus - Distributed RF Camera System '''Lead: John'''

*Argus is building a rocket equipped with a new camera system, allowing us to easily take video (and possibly stream live!) from the interior and exterior of rockets as they fly.
** Electrical Engineering - circuit board design, electrical integration.
** Signals - RF & transmission tech.

== Competition (IREC/SA Cup) ==
* Structures
* Payload
* Recovery
* Avionics, '''Leads: Sharon, Julea''' {{slack-user|splatt}} {{slack-user|juleachin}}
** Design, implement, and test all the hardware and software that goes into our flight computers
** Design and manufacture structures for avionics bay and work with other subteams to implement interfaces and integration processes
** Design and test radio communications system for our rocket to talk to the ground
** Write software to parse and visualize data, build a protective cooling case for laptops & other electronics so they don't die in the blazing desert heat and dust (yes there's a story here)
* Launch Operations, '''Lead: WANTED'''
** Work with each subteam to coordinate and prepare launch materials
** Plan & execute travel and launch logistics
** Oversee launch procedures, checklists, and go/no calls
** Many more additional projects for ground support designable around personal interests
* Simulations

= Satellites =

= Biology =

* Enzymatic DNA Synthesis Methods, '''Lead: Michael Uttmark''' {{slack-user|uttmark}}
** Test commercial blocking groups for compatibility with [[Terminal Deoxynucleotidyl Transferase]]
** Chemically synthesize nucleotides with different reversible blocking groups
** Characterize and optimize [[Enzymatic Synthesis Methods | enzymatic DNA synthesis]] reaction efficiency
** Research purification methods for synthesized DNA
** Design and test your own synthesis method!
* Sequence Verification
** Execute and optimize any one of our existing verification procedures--[[Polyacrylamide Gel Electrophoresis]], [[Pyrosequencing]], or [[Ligation and Sequencing]]
** Adapt LCMS or MALDI-TOF procedures for detecting single-base addition or determining the sequence of a sample.
** Come up with new ways to verify single-base addition to a starting strand of DNA
* Microfluidic Device Design
** Design and program an [[Electrowetting on Dielectric]] microfluidic PCB
** Simulate and test how a microfluidic system would work in microgravity
** Port our DNA synthesis method to a solid substrate like controlled pore glass or streptavidin-biotin magnetic beads
** Optimize an integrated microfluidic protocol for DNA synthesis and verification on the electrowetting PCB and on the [[Beckman Biomek 2000]] liquid handling robot in lab
** Research and test other automated [https://en.wikipedia.org/wiki/Microfluidics fluid handling methods], like [https://en.wikipedia.org/wiki/Acoustic_droplet_ejection acoustic droplet ejection] or [https://en.wikipedia.org/wiki/Optoelectrowetting optoelectrowetting].
** Build a system for cooling and temperature control of the device, perhaps using [https://en.wikipedia.org/wiki/Thermoelectric_cooling Peltiers]
** Figure out how to power our PCB from a cubesat or other launch vehicle
** Build testing rigs for DNA synthesis methods that are needed for experiments in lab

= Policy =

= Operations =

== Community ==
* Come up with a theme for Special Dinner and make decorations (like a model Falcon 9!)
* Help {{slack-user|dragland}} run SSI general dinners
* Plan and run general community events like Trivia Night, Pathfinder, and Movie Night
== Diversity ==
* Build connections with engineering diversity groups on campus
* Help {{slack-user|ruqayyatoorawa}} run workshops
== Events ==
* Find an interesting company and arrange a tour or talk
* Help handle logistics of an existing talk, like by meeting an astronaut and walking him to Durand 450
* Give a CEO or Venture Capitalist a tour of ESIII
== Finance ==
* Complete reimbursements
* Apply for grants & seek out new sponsors
== Marketing ==
* Design awesome swag (t-shirts, jackets, posters)
* Reach out to reporters
* Social media guru! (Facebook, Twitter, and Instagram posts)
* Creating Snapchat filters for events
* Designing flyers for upcoming talks
* Going on launches to take pictures and videos
== Outreach ==
* Start discussions with local highschools and their science clubs
* Organize or join an existing trip to a local school
== Sponsors ==
* Pursue a sponsorship (we'll walk you through how!)
* Compile a list of bay-area aerospace companies
== Website ==
* Overhaul the budgeting system
* Give the sponsors page dynamic content
* Manage this very wiki
* Manage our public and internal websites
== Workspace ==
* Make space-themed artwork to decorate ESIII
* Plant more herbs
* Paint a mural
* Track inventory of supplies and parts

[[Category:Getting started]]