Stanford SSI Wiki - User contributions [en]

User:Jcreus

2020-08-07T04:57:55Z

Jcreus:

Hi!

Hi again!

File:Salmon.PNG

2019-04-18T08:46:35Z

Jcreus: (C) Tim Vrakas.

User:Jcreus

2019-04-18T08:17:07Z

Jcreus: Created page with "Hi!"

Hi!

SVN

2018-04-03T19:05:22Z

Jcreus: am lazy

#REDIRECT [[How to Install and Configure Altium]]

List of SVN Repositories

2017-11-18T00:20:47Z

Jcreus: updating notifications

{| class="wikitable"
! Repo Name + Link
! Contents
! Notifications In
|-
| {{altium-repo}}
| Core files for using Altium, including part libraries, templates, and examples
| {{slack-channel|altium}}
|-
| {{svn-repo|balloons-altium}}
| Non-ValBal Balloons PCB projects
| {{slack-channel|balloons-habees}}
|-
| {{svn-repo|valbal}}
| ValBal PCB, mechanical design, and simulation files
| {{slack-channel|balloons-vb-ee}}{{slack-channel|balloons-vb-me}}
|-
| {{svn-repo|biology-altium}}
| Biology PCB projects
|
|-
| {{svn-repo|rockets-altium}}
| Rockets PCB projects
| {{slack-channel|rockets-avionics}}
|-
| {{svn-repo|rockets-irec}}
| Rockets IREC simulation and analysis files
| {{slack-channel|rockets-irec}}
|-
| {{svn-repo|rockets-prop}}
| Rockets engine design and simulation files
| {{slack-channel|rockets-helios}}
|-
| {{svn-repo|satellites-altium}}
| Satellites PCB projects
|
|-
| {{svn-repo|satellites-pointr}}
| Optical and optoEE simulation files for the POINTR mission
|
|-
| {{svn-repo|raccoonworks-iceradar}}
| Radioglaciology PCB projects
|
|}

[[Category:Altium]]

Your First Altium Project

2017-11-09T01:16:04Z

Jcreus: categorization will make it possible to use novel graph theory algorithms on the SSI wiki 😏

{{guide| authors=Sasha Maldonado ({{slack-user|smaldonado}})}}

Hello! You're embarking on a journey to learn how to use Altium Designer, SSI's preferred circuit board design tool made available thanks to the considerable generosity of the folks at Altium Ltd.

This guide will assume that you have successfully completed [[How to Install and Configure Altium|installing and configuring Altium]]. Please complete that first before proceeding.

==Major Key==

===Updating Your SVN===

First, you'll want to update your Altium SVN. This is good to do periodically, and commit messages in {{slack-channel|altium}} will help you know when there are important changes that you will want to update to get.

To do this, find your Altium SVN root folder. This will likely be called "altium-core" or "SSI-SVN-Altium" (I will refer to it as "altium-core" from now on). Right click and hit "SVN Update." Depending on how much you have to sync up, this may take a minute or two, and will complete on its own.

