https://ssi-wiki.stanford.edu/w/api.php?action=feedcontributions&user=Rwong&feedformat=atomStanford SSI Wiki - User contributions [en]2024-03-28T18:16:10ZUser contributionsMediaWiki 1.35.0https://ssi-wiki.stanford.edu/w/index.php?title=Argus&diff=3321Argus2017-10-22T21:42:53Z<p>Rwong: Page creation</p>
<hr />
<div>The Argus team is one of the 2017-18 Daedalus Projects focused on designing a rocket dedicated to developing a wirelessly-activated camera network and live video telemetry.<br />
<br />
{{rocket-project<br />
| header = Argus<br />
| img link =<br />
| launch details = <br />
<br />
{{rocket-launch<br />
|number=1<br />
|launch class = Pending<br />
|launch date = Pending<br />
|launch site = Pending<br />
|next={{rocket-launch<br />
|number=2<br />
|launch class = Pending<br />
|launch date = Pending<br />
|launch site = Pending<br />
|next={{rocket-launch<br />
|number=3<br />
|launch class = Pending<br />
|launch date = Pending<br />
|launch site = Pending<br />
}}<br />
}}<br />
}}<br />
<br />
| program = Project Daedalus<br />
| next = Charybdis<br />
}}<br />
<br />
<br />
<br />
= Team Summary =<br />
<br />
* Person 1 - Team Lead?<br />
* Person 2 - Structures Lead<br />
* Person 3 - etc etc<br />
<br />
= Launch Vehicle and Payload Summary =<br />
<br />
* Expected Apogee: xx ft<br />
* Payload: xx<br />
<br />
= Vehicle Criteria =<br />
<br />
== Mission Success Criteria ==<br />
''EXAMPLE''<br />
<br />
The mission will be considered successful if the recovered rocket would be able to pass a L3 certification inspection. This means that if the rocket experiences excessive damage to the point that it could not be re-flown that day with a reloaded motor, then the recovery system will have failed. Another criteria is that the rocket will have landed within a 300ft radius of its original target landing space.<br />
<br />
== Constraints ==<br />
''EXAMPLE''<br />
<br />
# Tripoli height ceiling of 16,800 ft<br />
# Rocket construction to be made using a “minimum of metallic parts” excepting those necessary for airframe integrity<br />
# Motor impulse to not exceed 10,240 N-s<br />
# Redundant avionics, wiring, and safe arm systems<br />
# Automated program for descent path<br />
# Manual back up control system for descent path<br />
# Back up recovery system consisting of main parachute<br />
# Vertical descent speed of 20 ft/s maximum upon landing<br />
# Budget<br />
<br />
<br />
= Manufacturing and Assembly =<br />
<br />
''What are you making the rocket out of? What manufacturing processes? Who has oversight over assembly? What considerations are affecting your choices for materials, processes, workflow? ''<br />
<br />
= Systems Integration and Testing =<br />
<br />
== Major Event Timetable==<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
! Date<br />
! Event<br />
! Objectives<br />
|-<br />
| Soon<br />
| PDR<br />
| Full CAD, prototyped xyz<br />
|- <br />
| Someday<br />
| Launch 1 <br />
| Expected apogee: some# ft; x # of things do these things<br />
|}<br />
<br />
= Risk Management =<br />
<br />
== Safety Hazards ==<br />
<br />
''EXAMPLE''<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
! Risk<br />
! Likelihood<br />
! Consequence<br />
! Mitigation<br />
|-<br />
| Ematches don't ignite<br />
| Medium<br />
| High - No separation event; descent at terminal velocity<br />
| Redundant ematch events on heterogeneous altimeter systems<br />
|-<br />
| Parachute tangles<br />
| High<br />
| Medium - descent > recommended 20 ft/sec<br />
| Extensive ground testing; procedural method for packing parachutes according to best practices<br />
|}<br />
<br />
== Budget Risks ==<br />
<br />
''EXAMPLE''<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
! Risk<br />
! Likelihood<br />
! Mitigation<br />
|-<br />
| Overspend on machining parts<br />
| Medium<br />
| Measure thrice, cut once; MATH<br />
|-<br />
| Unknown motor choices<br />
| High<br />
| Allocate x% margin for motor purchases for x test flights<br />
|}<br />
<br />
<br />
<br />
[[Category: Daedalus]]<br />
[[Category: Rockets]]<br />
[[Category: Documentation]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=SpaceJams&diff=3294SpaceJams2017-10-13T00:17:57Z<p>Rwong: /* Discussion Lead Schedule (Fall 2017) */</p>
<hr />
<div>= What is SpaceJams?=<br />
SpaceJams is our weekly Policy "meeting". It is meant to be an informal get-together (with food!) for anyone in SSI that is interested in gaining a broader perspective on the space industry and learning about a particular topic or recent space news. We want this to be a welcoming and interactive space (pun intended) where anyone can jump in with questions, ideas, or insights. <br />
<br />
The overall structure is loosely as follows:<br />
* Each week, a member (or a couple of members) will be Discussion Leads, bringing in a topic or article(s) of interest and any relevant historical contexts that they feel the group would benefit from. <br />
* The Discussion Leads share and summarize the article or topic of choice, presenting any conflicting opinions, strategies, or current difficulties that makes this a relevant and intriguing topic.<br />
* Discussion Leads prepare a series of questions to pose to the group for discussion and any possible proposals or areas for further research. More often than not, there won't be a simple resolution to a topic -- and that's fine! The goal here isn't to solve the problems facing the aerospace industry, but rather to gain a better understanding of what's happening. Where we can, we may try to hypothesize what possible futures may look like.<br />
<br />
= Discussion Lead Schedule (Fall 2017) =<br />
<br />
Week 3 (Sun 10/8): Rebecca <br />
<br />
Week 4 (Sat 1014): Thomas<br />
<br />
Week 5:<br />
<br />
Week 6:<br />
<br />
Week 7:<br />
<br />
Week 8:<br />
<br />
Week 9:<br />
<br />
= Possible Discussion Topics =<br />
Not sure where to start? Take a look at just a handful of issues present in the space world these days...<br />
<br />
* Back to the Moon or go to Mars?<br />
* US Space Corps<br />
* Space debris -- Who's problem is it? How to enforce rules?<br />
* (Asteroid) Mining and territorial ownership<br />
* NASA's Space Launch System (SLS) <br />
* Legislative oversight for national colonization of outer space bodies?<br />
* What are the most important considerations for Mars colonization?<br />
* The right role for NASA given private launchers like SpaceX, Blue Origin, Rocket Lab, etc<br />
* How much human safety should be a priority<br />
* What we should be developing? (e.g. focus on launch, or do we need more human health stuff)<br />
* Why should we settle other planets vs focus on taking care of Earth?<br />
* Why should we go to or explore space at all?<br />
* How will colonization affect society and culture?<br />
* Space weaponry laws (and how they affect space debris clearance)<br />
* Military vs. civilian space divides<br />
* How Earth imaging companies like Planet should handle privacy or security issues<br />
* Should countries try for self-sufficiency in space at greater expense<br />
* How should the US respond if China goes for the moon again? <br />
* Expanding commercial crew?<br />
* Deep Space Gateway pro/con <br />
* Planetary protection issues (e.g. Europa science?)<br />
<br />
Other great places to start:<br />
* http://spacenews.com<br />
* http://space.com<br />
* https://phys.org/space-news/<br />
* https://www.nbcnews.com/science/space<br />
* http://spacedaily.com<br />
* Any other reputable news sources (Newsweek, Forbes, Popular Science, LA/NY Times, etc)<br />
[[Category: Policy]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=ITAR&diff=3293ITAR2017-10-13T00:17:22Z<p>Rwong: </p>
<hr />
<div>The '''International Traffic in Arms Regulations (ITAR)''' is a set of US regulations governing the use and sharing of technologies with significant military implications, also known as '''export control'''. SSI and aerospace industry as a whole operate under the authority of ITAR, as many rocket, satellite, and aerospace technologies provide the US military advantages over other countries that the US government has sought to maintain. While the efficacy and utility of this policy are debated [https://en.wikipedia.org/wiki/International_Traffic_in_Arms_Regulations#Controversy], the regulations still apply to SSI and members of the space industry, and violations carry significant fines and potentially decades-long prison terms. As a Stanford entity, SSI's activities are overseen by the Stanford Export Control Office, who works to ensure that no ITAR violations occur. '''An ITAR violation is performing an [[#Export|export]] activity without a license from the US State Department.''' This article discusses the important concepts of ITAR and their applicability to SSI.<br />
<br />
== Important Terms and Concepts ==<br />
<br />
=== Export ===<br />
§120.17 defines '''export''' as:<br />
*Sending or taking a defense article out of the United States in any manner, except by mere travel outside of the United States by a person whose personal knowledge includes technical data; or<br />
*Transferring registration, control or ownership to a foreign person of any aircraft, vessel, or satellite covered by the U.S. Munitions List, whether in the United States or abroad; or<br />
*Disclosing (including oral or visual disclosure) or transferring in the United States any defense article to an embassy, any agency or subdivision of a foreign government (e.g., diplomatic missions); or<br />
*Disclosing (including oral or visual disclosure) or transferring technical data to a foreign person, whether in the United States or abroad; or<br />
*Performing a defense service on behalf of, or for the benefit of, a foreign person, whether in the United States or abroad.<br />
A launch vehicle or payload shall not, by reason of the launching of such vehicle, be considered an export for purposes of ITAR. However, for certain limited purposes, controls may apply to any sale, transfer or proposal to sell or transfer defense articles or defense services.<br />
<br />
'''''Exporting'' (by any of the above definitions) without proper licensure is a federal offense punishable by hundreds of thousands of dollars in fines or twenty years in federal prison.''' Institutions whose members commit ITAR violations also have significantly reduced chances of winning federal contracts and other government bids.<br />
<br />
=== Defense Article ===<br />
§120.6 defines '''Defense Article''' to refer to any item listed in Part 121, the [[#The United States Munitions List (USML)|United States Munitions List (USML)]].<br />
''This term includes technical data recorded or stored in any physical form, models, mockups or other items that reveal technical data directly relating to items designated in §121.1 (the USML). It also includes forgings, castings, and other unfinished products, such as extrusions and machined bodies, that have reached a stage in manufacturing where they are clearly identifiable by mechanical properties, material composition, geometry, or function as defense articles. It does not include basic marketing information on function or purpose or general system descriptions.''<br />
=== Significant Military Equipment ===<br />
§120.7 specially classifies certain defense articles with “substantial military capability” from Part 121 as '''Significant Military Equipment''' (SME), subject to additional controls.<br />
=== Major Defense Equipment ===<br />
§120.8 defines '''Major Defense Equipment''' to mean any SME with R&D costs above $50M or production costs above $200M.<br />
=== Defense Service ===<br />
§120.6 defines '''Defense Service''' as:<br />
*The furnishing of assistance (including training) to foreign persons, whether in the United States or abroad in the design, development, engineering, manufacture, production, assembly, testing, repair, maintenance, modification, operation, demilitarization, destruction, processing or use of defense articles;<br />
*The furnishing to foreign persons of any [[#Technical Data|technical data]] controlled under the ITAR, whether in the United States or abroad; or<br />
*Military training of foreign units and forces, regular and irregular, including formal or informal instruction of foreign persons in the United States or abroad or by correspondence courses, technical, educational, or information publications and media of all kinds, training aid, orientation, training exercise, and military advice.<br />
=== Technical Data ===<br />
§120.10 defines '''Technical Data''' as:<br />
*Information, other than software, which is required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of defense articles. This includes information in the form of blueprints, drawings, photographs, plans, instructions or documentation.<br />
*Classified information relating to defense articles and defense services on the U.S. Munitions List and 600-series items controlled by the Commerce Control List;<br />
*Information covered by an invention secrecy order; or<br />
*Software directly related to [[#Defense Article|defense articles]].<br />
Importantly, the above definition ''does not include'' information concerning general scientific, mathematical, or engineering principles commonly taught in schools, colleges, and universities, or information in the [[#Public Domain|public domain]] or telemetry data. It also does not include basic marketing information on function or purpose or general system descriptions of defense articles.<br />
=== Public Domain ===<br />
'''Public domain''', defined in §120.11 for the purposes of the ITAR, refers to all information that is available:<br />
*Through sales at newsstands and bookstores;<br />
*Through subscriptions which are available without restriction to any individual who desires to obtain or purchase the published information;<br />
*Through second class mailing privileges granted by the U.S. Government;<br />
*At libraries open to the public or from which the public can obtain documents;<br />
*Through patents available at any patent office;<br />
*Through unlimited distribution at a conference, meeting, seminar, trade show or exhibition, generally accessible to the public, in the United States;<br />
*Through public release (i.e., unlimited distribution) in any form (e.g., not necessarily in published form) after approval by the cognizant U.S. government department or agency;<br />
*Through '''[[#Fundamental Research|fundamental research]]''' in science and engineering at accredited institutions of higher learning in the U.S. where the resulting information is ordinarily published and shared broadly in the scientific community. <br />
=== Fundamental Research ===<br />
'''Fundamental research''' is defined as ''basic and applied research in science and engineering where the resulting information is ordinarily published and shared broadly within the scientific community, as distinguished from research the results of which are restricted for proprietary reasons or specific U.S. Government access and dissemination controls.''<br />
<br />
Applied research is further defined as ''a systemic study to gain knowledge or understanding necessary to determine the means by which a recognized and specific need may be met. It is a systematic application of knowledge toward the production of useful materials, devices, and systems or methods, including design, development, and improvement of prototypes and new processes to meet specific requirements.''<br />
<br />
University research will not be considered fundamental research if:<br />
*The University or its researchers accept other restrictions on publication of scientific and technical information resulting from the project or activity, or<br />
*The research is funded by the U.S. Government and specific access and dissemination controls protecting information resulting from the research are applicable.<br />
<br />
== The United States Munitions List (USML) ==<br />
This section (§121.1) is extraordinarily comprehensive, and can be read [http://www.ecfr.gov/cgi-bin/retrieveECFR?gp=&SID=df3f1df6ae91cbdda2843035ec5b7fdf&mc=true&r=PART&n=pt22.1.121 here]. In the portions relating to aerospace technologies, certain items of interest to SSI are included, such as essentially all components of Class 3 ('''not''' L3) rockets and certain components in high-precision imaging satellites. No balloon technologies except those designed explicitly for military purposes are subject to US Export Controls.<br />
<br />
== Interpretation ==<br />
ITAR is interpreted differently at various universities within the US. Stanford's interpretation of the ITAR involves an ongoing discussion regarding the definition of [[#Fundamental Research|"'''fundamental research'''"]]. SSI works to ensure its activities fall within the purview of fundamental research and in compliance with the ITAR by frequently publicizing information about group activities (such as through this Wiki), securing group property, not engaging in military training, and otherwise ensuring appropriate conduct.<br />
<br />
[[Category:Raccoonworks]] [[Category:Policy]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Slack_Directory&diff=3275Slack Directory2017-10-03T07:57:21Z<p>Rwong: /* Policy */</p>
<hr />
<div>== Non-team specific Channels ==<br />
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.<br />
=== General Channels ===<br />
:* #general - typically for general SSI-wide announcements <br />
:* #random - for things you want to share with SSI that doesn’t belong in any other channels<br />
:* #dankmemes - pretty self explanatory. Try typing "/dank" in the channel.<br />
:* #spacenews - to talk about the current state of space affairs<br />
:* #ssipac - politics<br />
:* #best-of-slack - compilation of the best moments on SSI slack<br />
:* #welcome-to-ssi - channel to welcome new members and answer any questions<br />
:* #diverssity - A place to speak about relavant issues <br />
:* #women - A place for women and gender minorities to speak about relavant issues and bond and stuff<br />
:* #new-frosh - for the new frosh to speak among each other about young people problems<br />
=== Fun channels ===<br />
:* #ssi-finds-a-path - DnD roleplaying<br />
:* #ssi-does-exercise - ssi attempts to stay fit<br />
:* #ssi-makes-stuff - a channel to discuss non ssi related personal projects<br />
:* #ssiplacesblocks - ssi’s minecraft group<br />
:* #ssi-plays-video-games - video games in general, played together. <br />
:* #ssi-jams - ssi makes melodic noises<br />
<br />
=== Non team-specific Engineering Channels ===<br />
Interteam collaboration on a technical projects. Why is it called raccoonworks? Who knows.<br />
:* #raccoonworks-eecs - to talk about and get help with random EE or CS related things<br />
:* #raccoonworks-me - to talk about and get help with random ME related things<br />
:* #prak-ssi<br />
=== Class Channels ===<br />
Want to collaborate on a classes with other SSI members? We make channels for classes in the format: #ssitakes[course#]. Ex:<br />
:* #ssitakesme203<br />
:* #ssitakescs106b<br />
<br />
== Team Channels ==<br />
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! <br />
=== Rockets ===<br />
:* #rockets<br />
:* #rockets-irec - our largest project each year<br />
:* #rockets-argus - the Argus Daedalus Project, with RF activated cameras and so forth.<br />
:* #rockets-charybdis - the Charybdis Daedalus Project, which is a rocket that spins like a rifle bullet. <br />
:* #rockets-icarus - the Icarus Daedalus Project, which is a rocket that has a multi-activated reefed parachute. <br />
:* #rockets-ksp: shooting for the Mun (playing Kerbal Space Program)<br />
<br />
=== Balloons ===<br />
:* #balloons<br />
:* #balloons-valbal<br />
:* #balloons-buzz<br />
:* #balloons-habees<br />
:* #balloons-habhive<br />
:* #habmc<br />
<br />
=== Sats ===<br />
:* #satellites<br />
=== Bio ===<br />
:* #biology<br />
:* #biology-reading<br />
:* #biology-terminator<br />
:* #biology-backspace<br />
:* #biology-device<br />
=== Operations ===<br />
:* #operations<br />
:* #operations-herbs<br />
:* #operations-community<br />
:* #operations-diverssity<br />
:* #operations-marketing<br />
=== Policy ===<br />
:* #policy<br />
:* #policy-class - Help plan AA47SI<br />
<br />
== Contacts ==<br />
:* {{slack-user|kai}} - Operations lead. Talk to him if you want to help make SSI run!<br />
:* {{slack-user|dragland}} and {{slack-user|paigebrown}} - Balloons coleads<br />
:* {{slack-user|thomaswhite}} and {{slack-user|williamalvero}} - Rockets coleads<br />
:* {{slack-user|chao16}} and {{slack-user|tomusiak}} - Biology Co-Leads<br />
:* {{slack-user|rebeccawong}} - Policy Lead<br />
:* {{slack-user|johndean}} and {{slack-user|smaldonado}} - Co-Presidents</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Slack_Directory&diff=3274Slack Directory2017-10-03T07:56:14Z<p>Rwong: /* Policy */</p>
<hr />
<div>== Non-team specific Channels ==<br />
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.<br />
=== General Channels ===<br />
:* #general - typically for general SSI-wide announcements <br />
:* #random - for things you want to share with SSI that doesn’t belong in any other channels<br />
:* #dankmemes - pretty self explanatory. Try typing "/dank" in the channel.<br />
:* #spacenews - to talk about the current state of space affairs<br />
:* #ssipac - politics<br />
:* #best-of-slack - compilation of the best moments on SSI slack<br />
:* #welcome-to-ssi - channel to welcome new members and answer any questions<br />
:* #diverssity - A place to speak about relavant issues <br />
:* #women - A place for women and gender minorities to speak about relavant issues and bond and stuff<br />
:* #new-frosh - for the new frosh to speak among each other about young people problems<br />
=== Fun channels ===<br />
:* #ssi-finds-a-path - DnD roleplaying<br />
:* #ssi-does-exercise - ssi attempts to stay fit<br />
:* #ssi-makes-stuff - a channel to discuss non ssi related personal projects<br />
:* #ssiplacesblocks - ssi’s minecraft group<br />
:* #ssi-plays-video-games - video games in general, played together. <br />
:* #ssi-jams - ssi makes melodic noises<br />
<br />
=== Non team-specific Engineering Channels ===<br />
Interteam collaboration on a technical projects. Why is it called raccoonworks? Who knows.<br />
:* #raccoonworks-eecs - to talk about and get help with random EE or CS related things<br />
:* #raccoonworks-me - to talk about and get help with random ME related things<br />
:* #prak-ssi<br />
=== Class Channels ===<br />
Want to collaborate on a classes with other SSI members? We make channels for classes in the format: #ssitakes[course#]. Ex:<br />
:* #ssitakesme203<br />
:* #ssitakescs106b<br />
<br />
== Team Channels ==<br />
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! <br />
=== Rockets ===<br />
:* #rockets<br />
:* #rockets-irec - our largest project each year<br />
:* #rockets-argus - the Argus Daedalus Project, with RF activated cameras and so forth.<br />
:* #rockets-charybdis - the Charybdis Daedalus Project, which is a rocket that spins like a rifle bullet. <br />
:* #rockets-icarus - the Icarus Daedalus Project, which is a rocket that has a multi-activated reefed parachute. <br />
:* #rockets-ksp: shooting for the Mun (playing Kerbal Space Program)<br />
<br />
=== Balloons ===<br />
:* #balloons<br />
:* #balloons-valbal<br />
:* #balloons-buzz<br />
:* #balloons-habees<br />
:* #balloons-habhive<br />
:* #habmc<br />
<br />
=== Sats ===<br />
:* #satellites<br />
=== Bio ===<br />
:* #biology<br />
:* #biology-reading<br />
:* #biology-terminator<br />
:* #biology-backspace<br />
:* #biology-device<br />
=== Operations ===<br />
:* #operations<br />
:* #operations-herbs<br />
:* #operations-community<br />
:* #operations-diverssity<br />
:* #operations-marketing<br />
=== Policy ===<br />
:* #policy - All general discussions<br />
:* #policy-class - Help plan AA47SI<br />
<br />
== Contacts ==<br />
:* {{slack-user|kai}} - Operations lead. Talk to him if you want to help make SSI run!<br />
:* {{slack-user|dragland}} and {{slack-user|paigebrown}} - Balloons coleads<br />
:* {{slack-user|thomaswhite}} and {{slack-user|williamalvero}} - Rockets coleads<br />
:* {{slack-user|chao16}} and {{slack-user|tomusiak}} - Biology Co-Leads<br />
:* {{slack-user|rebeccawong}} - Policy Lead<br />
:* {{slack-user|johndean}} and {{slack-user|smaldonado}} - Co-Presidents</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Slack_Directory&diff=3273Slack Directory2017-10-03T07:55:49Z<p>Rwong: /* Policy */</p>
<hr />
<div>== Non-team specific Channels ==<br />
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.<br />
=== General Channels ===<br />
:* #general - typically for general SSI-wide announcements <br />
:* #random - for things you want to share with SSI that doesn’t belong in any other channels<br />
:* #dankmemes - pretty self explanatory. Try typing "/dank" in the channel.<br />
:* #spacenews - to talk about the current state of space affairs<br />
:* #ssipac - politics<br />
:* #best-of-slack - compilation of the best moments on SSI slack<br />
:* #welcome-to-ssi - channel to welcome new members and answer any questions<br />
:* #diverssity - A place to speak about relavant issues <br />
:* #women - A place for women and gender minorities to speak about relavant issues and bond and stuff<br />
:* #new-frosh - for the new frosh to speak among each other about young people problems<br />
=== Fun channels ===<br />
:* #ssi-finds-a-path - DnD roleplaying<br />
:* #ssi-does-exercise - ssi attempts to stay fit<br />
:* #ssi-makes-stuff - a channel to discuss non ssi related personal projects<br />
:* #ssiplacesblocks - ssi’s minecraft group<br />
:* #ssi-plays-video-games - video games in general, played together. <br />
:* #ssi-jams - ssi makes melodic noises<br />
<br />
=== Non team-specific Engineering Channels ===<br />
Interteam collaboration on a technical projects. Why is it called raccoonworks? Who knows.<br />
:* #raccoonworks-eecs - to talk about and get help with random EE or CS related things<br />
:* #raccoonworks-me - to talk about and get help with random ME related things<br />
:* #prak-ssi<br />
=== Class Channels ===<br />
Want to collaborate on a classes with other SSI members? We make channels for classes in the format: #ssitakes[course#]. Ex:<br />
:* #ssitakesme203<br />
:* #ssitakescs106b<br />
<br />
== Team Channels ==<br />
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! <br />
=== Rockets ===<br />
:* #rockets<br />
:* #rockets-irec - our largest project each year<br />
:* #rockets-argus - the Argus Daedalus Project, with RF activated cameras and so forth.<br />
:* #rockets-charybdis - the Charybdis Daedalus Project, which is a rocket that spins like a rifle bullet. <br />
:* #rockets-icarus - the Icarus Daedalus Project, which is a rocket that has a multi-activated reefed parachute. <br />
:* #rockets-ksp: shooting for the Mun (playing Kerbal Space Program)<br />
<br />
=== Balloons ===<br />
:* #balloons<br />
:* #balloons-valbal<br />
:* #balloons-buzz<br />
:* #balloons-habees<br />
:* #balloons-habhive<br />
:* #habmc<br />
<br />
=== Sats ===<br />
:* #satellites<br />
=== Bio ===<br />
:* #biology<br />
:* #biology-reading<br />
:* #biology-terminator<br />
:* #biology-backspace<br />
:* #biology-device<br />
=== Operations ===<br />
:* #operations<br />
:* #operations-herbs<br />
:* #operations-community<br />
:* #operations-diverssity<br />
:* #operations-marketing<br />
=== Policy ===<br />
:* #policy<br />
:* #policy-class Help plan AA47SI<br />
<br />
== Contacts ==<br />
:* {{slack-user|kai}} - Operations lead. Talk to him if you want to help make SSI run!<br />
:* {{slack-user|dragland}} and {{slack-user|paigebrown}} - Balloons coleads<br />
:* {{slack-user|thomaswhite}} and {{slack-user|williamalvero}} - Rockets coleads<br />
:* {{slack-user|chao16}} and {{slack-user|tomusiak}} - Biology Co-Leads<br />
:* {{slack-user|rebeccawong}} - Policy Lead<br />
:* {{slack-user|johndean}} and {{slack-user|smaldonado}} - Co-Presidents</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Slack_Directory&diff=3272Slack Directory2017-10-03T07:55:09Z<p>Rwong: /* Policy */</p>
<hr />
<div>== Non-team specific Channels ==<br />
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.<br />
=== General Channels ===<br />
:* #general - typically for general SSI-wide announcements <br />
:* #random - for things you want to share with SSI that doesn’t belong in any other channels<br />
:* #dankmemes - pretty self explanatory. Try typing "/dank" in the channel.<br />
:* #spacenews - to talk about the current state of space affairs<br />
:* #ssipac - politics<br />
:* #best-of-slack - compilation of the best moments on SSI slack<br />
:* #welcome-to-ssi - channel to welcome new members and answer any questions<br />
:* #diverssity - A place to speak about relavant issues <br />
:* #women - A place for women and gender minorities to speak about relavant issues and bond and stuff<br />
:* #new-frosh - for the new frosh to speak among each other about young people problems<br />
=== Fun channels ===<br />
:* #ssi-finds-a-path - DnD roleplaying<br />
:* #ssi-does-exercise - ssi attempts to stay fit<br />
:* #ssi-makes-stuff - a channel to discuss non ssi related personal projects<br />
:* #ssiplacesblocks - ssi’s minecraft group<br />
:* #ssi-plays-video-games - video games in general, played together. <br />
:* #ssi-jams - ssi makes melodic noises<br />
<br />
=== Non team-specific Engineering Channels ===<br />
Interteam collaboration on a technical projects. Why is it called raccoonworks? Who knows.<br />
:* #raccoonworks-eecs - to talk about and get help with random EE or CS related things<br />
:* #raccoonworks-me - to talk about and get help with random ME related things<br />
:* #prak-ssi<br />
=== Class Channels ===<br />
Want to collaborate on a classes with other SSI members? We make channels for classes in the format: #ssitakes[course#]. Ex:<br />
:* #ssitakesme203<br />
:* #ssitakescs106b<br />
<br />
== Team Channels ==<br />
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! <br />
=== Rockets ===<br />
:* #rockets<br />
:* #rockets-irec - our largest project each year<br />
:* #rockets-argus - the Argus Daedalus Project, with RF activated cameras and so forth.<br />
:* #rockets-charybdis - the Charybdis Daedalus Project, which is a rocket that spins like a rifle bullet. <br />
:* #rockets-icarus - the Icarus Daedalus Project, which is a rocket that has a multi-activated reefed parachute. <br />
:* #rockets-ksp: shooting for the Mun (playing Kerbal Space Program)<br />
<br />
=== Balloons ===<br />
:* #balloons<br />
:* #balloons-valbal<br />
:* #balloons-buzz<br />
:* #balloons-habees<br />
:* #balloons-habhive<br />
:* #habmc<br />
<br />
=== Sats ===<br />
:* #satellites<br />
=== Bio ===<br />
:* #biology<br />
:* #biology-reading<br />
:* #biology-terminator<br />
:* #biology-backspace<br />
:* #biology-device<br />
=== Operations ===<br />
:* #operations<br />
:* #operations-herbs<br />
:* #operations-community<br />
:* #operations-diverssity<br />
:* #operations-marketing<br />
=== Policy ===<br />
:* #policy <br />
<br />
== Contacts ==<br />
:* {{slack-user|kai}} - Operations lead. Talk to him if you want to help make SSI run!<br />
:* {{slack-user|dragland}} and {{slack-user|paigebrown}} - Balloons coleads<br />
:* {{slack-user|thomaswhite}} and {{slack-user|williamalvero}} - Rockets coleads<br />
:* {{slack-user|chao16}} and {{slack-user|tomusiak}} - Biology Co-Leads<br />
:* {{slack-user|rebeccawong}} - Policy Lead<br />
:* {{slack-user|johndean}} and {{slack-user|smaldonado}} - Co-Presidents</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=3260How to Join SSI2017-09-30T22:53:09Z<p>Rwong: /* Resources */</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10 in exchange for a t-shirt) to our financial officers - any leadership team member can accept these in cash, or you can Venmo our Financial Officer, Gabi Palavecino, directly. Message her on Slack for details ({{slack-user|gabipalavecino}}). If dues present a financial hardship, message {{slack-user|smaldonado}}, {{slack-user|johndean}}, or {{slack-user|gabipalavecino}}, and we'll waive them.<br />
# Join the SSI Slack [https://ssi-teams.slack.com/signup here].<br />
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].<br />
# In order to allow you access to our workspace, [[End Station III]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.<br />
##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.<br />
##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.<br />
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.<br />
##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.<br />
##Send a message in {{slack-channel|welcome-to-ssi}} that you've completed everything!<br />
<br />
=Resources=<br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
To see what a list of what channels there are to join, check out the [[Slack Directory]].<br />
<br />
[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams.<br />
<br />
== [https://stanfordssi.org/leadership SSI Leadership] ==<br />
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.<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [http://stanfordssi.org/join All The Mailing Lists] ==<br />
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)<br />
<br />
== [[End Station III]] ==<br />
<br />
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.<br />
<br />
[[File:whereisesiii.png|thumb|left]]<br />
<br />
== [[Find a Project]] ==<br />
<br />
If you're ever feeling overwhelmed or lost about all the things going on in SSI, use this page to see what's what! Reach out to someone working on a project you're interested in and they'll help you get started. If you have questions or just want to chat, poke any leadership member.<br />
<br />
[[Category:Getting started]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=3259Find a Project2017-09-30T22:47:44Z<p>Rwong: /* Biology */</p>
<hr />
<div>= SSI Overload = <br />
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.<br />
<br />
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.''<br />
<br />
= Balloons =<br />
<br />
== HABMC ==<br />
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<br />
* 3D visualizations using Cesium or Unity<br />
* Natural Language Processing for the commands module<br />
* Create a mobile app using React Native<br />
* Improved [[Balloons Radio Projects|RF integrations]]<br />
* Overhaul security on websocket connections<br />
* Navigation algorithms<br />
<br />
== ValBal ==<br />
<br />
== HABEES ==<br />
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!<br />
<br />
* 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!<br />
** Motor/Servo Driver <br />
** External/Internal Payload Heaters<br />
** Atmospheric Gas Sensors<br />
** Wind Sensors<br />
** SSTV Radio Board<br />
** WinLink Radio Email Board<br />
** APRS Radio Board<br />
** 12V Battery Management System<br />
** General Purpose Radio Transceiver<br />
** Camera Board<br />
** CubeSat Mapping Board<br />
** Literally anything else<br />
* 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!<br />
** Software for tracking something (with motors/servos)<br />
** Improving filtering/error checking for sensors<br />
** Compression algorithms for logged & transmitted data<br />
** Enhancing speed, quality, and throughput of CAN Bus<br />
** Enhancing TestBench (QueenBee) test software<br />
** Introducing/Developing radio encoding & decoding schemes<br />
** Developing forward & reverse error correction for radio links<br />
** Developing Point-To-Point radar link software<br />
<br />
== BUZZ ==<br />
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!<br />
* Improved ATV link quality<br />
* Teensy-native SSTV Transmission & Reception<br />
* APRS development<br />
* Native GFSK/FSK/OOK transceivers & software<br />
* WiFi downlink/uplink (2.4GHz / 5 GHz)<br />
* Stanford Ground Station (high gain, directional)<br />
* Portable Field Ground Station<br />
* Balloons National Ground Station Networ<br />
* WinLink Global Radio E-Mail<br />
* Digital Video/Image encoding<br />
<br />
= Rockets =<br />
<br />
== Daedalus ==<br />
<br />
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. <br />
<br />
Icarus - Reefed Parachute, '''Lead: Saylor'''<br />
<br />
*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:<br />
** Mechanics and mechanical engineering - designing, simulating and building a deployment mechanism. <br />
** Mechanics and aerodynamics - designing the parachute and its aerodynamic properties. <br />
** Electrical engineering - PCB design, electrical integration and programming. Focus on high reliability and low size & power. <br />
<br />
Charybdis - Spin Stabilization '''Contact: William'''<br />
<br />
*Charybdis is building a rocket that spins like a rifle bullet, then stops spinning mid-air to deploy parachutes. <br />
** Mechanical engineering - designing reliable deployment mechanism. <br />
** Aerodynamics and simulation - designing fin system to create desired spin. <br />
<br />
<br />
Argus - Distributed RF Camera System '''Lead: John'''<br />
<br />
*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. <br />
** Electrical Engineering - circuit board design, electrical integration. <br />
** Signals - RF & transmission tech.<br />
<br />
== Competition (IREC/SA Cup) ==<br />
* Structures<br />
* Payload<br />
* Recovery<br />
* Avionics, '''Leads: Sharon, Julea''' {{slack-user|splatt}} {{slack-user|juleachin}}<br />
** Design, implement, and test all the hardware and software that goes into our flight computers<br />
** Design and manufacture structures for avionics bay and work with other subteams to implement interfaces and integration processes<br />
** Design and test radio communications system for our rocket to talk to the ground <br />
** 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)<br />
* Launch Operations, '''Lead: WANTED'''<br />
** Work with each subteam to coordinate and prepare launch materials<br />
** Plan & execute travel and launch logistics <br />
** Oversee launch procedures, checklists, and go/no calls<br />
** Many more additional projects for ground support designable around personal interests<br />
* Simulations<br />
<br />
= Satellites =<br />
=== STAR-CROSSED===<br />
The Stanford Timing And Ranging –Cross-linking Optical Small Satellite Demonstration mission is an ambitious proposal seeking to place two cubesats in low Earth orbit and establish a laser-based data link between them across hundreds of kilometers. Such a mission has never before been attempted. If successful, the technology developed will enable a dramatic leap forward in the capabilities of both cubesats and larger satellitesto communicate high volumes of data across long distances.<br />
<br />
Optical links using lasers are capable of dramatically higher data transmission speeds than existing radio systems, but have never been successfully demonstrated at the cubesat scale. A cubesat-sized optical communications system willenable high-speed links between cubesats, allowing for networks built from affordable satellites.Miniaturizing an optical communications system to fit in a cubesat would also make it far easier for larger satellites to add optical networking capabilities, an almost essential component of proposed internet satellite constellations.<br />
<br />
Satellites with optical links can not only transmit data faster, but also better synchronize their timekeeping with each other and measure their separation distance, important features of boththe GPS system and groups of scientific satellites. With an optical network, satellites could conduct previously impossible scientific missions and significantly improve the accuracy of GPS<br />
<br />
Now is the perfect time to get involved with STAR-CROSSD. A number of subsystems need to be analyzed, designed, built, and tested, with opportunities to learn about electrical, mechanical, and software engineering, satellite operations, and more.<br />
<br />
=== POINTR ===<br />
Polar Orbiting INfrared Tracking Receiver (POINTR) has been Satellites’ primary focus since February. POINTR is an in flight demonstration of an optical receiver pointing, acquisition and tracking (PAT) system. The optical receiver payload hosted on Audacy’s 3U cubesat would be pointed to the ground to acquire and track a beacon laser sent from a suitable ground facility, currently proposed as NASA JPL’s OCTL facility. This mission would demonstrate the operational and technical requirements related to two satellites establishing an optical communications link with each other. The requirements include mission planning, command and execution of a pointing maneuver, acquisition of an incoming optical signal and tracking of the optical signal. This mission can be broken into four main goals:<br />
<br />
* Demonstrate a subset of technology for full bidirectional optical communications mission within the constraints placed by Audacy’s primary mission.<br />
<br />
* Increase chance of bidirectional optical communications mission success.<br />
<br />
* Develop experience within SSI designing and building space hardware.<br />
<br />
* Contribute to the cubesat and satellite optical communications technical fields.<br />
<br />
=== Our Subteams ===<br />
* '''Avionics'''<br />
**'''The Gist'''The Avionics group works on all of the core electrical systems for the Satellites team, including electrical power distribution, sensors, and computing. Learn how to design and reflow Printed Circuit Boards (PCBs) and work with signal-processing to understand light signals in the inky darkness of space! <br />
**'''The People To Talk to''' Sasha, Shi, Meera<br />
<br />
* '''GNC'''<br />
**'''The Gist''' The GNC group ("Guidance, Navigation, and Control") is responsible for determining and controlling the position and rotation of satellites in space even while hundreds or sometimes thousands of miles away. Join GNC to work with us on cutting-edge technologies and a system to control our satellites in orbit from the comfort of the SSI space bunker.<br />
**'''The People To Talk to''' Sasha<br />
<br />
* '''Optics'''<br />
**'''The Gist''' Optics is all about putting light to work - starting from simple laser pointers to finally sending a communications signal across 10 kilometers in space! We use lasers, lenses, filters, sensors and even moving mirrors to send light flying through space and catch it on the other side.<br />
**'''The People To Talk to''' Michael Taylor<br />
<br />
* '''Software'''<br />
**'''The Gist''' The software team tackles the many different challenges of software needed for satellites: from flight software to web development, we do it all. For flight software, we take advantage of parallel communications modules to manage real-time requirements on pointing control. For web development, we are partnering with the ground operations team to build thorough mission control software and web interface. If any of this seems daunting or complicated, don’t worry. We all started from scratch. Join software and get your code in space!<br />
**'''The People To Talk to''' Orien, Joan<br />
<br />
* '''Ground Ops'''<br />
**'''The Gist''' The Ground Operations team will build mission control software and web interface to analyze satellite behavior in-flight and react accordingly. Aside from software, physics and orbital mechanics are crucial parts of this team’s ability. This team is responsible for testing spacecraft stability, fault tolerance, and final mission success.<br />
**'''The People To Talk to''' Orien<br />
<br />
*'''Structures'''<br />
**'''The Gist''' The Structures team designs and builds all necessary flight mechanics, ranging from the overall structure to individual component mounts. We go through the full development process - whiteboard drawings, SolidWorks, and finally manufacturing.The Structures team is also responsible for many of the environmental considerations, such as the thermal and vacuum requirements of space, as well as the shock and vibration profile of launch.<br />
**'''The People To Talk to''' Anjali, Sandip<br />
<br />
= Biology =<br />
<br />
== Enzymatic DNA Synthesis Methods == <br />
'''Lead: Michael Uttmark''' {{slack-user|uttmark}}<br />
** Test commercial blocking groups for compatibility with [[Terminal Deoxynucleotidyl Transferase]]<br />
** Chemically synthesize nucleotides with different reversible blocking groups<br />
** Characterize and optimize [[Enzymatic Synthesis Methods | enzymatic DNA synthesis]] reaction efficiency<br />
** Build and run stochastic computer models of DNA synthesis to optimize reaction parameters<br />
** Research purification methods for synthesized DNA <br />
** Design and test your own synthesis method!<br />
<br />
== Sequence Verification ==<br />
** Execute and optimize any one of our existing verification procedures--[[Polyacrylamide Gel Electrophoresis]], [[Pyrosequencing]], or [[Ligation and Sequencing]]<br />
** Adapt LCMS or MALDI-TOF procedures for detecting single-base addition or determining the sequence of a sample. <br />
** Come up with new ways to verify single-base addition to a starting strand of DNA<br />
<br />
== Microfluidic Device Design ==<br />
** Design and program an [[Electrowetting on Dielectric]] microfluidic PCB<br />
** Simulate and test how a microfluidic system would work in microgravity<br />
** Port our DNA synthesis method to a solid substrate like controlled pore glass or streptavidin-biotin magnetic beads<br />
** 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<br />
** 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].<br />
** Build a system for cooling and temperature control of the device, perhaps using [https://en.wikipedia.org/wiki/Thermoelectric_cooling Peltiers]<br />
** Write an algorithm to minimize the number of groups of compatible templates needed for the [[Enzymatic Synthesis Methods | exonuclease method]]<br />
** Figure out how to power our PCB from a cubesat or other launch vehicle<br />
** Build testing rigs for DNA synthesis methods that are needed for experiments in lab<br />
<br />
= Policy =<br />
<br />
== DC Trip ==<br />
* Be a lead/co-lead for our DC trip in partnership with Citizens for Space<br />
<br />
== [[SpaceJams]] ==<br />
* Be a Discussion Lead(s) for a week and do a deep dive on a topic/news article of your choice<br />
<br />
== Your Project Here ==<br />
* Message {{slack-user|rebeccawong}} and let's chat about what you're interested in doing!<br />
<br />
= Operations =<br />
<br />
== Community ==<br />
* Come up with a theme for Special Dinner and make decorations (like a model Falcon 9!)<br />
* Help {{slack-user|dragland}} run SSI general dinners<br />
* Plan and run general community events like Trivia Night, Pathfinder, and Movie Night<br />
== Diversity ==<br />
* Build connections with engineering diversity groups on campus<br />
* Help {{slack-user|ruqayyatoorawa}} run workshops<br />
== Events ==<br />
* Find an interesting company and arrange a tour or talk<br />
* Help handle logistics of an existing talk, like by meeting an astronaut and walking him to Durand 450<br />
* Give a CEO or Venture Capitalist a tour of ESIII<br />
== Finance == <br />
* Complete reimbursements <br />
* Apply for grants & seek out new sponsors<br />
== Marketing ==<br />
* Design awesome swag (t-shirts, jackets, posters)<br />
* Reach out to reporters<br />
* Social media guru! (Facebook, Twitter, and Instagram posts)<br />
* Creating Snapchat filters for events<br />
* Designing flyers for upcoming talks<br />
* Going on launches to take pictures and videos<br />
== Outreach ==<br />
* Start discussions with local highschools and their science clubs<br />
* Organize or join an existing trip to a local school<br />
== Sponsors ==<br />
* Pursue a sponsorship (we'll walk you through how!)<br />
* Compile a list of bay-area aerospace companies<br />
== Website ==<br />
* Overhaul the budgeting system<br />
* Give the sponsors page dynamic content<br />
* Manage this very wiki<br />
* Manage our public and internal websites<br />
== Workspace ==<br />
* Make space-themed artwork to decorate ESIII<br />
* Plant more herbs<br />
* Paint a mural<br />
* Track inventory of supplies and parts<br />
<br />
[[Category:Getting started]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=3258Find a Project2017-09-30T22:45:23Z<p>Rwong: </p>
<hr />
<div>= SSI Overload = <br />
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.<br />
<br />
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.''<br />
<br />
= Balloons =<br />
<br />
== HABMC ==<br />
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<br />
* 3D visualizations using Cesium or Unity<br />
* Natural Language Processing for the commands module<br />
* Create a mobile app using React Native<br />
* Improved [[Balloons Radio Projects|RF integrations]]<br />
* Overhaul security on websocket connections<br />
* Navigation algorithms<br />
<br />
== ValBal ==<br />
<br />
== HABEES ==<br />
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!<br />
<br />
* 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!<br />
** Motor/Servo Driver <br />
** External/Internal Payload Heaters<br />
** Atmospheric Gas Sensors<br />
** Wind Sensors<br />
** SSTV Radio Board<br />
** WinLink Radio Email Board<br />
** APRS Radio Board<br />
** 12V Battery Management System<br />
** General Purpose Radio Transceiver<br />
** Camera Board<br />
** CubeSat Mapping Board<br />
** Literally anything else<br />
* 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!<br />
** Software for tracking something (with motors/servos)<br />
** Improving filtering/error checking for sensors<br />
** Compression algorithms for logged & transmitted data<br />
** Enhancing speed, quality, and throughput of CAN Bus<br />
** Enhancing TestBench (QueenBee) test software<br />
** Introducing/Developing radio encoding & decoding schemes<br />
** Developing forward & reverse error correction for radio links<br />
** Developing Point-To-Point radar link software<br />
<br />
== BUZZ ==<br />
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!<br />
* Improved ATV link quality<br />
* Teensy-native SSTV Transmission & Reception<br />
* APRS development<br />
* Native GFSK/FSK/OOK transceivers & software<br />
* WiFi downlink/uplink (2.4GHz / 5 GHz)<br />
* Stanford Ground Station (high gain, directional)<br />
* Portable Field Ground Station<br />
* Balloons National Ground Station Networ<br />
* WinLink Global Radio E-Mail<br />
* Digital Video/Image encoding<br />
<br />
= Rockets =<br />
<br />
== Daedalus ==<br />
<br />
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. <br />
<br />
Icarus - Reefed Parachute, '''Lead: Saylor'''<br />
<br />
*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:<br />
** Mechanics and mechanical engineering - designing, simulating and building a deployment mechanism. <br />
** Mechanics and aerodynamics - designing the parachute and its aerodynamic properties. <br />
** Electrical engineering - PCB design, electrical integration and programming. Focus on high reliability and low size & power. <br />
<br />
Charybdis - Spin Stabilization '''Contact: William'''<br />
<br />
*Charybdis is building a rocket that spins like a rifle bullet, then stops spinning mid-air to deploy parachutes. <br />
** Mechanical engineering - designing reliable deployment mechanism. <br />
** Aerodynamics and simulation - designing fin system to create desired spin. <br />
<br />
<br />
Argus - Distributed RF Camera System '''Lead: John'''<br />
<br />
*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. <br />
** Electrical Engineering - circuit board design, electrical integration. <br />
** Signals - RF & transmission tech.<br />
<br />
== Competition (IREC/SA Cup) ==<br />
* Structures<br />
* Payload<br />
* Recovery<br />
* Avionics, '''Leads: Sharon, Julea''' {{slack-user|splatt}} {{slack-user|juleachin}}<br />
** Design, implement, and test all the hardware and software that goes into our flight computers<br />
** Design and manufacture structures for avionics bay and work with other subteams to implement interfaces and integration processes<br />
** Design and test radio communications system for our rocket to talk to the ground <br />
** 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)<br />
* Launch Operations, '''Lead: WANTED'''<br />
** Work with each subteam to coordinate and prepare launch materials<br />
** Plan & execute travel and launch logistics <br />
** Oversee launch procedures, checklists, and go/no calls<br />
** Many more additional projects for ground support designable around personal interests<br />
* Simulations<br />
<br />
= Satellites =<br />
=== STAR-CROSSED===<br />
The Stanford Timing And Ranging –Cross-linking Optical Small Satellite Demonstration mission is an ambitious proposal seeking to place two cubesats in low Earth orbit and establish a laser-based data link between them across hundreds of kilometers. Such a mission has never before been attempted. If successful, the technology developed will enable a dramatic leap forward in the capabilities of both cubesats and larger satellitesto communicate high volumes of data across long distances.<br />
<br />
Optical links using lasers are capable of dramatically higher data transmission speeds than existing radio systems, but have never been successfully demonstrated at the cubesat scale. A cubesat-sized optical communications system willenable high-speed links between cubesats, allowing for networks built from affordable satellites.Miniaturizing an optical communications system to fit in a cubesat would also make it far easier for larger satellites to add optical networking capabilities, an almost essential component of proposed internet satellite constellations.<br />
<br />
Satellites with optical links can not only transmit data faster, but also better synchronize their timekeeping with each other and measure their separation distance, important features of boththe GPS system and groups of scientific satellites. With an optical network, satellites could conduct previously impossible scientific missions and significantly improve the accuracy of GPS<br />
<br />
Now is the perfect time to get involved with STAR-CROSSD. A number of subsystems need to be analyzed, designed, built, and tested, with opportunities to learn about electrical, mechanical, and software engineering, satellite operations, and more.<br />
<br />
=== POINTR ===<br />
Polar Orbiting INfrared Tracking Receiver (POINTR) has been Satellites’ primary focus since February. POINTR is an in flight demonstration of an optical receiver pointing, acquisition and tracking (PAT) system. The optical receiver payload hosted on Audacy’s 3U cubesat would be pointed to the ground to acquire and track a beacon laser sent from a suitable ground facility, currently proposed as NASA JPL’s OCTL facility. This mission would demonstrate the operational and technical requirements related to two satellites establishing an optical communications link with each other. The requirements include mission planning, command and execution of a pointing maneuver, acquisition of an incoming optical signal and tracking of the optical signal. This mission can be broken into four main goals:<br />
<br />
* Demonstrate a subset of technology for full bidirectional optical communications mission within the constraints placed by Audacy’s primary mission.<br />
<br />
* Increase chance of bidirectional optical communications mission success.<br />
<br />
* Develop experience within SSI designing and building space hardware.<br />
<br />
* Contribute to the cubesat and satellite optical communications technical fields.<br />
<br />
=== Our Subteams ===<br />
* '''Avionics'''<br />
**'''The Gist'''The Avionics group works on all of the core electrical systems for the Satellites team, including electrical power distribution, sensors, and computing. Learn how to design and reflow Printed Circuit Boards (PCBs) and work with signal-processing to understand light signals in the inky darkness of space! <br />
**'''The People To Talk to''' Sasha, Shi, Meera<br />
<br />
* '''GNC'''<br />
**'''The Gist''' The GNC group ("Guidance, Navigation, and Control") is responsible for determining and controlling the position and rotation of satellites in space even while hundreds or sometimes thousands of miles away. Join GNC to work with us on cutting-edge technologies and a system to control our satellites in orbit from the comfort of the SSI space bunker.<br />
**'''The People To Talk to''' Sasha<br />
<br />
* '''Optics'''<br />
**'''The Gist''' Optics is all about putting light to work - starting from simple laser pointers to finally sending a communications signal across 10 kilometers in space! We use lasers, lenses, filters, sensors and even moving mirrors to send light flying through space and catch it on the other side.<br />
**'''The People To Talk to''' Michael Taylor<br />
<br />
* '''Software'''<br />
**'''The Gist''' The software team tackles the many different challenges of software needed for satellites: from flight software to web development, we do it all. For flight software, we take advantage of parallel communications modules to manage real-time requirements on pointing control. For web development, we are partnering with the ground operations team to build thorough mission control software and web interface. If any of this seems daunting or complicated, don’t worry. We all started from scratch. Join software and get your code in space!<br />
**'''The People To Talk to''' Orien, Joan<br />
<br />
* '''Ground Ops'''<br />
**'''The Gist''' The Ground Operations team will build mission control software and web interface to analyze satellite behavior in-flight and react accordingly. Aside from software, physics and orbital mechanics are crucial parts of this team’s ability. This team is responsible for testing spacecraft stability, fault tolerance, and final mission success.<br />
**'''The People To Talk to''' Orien<br />
<br />
*'''Structures'''<br />
**'''The Gist''' The Structures team designs and builds all necessary flight mechanics, ranging from the overall structure to individual component mounts. We go through the full development process - whiteboard drawings, SolidWorks, and finally manufacturing.The Structures team is also responsible for many of the environmental considerations, such as the thermal and vacuum requirements of space, as well as the shock and vibration profile of launch.<br />
**'''The People To Talk to''' Anjali, Sandip<br />
<br />
= Biology =<br />
<br />
* Enzymatic DNA Synthesis Methods, '''Lead: Michael Uttmark''' {{slack-user|uttmark}}<br />
** Test commercial blocking groups for compatibility with [[Terminal Deoxynucleotidyl Transferase]]<br />
** Chemically synthesize nucleotides with different reversible blocking groups<br />
** Characterize and optimize [[Enzymatic Synthesis Methods | enzymatic DNA synthesis]] reaction efficiency<br />
** Build and run stochastic computer models of DNA synthesis to optimize reaction parameters<br />
** Research purification methods for synthesized DNA <br />
** Design and test your own synthesis method!<br />
* Sequence Verification<br />
** Execute and optimize any one of our existing verification procedures--[[Polyacrylamide Gel Electrophoresis]], [[Pyrosequencing]], or [[Ligation and Sequencing]]<br />
** Adapt LCMS or MALDI-TOF procedures for detecting single-base addition or determining the sequence of a sample. <br />
** Come up with new ways to verify single-base addition to a starting strand of DNA<br />
* Microfluidic Device Design<br />
** Design and program an [[Electrowetting on Dielectric]] microfluidic PCB<br />
** Simulate and test how a microfluidic system would work in microgravity<br />
** Port our DNA synthesis method to a solid substrate like controlled pore glass or streptavidin-biotin magnetic beads<br />
** 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<br />
** 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].<br />
** Build a system for cooling and temperature control of the device, perhaps using [https://en.wikipedia.org/wiki/Thermoelectric_cooling Peltiers]<br />
** Write an algorithm to minimize the number of groups of compatible templates needed for the [[Enzymatic Synthesis Methods | exonuclease method]]<br />
** Figure out how to power our PCB from a cubesat or other launch vehicle<br />
** Build testing rigs for DNA synthesis methods that are needed for experiments in lab<br />
<br />
= Policy =<br />
<br />
== DC Trip ==<br />
* Be a lead/co-lead for our DC trip in partnership with Citizens for Space<br />
<br />
== [[SpaceJams]] ==<br />
* Be a Discussion Lead(s) for a week and do a deep dive on a topic/news article of your choice<br />
<br />
== Your Project Here ==<br />
* Message {{slack-user|rebeccawong}} and let's chat about what you're interested in doing!<br />
<br />
= Operations =<br />
<br />
== Community ==<br />
* Come up with a theme for Special Dinner and make decorations (like a model Falcon 9!)<br />
* Help {{slack-user|dragland}} run SSI general dinners<br />
* Plan and run general community events like Trivia Night, Pathfinder, and Movie Night<br />
== Diversity ==<br />
* Build connections with engineering diversity groups on campus<br />
* Help {{slack-user|ruqayyatoorawa}} run workshops<br />
== Events ==<br />
* Find an interesting company and arrange a tour or talk<br />
* Help handle logistics of an existing talk, like by meeting an astronaut and walking him to Durand 450<br />
* Give a CEO or Venture Capitalist a tour of ESIII<br />
== Finance == <br />
* Complete reimbursements <br />
* Apply for grants & seek out new sponsors<br />
== Marketing ==<br />
* Design awesome swag (t-shirts, jackets, posters)<br />
* Reach out to reporters<br />
* Social media guru! (Facebook, Twitter, and Instagram posts)<br />
* Creating Snapchat filters for events<br />
* Designing flyers for upcoming talks<br />
* Going on launches to take pictures and videos<br />
== Outreach ==<br />
* Start discussions with local highschools and their science clubs<br />
* Organize or join an existing trip to a local school<br />
== Sponsors ==<br />
* Pursue a sponsorship (we'll walk you through how!)<br />
* Compile a list of bay-area aerospace companies<br />
== Website ==<br />
* Overhaul the budgeting system<br />
* Give the sponsors page dynamic content<br />
* Manage this very wiki<br />
* Manage our public and internal websites<br />
== Workspace ==<br />
* Make space-themed artwork to decorate ESIII<br />
* Plant more herbs<br />
* Paint a mural<br />
* Track inventory of supplies and parts<br />
<br />
[[Category:Getting started]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=SpaceJams&diff=3200SpaceJams2017-09-19T07:40:20Z<p>Rwong: /* Possible Discussion Topics */</p>
<hr />
<div>= What is SpaceJams?=<br />
SpaceJams is our weekly Policy "meeting". It is meant to be an informal get-together (with food!) for anyone in SSI that is interested in gaining a broader perspective on the space industry and learning about a particular topic or recent space news. We want this to be a welcoming and interactive space (pun intended) where anyone can jump in with questions, ideas, or insights. <br />
<br />
The overall structure is loosely as follows:<br />
* Each week, a member (or a couple of members) will be Discussion Leads, bringing in a topic or article(s) of interest and any relevant historical contexts that they feel the group would benefit from. <br />
* The Discussion Leads share and summarize the article or topic of choice, presenting any conflicting opinions, strategies, or current difficulties that makes this a relevant and intriguing topic.<br />
* Discussion Leads prepare a series of questions to pose to the group for discussion and any possible proposals or areas for further research. More often than not, there won't be a simple resolution to a topic -- and that's fine! The goal here isn't to solve the problems facing the aerospace industry, but rather to gain a better understanding of what's happening. Where we can, we may try to hypothesize what possible futures may look like.<br />
<br />
= Discussion Lead Schedule (Fall 2017) =<br />
<br />
Week 3 (Sun 10/8): Rebecca & ?<br />
<br />
Week 4:<br />
<br />
Week 5:<br />
<br />
Week 6:<br />
<br />
Week 7:<br />
<br />
Week 8:<br />
<br />
Week 9:<br />
<br />
= Possible Discussion Topics =<br />
Not sure where to start? Take a look at just a handful of issues present in the space world these days...<br />
<br />
* Back to the Moon or go to Mars?<br />
* US Space Corps<br />
* Space debris -- Who's problem is it? How to enforce rules?<br />
* (Asteroid) Mining and territorial ownership<br />
* NASA's Space Launch System (SLS) <br />
* Legislative oversight for national colonization of outer space bodies?<br />
* What are the most important considerations for Mars colonization?<br />
* The right role for NASA given private launchers like SpaceX, Blue Origin, Rocket Lab, etc<br />
* How much human safety should be a priority<br />
* What we should be developing? (e.g. focus on launch, or do we need more human health stuff)<br />
* Why should we settle other planets vs focus on taking care of Earth?<br />
* Why should we go to or explore space at all?<br />
* How will colonization affect society and culture?<br />
* Space weaponry laws (and how they affect space debris clearance)<br />
* Military vs. civilian space divides<br />
* How Earth imaging companies like Planet should handle privacy or security issues<br />
* Should countries try for self-sufficiency in space at greater expense<br />
* How should the US respond if China goes for the moon again? <br />
* Expanding commercial crew?<br />
* Deep Space Gateway pro/con <br />
* Planetary protection issues (e.g. Europa science?)<br />
<br />
Other great places to start:<br />
* http://spacenews.com<br />
* http://space.com<br />
* https://phys.org/space-news/<br />
* https://www.nbcnews.com/science/space<br />
* http://spacedaily.com<br />
* Any other reputable news sources (Newsweek, Forbes, Popular Science, LA/NY Times, etc)<br />
[[Category: Policy]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=SpaceJams&diff=3199SpaceJams2017-09-19T07:34:11Z<p>Rwong: </p>
<hr />
<div>= What is SpaceJams?=<br />
SpaceJams is our weekly Policy "meeting". It is meant to be an informal get-together (with food!) for anyone in SSI that is interested in gaining a broader perspective on the space industry and learning about a particular topic or recent space news. We want this to be a welcoming and interactive space (pun intended) where anyone can jump in with questions, ideas, or insights. <br />
<br />
The overall structure is loosely as follows:<br />
* Each week, a member (or a couple of members) will be Discussion Leads, bringing in a topic or article(s) of interest and any relevant historical contexts that they feel the group would benefit from. <br />
* The Discussion Leads share and summarize the article or topic of choice, presenting any conflicting opinions, strategies, or current difficulties that makes this a relevant and intriguing topic.<br />
* Discussion Leads prepare a series of questions to pose to the group for discussion and any possible proposals or areas for further research. More often than not, there won't be a simple resolution to a topic -- and that's fine! The goal here isn't to solve the problems facing the aerospace industry, but rather to gain a better understanding of what's happening. Where we can, we may try to hypothesize what possible futures may look like.<br />
<br />
= Discussion Lead Schedule (Fall 2017) =<br />
<br />
Week 3 (Sun 10/8): Rebecca & ?<br />
<br />
Week 4:<br />
<br />
Week 5:<br />
<br />
Week 6:<br />
<br />
Week 7:<br />
<br />
Week 8:<br />
<br />
Week 9:<br />
<br />
= Possible Discussion Topics =<br />
Not sure where to start? Take a look at just a handful of issues present in the space world these days...<br />
<br />
* Back to the Moon or go to Mars?<br />
* US Space Corps<br />
* Space debris -- Who's problem is it? How to enforce rules?<br />
* (Asteroid) Mining and territorial ownership<br />
* NASA's Space Launch System (SLS) <br />
* National colonization of outer space bodies<br />
* The right role for NASA given private launchers like SpaceX, Blue Origin, Rocket Lab, etc<br />
* How much human safety should be a priority<br />
* What we should be developing? (e.g. focus on launch, or do we need more human health stuff)<br />
* Why should we settle other planets vs focus on taking care of Earth?<br />
* Why should we go to or explore space at all?<br />
* How will colonization affect society and culture?<br />
* Space weaponry laws (and how they affect space debris clearance)<br />
* Military vs. civilian space divides<br />
* How Earth imaging companies like Planet should handle privacy or security issues<br />
* Should countries try for self-sufficiency in space at greater expense<br />
* How should the US respond if China goes for the moon again? <br />
* Expanding commercial crew?<br />
* Deep Space Gateway pro/con <br />
* Planetary protection issues (e.g. Europa science?)<br />
<br />
[[Category: Policy]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=SpaceJams&diff=3197SpaceJams2017-09-19T07:27:42Z<p>Rwong: /* What is SpaceJams? */</p>
<hr />
<div>= What is SpaceJams?=<br />
SpaceJams is our weekly Policy "meeting". It is meant to be an informal get-together (with food!) for anyone in SSI that is interested in gaining a broader perspective on the space industry and learning about a particular topic or recent space news. We want this to be a welcoming and interactive space (pun intended) where anyone can jump in with questions, ideas, or insights. <br />
<br />
The overall structure is loosely as follows:<br />
* Each week, a member (or a couple of members) will be Discussion Leads, bringing in a topic or article(s) of interest and any relevant historical contexts that they feel the group would benefit from. <br />
* The Discussion Leads share and summarize the article or topic of choice, presenting any conflicting opinions, strategies, or current difficulties that makes this a relevant and intriguing topic.<br />
* Discussion Leads prepare a series of questions to pose to the group for discussion and any possible proposals or areas for further research. More often than not, there won't be a simple resolution to a topic -- and that's fine! The goal here isn't to solve the problems facing the aerospace industry, but rather to gain a better understanding of what's happening. Where we can, we may try to hypothesize what possible futures may look like.<br />
<br />
= Discussion Lead Schedule (Fall 2017) =<br />
<br />
Week 3 (Sun 10/8): Rebecca & ?<br />
<br />
Week 4:<br />
<br />
Week 5:<br />
<br />
Week 6:<br />
<br />
Week 7:<br />
<br />
Week 8:<br />
<br />
Week 9:<br />
<br />
[[Category: Policy]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Policy_Team&diff=3194Policy Team2017-09-19T07:26:52Z<p>Rwong: </p>
<hr />
<div>The Policy Team explores how and why space development occurs and how the approach towards space is changing. By seeking an understanding of the legislation, market trends, history, and philosophy that has affected the development of the space industry, we hope to build up a community of students that can speak intelligently about the nuances of the space sector in today's world. Throughout the year, we’ll tackle the most pressing questions of modern space exploration through research, discussions, debates, and an immersive trip to DC. <br />
<br />
Also back for its third run this Winter, the Policy Team will again offer an introductory class on space policy this Winter quarter, [[AA 47SI: Why Go to Space?]], featuring guest speakers from industry, academia, and government. Though a small team in its current form, we’re excited for new members to join us in understanding space beyond just the nuts and bolts.<br />
<br />
Join us at our weekly "meetings", [[SpaceJams]], and don't hesitate to reach out to the current team lead, Rebecca {{slack-user|rebeccawong}}<br />
<br />
<noinclude>[[Category:Policy| ]]</noinclude></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=SpaceJams&diff=3191SpaceJams2017-09-19T07:25:39Z<p>Rwong: Created page with "= What is SpaceJams?= SpaceJams is our weekly Policy "meeting". It is meant to be an informal get-together (with food!) for anyone in SSI that is interested in gaining a broad..."</p>
<hr />
<div>= What is SpaceJams?=<br />
SpaceJams is our weekly Policy "meeting". It is meant to be an informal get-together (with food!) for anyone in SSI that is interested in gaining a broader perspective on the space industry and learning about a particular topic or recent space news. We want this to be a welcoming and interactive space (pun intended) where anyone can jump in with questions, ideas, or insights. <br />
<br />
The overall structure is loosely as follows:<br />
* Each week, a member (or a couple of members) will be Discussion Leads, bringing in a topic or article(s) of interest and any relevant historical contexts that they feel the group would benefit from. <br />
* The Discussion Leads spend ~ 10 minutes sharing and summarizing the article or topic of choice, presenting any conflicting opinions, strategies, or current difficulties that makes this a relevant and intriguing topic.<br />
* Discussion Leads prepare a series of questions to pose to the group for discussion and any possible proposals or areas for further research. More often than not, there won't be a simple resolution to a topic -- and that's fine! The goal here isn't to solve the problems facing the aerospace industry, but rather to gain a better understanding of what's happening. Where we can, we may try to hypothesize what possible futures may look like.<br />
<br />
= Discussion Lead Schedule (Fall 2017) =<br />
<br />
Week 3 (Sun 10/8): Rebecca & ?<br />
<br />
Week 4:<br />
<br />
Week 5:<br />
<br />
Week 6:<br />
<br />
Week 7:<br />
<br />
Week 8:<br />
<br />
Week 9:<br />
<br />
[[Category: Policy]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=AA_47SI:_Why_Go_to_Space%3F&diff=3186AA 47SI: Why Go to Space?2017-09-19T07:11:43Z<p>Rwong: </p>
<hr />
<div>AA 47SI is a student-initiated policy class that was initiated by Rishi Bedi and [[user:Thomas|Thomas Teisberg]] in the Winter of 2016. This year it will be led by Thomas White and Anjali Roychowdhury. This course is an introduction to space policy issues, with an emphasis on the modern United States. It presents a historical overview of space programs from all around the world and discusses present policy issues, through lectures and guest speakers from NASA, the Department of Defense, new and legacy space industry companies, and other stakeholders. Students will present on one issue that piques their interest, selecting from various domains including commercial concerns, military questions, and geopolitical considerations.<br />
<br />
[[Category: Policy]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Policy_Team&diff=3185Policy Team2017-09-19T07:08:33Z<p>Rwong: update!</p>
<hr />
<div>The Policy Team explores how and why space development occurs and how the approach towards space is changing. By seeking an understanding of the legislation, market trends, history, and philosophy that has affected the development of the space industry, we hope to build up a community of students that can speak intelligently about the nuances of the space sector in today's world. Throughout the year, we’ll tackle the most pressing questions of modern space exploration through research, discussions, debates, and an immersive trip to DC. Also back for its third run this Winter, the Policy Team will again offer an introductory class on space policy this Winter quarter, [[AA 47SI: Why Go to Space?]], featuring guest speakers from industry, academia, and government. Though a small team in its current form, we’re excited for new members to join us in understanding space beyond just the nuts and bolts.<br />
<br />
The current team lead is Rebecca {{slack-user|rebeccawong}}<br />
<br />
<noinclude>[[Category:Policy| ]]</noinclude></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Operations_Team&diff=3183Operations Team2017-09-19T06:57:04Z<p>Rwong: /* Alumni */</p>
<hr />
<div>Operations is the place in SSI to learn professional skills and connect to the wider aerospace community. The skills you’ll learn are so diverse -- from graphic design to how to get a sponsorship -- that they’re near impossible to summarize. Space is so much more than just the technology, and Operations where it all happens. If you want to know how to manage a group of 200 members with a six figure budget, make space art to decorate our workspace, or get connected to the top of the space industry, Operations is the place for you. <br />
<br />
Space would hardly be possible without the people behind the hardware, getting sponsorships, building community, and talking to CEOs and Venture Capitalists across the industry. We’ve brought in speakers like Charlie Bolden, the then-administrator of NASA, and this year will be hosting Gwynne Shotwell, the President of SpaceX. We have a half dozen different efforts that form the backbone of SSI. The current team lead is Kai Marshland {{slack-user|kai}} -- feel free to reach out if you want to get involved!<br />
<br />
Operations is split into a number of subgroups<br />
<br />
= Events =<br />
Operations brings space to Stanford and sends its members out into the world. The entire Operations team started with Events and we’re only getting better. In the fall, we’re bringing in two NASA astronauts, one of whom was the Chief Scientist for all of NASA, and Gwynne Shotwell, the President of SpaceX; later in the year, we’ll be working with Ubiquity and Bessemer Ventures to run a panel with more CEOs followed by a networking event. Throughout the year, we host talks & tours at Stanford while sending our members beyond. <br />
<br />
= Marketing =<br />
Marketing is where you can learn graphic design in order to make gorgeous materials like this very pamphlet, or reach out to magazines like Wired, Techcrunch, and the Stanford Daily in order to showcase our projects to the world. Oh, and if you want to manage our social media (aka make dank memes) this is the place to be. You have them to thank for all of our gorgeous materials, posters, and swag.<br />
<br />
= Website =<br />
Our Website group manages both the beautiful main website and the internal site, which in addition to looking gorgeous brims with tools like the reimbursement system and resume book. Through a full, feature-rich system (if you want to make enterprise software, this is a great way to get started) the Website makes managing SSI a dream.<br />
<br />
= Diversity =<br />
If you’ve ever resented the fact that the space industry has historically been dominated by balding white men, the Diversity group works to make our own group as inclusive as possible as we train the next generation of industry leaders. We want space to be the most welcoming community possible, and that stretches far beyond SSI -- but Diversity the ones who run workshops, train each other, and work to make that happen. <br />
<br />
= Outreach =<br />
Outreach efforts focus on bringing our stories to local schools and even the Maker Faire. Outreach launches SSI straight out of the Stanford bubble and into the real world.<br />
<br />
= Finance =<br />
Finance should really be called the wolves of wall-ssi, because they focus on managing the six-figure budget, handling reimbursements, and interfacing with Stanford administrators.<br />
<br />
= Workspace =<br />
Workspace manages the 60-foot-tall underground bunker we call home. That means running a machine shop, planting herbs, and painting space-themed murals across our cavernous space.<br />
<br />
= Community =<br />
Community is why SSI feels like a home. Community runs dinners, trivia night, and even our spring retreat. Plus, if you like memes, we might have a channel on slack for that which technically falls under operations. Community is what makes SSI, in the words of one of our members, “the family I always wish I had.”<br />
<br />
= Sponsors =<br />
Sponsorships leverages the alumni network and SSI’s own contacts in order to keep SSI funded. Extorting aerospace executives makes SSI's projects possible. <br />
<br />
= Alumni = <br />
Here in the valley, you're an ancient, creaking Methuselah by the time you reach 22. Unless, of course, you're part of the SSI alumni network, which is run by the group of the same name. Alumni keeps this running, organizing events for aged 20-somethings to rest their aching bones.<br />
<br />
This year we're starting an official program for our beloved elderly. If you've got ideas or want to help build up this awesome network, poke Rebecca {{slack-user|rebeccawong}}<br />
<br />
----<br />
<br />
<br />
<noinclude>[[Category:Operations]]</noinclude></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=3094Find a Project2017-09-17T22:10:52Z<p>Rwong: </p>
<hr />
<div>= SSI Overload = <br />
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.<br />
<br />
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.''<br />
<br />
= Balloons =<br />
<br />
== HABMC ==<br />
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<br />
* 3D visualizations using Cesium or Unity<br />
* Natural Language Processing for the commands module<br />
* Create a mobile app using React Native<br />
* Improved [[Balloons Radio Projects|RF integrations]]<br />
* Overhaul security on websocket connections<br />
* Navigation algorithms<br />
<br />
== ValBal ==<br />
<br />
== HABEES ==<br />
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!<br />
<br />
== BUZZ ==<br />
<br />
= Rockets =<br />
== Onboarding ==<br />
<br />
== Daedalus ==<br />
<br />
== Competition (IREC/SA Cup) ==<br />
* Structures<br />
* Payload<br />
* Recovery<br />
* Avionics, '''Leads: Sharon, Julea''' {{slack-user|splatt}} {{slack-user|juleachin}}<br />
** Design, implement, and test all the hardware and software that goes into our flight computers<br />
** Design and manufacture structures for avionics bay and work with other subteams to implement interfaces and integration processes<br />
** Design and test radio communications system for our rocket to talk to the ground <br />
** 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)<br />
* Launch Operations, '''Lead: WANTED'''<br />
** Work with each subteam to coordinate and prepare launch materials<br />
** Plan & execute travel and launch logistics <br />
** Oversee launch procedures, checklists, and go/no calls<br />
** Many more additional projects for ground support designable around personal interests<br />
* Simulations<br />
<br />
= Satellites =<br />
<br />
= Biology =<br />
<br />
= Policy =<br />
<br />
= Operations =<br />
<br />
== Community ==<br />
* Come up with a theme for Special Dinner and make decorations (like a model Falcon 9!)<br />
* Help {{slack-user|dragland}} run SSI general dinners<br />
* Plan and run general community events like Trivia Night, Pathfinder, and Movie Night<br />
== Diversity ==<br />
* Build connections with engineering diversity groups on campus<br />
* Help {{slack-user|ruqayyatoorawa}} run workshops<br />
== Events ==<br />
* Find an interesting company and arrange a tour or talk<br />
* Help handle logistics of an existing talk, like by meeting an astronaut and walking him to Durand 450<br />
* Give a CEO or Venture Capitalist a tour of ESIII<br />
== Finance == <br />
* Complete reimbursements <br />
* Apply for grants & seek out new sponsors<br />
== Marketing ==<br />
* Design awesome swag (t-shirts, jackets, posters)<br />
* Reach out to reporters<br />
* Social media guru! (Facebook, Twitter, and Instagram posts)<br />
* Creating Snapchat filters for events<br />
* Designing flyers for upcoming talks<br />
* Going on launches to take pictures and videos<br />
== Outreach ==<br />
* Start discussions with local highschools and their science clubs<br />
* Organize or join an existing trip to a local school<br />
== Sponsors ==<br />
* Pursue a sponsorship (we'll walk you through how!)<br />
* Compile a list of bay-area aerospace companies<br />
== Website ==<br />
* Overhaul the budgeting system<br />
* Give the sponsors page dynamic content<br />
* Manage this very wiki<br />
* Manage our public and internal websites<br />
== Workspace ==<br />
* Make space-themed artwork to decorate ESIII<br />
* Plant more herbs<br />
* Paint a mural<br />
* Track inventory of supplies and parts</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=3085Find a Project2017-09-17T05:59:48Z<p>Rwong: /* Competition (IREC/SA Cup) */</p>
<hr />
<div>= SSI Overload = <br />
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.<br />
<br />
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.''<br />
<br />
= Balloons =<br />
= Rockets =<br />
== Onboarding ==<br />
<br />
== Daedalus ==<br />
<br />
== Competition (IREC/SA Cup) ==<br />
* Structures<br />
* Payload<br />
* Recovery<br />
* Avionics<br />
** Avionics Bay Hardware & Software: Responsible for selecting parts (sensors, microcontrollers, connectors, etc), designing and validating circuit boards, programming everything, working with RF for testing, and making sure we have reliable, redundant flight computers that will trigger recovery separation events and send data back to the ground. '''Skills: EE, CS; Lead: Sharon''' {{slack-user|splatt}}<br />
** Avionics Bay Structures & Integration: Responsible for design and manufacturing of structures for avionics bay; working with HW/SW for PCB interfaces and connections; working with Recovery for interfaces and connections; working with Structures and Systems for overall design, rocket placement, and integration processes. '''Skills: ME, Good organization & communications skills; Lead: Julea''' {{slack-user|juleachin}}<br />
** Avionics Radio (RF) Communications: Responsible for designing and testing radio communications system for rocket to talk to the ground including: radio and antenna selection; link budget creation; ground testing (on & off campus); working with HW/SW and Ground Station for interfaces. '''Skills: EE; Lead: Sharon''' {{slack-user|splatt}}<br />
** Avionics Ground Station: Responsible for writing software to parse and visualize data; working with RF to coordinate ground radios and antennas; designing & building protective case to make sure laptops & other electronics don't die in the blazing desert heat and dust. '''Skills: ME, CS; Lead: WANTED'''<br />
* Launch Operations: Responsible for working with each subteam to coordinate and prepare launch materials; planning & executing travel and launch logistics; overseeing launch procedures, checklists, and go/no calls. Additional projects for ground support designable around personal interests. '''Skills: Organization, Willingness to just jump in; Lead: WANTED'''<br />
* Simulations<br />
<br />
= Satellites =<br />
<br />
= Biology =<br />
<br />
= Policy =<br />
<br />
= Operations =<br />
<br />
== Alumni ==<br />
== Community ==<br />
== Diversity & Inclusion ==<br />
== Education & Outreach ==<br />
== Events ==<br />
== Finance & Sponsors == <br />
== Marketing ==<br />
== Website ==<br />
== Workspace ==</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=3084Find a Project2017-09-17T05:56:06Z<p>Rwong: /* Competition (IREC/SA Cup) */</p>
<hr />
<div>= SSI Overload = <br />
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.<br />
<br />
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.''<br />
<br />
= Balloons =<br />
= Rockets =<br />
== Onboarding ==<br />
<br />
== Daedalus ==<br />
<br />
== Competition (IREC/SA Cup) ==<br />
* Structures<br />
* Payload<br />
* Recovery<br />
* Avionics<br />
** Avionics Bay Hardware & Software: Responsible for selecting parts (sensors, microcontrollers, connectors, etc), designing and validating circuit boards, programming everything, working with RF for testing, and making sure we have reliable, redundant flight computers that will trigger recovery separation events and send data back to the ground. '''Skills: EE, CS; Lead: Sharon''' {{slack-user|splatt}}<br />
** Avionics Bay Structures & Integration: Responsible for design and manufacturing of structures for avionics bay; working with HW/SW for PCB interfaces and connections; working with Recovery for interfaces and connections; working with Structures and Systems for overall design, rocket placement, and integration processes. '''Skills: ME, Good organization & communications skills; Lead Julea''' {{slack-user|juleachin}}<br />
** Avionics Radio (RF) Communications: Responsible for designing and testing radio communications system for rocket to talk to the ground including: radio and antenna selection; link budget creation; ground testing (on & off campus); working with HW/SW and Ground Station for interfaces. '''Skills: EE; Lead: Sharon''' {{slack-user|splatt}}<br />
** Avionics Ground Station: Responsible for writing software to parse and visualize data; working with RF to coordinate ground radios and antennas; designing & building protective case to make sure laptops & other electronics don't die in the blazing desert heat and dust. '''Skills: ME, CS; Lead: WANTED'''<br />
* Launch Operations: Responsible for working with each subteam to coordinate and prepare launch materials; planning & executing travel and launch logistics; overseeing launch procedures, checklists, and go/no calls. Additional projects for ground support designable around personal interests. '''Skills: Organization, Willingness to just jump in; Lead: WANTED'''<br />
* Simulations<br />
<br />
= Satellites =<br />
<br />
= Biology =<br />
<br />
= Policy =<br />
<br />
= Operations =<br />
<br />
== Alumni ==<br />
== Community ==<br />
== Diversity & Inclusion ==<br />
== Education & Outreach ==<br />
== Events ==<br />
== Finance & Sponsors == <br />
== Marketing ==<br />
== Website ==<br />
== Workspace ==</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=3083Find a Project2017-09-17T05:55:20Z<p>Rwong: Prototype to get feedback</p>
<hr />
<div>= SSI Overload = <br />
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.<br />
<br />
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.''<br />
<br />
= Balloons =<br />
= Rockets =<br />
== Onboarding ==<br />
<br />
== Daedalus ==<br />
<br />
== Competition (IREC/SA Cup) ==<br />
* Structures<br />
* Payload<br />
* Recovery<br />
* Avionics<br />
** Avionics Bay Hardware & Software: Responsible for selecting parts (sensors, microcontrollers, connectors, etc), designing and validating circuit boards, programming everything, working with RF for testing, and making sure we have reliable, redundant flight computers that will trigger recovery separation events and send data back to the ground. '''Skills: EE, CS; Lead: Sharon {{slack-user|splatt}}'''<br />
** Avionics Bay Structures & Integration: Responsible for design and manufacturing of structures for avionics bay; working with HW/SW for PCB interfaces and connections; working with Recovery for interfaces and connections; working with Structures and Systems for overall design, rocket placement, and integration processes. '''Skills: ME, Good organization & communications skills; Lead Julea {{slack-user|juleachin}}'''<br />
** Avionics Radio (RF) Communications: Responsible for designing and testing radio communications system for rocket to talk to the ground including: radio and antenna selection; link budget creation; ground testing (on & off campus); working with HW/SW and Ground Station for interfaces. '''Skills: EE; Lead: Sharon {{slack-user|splatt}}'''<br />
** Avionics Ground Station: Responsible for writing software to parse and visualize data; working with RF to coordinate ground radios and antennas; designing & building protective case to make sure laptops & other electronics don't die in the blazing desert heat and dust. '''Skills: ME, CS; Lead: WANTED'''<br />
* Launch Operations: Responsible for working with each subteam to coordinate and prepare launch materials; planning & executing travel and launch logistics; overseeing launch procedures, checklists, and go/no calls. Additional projects for ground support designable around personal interests. '''Skills: Organization, Willingness to just jump in; Lead: WANTED'''<br />
* Simulations<br />
<br />
= Satellites =<br />
<br />
= Biology =<br />
<br />
= Policy =<br />
<br />
= Operations =<br />
<br />
== Alumni ==<br />
== Community ==<br />
== Diversity & Inclusion ==<br />
== Education & Outreach ==<br />
== Events ==<br />
== Finance & Sponsors == <br />
== Marketing ==<br />
== Website ==<br />
== Workspace ==</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=3082How to Join SSI2017-09-17T04:45:20Z<p>Rwong: /* Becoming an official member */ changed FO names and slack handles</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# 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.<br />
# Join the SSI Slack [https://ssi-teams.slack.com/signup here].<br />
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].<br />
# In order to allow you access to our workspace, [[End Station III]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.<br />
##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.<br />
##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.<br />
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.<br />
##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.<br />
##Send a message in {{slack-channel|welcome-to-ssi}} that you've completed everything!<br />
<br />
=Resources=<br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams.<br />
<br />
== [https://stanfordssi.org/leadership SSI Leadership] ==<br />
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.<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [http://stanfordssi.org/join All The Mailing Lists] ==<br />
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)<br />
<br />
== [[End Station III]] ==<br />
<br />
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.</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI%27s_Alumni_Network&diff=3046How to Join SSI's Alumni Network2017-09-13T08:54:00Z<p>Rwong: </p>
<hr />
<div>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!<br />
<br />
= [https://alumni.stanford.edu/get/page/groups/overview/?group_id=0038994816 Join our Stanford Alumni Group/Mailing List] =<br />
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.<br />
<br />
= [https://internal.stanfordssi.org/users/questionaire Join our Internal Database] =<br />
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.<br />
<br />
= Stay Connected with SSI! =<br />
*[https://www.facebook.com/StanfordSSI/ Like us on Facebook]<br />
*[https://twitter.com/stanfordssi Follow us on Twitter]<br />
*[https://www.instagram.com/stanford_ssi/ Check out our Instagram]<br />
*[https://www.linkedin.com/groups/6774947 Connect with others on LinkedIn]<br />
<br />
= Got Questions? =<br />
If you have questions about anything, don't hesitate to [mailto:rebeccawong@stanford.edu contact our current SSI Alumni Coordinator], Rebecca.</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI%27s_Alumni_Network&diff=3010How to Join SSI's Alumni Network2017-09-09T21:10:43Z<p>Rwong: </p>
<hr />
<div>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!<br />
<br />
= [https://alumni.stanford.edu/get/page/groups/overview/?group_id=0038994816 Join our Stanford Alumni Group/Mailing List] =<br />
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.<br />
<br />
= [https://internal.stanfordssi.org/users/questionaire Join our Internal Database] =<br />
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.<br />
<br />
= Got Questions? =<br />
If you have questions about anything, don't hesitate to [mailto:rebeccawong@stanford.edu contact our current SSI Alumni Coordinator], Rebecca.</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI%27s_Alumni_Network&diff=2896How to Join SSI's Alumni Network2017-08-19T07:04:07Z<p>Rwong: /* Join our Stanford Alumni Group/Mailing List */</p>
<hr />
<div>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!<br />
<br />
= [https://alumni.stanford.edu/get/page/groups/overview/?group_id=0038994816 Join our Stanford Alumni Group/Mailing List] =<br />
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.<br />
<br />
= [https://internal.stanfordssi.org/users/questionaire Join our Internal Database] =<br />
We love having our alumni offer advice with design reviews, host us for tours, and more. 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 go back in and update your information.<br />
<br />
= Got Questions? =<br />
If you have questions about anything, don't hesitate to [mailto:rebeccawong@stanford.edu contact our current SSI Alumni Coordinator], Rebecca.</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI%27s_Alumni_Network&diff=2895How to Join SSI's Alumni Network2017-08-19T06:59:44Z<p>Rwong: first publish</p>
<hr />
<div>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!<br />
<br />
= [https://alumni.stanford.edu/get/page/groups/overview/?group_id=0038994816 Join our Stanford Alumni Group/Mailing List] =<br />
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 to SSI alumni.<br />
<br />
= [https://internal.stanfordssi.org/users/questionaire Join our Internal Database] =<br />
We love having our alumni offer advice with design reviews, host us for tours, and more. 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 go back in and update your information.<br />
<br />
= Got Questions? =<br />
If you have questions about anything, don't hesitate to [mailto:rebeccawong@stanford.edu contact our current SSI Alumni Coordinator], Rebecca.</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=2415How to Join SSI2017-01-17T22:21:03Z<p>Rwong: added leadership link</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10 in exchange for a t-shirt) to one of our financial officers - Evan Long or Nate Simon can accept the dues.<br />
# In order to allow you access to our workspace, [[Mission Control]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.'''<br />
##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. Talk to Austin Pineault if you have questions about EH&S training.<br />
##Sign into the [http://internal.stanfordssi.org/trainings internal site] and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.<br />
##Attend a safety tour of MC. Send a message to Austin Pineault to set up a time.<br />
# Fill out [https://docs.google.com/a/stanford.edu/forms/d/e/1FAIpQLSesFRAbj9AWz6_tKHVAYKACvCQ4b3Gt9a3lyWpjh4vScXOBPg/viewform this form] so we can add you to our official roster!<br />
<br />
=Resources=<br />
<br />
Here are some resources that will get you up to speed and on the same page with us:<br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams<br />
<br />
== [https://stanfordssi.org/leadership SSI Leadership] ==<br />
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.<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [http://stanfordssi.org/join All The Mailing Lists] ==<br />
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)<br />
<br />
== [[Mission Control]] ==<br />
<br />
Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Clean_a_Rocket_Motor&diff=2390How to Clean a Rocket Motor2017-01-11T23:14:45Z<p>Rwong: bullets and spelling</p>
<hr />
<div>{{guide| authors=Rebecca Wong ({{slack-user|rebeccawong}})}}<br />
<br />
* Wait for motor to cool down <br />
* Discard of all internal components (Only keep the forward and aft closures and the casing) <br />
* Shake out any remnants of propellant or BP<br />
* Soak closures in vinegar for 15 min<br />
* Soak paper towels in vinegar and insert into casing and let sit for 15 min<br />
* Discard vinegar, rinse casings w water<br />
* Wipe everything with clorox wipes<br />
* Rinse again w water<br />
* Dry w paper towels<br />
* Apply light coat of grease to closures and screw onto casing <br />
* Enjoy your shiny "new" motor casing<br />
<br />
[[Category: Rockets]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Clean_a_Rocket_Motor&diff=2389How to Clean a Rocket Motor2017-01-11T23:14:10Z<p>Rwong: added some content. will be back later to format and explain</p>
<hr />
<div>{{guide| authors=Rebecca Wong ({{slack-user|rebeccawong}})}}<br />
<br />
Wait for motor to cool down <br />
Discard of all internal components (Only keep the forward and aft closures and the casing) <br />
Shake out any remnants of propellant or BP<br />
Soak closures in vinegar for 15 min<br />
Soak paper towels in vinegar and insert into casing and let sit for 15 min<br />
Discard vinegar, rinse casings w water<br />
Wipe everything with clorox wipes<br />
Rince again w water<br />
Dry w paper towels<br />
Apply light coat of grease to closures and screw onto casing <br />
Enjoy your shiny "new" motor casing<br />
<br />
[[Category: Rockets]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Clean_a_Rocket_Motor&diff=2388How to Clean a Rocket Motor2017-01-11T23:13:22Z<p>Rwong: created this page</p>
<hr />
<div>{{guide| authors=Rebecca Wong ({{slack-user|rebeccawong}})}}<br />
<br />
[[Category: Rockets]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=List_of_Missions&diff=2328List of Missions2016-11-21T09:50:15Z<p>Rwong: </p>
<hr />
<div>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.<br />
<br />
<br />
<br />
<gallery widths=200px heights=200px><br />
|align=center<br />
File:Rsz 11ssi 19.png|<center> [[SSI-19]], Balloons Team, May 16th, 2015 </center><br />
File:Rsz ssi-22.png |<center> [[SSI-22]], Balloons Team, May 31st, 2015 </center><br />
File:SSI-1E4.png|<center> [[SSI-1E4]], Satellites Team, June 4, 2015 </center><br />
File:Ssi 23.png |<center> [[SSI-23]], Balloons Team, October 24th, 2015 </center><br />
File:Ssi 24.png |<center> [[SSI-24]], Balloons Team, October 24th, 2015 </center><br />
File:Ssi 25.png |<center> [[SSI-25]], Balloons Team, October 24th, 2015 </center><br />
File:SSI-R1.png|<center> SSI-R1, Rockets Team, February 6th, 2016 </center><br />
File:SSI-31.png|<center> [[SSI-31]], Balloons Team, February 13th, 2016 </center><br />
File:SSI-38.png|<center> [[SSI-38]], Balloons Team, May 8, 2016 </center><br />
File:STAR-CROSSD.png|<center> [[STAR-CROSSD]], Satellites Team, May, 2016 </center><br />
File:SSI-39.jpg|<center> [[SSI-39]], Balloons Team, May 30, 2016 </center><br />
File:SSI-40.png|<center> [[SSI-40]], Balloons Team, June 2016 </center><br />
File:SSI-41.png|<center> [[SSI-41]], Balloons Team, June 15, 2016 </center><br />
File:SSI-42.png|<center> [[SSI-42]], Balloons Team, July 12, 2016 </center><br />
File:SSI-R6.png|<center> SSI-R6, Rockets Team, July 6th, 2016 </center><br />
File:SSI-1E4-2.png|<center> SSI-1E4-2, Satellites Team, August 20, 2015 </center><br />
File:SSI-R8.jpg|<center> SSI-R8, Rockets Team, November 19th, 2016 </center><br />
<br />
</gallery></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=File:SSI-R6.png&diff=2327File:SSI-R6.png2016-11-21T09:49:27Z<p>Rwong: </p>
<hr />
<div></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=File:SSI-R8.jpg&diff=2326File:SSI-R8.jpg2016-11-21T09:46:18Z<p>Rwong: Rwong uploaded a new version of File:SSI-R8.jpg</p>
<hr />
<div></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=List_of_Missions&diff=2325List of Missions2016-11-21T09:32:29Z<p>Rwong: </p>
<hr />
<div>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.<br />
<br />
<br />
<br />
<gallery widths=200px heights=200px><br />
|align=center<br />
File:Rsz 11ssi 19.png|<center> [[SSI-19]], Balloons Team, May 16th, 2015 </center><br />
File:Rsz ssi-22.png |<center> [[SSI-22]], Balloons Team, May 31st, 2015 </center><br />
File:SSI-1E4.png|<center> [[SSI-1E4]], Satellites Team, June 4, 2015 </center><br />
File:Ssi 23.png |<center> [[SSI-23]], Balloons Team, October 24th, 2015 </center><br />
File:Ssi 24.png |<center> [[SSI-24]], Balloons Team, October 24th, 2015 </center><br />
File:Ssi 25.png |<center> [[SSI-25]], Balloons Team, October 24th, 2015 </center><br />
File:SSI-R1.png|<center> SSI-R1, Rockets Team, February 6th, 2016 </center><br />
File:SSI-31.png|<center> [[SSI-31]], Balloons Team, February 13th, 2016 </center><br />
File:SSI-38.png|<center> [[SSI-38]], Balloons Team, May 8, 2016 </center><br />
File:STAR-CROSSD.png|<center> [[STAR-CROSSD]], Satellites Team, May, 2016 </center><br />
File:SSI-39.jpg|<center> [[SSI-39]], Balloons Team, May 30, 2016 </center><br />
File:SSI-40.png|<center> [[SSI-40]], Balloons Team, June 2016 </center><br />
File:SSI-41.png|<center> [[SSI-41]], Balloons Team, June 15, 2016 </center><br />
File:SSI-42.png|<center> [[SSI-42]], Balloons Team, July 12, 2016 </center><br />
File:SSI-1E4-2.png|<center> SSI-1E4-2, Satellites Team, August 20, 2015 </center><br />
File:SSI-R8.jpg|<center> SSI-R8, Rockets Team, November 19th, 2016 </center><br />
<br />
</gallery></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=File:SSI-R8.jpg&diff=2324File:SSI-R8.jpg2016-11-21T09:31:49Z<p>Rwong: </p>
<hr />
<div></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=File:SSI-R8.png&diff=2323File:SSI-R8.png2016-11-21T09:27:07Z<p>Rwong: Rwong uploaded a new version of File:SSI-R8.png</p>
<hr />
<div></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=File:SSI-R8.png&diff=2322File:SSI-R8.png2016-11-21T09:23:24Z<p>Rwong: Rwong uploaded a new version of File:SSI-R8.png</p>
<hr />
<div></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=File:SSI-R8.png&diff=2321File:SSI-R8.png2016-11-21T09:14:36Z<p>Rwong: </p>
<hr />
<div></div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Install_and_Configure_Altium&diff=2316How to Install and Configure Altium2016-10-28T20:43:37Z<p>Rwong: /* Installing SSI Libraries */</p>
<hr />
<div>==Account Setup==<br />
<br />
Within the {{slack-channel|altium}} channel, request an account for both Altium itself and for Assembla, where our revision control system for board and part files is managed.<br />
<br />
==Installing Altium==<br />
<br />
Altium Designer can be downloaded [http://www.altium.com/products/downloads here]. Be aware that the software will only install on Windows operating systems. After downloading, install with the default settings, and sign in with your Altium account.<br />
<br />
==Installing SVN==<br />
You need an SVN client to use the SSI Altium repository. The recommended choice is to install [http://tortoisesvn.net/ Tortoise SVN].<br />
<br />
[https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-quick-start.html Here] is a resource for some basic info regarding SVN and setup <br />
<br />
Make sure you install the Windows context menu support.<br />
<br />
Set up Tortoise:<br />
- Make a directory to store all of the SSI data<br />
- Right click and select "SVN checkout"<br />
- Point to the repository at: http://subversion.assembla.com/svn/stanfordspaceinitiative<br />
- Enter your credentials<br />
<br />
When you are using the SVN, the most important commands are update, commit, lock, unlock, and add.<br />
<br />
==Installing SSI Libraries==<br />
This assumes you have set up Altium & the SSI SVN already. <br />
<br />
*Open --> libraries --> intlib --> SSI.LibPkg<br />
*Right click on package in the workspace area --> Compile Integrated Library<br />
*Go to the right toolbar and click on 'Libraries' and then the 'Libraries...' button. <br />
*Go under the second tab titled 'Installed' and click 'Import From File'. <br />
*Navigate to your SVN folder --> libraries --> intlib --> [possibly inside a folder titled 'Project Output for SSI'] --> SSI.IntLib<br />
*DONE!<br />
<br />
If there are changes to the library package, you will need to recompile (right click --> recompile). <br />
When you commit in SVN, do not add the SSI.IntLib file (it should already be in the ignore list)<br />
<br />
[[Category: Altium]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=So_You_Want_To...&diff=2257So You Want To...2016-10-23T05:24:33Z<p>Rwong: /* Learn About Radio Tracking */</p>
<hr />
<div>==Build An Awesome Foundation of Knowledge==<br />
<br />
[https://www.grc.nasa.gov/www/k-12/rocket/shortr.html NASA Beginner's Guide to Rockets]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/short.html NASA Beginner’s Guide to Aerodynamics]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/shortc.html NASA Beginner’s Guide to Compressible Aerodynamics]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/shortp.html NASA Beginner’s Guide to Propulsion]<br />
<br />
==Learn About Space Shuttles/NASA Projects==<br />
<br />
[http://spaceflight.nasa.gov/shuttle/reference/shutref/index.html Space Shuttle Reference]<br />
<br />
[http://history.nasa.gov/SP-4221/sp4221.htm The Space Shuttle Decision]<br />
<br />
[http://history.nasa.gov/SP-407/sp407.htm Space Shuttle]<br />
<br />
[http://history.nasa.gov/SP-436/sp436.htm Project Orion]<br />
<br />
[http://history.nasa.gov/SP-4001/cover.htm Project Mercury]<br />
<br />
[http://history.nasa.gov/SP-4002/cover.htm Project Gemini]<br />
<br />
==Learn About Rockets/HPR In General==<br />
<br />
[https://drive.google.com/drive/u/0/folders/0B_uGMv8pu2KgNnpTbUpMajlCMjg OpenRocket Tech Documentation]<br />
<br />
[https://drive.google.com/open?id=0B0L2asxf9DSOOXBld19neENoVkU Modern High Power Rocketry 2]<br />
<br />
[https://drive.google.com/drive/u/0/folders/0B_uGMv8pu2KgNnpTbUpMajlCMjg HPR Basics by NAR]<br />
<br />
[http://wiki.stanfordssi.org/L1_Certification Get your L1 Cert]<br />
<br />
==Learn About Controls==<br />
<br />
[https://www.site.uottawa.ca/~rhabash/ELG4152LN01.pdf A Brief Introduction]<br />
<br />
[https://www.facstaff.bucknell.edu/mastascu/eControlHTML/Intro/Intro1.html Another Brief Introduction ft. Comic Sans]<br />
<br />
[http://machinedesign.com/sensors/introduction-pid-control A Non Math-y Introduction to PID Control]<br />
<br />
[https://www.youtube.com/watch?v=oBc_BHxw78s&list=PLUMWjy5jgHK1NC52DXXrriwihVrYZKqjk An Awesome playlist of YouTube videos]<br />
<br />
==Learn About Kalman Filtering & Sensor Fusion==<br />
<br />
[https://en.wikipedia.org/wiki/Kalman_filter Wikipedia]<br />
<br />
[http://www.bzarg.com/p/how-a-kalman-filter-works-in-pictures/ Kalman Filtering Explained with Pictures]<br />
<br />
[https://www.overleaf.com/3972499sxgwkz Read about Joan & Rebecca killing brain cells learning (or attempting to learn) this stuff]<br />
<br />
[http://blog.tkjelectronics.dk/2012/09/a-practical-approach-to-kalman-filter-and-how-to-implement-it/ More info on how it works]<br />
<br />
[http://ozzmaker.com/2015/01/27/guide-interfacing-gyro-accelerometer-raspberry-pi-kalman-filter/ Using a RasPi]<br />
<br />
[http://forum.arduino.cc/index.php?topic=58048.0 Using an Arduino]<br />
<br />
[http://digitalcommons.calpoly.edu/cgi/viewcontent.cgi?article=1114&context=aerosp CalPoly paper, using Arduinos]<br />
<br />
[http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.69.880&rep=rep1&type=pdf Multi-sensor fusion with asynchronous readings] (provides a generic and powerful solution)<br />
<br />
[http://liu.diva-portal.org/smash/get/diva2:648377/FULLTEXT01.pdf Paper on Integration of IMUs & GPS]<br />
<br />
[http://www.acfr.usyd.edu.au/pdfs/training/multiSensorDataFusion/dataFusionNotes.pdf Long, but well written intro to multi sensor fusion and Kalman filtering]<br />
<br />
===Notes===<br />
<br />
The Kalman filter is linear quadratic estimator. We assume the system is linear, which should be good enough for our purposes. For non linear systems, do an extended Kalman filter. However, this takes much more computational resources and is much more unstable.<br />
<br />
A basic diagram of how this estimator works:<br />
<br />
[[File:Kalman_Filter_Estimator.png|center|400px]]<br />
<br />
===Other Resources===<br />
<br />
*[http://www.tech-ex.com/article_images3/9/440249/1-11.pdf More papers]<br />
*[https://agrosy.informatik.uni-kl.de/fileadmin/Literatur/Blank10.pdf “Welp Kalman filtering sometimes sucks but I think we should use it anyway"]<br />
*[http://gentlenav.googlecode.com/files/DCMDraft2.pdf Filtering with accelerometers and gyros and more fun stuff]<br />
*[https://www.xsens.com/images/stories/PDF/drift-free%20dynamic%20height%20sensor%20using%20mems%20imu%20aided%20by%20mems%20pressure%20sensor.pdf Mayhaps for balloons valbal]<br />
*[http://tid.uio.no/~jankbe/Filer/PhD_JKB_200207.pdf Really cool, but way too OP]<br />
*[http://gamepipe.usc.edu/~zyda/resources/pubs/IROS2001.pdf More gyro stuff]<br />
<br />
==Learn About Aero/Wings==<br />
<br />
[https://docs.google.com/a/stanford.edu/presentation/d/1xMbuJJt6TpkfMDQj7j8fbLxHWFOP7kkEhmNzFy-G7JA/ Chris’s slides]<br />
<br />
[https://drive.google.com/open?id=0B_uGMv8pu2KgS3BuNGtiNkUwWU0 Textbook]<br />
<br />
==Learn About Physics==<br />
<br />
[http://web.mit.edu/16.unified/www/FALL/systems/Lab_Notes/traj.pdf Trajectory Calculations]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/rocket/rktfor.html Forces on a Rocket]<br />
<br />
==Learn About Solid Mechanics==<br />
<br />
[https://docs.google.com/a/stanford.edu/presentation/d/1CZW9eUfra6TJbUV_fETYeGjo4aBgbjnJfozvG6ljoY8/ Chris’s slides]<br />
<br />
[https://drive.google.com/a/stanford.edu/file/d/0B-5MRX1wVAAdZ2xDMW1rX0t4OE0/ ME80 textbook]<br />
<br />
==Learn About Thermodynamics/Heat Transfer==<br />
<br />
[https://docs.google.com/a/stanford.edu/presentation/d/1pOug5fcGkt76gsBKJVQ3arGqYzyL0WgubFvMI3wZkkw/ Chris’s slides]<br />
<br />
[https://drive.google.com/open?id=0B_uGMv8pu2KgMDY1OGtlOXBKWjQ ME131A texbook]<br />
<br />
==Learn About Fluid Dynamics==<br />
<br />
[http://www.engineeringtoolbox.com/bernouilli-equation-d_183.html Simple Bernoulli] (low speed)<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/isentrop.html Compressible Flow] (high speed)<br />
<br />
[https://drive.google.com/open?id=0B-5MRX1wVAAdYlpDUHoyV2taeVk ME70/131B textbook]<br />
<br />
[http://history.nasa.gov/SP-367/chapt5.htm Transonic Flight]<br />
<br />
==Learn About Stability==<br />
<br />
[https://www.apogeerockets.com/downloads/PDFs/barrowman_report.pdf Barrowman Report]<br />
<br />
[https://www.apogeerockets.com/Tech/Rocket_Stability?pg=education&zenid=e8dadefb74ed8ef9521c42a1ea8112ff Compilation of Links on Stability]<br />
<br />
==Learn About Orbital Mechanics==<br />
<br />
[http://www.braeunig.us/space/orbmech.htm Intro to Orbital Mechanics]<br />
<br />
[https://drive.google.com/open?id=0B1NYU3-6sOTIa3RDMVFwYmpVWWs AA279A Lecture Notes]<br />
<br />
==Learn About Fins==<br />
[http://www.nakka-rocketry.net/fins.html Fins & Stability]<br />
<br />
[https://www.apogeerockets.com/technical_publication_16 Easy to Digest Info From Apogee Rocketry]<br />
<br />
[https://www.apogeerockets.com/education/downloads/Newsletter420.pdf Design & Construction Specifically for Low Power] <br />
<br />
==Learn About Reefing==<br />
<br />
[http://www.thefintels.com/aer/reef.htm People making their own reefing system]<br />
<br />
[http://www.rocketryforum.com/showthread.php?17067-Chute-Reef-Line-Cutter People discussing cable cutters]<br />
<br />
[http://aeroconsystems.com/cart/launch-and-recovery-accessories/cable-cutter-by-archetype-rocketry/ Aerocon Cable Cutters]<br />
<br />
==Learn About Radio Tracking==<br />
<br />
[http://rocstock.org/advanced/advanced-rocket-tracking-using-onboard-radio-transmitters/ Overview of Different Forms of Trackers]<br />
<br />
[https://docs.google.com/a/stanford.edu/spreadsheets/d/1oiBWdkrCbc3TfJFp_HMPpK0ARKysxRUMq5qcPeT1HbA/ Spreadsheet Comparison of Radio Trackers (see the Radio Tracking tab)]<br />
<br />
==Cram for An Amateur Ham Radio License==<br />
<br />
[http://www.kb6nu.com/wp-content/uploads/2015/03/2014-no-nonsense-tech-study-guide-v20.pdf No Nonsense Guide to Earning Your Technician License] (read this if you have the time)<br />
<br />
[https://hamstudy.org/tech2014 Flashcards to Cram The Night Before] (use these if you don’t have the time)<br />
<br />
[http://www.arrl.org/find-an-amateur-radio-license-exam-session ARRL Lookup When/Where Exams Are Held]<br />
<br />
==Use OpenRocket==<br />
<br />
[https://docs.google.com/a/stanford.edu/document/d/1G1YK35jDQAkZQerhjCX9vjJEk9FbQDSkZdqDFWjk5ec/edit?usp=sharing Guide to Getting Started with OpenRocket]<br />
<br />
==Use ''LaTeX''==<br />
<br />
[http://ricardo.ecn.wfu.edu/~cottrell/ecn297/latex_tut.pdf A Brief Introduction]<br />
<br />
[https://tobi.oetiker.ch/lshort/lshort.pdf A Not So Short Introduction]<br />
<br />
[https://latex-project.org/ftp.html LaTeX For Your Computer If You're So Inclined] (but really you should be using OverLeaf)<br />
<br />
[https://wch.github.io/latexsheet/ LaTeX Reference Sheet If Your Memory Sucks] (not perfect, but good for basic things)<br />
<br />
[https://www.sharelatex.com/learn/ Learn How To Do Pretty Much Anything You’d Like In LaTeX]<br />
<br />
[https://en.wikibooks.org/wiki/LaTeX Learn How To Do Pretty Much Anything You’d Like In LaTeX #2]<br />
<br />
==Convert ''LaTeX'' to Mediawiki==<br />
<br />
[http://pandoc.org/ Pandoc] is a wonderful tool that can convert a file to a different markup format. We use it to convert rocket PDRs from ''LaTeX'' to wiki articles.<br />
<br />
==Run CFD Simulations==<br />
<br />
[[CFD Workflow|Learn more about SSI's CFD Workflow]]<br />
<br />
[[Solidworks|How to install Solidworks on your computer]]<br />
<br />
[[Pointwise | More about our (potential) sponsor]]<br />
<br />
[[SU2 | How to install SU2 on Corn]]<br />
<br />
<br />
[[Category:Rockets]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=So_You_Want_To...&diff=2256So You Want To...2016-10-23T05:17:22Z<p>Rwong: </p>
<hr />
<div>==Build An Awesome Foundation of Knowledge==<br />
<br />
[https://www.grc.nasa.gov/www/k-12/rocket/shortr.html NASA Beginner's Guide to Rockets]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/short.html NASA Beginner’s Guide to Aerodynamics]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/shortc.html NASA Beginner’s Guide to Compressible Aerodynamics]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/shortp.html NASA Beginner’s Guide to Propulsion]<br />
<br />
==Learn About Space Shuttles/NASA Projects==<br />
<br />
[http://spaceflight.nasa.gov/shuttle/reference/shutref/index.html Space Shuttle Reference]<br />
<br />
[http://history.nasa.gov/SP-4221/sp4221.htm The Space Shuttle Decision]<br />
<br />
[http://history.nasa.gov/SP-407/sp407.htm Space Shuttle]<br />
<br />
[http://history.nasa.gov/SP-436/sp436.htm Project Orion]<br />
<br />
[http://history.nasa.gov/SP-4001/cover.htm Project Mercury]<br />
<br />
[http://history.nasa.gov/SP-4002/cover.htm Project Gemini]<br />
<br />
==Learn About Rockets/HPR In General==<br />
<br />
[https://drive.google.com/drive/u/0/folders/0B_uGMv8pu2KgNnpTbUpMajlCMjg OpenRocket Tech Documentation]<br />
<br />
[https://drive.google.com/open?id=0B0L2asxf9DSOOXBld19neENoVkU Modern High Power Rocketry 2]<br />
<br />
[https://drive.google.com/drive/u/0/folders/0B_uGMv8pu2KgNnpTbUpMajlCMjg HPR Basics by NAR]<br />
<br />
[http://wiki.stanfordssi.org/L1_Certification Get your L1 Cert]<br />
<br />
==Learn About Controls==<br />
<br />
[https://www.site.uottawa.ca/~rhabash/ELG4152LN01.pdf A Brief Introduction]<br />
<br />
[https://www.facstaff.bucknell.edu/mastascu/eControlHTML/Intro/Intro1.html Another Brief Introduction ft. Comic Sans]<br />
<br />
[http://machinedesign.com/sensors/introduction-pid-control A Non Math-y Introduction to PID Control]<br />
<br />
[https://www.youtube.com/watch?v=oBc_BHxw78s&list=PLUMWjy5jgHK1NC52DXXrriwihVrYZKqjk An Awesome playlist of YouTube videos]<br />
<br />
==Learn About Kalman Filtering & Sensor Fusion==<br />
<br />
[https://en.wikipedia.org/wiki/Kalman_filter Wikipedia]<br />
<br />
[http://www.bzarg.com/p/how-a-kalman-filter-works-in-pictures/ Kalman Filtering Explained with Pictures]<br />
<br />
[https://www.overleaf.com/3972499sxgwkz Read about Joan & Rebecca killing brain cells learning (or attempting to learn) this stuff]<br />
<br />
[http://blog.tkjelectronics.dk/2012/09/a-practical-approach-to-kalman-filter-and-how-to-implement-it/ More info on how it works]<br />
<br />
[http://ozzmaker.com/2015/01/27/guide-interfacing-gyro-accelerometer-raspberry-pi-kalman-filter/ Using a RasPi]<br />
<br />
[http://forum.arduino.cc/index.php?topic=58048.0 Using an Arduino]<br />
<br />
[http://digitalcommons.calpoly.edu/cgi/viewcontent.cgi?article=1114&context=aerosp CalPoly paper, using Arduinos]<br />
<br />
[http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.69.880&rep=rep1&type=pdf Multi-sensor fusion with asynchronous readings] (provides a generic and powerful solution)<br />
<br />
[http://liu.diva-portal.org/smash/get/diva2:648377/FULLTEXT01.pdf Paper on Integration of IMUs & GPS]<br />
<br />
[http://www.acfr.usyd.edu.au/pdfs/training/multiSensorDataFusion/dataFusionNotes.pdf Long, but well written intro to multi sensor fusion and Kalman filtering]<br />
<br />
===Notes===<br />
<br />
The Kalman filter is linear quadratic estimator. We assume the system is linear, which should be good enough for our purposes. For non linear systems, do an extended Kalman filter. However, this takes much more computational resources and is much more unstable.<br />
<br />
A basic diagram of how this estimator works:<br />
<br />
[[File:Kalman_Filter_Estimator.png|center|400px]]<br />
<br />
===Other Resources===<br />
<br />
*[http://www.tech-ex.com/article_images3/9/440249/1-11.pdf More papers]<br />
*[https://agrosy.informatik.uni-kl.de/fileadmin/Literatur/Blank10.pdf “Welp Kalman filtering sometimes sucks but I think we should use it anyway"]<br />
*[http://gentlenav.googlecode.com/files/DCMDraft2.pdf Filtering with accelerometers and gyros and more fun stuff]<br />
*[https://www.xsens.com/images/stories/PDF/drift-free%20dynamic%20height%20sensor%20using%20mems%20imu%20aided%20by%20mems%20pressure%20sensor.pdf Mayhaps for balloons valbal]<br />
*[http://tid.uio.no/~jankbe/Filer/PhD_JKB_200207.pdf Really cool, but way too OP]<br />
*[http://gamepipe.usc.edu/~zyda/resources/pubs/IROS2001.pdf More gyro stuff]<br />
<br />
==Learn About Aero/Wings==<br />
<br />
[https://docs.google.com/a/stanford.edu/presentation/d/1xMbuJJt6TpkfMDQj7j8fbLxHWFOP7kkEhmNzFy-G7JA/ Chris’s slides]<br />
<br />
[https://drive.google.com/open?id=0B_uGMv8pu2KgS3BuNGtiNkUwWU0 Textbook]<br />
<br />
==Learn About Physics==<br />
<br />
[http://web.mit.edu/16.unified/www/FALL/systems/Lab_Notes/traj.pdf Trajectory Calculations]<br />
<br />
[https://www.grc.nasa.gov/www/k-12/rocket/rktfor.html Forces on a Rocket]<br />
<br />
==Learn About Solid Mechanics==<br />
<br />
[https://docs.google.com/a/stanford.edu/presentation/d/1CZW9eUfra6TJbUV_fETYeGjo4aBgbjnJfozvG6ljoY8/ Chris’s slides]<br />
<br />
[https://drive.google.com/a/stanford.edu/file/d/0B-5MRX1wVAAdZ2xDMW1rX0t4OE0/ ME80 textbook]<br />
<br />
==Learn About Thermodynamics/Heat Transfer==<br />
<br />
[https://docs.google.com/a/stanford.edu/presentation/d/1pOug5fcGkt76gsBKJVQ3arGqYzyL0WgubFvMI3wZkkw/ Chris’s slides]<br />
<br />
[https://drive.google.com/open?id=0B_uGMv8pu2KgMDY1OGtlOXBKWjQ ME131A texbook]<br />
<br />
==Learn About Fluid Dynamics==<br />
<br />
[http://www.engineeringtoolbox.com/bernouilli-equation-d_183.html Simple Bernoulli] (low speed)<br />
<br />
[https://www.grc.nasa.gov/www/k-12/airplane/isentrop.html Compressible Flow] (high speed)<br />
<br />
[https://drive.google.com/open?id=0B-5MRX1wVAAdYlpDUHoyV2taeVk ME70/131B textbook]<br />
<br />
[http://history.nasa.gov/SP-367/chapt5.htm Transonic Flight]<br />
<br />
==Learn About Stability==<br />
<br />
[https://www.apogeerockets.com/downloads/PDFs/barrowman_report.pdf Barrowman Report]<br />
<br />
[https://www.apogeerockets.com/Tech/Rocket_Stability?pg=education&zenid=e8dadefb74ed8ef9521c42a1ea8112ff Compilation of Links on Stability]<br />
<br />
==Learn About Orbital Mechanics==<br />
<br />
[http://www.braeunig.us/space/orbmech.htm Intro to Orbital Mechanics]<br />
<br />
[https://drive.google.com/open?id=0B1NYU3-6sOTIa3RDMVFwYmpVWWs AA279A Lecture Notes]<br />
<br />
==Learn About Fins==<br />
[http://www.nakka-rocketry.net/fins.html Fins & Stability]<br />
<br />
[https://www.apogeerockets.com/technical_publication_16 Easy to Digest Info From Apogee Rocketry]<br />
<br />
[https://www.apogeerockets.com/education/downloads/Newsletter420.pdf Design & Construction Specifically for Low Power] <br />
<br />
==Learn About Reefing==<br />
<br />
[http://www.thefintels.com/aer/reef.htm People making their own reefing system]<br />
<br />
[http://www.rocketryforum.com/showthread.php?17067-Chute-Reef-Line-Cutter People discussing cable cutters]<br />
<br />
[http://aeroconsystems.com/cart/launch-and-recovery-accessories/cable-cutter-by-archetype-rocketry/ Aerocon Cable Cutters]<br />
<br />
==Learn About Radio Tracking==<br />
<br />
[http://rocstock.org/advanced/advanced-rocket-tracking-using-onboard-radio-transmitters/ Overview of Different Forms of Trackers]<br />
[https://docs.google.com/a/stanford.edu/spreadsheets/d/1oiBWdkrCbc3TfJFp_HMPpK0ARKysxRUMq5qcPeT1HbA/ Spreadsheet Comparison of Radio Trackers (see the Radio Tracking tab)]<br />
<br />
==Cram for An Amateur Ham Radio License==<br />
<br />
[http://www.kb6nu.com/wp-content/uploads/2015/03/2014-no-nonsense-tech-study-guide-v20.pdf No Nonsense Guide to Earning Your Technician License] (read this if you have the time)<br />
<br />
[https://hamstudy.org/tech2014 Flashcards to Cram The Night Before] (use these if you don’t have the time)<br />
<br />
[http://www.arrl.org/find-an-amateur-radio-license-exam-session ARRL Lookup When/Where Exams Are Held]<br />
<br />
==Use OpenRocket==<br />
<br />
[https://docs.google.com/a/stanford.edu/document/d/1G1YK35jDQAkZQerhjCX9vjJEk9FbQDSkZdqDFWjk5ec/edit?usp=sharing Guide to Getting Started with OpenRocket]<br />
<br />
==Use ''LaTeX''==<br />
<br />
[http://ricardo.ecn.wfu.edu/~cottrell/ecn297/latex_tut.pdf A Brief Introduction]<br />
<br />
[https://tobi.oetiker.ch/lshort/lshort.pdf A Not So Short Introduction]<br />
<br />
[https://latex-project.org/ftp.html LaTeX For Your Computer If You're So Inclined] (but really you should be using OverLeaf)<br />
<br />
[https://wch.github.io/latexsheet/ LaTeX Reference Sheet If Your Memory Sucks] (not perfect, but good for basic things)<br />
<br />
[https://www.sharelatex.com/learn/ Learn How To Do Pretty Much Anything You’d Like In LaTeX]<br />
<br />
[https://en.wikibooks.org/wiki/LaTeX Learn How To Do Pretty Much Anything You’d Like In LaTeX #2]<br />
<br />
==Convert ''LaTeX'' to Mediawiki==<br />
<br />
[http://pandoc.org/ Pandoc] is a wonderful tool that can convert a file to a different markup format. We use it to convert rocket PDRs from ''LaTeX'' to wiki articles.<br />
<br />
==Run CFD Simulations==<br />
<br />
[[CFD Workflow|Learn more about SSI's CFD Workflow]]<br />
<br />
[[Solidworks|How to install Solidworks on your computer]]<br />
<br />
[[Pointwise | More about our (potential) sponsor]]<br />
<br />
[[SU2 | How to install SU2 on Corn]]<br />
<br />
<br />
[[Category:Rockets]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=2186How to Join SSI2016-10-15T21:46:44Z<p>Rwong: /* Becoming an official member */</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10 in exchange for a t-shirt) to one of our financial officers - Evan Long or Nate Simon can accept the dues.<br />
# In order to allow you access to our workspace, [[Mission Control]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.'''<br />
##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. Talk to Austin Pineault if you have questions about EH&S training.<br />
##Sign into the [http://internal.stanfordssi.org/trainings internal site] and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.<br />
##Attend a safety tour of MC. [https://docs.google.com/spreadsheets/d/1n4HBXtpOF_5vcevDjLNPQv4V4OyrZPs6im7FKDkLDJw/edit#gid=0 Sign up for a slot on this form]. (Or ask Elizabeth Hillstrom or John Dean for details.)<br />
# Fill out [https://docs.google.com/a/stanford.edu/forms/d/e/1FAIpQLSesFRAbj9AWz6_tKHVAYKACvCQ4b3Gt9a3lyWpjh4vScXOBPg/viewform this form] so we can add you to our official roster!<br />
<br />
=Resources=<br />
<br />
Here are some resources that will get you up to speed and on the same page with us:<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']<br />
<br />
== [http://stanfordssi.org/join All The Mailing Lists] ==<br />
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)<br />
<br />
== [[Mission Control]] ==<br />
<br />
Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=2184How to Join SSI2016-10-07T21:14:16Z<p>Rwong: /* All The Mailing Lists */</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10) to one of our financial officers - Evan Long or Nate Simon can accept the dues.<br />
# In order to allow you access to our workspace, [[Mission Control]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.'''<br />
##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. Talk to Austin Pineault if you have questions about EH&S training.<br />
##Sign into the [http://internal.stanfordssi.org/trainings internal site] and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.<br />
##Attend a safety tour of MC. [https://docs.google.com/spreadsheets/d/1n4HBXtpOF_5vcevDjLNPQv4V4OyrZPs6im7FKDkLDJw/edit#gid=0 Sign up for a slot on this form]. (Or ask Elizabeth Hillstrom or John Dean for details.)<br />
# Fill out [https://docs.google.com/a/stanford.edu/forms/d/e/1FAIpQLSesFRAbj9AWz6_tKHVAYKACvCQ4b3Gt9a3lyWpjh4vScXOBPg/viewform this form] so we can add you to our official roster!<br />
<br />
=Resources=<br />
<br />
Here are some resources that will get you up to speed and on the same page with us:<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']<br />
<br />
== [http://stanfordssi.org/join All The Mailing Lists] ==<br />
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)<br />
<br />
== [[Mission Control]] ==<br />
<br />
Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=2183How to Join SSI2016-10-07T21:03:05Z<p>Rwong: /* Resources */</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10) to one of our financial officers - Evan Long or Nate Simon can accept the dues.<br />
# In order to allow you access to our workspace, [[Mission Control]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.'''<br />
##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. Talk to Austin Pineault if you have questions about EH&S training.<br />
##Sign into the [http://internal.stanfordssi.org/trainings internal site] and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.<br />
##Attend a safety tour of MC. [https://docs.google.com/spreadsheets/d/1n4HBXtpOF_5vcevDjLNPQv4V4OyrZPs6im7FKDkLDJw/edit#gid=0 Sign up for a slot on this form]. (Or ask Elizabeth Hillstrom or John Dean for details.)<br />
# Fill out [https://docs.google.com/a/stanford.edu/forms/d/e/1FAIpQLSesFRAbj9AWz6_tKHVAYKACvCQ4b3Gt9a3lyWpjh4vScXOBPg/viewform this form] so we can add you to our official roster!<br />
<br />
=Resources=<br />
<br />
Here are some resources that will get you up to speed and on the same page with us:<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']<br />
<br />
== [http://stanfordssi.org/join All The Mailing Lists] ==<br />
<br />
== [[Mission Control]] ==<br />
<br />
Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=2179How to Join SSI2016-10-06T06:17:46Z<p>Rwong: /* Resources */</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10) to one of our financial officers - Evan Long or Nate Simon can accept the dues.<br />
# In order to allow you access to our workspace, [[Mission Control]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.'''<br />
##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.<br />
##Sign into the [http://internal.stanfordssi.org/trainings internal site] and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.<br />
##Attend a safety tour of MC. [https://docs.google.com/spreadsheets/d/1n4HBXtpOF_5vcevDjLNPQv4V4OyrZPs6im7FKDkLDJw/edit#gid=0 Sign up for a slot on this form]. (Or ask Elizabeth Hillstrom or John Dean for details.)<br />
# Fill out [https://docs.google.com/a/stanford.edu/forms/d/e/1FAIpQLSesFRAbj9AWz6_tKHVAYKACvCQ4b3Gt9a3lyWpjh4vScXOBPg/viewform this form] so we can add you to our official roster!<br />
<br />
=Resources=<br />
<br />
Here are some resources that will get you up to speed and on the same page with us:<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']<br />
<br />
== [[Mission Control]] ==<br />
<br />
Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=2178How to Join SSI2016-10-06T06:17:38Z<p>Rwong: /* Resources */</p>
<hr />
<div>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.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10) to one of our financial officers - Evan Long or Nate Simon can accept the dues.<br />
# In order to allow you access to our workspace, [[Mission Control]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##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.'''<br />
##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.<br />
##Sign into the [http://internal.stanfordssi.org/trainings internal site] and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.<br />
##Attend a safety tour of MC. [https://docs.google.com/spreadsheets/d/1n4HBXtpOF_5vcevDjLNPQv4V4OyrZPs6im7FKDkLDJw/edit#gid=0 Sign up for a slot on this form]. (Or ask Elizabeth Hillstrom or John Dean for details.)<br />
# Fill out [https://docs.google.com/a/stanford.edu/forms/d/e/1FAIpQLSesFRAbj9AWz6_tKHVAYKACvCQ4b3Gt9a3lyWpjh4vScXOBPg/viewform this form] so we can add you to our official roster!<br />
<br />
=Resources=<br />
<br />
Here are some resources that will get you up to speed and on the same page with us:<br />
<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams<br />
<br />
==The Wiki==<br />
<br />
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.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
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. <br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
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!<br />
<br />
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']<br />
<br />
== [[Mission Control]] ==<br />
<br />
Mission Control can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in Durand 390, Mission Control houses work sessions and project storage. Note: keycode access is required to the room. For specific questions, contact MC Hammer: Austin Pineault. Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Install_and_Configure_Altium&diff=2069How to Install and Configure Altium2016-06-27T00:53:05Z<p>Rwong: Migrated some info from the README</p>
<hr />
<div><br />
=Installing SVN=<br />
You need an SVN client to use the SSI Altium repository. I know you're running Windows since you have Altium, so go install [http://tortoisesvn.net/ Tortoise SVN].<br />
<br />
[https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-quick-start.html Here] is a resource for some basic info regarding SVN and setup <br />
<br />
Make sure you install the Windows context menu support.<br />
<br />
Set up Tortoise:<br />
- Make a directory to store all of the SSI data<br />
- Right click and select "SVN checkout"<br />
- Point to the repository at: http://subversion.assembla.com/svn/stanfordspaceinitiative<br />
- Enter your credentials<br />
<br />
When you are using the SVN, the most important commands are update, commit, lock, unlock, and add.<br />
<br />
<br />
=Installing SSI Libraries=<br />
This assumes you have set up Altium & the SSI SVN already. <br />
<br />
*Open --> libraries --> intlib --> SSI.LibPkg<br />
*Right click on package in the workspace area --> Compile Integrated Library<br />
*Go to the right toolbar and click on 'Libraries' and then the 'Libraries...' button. <br />
*Go under the second tab titled 'Installed' and click 'Import From File'. <br />
*Navigate to your SVN folder --> libraries --> intlib --> [possibly inside a folder titled 'Project Output for SSI'] --> SSI.IntLib<br />
*DONE!<br />
<br />
If there are changes to the library package, you will need to recompile and reinstall (I think). <br />
When you commit in SVN, do not add the SSI.IntLib file<br />
<br />
[[Category: Altium]]<br />
[[Link title]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Install_and_Configure_Altium&diff=2068How to Install and Configure Altium2016-06-27T00:33:55Z<p>Rwong: I can't spell</p>
<hr />
<div><br />
=Installing SSI Libraries=<br />
This assumes you have set up Altium & the SSI SVN already. <br />
<br />
*Open --> libraries --> intlib --> SSI.LibPkg<br />
*Right click on package in the workspace area --> Compile Integrated Library<br />
*Go to the right toolbar and click on 'Libraries' and then the 'Libraries...' button. <br />
*Go under the second tab titled 'Installed' and click 'Import From File'. <br />
*Navigate to your SVN folder --> libraries --> intlib --> [possibly inside a folder titled 'Project Output for SSI'] --> SSI.IntLib<br />
*DONE!<br />
<br />
If there are changes to the library package, you will need to recompile and reinstall (I think). <br />
When you commit in SVN, do not add the SSI.IntLib file<br />
<br />
[[Category: Altium]]</div>Rwonghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Install_and_Configure_Altium&diff=2067How to Install and Configure Altium2016-06-27T00:33:33Z<p>Rwong: added to Altium category</p>
<hr />
<div><br />
=Installing SSI Libraries=<br />
This assumes you have set up Altium & the SSI SVN already. <br />
<br />
*Open --> libraries --> intlib --> SSI.LibPkg<br />
*Right click on package in the workspace area --> Compile Integrated Library<br />
*Go to the right toolbar and click on 'Libraries' and then the 'Libraries...' button. <br />
*Go under the second tab titled 'Installed' and click 'Import From File'. <br />
*Navigate to your SVN folder --> libraries --> intlib --> [possibly inside a folder titled 'Project Output for SSI'] --> SSI.IntLib<br />
*DONE!<br />
<br />
If there are changes to the library package, you will need to recompile and reinstall (I think). <br />
When you commit in SVN, do not add the SSI.IntLib file<br />
<br />
[[Category: Altiuim]]</div>Rwong