===Open Altium===
[[File:ProjectsPanel.png|thumb|200px|right|This is a super useful panel to have open pretty much whenever you're in Altium.]]

If you haven't already :)

===Open SSI.LibPkg and Recompile===

If you do not see the "Projects" panel of your Altium window (see image on right - if open, the panel is typically on the left side of your screen), you will need to open it. This can be done in "View → Workspace Panels → System → Projects," also accessible with the keyboard shortcut {{altium-shortcut|v → w → s → p}}.

From Altium, go to File → Open Project... and open altium-core/libraries/intlib/SSI.LibPkg (its file name may just show up as "SSI"). Open the file; it should expand in your Projects panel, as shown at right.

Right click in your Projects panel on "SSI.LibPkg" and hit "Compile." This will start the compilation process, which will take about a minute. This is important to do every time you update the SVN (unfortunately). Long term solutions to eliminate this requirement are being pursued but for now it's how things work.

===Make Your Own Copy of Major Key===

From outside of Altium, go to altium-core/starter-projects/ and copy the folder "major-key-starter." Copy it into the folder called "working," and change its name to "major-key-<your-name>." Go into that folder and double-click on "major-key.PrjPcb" (possibly just showing up as "major-key") to open it in Altium.

===Check Out The Schematic===

From Altium, look at the Projects panel, and expand major-key. Open "TopSheet.SchDoc."

This document is the "top sheet" (hence the name) for the project. A board in Altium consists of one or more "sheets," pages of the electrical schematic. They are arranged hierarchically - every design with more than one sheet needs a "top" sheet and then "subsheets," which can be nested an arbitrary number of times (subsheets can have subsheets, which can have subsheets, which can have subsheets...) The green box (known as a "sheet symbol") represents a subsheet, containing the schematic for an Arduino microcontroller. You can open that sheet either from the Projects panel or by hitting {{altium-shortcut|ctrl + double click}} on the sheet symbol.

We'll make one small edit to the subsheet for this project, and it may prove helpful to look at as an example of what an Altium schematic can look like.

====Add Missing Sheet Entries====

The yellow symbols on the right edge of the sheet symbol are called "sheet entries." They pass signals from the subsheet up to the top sheet, kind of like parameters in a function. Each sheet entry has a name and a direction - "input," "output," "bidirectional," and "unspecified."

[[Category:Getting started]]
[[Category:Altium]]

Signal to noise ratio

2017-09-18T07:57:52Z

Jcreus: fixing double redirect

#REDIRECT [[Signal-to-Noise Ratio]]

Dna synthesizer

2017-09-18T07:57:35Z

Jcreus: fixing double redirect

#REDIRECT [[DNA Synthesizer]]

SSI DNA synthesizer

2017-09-18T07:57:18Z

Jcreus: fixing double redirect

#REDIRECT [[DNA Synthesizer]]

Policy Team

2017-09-18T07:53:10Z

Jcreus:

The Policy team researches the legislation, market trends, history, and philosophy that has affected the development of the space industry. The team will be launching a student-taught class this Autumn quarter, [[AA 47SI: Why Go to Space?]].

The current team lead is Rishi Bedi.

<noinclude>[[Category:Policy| ]]</noinclude>

Ligation and Sequencing

2017-09-18T07:41:17Z

Jcreus:

==Overview==
Ligation and Sequencing is a method to detect single or multiple base addition to a single strand of DNA by [[Enzymatic Synthesis Methods]]. This detection method involves sequencing the added bases with a commercial sequencing service. The segment to be sequenced is effectively put in the middle of the starting DNA to avoid poor quality sequencing reads usually encountered at the ends of linear DNA.

==Starting DNA==
Instead of adding to a DNA oligonucleotide (~15 nt long), the addition will be performed on a single linear DNA strand with a known sequence that is long enough to be circularized (~1 kb). Long single-stranded DNA can be obtained by cutting a [https://www.neb.com/products/n4040-m13mp18-single-stranded-dna#pd-description single-stranded DNA plasmid] with restriction enzymes. Single-stranded DNA cannot be amplified by PCR.

==Ligation==
Once multiple bases have been added to the linear single strand of DNA, the DNA will be circularized with [http://www.epibio.com/enzymes/ligases-kinases-phosphatases/dna-ligases/circligase-ssdna-ligase?details single-stranded DNA ligase]. If the DNA is not circularized, the extended 3' end will be ligated to the 5' end of another linear piece of DNA, resulting in the same desired sequence.

==Sequencing==
Once the DNA sample is purified to remove any remaining nucleotides or enzyme, the circularized DNA can be sent for sequencing by a commercial sequencing service. The primer used to sequence the DNA should be a reverse primer taken from ~200 nt downstream of the 5' end of the original linear starting DNA. The sequencing results should reveal which bases were added and give a rough quantification of addition efficiency.

[[Category:Biology]]

Category:Alumni

2017-09-18T07:41:06Z

Jcreus: Created page with "Category:Operations"

[[Category:Operations]]

How to Join SSI's Alumni Network

2017-09-18T07:40:58Z

Jcreus:

Thanks for stopping by and learning how to become part of our growing community of SSI Alumni & Friends! Whether you are a recent grad or a community member interested in SSI, we'd love to stay in touch with you!

= [https://alumni.stanford.edu/get/page/groups/overview/?group_id=0038994816 Join our Stanford Alumni Group/Mailing List] =
Once you've joined, you'll be added to future discussions and announcements sent to [mailto:ssi_alum@discussions.stanford.edu ssi_alum@discussions.stanford.edu], and you can post to the list to share your own events, space news, etc as well. You should receive notifications about postings via email, unless you change your delivery option under "My Profile/Preferences." Please keep the postings relevant.

= [https://internal.stanfordssi.org/users/questionaire Join our Internal Database] =
We love having our alumni offer advice with design reviews, host us for tours, and more. Sign in with any Google account and please fill out our short form so we know where you are, what you do, and how you'd like to help the group. In return for joining our database (even if you choose not to get involved!), you'll receive a copy of our quarterly newsletter. If anything changes later on, you can easily log back in and update your information.

= Stay Connected with SSI! =
*[https://www.facebook.com/StanfordSSI/ Like us on Facebook]
*[https://twitter.com/stanfordssi Follow us on Twitter]
*[https://www.instagram.com/stanford_ssi/ Check out our Instagram]
*[https://www.linkedin.com/groups/6774947 Connect with others on LinkedIn]

= Got Questions? =
If you have questions about anything, don't hesitate to [mailto:rebeccawong@stanford.edu contact our current SSI Alumni Coordinator], Rebecca.

[[Category:Alumni]]

High-powered rockets

2017-09-18T07:40:38Z

Jcreus: ohp

{{rocket-stub}}
[https://en.wikipedia.org/wiki/High-power_rocketry]

[[Category:Rockets]]

High-powered rockets

2017-09-18T07:40:22Z

Jcreus:

{{rockets-stub}}
[https://en.wikipedia.org/wiki/High-power_rocketry]

[[Category:Rockets]]

Microfluidics

2017-09-18T07:40:03Z

Jcreus:

Microfluidics is the study of small amounts of fluid, typically around ~1 microliter in volume. The study of fluids around ~1 nanoliter in volume is sometimes called nanofluidics.

==Microfluidic Zero-Gravity DNA Synthesizer==
SSI Bio is building a [[DNA synthesizer]] using microfluidics for their 2016 pilot project.

[[Category:Biology]]

Stanford Student Space Initiative (SSI)

2017-09-18T07:39:49Z

Jcreus:

{{teams-table}}

The Stanford Student Space Initiative (SSI) is a completely student-run organization founded in 2013 with the mission of giving future leaders of the space industry the hands-on experience and broader insight they need to realize the next era of space development.

SSI is the largest project-based group on campus. We’re the gathering place for people who want to act on their interests in space. Since 2013, we’ve flown a zero gravity experiment with NASA, helped build multiple CubeSats, inspired 60 teams in 20 countries to launch high altitude balloons, certified over 30 students for high powered rocketry, hosted over 100 speakers at talks and conferences, been featured in media like Popular Science, and helped our members intern and work at top aerospace companies and organizations.

Over the next year, our teams will launch a suite of [[:Category:Rockets | rockets]] designed to test novel rocketry technologies and compete for international prizes, build the first [[:Category:Satellites | satellite]] of our own, continue to send [[:Category:High Altitude Balloons | high altitude balloons]] across the country and beyond, develop the first in-space [[:Category:Biology | DNA synthesizer]], teach the second edition of our [[AA 47SI: Why Go to Space?|space policy class]], and organize speaker events and workshops with industry leaders.

We invite you to join us.

[[Category:Stanford Space Initiative| ]]

STINGR Gesture Specification I

2017-09-18T07:39:21Z

Jcreus:

Below is STINGR Gesture Specification I -- the original concept for STINGR Gestures, which was replaced by STINGR Gesture Specification II.

== Gesture Specification ==
As mentioned above, a Gesture consists of a series of frames, each with a specific purpose. Each Gesture is transmitted on the CAN Bus, and allows all boards to determine if a Gesture is targeted towards them, and act appropriately. This section defines the specification of a Gesture, including a description of each of the frames.

More explicitly, a Gesture looks as so, with the leftmost frames being transmitted first, and the rightmost frames being transmitted last.

{| class="wikitable"
| style="background-color: #4CC9FF;"|
Type (Req/Resp) (1 bit)
| style="background-color: #8AFFDF;"|
State Flags (7 bits)
| style="background-color: #FFA6CE;"|
Source Identifier (8 bit)
| style="background-color: #EDFF7A;"|
Destination Identifier (8 bit)
| style="background-color: #AD6DF9;"|
Data (4-500 bytes)
| style="background-color: #C25959;"|
Checksum (8 byte)
|}

=== Type Frame ===
The Type frame, the first frame in a Gesture, is a 1 bit frame that determines whether a Gesture is a request from one board to another, or a response from one board from a prior request. This frame is a 0 for a request, and a 1 for a response.

=== State Flags Frame ===
The 7 bits following the Type bit are the State Flag bits. This 7-bit frame allows transmitting boards to provide specialty signals to the receiving board. A low bit indicates a flag that isn't down, while a high bit indicates a raised flag. The current flags are as follows, from LSB to MSB.

{| class="wikitable"
|High Priority
|Low Priority
|No Override
|Reserved
|Reserved
|Reserved
|Reserved
|}

The flags are defined as follows:
* '''High Priority''': The board receiving the request should cease all operation immediately and respond to the request before continuing.
* '''Low Priority''': The board receiving the request can wait to respond to the request until most convenient.
* '''No Override''': The board receiving the request has no choice but to comply with the request sent -- it should not exert any effort attempting to question or combat the transmitting board. If this flag is low, a board receiving a request has the ability to ask the transmitting board for clarification or request a re-consideration. If this flag is high, the receiving board should execute the request regardless.

Flags are stacking, meaning multiple flags can be high. For example, a high high-priority flag and high no-override flag means a board not only must comply without question, but it should do so immediately prior to continuing any of its standard operations.

=== Source & Destination Identifiers ===
The Source & Destination Identifiers, the second and third frames in a Gesture, are 8 bit frames that indicate the source of the Gesture. Each board developed for the HONEY architecture is catalogued and given a unique identifier code. These unique identifiers allow boards to identify who a request or response from, and respond accordingly. Note that each unique board is given a unique identifier -- The Count, the first HONEY-compliant avionics board, has the identifier of 0, but a subsequent revision of avionics would acquire a new identifier code. This allows boards to be aware of the specific revisions that are flying in the stack -- allowing them to dynamically take advantage of the utilities of newer boards as they are added. The identifiers are encoded into the STINGR suite, and one can call a simple function to determine what board was the source or destination, without memorizing or encoding any of these identifiers in local board code.

There is also a unique, reserved designator, which is designator 256 (11111111). This designator is reserved for the broadcast functionality. Gestures with a destination identifier of 256 target ''all'' boards in the stack. That is, if a board wishes to notify all boards in the stack of some particular information, it can do so by designating a destination identifier of 256 -- all boards are configured, via STINGR, to process these gestures, even though the destination identifier isn't their own unique identifier. These are formally referred to as ''broadcast gestures''.

The following are the current identifier codes, as of writing (June 21, 2017).

{| class="wikitable"
|-
|The Count (Gen 4 Avionics)
|00000000
|-
|Biscuit (Gen 2 BMS)
|00000001
|-
|Macaw (Gen 1 Radio)
|00000010
|}

=== Data Frame ===
The data frame carries the entirety of the request or response. This frame is variable in length, and can be as little as four bytes (at a minimum) or as much as 500 bytes (although this isn't a strict limit, but messages should seldom exceed 496 characters).

The data frame, in order to accommodate the large variety of possible data types that might arise in the HONEY architecture, is encoded strictly in ASCII characters as a char buffer. This allows boards to send messages as character strings -- STINGR is designed to understand and decode standardized messages, but this framework allows boards to send absolutely any data.

The payload portion of the data frame can be empty -- in this case, the data frame consists of four bytes. These are the start and end designators, which designate the start and end of the data payload. The start designator is '/1' while the end designator is '/0'

{| class="wikitable"
|Start Flag (2 bytes - '/1')
|Payload (0-496 bytes)
|End Flag (2 bytes - '/0')
|}

=== Checksum Frame ===
The Checksum Frame performs a checksum operation on the payload of the data frame, producing an 8-byte output. Receiving boards should perform an identical checksum operation on the data frame, and compare it to the received checksum value to verify data integrity. Identical checksums indicate proper transmission, while mismatched checksums indicate transmission error.

The current checksum calculation is as follows:

Each byte in the data payload (meaning, data excluding the start and end designators), takes its decimal ASCII value, which is multiplied by its position in the data frame. The sum of these products is the checksum value, which is 8 bytes.

Take the following data frame:

{| class="wikitable"
|/
|1
|H
|E
|L
|L
|O
|/
|0
|}

The checksum is performed on the data payload, meaning only '''HELLO'''. The calculation for each byte in the frame is as follows, following the guideline of taking the position of the character and multiplying that by its ASCII value:
{| class="wikitable"
|72 * 1 (H)
|69 * 2 (E)
|76 * 3 (L)
|76 * 4 (L)
|79 * 5 (O)
|}

The sum of these products is 1,137, the checksum value.

== Operation ==
The following operations are defined by STINGR Gesture Specification I -- for legacy operations defined by STINGR Gesture Specification I, visit its page.
STINGR has a specific control flow that must be strictly followed to ensure proper operation. Luckily, most of this is handled within the STINGR internal code. It is described here in full detail, however, for posterity, debugging purposes, and for context in the following section, which enumerates specific methods and their purposes/parameters.

=== Initialization ===
Each board using STINGR must initialize the suite in order to properly utilize it. This initialization routine allows proper communication between boards in the stack, as well as gives vital information to each board about the actual structure of the stack, which isn't formally known unless hardcoded (a poor choice).

When a board initializes STINGR, it must provide its unique identifier. Once STINGR obtains the unique identifier of a board, it will send a broadcast gesture on the CAN Bus -- this signal has a destination identifier of 256 -- that is, it is sent to all boards in the flight stack. This is the first gesture sent out by a board, and its definition is as follows:

{| class="wikitable"
| style="background-color: #4CC9FF;"|
Type -- 1 (Response)
| style="background-color: #8AFFDF;"|
State Flags -- 0 (no flags)
| style="background-color: #FFA6CE;"|
Source Identifier (8 bit)
| style="background-color: #EDFF7A;"|
Destination Identifier -- 256 (broadcast)
| style="background-color: #AD6DF9;"|
Data -- '/1/0' (empty payload)
| style="background-color: #C25959;"|
Checksum (8 byte)
|}

This particular gesture definition is reserved, and is known as the ''beacon gesture''. It is defined by a strict Type of 1, 0 State Flags, a unique source identifier, a broadcast destination identifier, an empty payload, and a checksum.

The beacon gesture indicates to all boards in the flight stack the presence and identity of a given board. Since all identifiers are enumerated within the STINGR source code, a beacon gesture allows any board to identify what boards are in the stack. Hence, if, for example, Macaw were to send a beacon gesture, with its identifier of 00000010, all boards would receive this gesture, correlate the identifier to that of Macaw, and consequently be aware of the presence of Macaw in the flight stack.

Once a board in the flight stack has sent its beacon gesture, it is now ''live'', and other boards are allowed to send it messages using STINGR. By means of each board in the flight stack sending out a beacon gesture, all boards will be aware of the full definition of the flight stack.

=== Standard Mode ===
Once STINGR passes initialization, it enters ''Standard Mode''. In Standard Mode, a board is able to send and receive gestures via the CAN Bus through STINGR. A board may send a message as frequently or infrequently as desired in Standard Mode. The other defining characteristic of Standard Mode is that, in Standard Mode, STINGR will transmit the beacon gesture every 60 seconds. This is known as the heartbeat gesture, and allows boards in the stack to continue to acknowledge the presence of a board, as well as register a boards presence if they hadn't already registered it.

=== Silent Mode ===
Silent Mode can be triggered by the ''Silence Gesture'', a gesture reserved for the avionics board. Silent Mode can be triggered for a specific board in the flight stack, or for the entirety of the flight stack.

To put a board into Silent Mode, the avionics transmits a reserved gesture that has a payload of '/0'. The Avionics can request a specific board to enter silent mode by specifying a destination identifier, or it can request all boards to enter silent mode by using the broadcast identifier.

Silence Gesture:
{| class="wikitable"
| style="background-color: #4CC9FF;"|
Type -- 0 (Request)
| style="background-color: #8AFFDF;"|
State Flags -- 0 (no flags)
| style="background-color: #FFA6CE;"|
Source Identifier (avionics identifier)
| style="background-color: #EDFF7A;"|
Destination Identifier
| style="background-color: #AD6DF9;"|
Data -- '/1/0/0' (payload is '/0')
| style="background-color: #C25959;"|
Checksum (8 byte)
|}
There is, additionally, a gesture to reverse this, and put a board back into Standard Mode -- this is the ''Unsilence Gesture'', which is identical to the Silence Gesture, except the payload is '/1', as shown below.
Unsilence Gesture:
{| class="wikitable"
| style="background-color: #4CC9FF;"|
Type -- 0 (Request)
| style="background-color: #8AFFDF;"|
State Flags -- 0 (no flags)
| style="background-color: #FFA6CE;"|
Source Identifier (avionics identifier)
| style="background-color: #EDFF7A;"|
Destination Identifier
| style="background-color: #AD6DF9;"|
Data -- '/1/1/0' (payload is '/1')
| style="background-color: #C25959;"|
Checksum (8 byte)
|}

[[Category:HONEY]]

Durand

2017-09-18T07:38:36Z

Jcreus:

{{problems}}

=[[Mission Control]]=

Durand 390 is SSI's headquarters.

=[[Durand 354 | 354]]=

=393=

What it is useful for, policy on use

=[[Durand 450 | 450]]=

Here is how to get to it, how to reserve it

=More useful links=

[link to durand address page Here is the associated Stanford Page.]
[link to campus map for durand Here is the associated campus-map.stanford.edu location.]

[[Category:Operations]]

Vector Graphics in Altium

2017-09-18T07:37:50Z

Jcreus:

Altium currently lacks well-integrated support for putting vector graphics onto the silkscreen. There are a couple of workarounds for this. SSI's preferred option for vector graphics that will be re-used is to add them to the SSI font.

For one-off's, there is the PCB Logo Importer Script provided by Altium and documented [http://wiki.altium.com/pages/viewpage.action?pageId=6848718 here] or in [http://letanphuc.net/2016/05/put-logo-pcb-altium/ more detail here].

== Using an existing logo ==

The SSI Altium libraries SVN includes an "SSI Logos" font that already contains most of the logos you might need (including SSI logos, team logos, and sponsor logos). You can find the font here:

https://subversion.assembla.com/svn/stanfordspaceinitiative/libraries/logos/SSI

Install the font by double-clicking and pressing Add or Install.

Then launch Altium and insert a String on the Top or Bottom Overlay layer. Select TrueType font and choose "SSI Logos" as the font.

Each logo corresponds to a particular character. For example, typing 'A' will insert the SSI Logo. You can find a full list of available graphics here:

https://stanfordssi.assembla.com/spaces/stanfordspaceinitiative/subversion/source/HEAD/libraries/logos/SSI/SSI_LogosKey.txt

== Adding a new SVG ==

[[Category:Altium]]

Mission Control

2017-09-18T07:37:14Z

Jcreus:

=Location=
[[File:Durand_450_Location.PNG]]

[[Category:Operations]]

List of Missions

2017-09-18T07:36:43Z

Jcreus:

This page contains a list of notable tests or launches which have been given mission status (denoted by a mission patch). The mission patch system was introduced in 2015.

<gallery widths=200px heights=200px>
|align=center
File:Rsz 11ssi 19.png|<center> [[SSI-19]], Balloons Team, May 16, 2015 </center>
File:Rsz ssi-22.png |<center> [[SSI-22]], Balloons Team, May 31, 2015 </center>
File:SSI-1E4.png|<center> [[SSI-1E4]], Satellites Team, June 4, 2015 </center>
File:Ssi 23.png |<center> [[SSI-23]], Balloons Team, October 24, 2015 </center>
File:Ssi 24.png |<center> [[SSI-24]], Balloons Team, October 24, 2015 </center>
File:Ssi 25.png |<center> [[SSI-25]], Balloons Team, October 24, 2015 </center>
File:SSI-R1.png|<center> SSI-R1, Rockets Team, February 6, 2016 </center>
File:SSI-31.png|<center> [[SSI-31]], Balloons Team, February 13, 2016 </center>
File:SSI-38.png|<center> [[SSI-38]], Balloons Team, May 8, 2016 </center>
File:STAR-CROSSD.png|<center> [[STAR-CROSSD]], Satellites Team, May 2016 </center>
File:SSI-39.jpg|<center> [[SSI-39]], Balloons Team, May 30, 2016 </center>
File:SSI-40.png|<center> [[SSI-40]], Balloons Team, June 2016 </center>
File:SSI-41.png|<center> [[SSI-41]], Balloons Team, June 15, 2016 </center>
File:SSI-42.png|<center> [[SSI-42]], Balloons Team, July 12, 2016 </center>
File:SSI-R6.png|<center> SSI-R6, Rockets Team, July 6, 2016 </center>
File:SSI-1E4-2.png|<center> SSI-1E4-2, Satellites Team, August 20, 2016 </center>
File:ZeusBadge.png|<center> [[SSI-44]], Balloons Team, October 22, 2016 </center>
File:SSI-47.png|<center> [[SSI-47]], Balloons Team, November 5, 2016 </center>
File:SSI-R8.jpg|<center> SSI-R8, Rockets Team, November 19, 2016 </center>
File:SSI-48.png|<center> [[SSI-48]], Balloons Team, December 11, 2016 </center>

</gallery>

[[Category:Stanford Space Initiative]]

PlatformIO

2017-09-18T07:36:24Z

Jcreus:

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

[[Category:Raccoonworks]]
[[Category:Getting started]]

SSI Press

2017-09-18T07:36:01Z

Jcreus:

Check out some of the top news about SSI and its founding!

[https://medium.com/stanford-select/countdown-c8a657779585#.t6jox1juf Stanford Journal Article on SSI], featuring an interview with former Co-President Charlex Cox, Stanford 2015 BS/2016 MS.

[http://www.stanforddaily.com/2014/01/30/stanford-students-to-conduct-experiment-in-reduced-gravity/ Stanford Daily article on SSI's first Zero-G project], featuring an interview with former Co-President Paul Warren, Stanford 2017.

[http://www.stanforddaily.com/2015/03/30/final_kj-student-space-initiative-triples-in-size-incorporates-new-research-areas/ Stanford Daily article on the growth of SSI] over its first two official years as a student group.

[http://www.cnet.com/news/aiming-sky-high-in-global-balloon-challenge/ CNET article on SSI's participation] in the first ever Global Space Balloon Challenge

[http://www.stanforddaily.com/2013/10/10/the-new-space-race/ Stanford Daily Op Ed on New Space] by former President and co-founder, David Gerson, Stanford 2014.

[[Category:Operations]]

History of the SSI Logo

2017-09-18T07:35:44Z

Jcreus:

Many of you may wonder where the artistic, beautiful SSI logo came from. Well, here is that story. You may think that it improved with time, but really, the first logo was the best we ever had - except that some people just didn't quite see the beauty in it... that's probably why we have no shirts with it on them.

The idea for a logo began in the spring of 2012 when SSI was just getting started and needed a logo for branding material that we were handing out about the group. David Gerson, the president of the time (full disclosure, I'm writing this article) had absolutely no artistic talent (or taste as will become apparent shortly) and so needed to outsource the idea. Kyle Anderson had made an image of a Stanford S with a rocket in the middle instead of a tree, so he was recruited to iterate on ideas and in Gerson's opinion, the best version was this - a Stanford S with a star in the middle with some stuff circling it (like the NASA meatball logo)

[[File:Logo_idea.jpg|600px]]

With no ability to turn this into something useable, Gerson sent this to a CS friend Omar Diab with instructions to make something space related and useable. Without much to go on, Omar leveraged the NASA meatball logo with a Stanford S in the middle. But Gerson wanted to make it clear that the group wasn't just about rockets, and so requested the addition of other things on the outside - because the other projects at the time were a PhoneSat and Lunabotics, the satellite and excavator were chosen which resulted in SSI's first official logo. Though there was an option (that wasn't chosen) that showed a moon rover instead. Omar definitely wouldn't have chosen to put these things on the outside himself, but Gerson insisted.

[[File:Stanford space logo excavator.png|600px]]

[[File:Stanford_space_logo-rover.png|600px]]

And yes, at the time our name was the Stanford Spaceflight Initiative. It would be months until we were forbidden from using Stanford in the name (we weren't an approved group) or using the Stanford S with a rocket in the middle (breaks branding rules). When that happened, we creatively changed things up to remove the Stanford S (we were too stubborn to change our name until later)

[[File:Ssi logo without stanford.png|600px|]]

Despite it obviously being amazing, Robert Jackson and Ben Todd soon started a campaign to get a better logo. We went through many iterations of things to try and find something that looked good, but many never saw the light of day. We even tried to hold a logo competition where the winner would receive $100, but that didn't result in anything. Eventually, Charlie Cox and Robert Jackson (second Co-Presidents of SSI) settled on a new version of the logo, which was actually a bit respectable:

[[File:SSI logo 2.jpg|600px|]]

This served faithfully, until the next generation of SSIers decided it was too phallic and modified it slightly to result in the logo we have today. It seems we did something right, because for the first time, a logo has lasted past a presidential transition.

[[File:Current_logo.png|600px]]

[[Category:Operations]]

Git and GitHub

2017-09-18T07:35:11Z

Jcreus:

{{Guide|authors=Sasha Maldonado {{slack-user|smaldonado}}}}

Git is a version control software that tracks changes made to software files and allows unsuccessful changes to be easily reverted. Projects in Git are stored as repositories, which are folders containing a list of files maintained by Git. GitHub is an online service that allows a team of users to easily work together on code, tracking who made which changes, allowing different users to pursue different solutions simultaneously, and helping all members of the team keep their local copies of shared code up to date. GitHub allows users to upload and download repositories, allowing team members to share new code they have written and to update their code to include their colleagues’ contributions.

==Setting up Git and GitHub==
===Checking for Git===
Git is built into most Unix-based operating systems (OS X and Linux). On a Unix system, find Terminal (on Mac, in Applications/Utilities) and type “git”. If a dialogue comes up saying that the command “git” is not found, you will need to download Git as described below. Otherwise proceed to “Setting Up Github.”
===Downloading Git===
On Windows systems and Unix systems that failed the test above, you will need to download a Git client. Go to the [https://git-scm.com/downloads Git download] page and pick out a download for your operating system. After downloading and installing Git, you should now have a program called Git Bash - this program is functionally equivalent to Terminal for all uses later in this document, and all of the commands described should have the same function in Git Bash as they do in Terminal.

===Setting Up GitHub===
Sign up for a free account on GitHub’s website. A recommended convention for usernames is your first initial followed by your last name. It is helpful for your username to resemble your real name so that people can easily tell who contributed what code so that they know who to contact with questions. After creating an account, you will need to be added to the SSI GitHub organization. GitHub does not currently have a feature to allow users to request to join organizations; to be invited, email or Slack message any member of the “Owners” group. The current lead GitHub administrator is Sasha Maldonado, {{slack-user|smaldonado}}.

==Git Usage==
===Navigation===
If you are familiar with basic shell commands (cd, ls), you can skip to the next section, which discusses more Git-specific commands. All commands are briefly summarized in a [[#Terminal/GitHub Basic Command Cheat Sheet|Cheat Sheet]] at the end of this document.

Git is run from the command line (Terminal/Git Bash), a text-based interface into which commands can be typed to perform actions. A default command line will look something like this, with “smaldonado” replaced with your username.

<tt>
smaldonado:~ smaldonado$
</tt>

The command line maintains a “pointer” to a specific folder in your file system, which is assumed as the reference for all file names typed into commands. When a new terminal (either Terminal or Git Bash) window is opened, the pointer will point to a default location denoted by a tilde, “~”.

<tt>
smaldonado:~ smaldonado$ pwd 
/Users/smaldonado
</tt>

The command pwd (“print working directory”) causes the console to print the current location of the pointer. In the example above, pwd is used to show the real location of the default “~” directory. Note that the example above is the location of the default directory on OS X and that it will be different on Windows and Linux operating systems. Your pointer’s current directory, relative to the default, will be shown in the first part of the command line after the colon (see below for an example).

To change the location of the pointer, the command cd (“change directory”) is used. Commands beginning with a “/” start from your computer’s root (lowest) directory, and are generally not necessary. All other cd commands are assumed to be relative to the pointer; for example, the command below moves the pointer to a folder called “GitHub” stored in the default directory.

<tt>
smaldonado:~ smaldonado$ cd GitHub 
smaldonado:GitHub smaldonado$ pwd 
/Users/smaldonado/GitHub 
</tt>

When changing to a folder with a space in its name, you will need to “escape” the space by placing a “\” character in front of it. For example, to switch to a folder called “GitHub Projects,” you would need to type the folder name as shown below.

<tt>
smaldonado:~ smaldonado$ cd GitHub\ Projects
</tt>

The cd command also includes an autocomplete feature; by typing the first several letters of a folder name and then hitting TAB, the terminal will attempt to find a directory beginning with the letters typed in. This feature is good for filenames with spaces, as they will automatically be escaped.

The cd command can be used to move several levels down in one line. For example, the following is a valid command that moves the pointer to the folder “opt-comms” within “GitHub.”

<tt>
smaldonado:~ smaldonado$ cd GitHub/opt-comms/
</tt>

The “/” character within a file name shows that the text to the right of it is a subfolder. Ending a location with a “/” (as above) is optional and does not affect the command being run. You can also go up a subfolder level by using “../” in a file path. For example, to switch to a “rockets” folder also stored in “GitHub” from “opt-comms,” you would type the highlighted line below.

<tt>
smaldonado:opt-comms smaldonado$ pwd 
/Users/smaldonado/GitHub/opt-comms 
smaldonado:opt-comms smaldonado$ cd ../rockets/ 
smaldonado:rockets smaldonado$ pwd 
/Users/smaldonado/GitHub/rockets 
</tt>

FInally, simply typing cd will take the pointer back to its default location. To help illustrate this, the following list of commands is provided. All listed commands perform the same function of moving the pointer back to the default location.

<tt>
smaldonado:~ smaldonado$ cd 
smaldonado:~ smaldonado$ cd ~ 
smaldonado:~ smaldonado$ cd ~/ 
smaldonado:~ smaldonado$ cd /Users/smaldonado 
smaldonado:~ smaldonado$ cd /Users/smaldonado/ 
</tt>

The command '''ls''' (“list”) shows the names of all files and folders stored in the folder the pointer is currently on. This is quite useful, and strings of cd and ls commands are common.

There are many other useful commands that can’t be covered here, and the discussions above are quite cursory. To get more detailed information about any command, use the man (“manual”) command, followed by the name of another command.

<tt>
smaldonado:~ smaldonado$ man ls
</tt>

The above line will display the manual page for the ls command; scroll through it using the arrow keys, and exit by hitting the “q” key. The language for manual pages takes a bit of getting used to, and for introductory purposes the internet may prove a better resource for learning the functions of commands. However, the manual page is the definitive reference for how to invoke all of the possible functions of a given command.

==Configuring Git+GitHub on a Computer==

Once you’ve completed all of the setup for both Git and GitHub, you can begin to download the SSI code. First, it is strongly recommended that you create a “git” folder in or close to your default directory. You can either do this through your computer’s file system or from the command line with the command mkdir ‘git’ (mkdir, “make directory”). cd to this directory (or wherever you would like to store local copies of SSI code).

SSI’s code is broken up into repositories based on project. All of the available SSI repositories (“repos”) are available on the SSI GitHub page. To download a repo, go to its page from the SSI main page and locate the “HTTPS Clone URL” and copy it to your clipboard (as shown in the right of the image below).

[[File:GitHubExample.png|center|500px]]

Then, in your terminal (in your designated GitHub directory), type:

<tt>
git clone
</tt>

Followed by a space and the URL you copied from GitHub. You may need to right click (as opposed to ctrl/cmd+v) in order to paste the URL. Hit enter, and you should begin to download the selected repository. Once it’s done, you have a local copy! You can repeat this process with other repositories as desired.

==High Level Git and GitHub Overview==
Git (with GitHub) contains four different “layers” to be aware of:

[[File:GitHubLayers.png|center|500px]]

*The ''Working Directory'' refers to a real folder stored on your computer containing real, editable files that you can add, delete, move, and change harmlessly.
*The ''Index'' (AKA ''Staged Commit'') holds snapshots of files before they are more permanently committed. The git add command takes snapshots of files in the working directory at the moment the command is run and puts those snapshots into the Index.
*The ''Commits'' layer contains a record of snapshots made over the lifetime of a repository. The Commits begin with a snapshot of the first set of files added to the repository, and in each subsequent commit those files have been somehow modified; changed, added, deleted, moved, etc. Essentially, each commit is a saved state of the project folder, and any commit - or even individual files from a past commit - can be easily reverted to if it is determined that subsequent changes are undesired. The git commit command turns the contents of the Index into a new commit in the Commits layer.
*The ''Remote'' layer functions much like the Commits layer, storing a lifelong history of commits synchronized across users and, in the case of the SSI GitHub, publicly viewable. This publicity means that anyone can keep up to date with the code put in the Remote layer, but only members of the SSI team can add their changes to the SSI Remote repository. The command git push adds all of the commits made locally since the last git push to the Remote layer.

One important Git concept that these four layers don’t communicate is branching. Git can track more than one lineage of changes to a set of files; each history of changes starting from a common commit is a branch. One of Git’s most powerful features is being able to merge divergent edits made to a repository - sometimes even to the same file - allowing individuals to simultaneously pursue different lines of edits and then combine their work into a single releasable set of files. This feature has insofar not been often used in SSI, but it is still important to mention. Every local instance of Git has a “working branch” that all of its commits are added to (by default, “master”), and when these commits are pushed to GitHub, they are added to an online branch with the name used by the local working branch. Without making changes to your Git installation, you will by default use the “master” branch, which is generally okay for SSI purposes. See [[Advanced SSI GitHub Usage]] for more on when and how to use branches.

==Using Git Commands==
Note: In the syntax examples below, the items in angle brackets (<>) are descriptions of what should be included in each command. Do not include the angle brackets.

All of the following commands (except git clone) must be run from your terminal while your working directory is the relevant repository folder (for example, “GitHub/opt-comms”). These commands all operate on only one repository at a time. git clone must be run from your desired GitHub folder, and will create a folder for the repository being cloned.

'''git clone''' is run once when first beginning to work with an online repository. git clone copies the most recent online commit into a new working directory and locally saves the commit history stored online. It also does the configuration needed to make git push and git pull work.

Syntax:
<tt>
git clone <https clone link>
</tt>

'''git add''' adds snapshots of files currently in the working directory to the index. Subsequent changes will not be added to the index unless another git add command is run.

Syntax:
<tt>
git add <filename of file to be added> 
git add --all 
</tt> - adds all files changed, added, deleted, etc.

'''git status''' shows what files have been changed since the last locally stored commit and shows which of those changed files are in the index waiting to be committed. It is good practice to run this after the last git add before a git commit to make sure all of the correct files are being committed.

Syntax:
<tt>
git status
</tt>

'''git commit''' takes all of the snapshots in the index and turns them into a local commit. It is very important to leave a message explaining what changes were made in each commit; a single sentence change summary is usually sufficient.

Syntax:
<tt>
git commit -m ‘<brief, descriptive commit message>’
</tt>

'''git push''' takes all of the local commits that have been made since the last online commit and adds them to the online repository. In order for this to happen, the local commits must all follow from the last commit online. If this is not the case, git pull must be used to download the current online commits and reconcile their differences with the commits stored locally. git push can then be used again.

Syntax:
<tt>
git push
</tt> 
- when pushing normally to the “master” branch

'''git pull''' takes the most recent online commit and merges it with your most recent local commit, making your local files safe to push up to GitHub online. A good workflow for git push and git pull is as follows:

*Before starting work on one or more code files, git pull to bring your local files up to sync with the latest code online.
*Make changes to your code, periodically using git commit as you improve your code.
*When done with an editing session, git push to put all of your commits online. This is important both for making use-ready code available to everyone who may need it and for allowing others to continue editing your code from where you left off.

Syntax:
<tt>
git pull
</tt> 
- when pulling normally

==Terminal/GitHub Basic Command Cheat Sheet==
===Generic===

<tt>
cd <path>
</tt> 
- Change the current working directory for Terminal

<tt>
pwd
</tt> 
- Show the absolute location of the current working directory

<tt>
ls
</tt> 
- List all of the files within the current working directory

<tt>
man <other command>
</tt> 
- Display the Unix Manual entry for any command
===Git/GitHub Specific===

<tt>
git clone <https clone link>
</tt> 
- Copy an online repository into the current working directory, creating a new folder there for the repository’s local copy.

<tt>
git add <filename of file to be added>
</tt> 
- Adds a specific changed file to the staging area for the next local commit.

<tt>
git add --all
</tt> 
- Adds all files that have been changed, added, deleted, etc. locally since the last local commit to the stage for the next local commit.

<tt>
git status
</tt> 
- Show all files that have been locally changed and whether or not their changed versions have been staged for the next local commit.

<tt>
git commit -m ‘<brief, descriptive commit message>’
</tt> 
- Make a local record of changes in files added to the staging area.

<tt>
git push
</tt> 
- Push all committed local changes to the online “master” branch.

<tt>
git pull
</tt> 
- Retrieve all changes made to the online “master” branch since the last local commit and download them for local use.

[[Category:Getting started]]

Dna synthesizer

2017-09-18T07:34:50Z

Jcreus: use redirect

#REDIRECT [[DNA synthesizer]]

Find a Project

2017-09-18T07:34:25Z

Jcreus:

= 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 ==

== 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 =

= 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]]

How to Join SSI

2017-09-18T07:34:04Z

Jcreus:

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!

[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]]

Category:Getting started

2017-09-18T07:33:43Z

Jcreus: Created page with "Category:Stanford Space Initiative"

[[Category:Stanford Space Initiative]]

Category:Rockets Guides

2017-09-18T07:33:32Z

Jcreus:

Rockets has collected a wide variety of resources for aspiring rocket scientists. Here you can find guides on everything from simulation to motor cleaning, plus links to even more useful stuff.

[[Category: Rockets]]
[[Category:Getting started]]

Category:Operations stubs

2017-09-18T07:32:13Z

Jcreus: Created page with "__HIDDENCAT__ Category:Stubs"

__HIDDENCAT__

[[Category:Stubs]]

Template:Operations-stub

2017-09-18T07:31:44Z

Jcreus:

{{qualified-stub | image link = File:operationsIcon.png | subject = operations}}
<includeonly>[[Category:Operations stubs]]</includeonly><noinclude>
To use, simply put <code><nowiki>{{operations-stub}}</nowiki></code> at the base of a Operations-related stub.

[[Category: Templates]]
</noinclude>

Template:Balloon-stub

2017-09-18T07:30:12Z

Jcreus:

<includeonly>
{{qualified-stub | image link = File:balloonIcon.png | subject = balloons}}
[[Category:Balloons stubs]]
</includeonly><noinclude>
To use, simply put <code><nowiki>{{balloon-stub}}</nowiki></code> at the base of a Balloons-related stub.
[[Category: Templates]]
</noinclude>

Template:Satellites-stub

2017-09-18T07:29:36Z

Jcreus:

<includeonly>
{{qualified-stub | image link = File:satelliteIcon.png | subject = satellites}}
[[Category:Satellites stubs]]
</includeonly><noinclude>
To use, simply put <code><nowiki>{{satellites-stub}}</nowiki></code> at the base of a Satellites-related stub.

[[Category: Templates]]
</noinclude>

Template:Satellites-stub

2017-09-18T07:28:43Z

Jcreus:

To use, simply put <code><nowiki>{{satellites-stub}}</nowiki></code> at the base of a Satellites-related stub.

<onlyinclude>
{{qualified-stub | image link = File:satelliteIcon.png | subject = satellites}}
<includeonly>
[[Category:Satellites stubs]]
</includeonly>
</onlyinclude>
[[Category: Templates]]

Template:Rocket-stub

2017-09-18T07:27:28Z

Jcreus:

<includeonly>
{{qualified-stub | image link = File:rocketsIcon.png | subject = rockets}}
[[Category:Rockets stubs]]
</includeonly><noinclude>
To use, simply put <code><nowiki>{{rocket-stub}}</nowiki></code> at the base of a Rockets-related stub.
[[Category: Templates]]
</noinclude>

Category:Biology stubs

2017-09-18T07:26:39Z

Jcreus: Created page with "__HIDDENCAT__ Category:Stubs"

__HIDDENCAT__
[[Category:Stubs]]

Template:Biology-stub

2017-09-18T07:26:04Z

Jcreus:

<includeonly>
{{qualified-stub | image link = File:BiologyIcon.png | subject = biology}}
[[Category:Biology stubs]]
</includeonly><noinclude>
To use, simply put <code><nowiki>{{biology-stub}}</nowiki></code> at the base of a Biology-related stub.

[[Category: Templates]]
</noinclude>

Category:Rockets stubs

2017-09-18T07:24:30Z

Jcreus: making hidden

__HIDDENCAT__

[[Category:Stubs]]

Category:Balloons stubs

2017-09-18T07:24:16Z

Jcreus: making hidden

__HIDDENCAT__

[[Category:Stubs]]

Category:Hidden categories

2017-09-18T07:23:50Z

Jcreus: Created page with "Category:Wiki"

[[Category:Wiki]]

Category:Satellites stubs

2017-09-18T07:23:41Z

Jcreus: Created page with "__HIDDENCAT__ Category:Stubs"

__HIDDENCAT__
[[Category:Stubs]]

Template:Satellites-stub

2017-09-18T07:20:38Z

Jcreus:

To use, simply put <code><nowiki>{{satellites-stub}}</nowiki></code> at the base of a Satellites-related stub.

<onlyinclude>
{{qualified-stub | image link = File:satelliteIcon.png | subject = satellites}}
</onlyinclude>
<includeonly>
[[Category:Satellites stubs]]
</includeonly>
[[Category: Templates]]

Category:Rockets stubs

2017-09-18T07:20:20Z

Jcreus: Created page with "Category:Stubs"

[[Category:Stubs]]

Template:Rocket-stub

2017-09-18T07:19:58Z

Jcreus:

To use, simply put <code><nowiki>{{rocket-stub}}</nowiki></code> at the base of a Rockets-related stub.

<onlyinclude>
{{qualified-stub | image link = File:rocketsIcon.png | subject = rockets}}
</onlyinclude>
<includeonly>
[[Category:Rockets stubs]]
</includeonly>
[[Category: Templates]]

Category:Stubs

2017-09-18T07:19:31Z

Jcreus: Created page with "Category:Wiki"

[[Category:Wiki]]

Category:Balloons stubs

2017-09-18T07:19:23Z

Jcreus: Created page with "Category:Stubs"

[[Category:Stubs]]

Template:Balloon-stub

2017-09-18T07:19:12Z

Jcreus:

To use, simply put <code><nowiki>{{balloon-stub}}</nowiki></code> at the base of a Balloons-related stub.

<onlyinclude>
{{qualified-stub | image link = File:balloonIcon.png | subject = balloons}}
</onlyinclude>
<includeonly>
[[Category:Balloons stubs]]
</includeonly>
[[Category: Templates]]

Template:Balloon-stub

2017-09-18T07:17:48Z

Jcreus:

To use, simply put <code><nowiki>{{balloon-stub}}</nowiki></code> at the base of a Balloons-related stub.

<onlyinclude>
{{qualified-stub | image link = File:balloonIcon.png | subject = balloons}}
[[Category:Balloons stubs]]
</onlyinclude>
[[Category: Templates]]