https://ssi-wiki.stanford.edu/w/api.php?action=feedcontributions&user=Aabdalla&feedformat=atomStanford SSI Wiki - User contributions [en]2024-03-29T00:34:35ZUser contributionsMediaWiki 1.35.0https://ssi-wiki.stanford.edu/w/index.php?title=Gas_storage&diff=4457Gas storage2022-04-06T00:51:01Z<p>Aabdalla: </p>
<hr />
<div>SSI gas tanks are currently stored in the Durand gas cage. For the moment we're limited to a maximum of 5 tanks. If you'd like to help manage SSI's chemical inventory:<br />
<br />
# Have all of the gas purchasers request a new user account [https://ehs.stanford.edu/request-a-new-chemtracker-user-account here] so that you are able to view and edit the inventory<br />
# Once your account is set up you can play around with the (up to 5) tanks in our inventory. They should be assigned to room 067 or 069 (9999HZ is for empty storage only)<br />
# Ensure the inventory is accurate when making new purchases (this is closely looked at by the county inspector)<br />
#* If you order to replace a gas in the inventory there is no need to enter it in twice, just make sure it reflects what is physically in the space<br />
# Verify the gas inventory at least once a year in the cage and in ChemTracker by clicking “modify all to current date”<br />
<br />
If SSI ever switches advisors have our new responsible PI/Advisor request a chemical owner account [https://ehs.stanford.edu/request-a-new-chemical-owner-account here]</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Gas_storage&diff=4456Gas storage2022-04-06T00:50:13Z<p>Aabdalla: </p>
<hr />
<div>SSI gas tanks are currently stored in the Durand gas cage. For the moment we're limited to a maximum of 5 tanks. If you'd like to help manage SSI's chemical inventory:<br />
<br />
# Have all of the gas purchasers request a new user account [https://ehs.stanford.edu/request-a-new-chemtracker-user-account here] so that you are able to view and edit the inventory<br />
# Once your account is set up you can play around with the (up to 5) tanks in our inventory. They should be assigned to room 067 or 069 (9999HZ is for empty storage only)<br />
# Ensure the inventory is accurate when making new purchases (this is closely looked at by the county inspector)<br />
##* If you order to replace a gas in the inventory there is no need to enter it in twice, just make sure it reflects what is physically in the space<br />
# Verify the gas inventory at least once a year in the cage and in ChemTracker by clicking “modify all to current date”<br />
<br />
If SSI ever switches advisors have our new responsible PI/Advisor request a chemical owner account [https://ehs.stanford.edu/request-a-new-chemical-owner-account here]</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Gas_storage&diff=4439Gas storage2021-11-04T16:43:34Z<p>Aabdalla: rewording what Sade said</p>
<hr />
<div>SSI gas tanks are currently stored in the Durand gas cage. For the moment we're limited to a maximum of 5 tanks. If you'd like to help manage SSI's chemical inventory:<br />
<br />
* Request a new chemical owner account for the responsible PI/Advisor here<br />
* Have all of the gas purchasers request a new user account here so that you are able to view and edit the inventory<br />
* Once your account is set up you can play around with the (up to 5) tanks in our inventory. They should be assigned to room 067 or 069 (9999HZ is for empty storage only)<br />
* Ensure the inventory is accurate when making new purchases (this is closely looked at by the county inspector)<br />
** If you order to replace a gas in the inventory there is no need to enter it in twice, just make sure it reflects what is physically in the space<br />
* Verify the gas inventory at least once a year in the cage and in ChemTracker by clicking “modify all to current date”</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=User:Aabdalla&diff=4438User:Aabdalla2021-10-29T23:25:32Z<p>Aabdalla: Created page with "Ahmed (he/him) is a current Co-President of SSI. He is a senior studying Physics and Math."</p>
<hr />
<div>Ahmed (he/him) is a current Co-President of SSI. He is a senior studying Physics and Math.</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Gas_storage&diff=4437Gas storage2021-10-29T23:05:45Z<p>Aabdalla: created page about gas storage policies</p>
<hr />
<div>SSI gas tanks are currently stored in the Durand gas cage. For the moment we're limited to a maximum of 5 tanks. If you'd like to help manage SSI's chemical inventory:<br />
<br />
* Request a new chemical owner account for the responsible PI/Advisor here<br />
* Have all of the gas purchasers request a new user account here so that you are able to view and edit the inventory<br />
* Once your account is set up you can add the 3 nitrous oxides and 2 helium tanks into your inventory to the designated space, either room 067 or 069 (9999HZ is for empty storage only)<br />
* Ensure the inventory is accurate when making new purchases (this is closely looked at by our county inspector)<br />
** If you order to replace a gas in the inventory there is no need to enter it in twice, just make sure it reflects what is physically in the space<br />
* Verify the gas inventory at least once a year in the cage and in ChemTracker by clicking “modify all to current date”</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=User:Ehillstrom&diff=4436User:Ehillstrom2021-10-29T23:03:31Z<p>Aabdalla: past tense</p>
<hr />
<div>Elizabeth Hillstrom is a past co-president of SSI. She studied Mechanical Engineering.</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=4434How to Join SSI2021-10-05T22:39:49Z<p>Aabdalla: added covid stuff</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 />
<!--# Fill out this 30-second form: [https://stanfordssi.org/q https://stanfordssi.org/q] (you should use your Stanford email if you have one)--><br />
# Join the SSI Slack [https://join.slack.com/t/ssi-teams/shared_invite/zt-gahlixrm-DyAtkyxTrUkt7K6HvPsxIA here].<br />
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].<br />
# <s>Pay dues ($10 in exchange for a t-shirt) to our financial officers via Venmo [redacted]. For questions/details or if dues present a financial hardship, message the Co-Presidents or Financial Officers and we'll waive them. See [[Leadership]].</s> Canceled due to COVID!<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: <br />
###'''EHS-4200: General Safety, Injury Prevention (IIPP), and Emergency Preparedness'''<br />
###'''EHS-1900: Chemical Safety for Laboratories'''<br />
###'''EHS-2200: Compressed Gas Safety'''<br />
###'''EHS-2470: COVID-19 Hygiene Best Practices'''<br />
##: If you've completed any of these previously for a laboratory class or other university purpose, you don't need to repeat them.<br />
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.<br />
##Due to these uNpReCeDeNtED times, we're also asking all members to fill out [https://forms.gle/diyuvKRrrFyQZbgY8 this form] agreeing to abide by our COVID Operating Procedures.<br />
<!-- ##Complete the [https://forms.gle/vUqqcK1dCdgnhpFM8 Workspace Access Form] You go back and modify your answers, but won't get access until you've completed trainings and a tour. --><br />
# Take a look at [https://s3-us-west-1.amazonaws.com/habmc/assets/assi.pdf Approaching SSI], a handbook for new (and prospective) members!<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://stanfordssi.org/events 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/drive/u/0/folders/0AOLUM8S1U9vqUk9PVA 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. If you don't have access, ask in {{slack-channel|SSIT}}<br />
<br />
== [https://stanfordssi.org/mailing-list The Mailing List] ==<br />
We use SSI General for organization-wide announcements, and it's a good way to hear about events that get lost in the depths of slack (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>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=4429Find a Project2021-09-30T07:49:42Z<p>Aabdalla: </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 />
== Mars ==<br />
Team Leads: {{Slack-user|@shreya garg=Shreya Garg|@Kylie=Kylie Holland}}<br />
<br />
In the Mars team, SSI’s newest venture, we believe that humanity is destined to move beyond Earth and settle the Solar System. Our multidisciplinary work combines the fields of materials science, chemical engineering, civil engineering, economics, and anything else that helps our goals! Whether you’re majoring in one of those fields or are undeclared, all you need to be a productive member of our team is a passion for interplanetary exploration. This team is meant to be a great learning opportunity for all its members to become familiar with in situ resource utilization (ISRU) and other technologies that will build our future in space. ISRU promises to produce the resources necessary to sustain human life on other planets. The ability to make potable water, breathable air, and construction materials in situ means that the major constraint on interplanetary missions, the need to bring massive amounts of cargo, can be sidestepped. This would reduce the cost of a Mars mission by orders of magnitude and help expedite it. ISRU also provides the only way for Martian settlements to be truly self-sustaining, allowing humanity to become a multiplanetary species and kickstart a new era of history.<br />
<br />
=== Mars Tractor ===<br />
The tractor subteam is designing and constructing an autonomous roving vehicle dubbed the Mars Tractor that can gather extraterrestrial soil, deposit said soil into the bricks subteam’s brick machine, and manipulate produced bricks to construct simple structures like walls and roads. The machine features a modified rocker-bogie suspension configuration (similar to NASA’s Mars rovers), allowing it to tumble over uneven terrain. Its tools feature a custom soil-gathering drum and forklift-like attachment for carrying bricks. Basic computer vision will allow it to interface with the brick machine using visual tags while avoiding large obstacles. <br />
<br />
<br />
The team has built a first draft of the mechanical and electrical systems, and has also begun work on the control code and computer vision software. Over the summer and into next year, the team will finish the basic tractor and design specialized arms for lifting, scooping, and placing soil and bricks. This project is particularly well suited to people interested in CS, MechE, EE, product design, and robotics!<br />
<br />
=== Mars Simulation ===<br />
The Mars Simulation team works to build a flexible Martian environment and mission architecture simulation platform. This past year, we’ve been building a minimum-viable-product capable of simulating SpaceX’s proposed mission architecture. Going forward, we hope to work with contacts at NASA to refine the system into a realistic, open-source mission planner! This project involves research, coding, visualization design, UX testing and design, and more! Ideal for students interested in CS, mission planning/space exploration strategy, communications, and UX/UI!<br />
<br />
=== Mars Bricks ===<br />
The bricks subteam experiments with methods of turning Martian and lunar soil into building materials for habitats and other structures. The main material we worked with is called biopolymer-bound soil composite (BSC), which is solely composed of an aggregate soil, a protein binder (such as bovine serum albumin), and reclaimable water (which is necessary for mixing and can be recaptured during desiccation). BSC has similar compressive strength as Portland cement concrete, the world’s most common construction material. While concrete production accounts for about 8% of global CO2 emissions, BSC provides a possible carbon-neutral alternative. We are currently designing a prototype device to autonomously produce BSC bricks.<br />
<br />
This subteam won an opportunity to send an experiment to the ISS via SPOCS (Student Payload Opportunity with Citizen Science), a NASA design competition. We will send a payload that will test how BSC dries in microgravity aboard the International Space Station, which will provide valuable data to compare with ground experiments, hopefully shedding light on the material’s usage on the Moon and Mars.<span data-stringify-type="paragraph-break" class="c-mrkdwn__br"></span>Over the next year, we will process data and publish results from our ISS experiment. Additionally, we will finish designing our brick-making machine and start testing and iterating! This project would be particularly well suited for people interested in urban studies/housing, chemical engineering, materials science, MechE, EE, CS, and product design, as well as anyone who loved playing in mud puddles as a kid!<br />
<br />
== Balloons ==<br />
<br />
'''Please see the [[Balloons]] page for more info.'''<br />
<br />
=== HABMC ===<br />
'''Please see the [https://ssi-wiki.stanford.edu/HABMC HABMC] page for more info.'''<br />
<br />
Team Lead: {{slack-user|sunet-id = richchen|display-name=Richard Chen}}<br />
<br />
HABMC is SSI's in-house developed web-based High Altitude Balloon Mission Control (HABMC) platform. From here, we can track our balloons all over the world, streaming live telemetry data from onboard sensors and controlling the balloons altitude and trajectory by sending commands. Infinitely adaptable and expandable, HABMC allows balloons to launch a diverse set of payload types and receive data ''from'' anywhere in the world, ''to'' anywhere in the world. HABMC can be found [https://habmc.stanfordssi.org/flight here.]<br />
=== Cycloon ===<br />
'''Please see the [https://ssi-wiki.stanford.edu/Cycloon Cycloon] page for more info.''' <br />
<br />
Team Lead: {{slack-user|sunet-id = hagop|display-name=Hagop Chinchinian}} <br />
<br />
Balloons launched by SSI from California have flown over three continents and two oceans. What better way to leverage these high-precision, long-endurance flight capabilities than to fly into and collect data from hurricanes, nature’s most awe-inspiring and destructive storms?<br />
<br />
That’s exactly what Cycloon is up to. In just one quarter, our team successfully launched five missions that tested marine tethers, control algorithms, launch maneuvers, and trajectory optimizations to reach storms over the ocean. In the coming year, we’ll be developing radiosondes to drop into weather systems over the continental US, with our eyes set on the big prize: collecting data from an Atlantic or Pacific hurricane in fall 2022 and publishing our results in a conference!<br />
<br />
Our task is exciting and ambitious, and a ton of cool challenges await. Want to design lightweight, power-optimized embedded systems? Have a ham radio license and ideas for scaling up data downlink? Interested in inventing new search and optimization algorithms? Just love meteorology and want to direct engineering efforts for a scientific objective? Can’t wait to see the day when the next NHC advisory means dozens of balloons launched within 48 hours? We can’t either! Join Cycloon to develop cutting-edge technology, perform important scientific research, and create a meaningful impact on the world!<br />
<br />
=== Balloonerang ===<br />
'''Please see the [https://ssi-wiki.stanford.edu/Balloonerang Balloonerang] page for more info.'''<br />
<br />
Team Lead: {{slack-user|sunet-id = rsanda|display-name=Rohan Sanda}}<br />
<br />
Retrieving payloads is just as important as launching them. Balloonerang tackles the challenge of payload recovery with a single, integrated, guided recovery system, simulating when aerodynamics, mechanical, and controls work become inseparable. It is the newest and fastest growing balloons team.<br />
<br />
A Balloonerang payload is launched to near-space and then autonomously glides to land near the outskirts of inhabited areas, reducing time and cost of recovery operations. This stubby glider spends up to a week in the freezing upper atmosphere, ballasting weight, recharging batteries with onboard solar panels, keeping itself and the payload warm, and communicating important data back to Earth with its satellite radio system. When it’s time to terminate the mission, the glider severs its connection to the balloon and zipps back to earth at over 70mph, fighting hundred mile per hour jetstreams, stabilizing itself in high altitude turbulence, and guiding itself to a mission defined recovery site. At 400 feet above the ground, the glider deploys the parachute and descends safely to the ground. Whew! What a journey! And what an adventure for you to go on!<br />
<br />
If you’re interested in CAD design, board fabrication, data visualization, aerodynamics, optimizing flight paths, or anything electronics, Balloonerang has a place for you to shine. Join this tight knit team to experience a little bit of everything: flight control algorithms, complex mechanical design, and hands-on electrical engineering experience.<br />
<br />
=== ValBal ===<br />
'''Note: the below project is no longer active in SSI. Please see the [[Balloons]] page for an updated list of projects.'''<br />
ValBal (Valve and Ballast), is a world record-breaking high-altitude balloon payload that autonomously maintains a set altitude for days of flight by venting helium gas and dropping ballast. If you are interested in MechE, EE, CS, Physics, or even MatSci or ChemE, there's a place for you on the ValBal team!<br />
*MechE -- '''Lead: Paige Brown'''<br />
ValBal's current design is a 3 part 3D printed nylon structure that uses motors to vent helium gas directly from the balloon neck, cut down the payload in the event of an emergency, and turn a wheel to dispense bb pellets as ballast from a lower compartment. The structure supports, at its heart, the avionics, which powers and control the motors and sensors. Contact {{slack-user|paigebrown}} if you're interested in:<br />
*Computer Aided Design (CAD) in SolidWorks<br />
*3D printing<br />
*Messing with dry ice<br />
*Laser cutting<br />
*Random jank manufacturing tricks<br />
*and everything else that goes into making ValBal mechanics run smoothly<br />
<br />
*EE -- '''Lead: Aria Tedjarati''' <br />
ValBal’s current electrical system consists of two compact, low-cost, 4 layer printed circuit boards with a custom avionics platform and a prototype digital radio communication link. The avionics consist of a multitude of sensors, a GPS, a two-way satellite communications system, motor drivers, power regulation, an embedded micro-controller, and much, much more! The digital radio system consists of a 433 MHz GFSK modulated, Reed-Solomon error corrected link that has been proven to reach ranges of 200 km at data-rates significantly greater than that of the Iridium constellation at 1/5th of the power consumption and 1/20th the cost. There are a multitude of ways to join the electrical engineering aspect of ValBal, so if any of this stuff interests you, join! Contact {{slack-user|ariatedjarati}} for more information.<br />
<br />
*CS -- '''Lead: Davy Ragland''' <br />
With ValBal CS, you will learn how to design and build robust, reliable, and flight critical embedded systems code. Since we cannot simply patch the firmware when it is flying, and if something goes wrong we could literally crash, we have to model our system in a way that accounts for complex states, edge cases, and emergent properties. From smart subsystem rebooting to bidirectional comms with parameter tuning, and from a multitude of flight modes to heavily optimized processor and memory behavior, ValBal is the perfect place to hone your skills building something that not only works, but works to industry standards. <br />
Contact {{slack-user|dragland}} to get involved!<br />
<br />
*Physics -- As a physics major, there are plenty of opportunities for you to work on ValBal. It is an insanely complex system; the flight dynamics are not yet completely understood and require simulating atmospheric and thermal effects. Good models are critical to create a good controller, another key component to ValBal that limits our possible endurance. At the same time, you can help with the design of the payload itself, considering how to optimize it for the harsh environment and coming up with good designs. Contact {{slack-user|jcreus}} for more inforation and a good dose of jank.<br />
<br />
*MatSci/ChemE -- '''Lead: Paige Brown'''<br />
ValBal has a '''fatal problem''': latex balloons are quickly weakened by UV radiation and ozone at high altitudes, leading to mission ending failure in just a few days. If this sounds like an interesting problem to you, and you want to be an integral part of helping us circumnavigate the world someday, come help us figure out how to strengthen or alter the latex balloon with s c i e n c e. Contact {{slack-user|paigebrown}} if you're interested!<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, '''Lead: Will'''<br />
** Design and test all airframe hardware<br />
** Design and build tools for integration of the rocket<br />
** Ensure all subsystems are designed and build to correct dimensions<br />
* Payload, '''Lead: WANTED'''<br />
** Design and execute an interesting research project of your choice<br />
** Design a payload of 8.8lbs to be carried to 30,000ft<br />
* Recovery, '''Lead: Saylor'''<br />
** Design and sew a parachute and test it to confirm its Coefficient of Drag<br />
** Design and test a deployment mechanism for our rocket<br />
** Ensure our rocket comes down in one piece<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: Tylor Jilk'''<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, '''Lead: Ruqayya'''<br />
** Develop computer simulations to predict the flight path of our rocket<br />
** Inform the decision making of the team with analysis of motors, weights and design<br />
<br />
== Satellites ==<br />
<br />
===🌲🛰Sequoia 🛰🌲===<br />
We are build a small satellite for earth observation and machine learning. Check out our page for more info! [[Satellites]]<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''' {{slack-user|}}[https://ssi-teams.slack.com/messages/Akasha Akasha], {{slack-user|}}[https://app.slack.com/client/T04HYQ78L/DPXT9NFJ8/details/top Ian]<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''' Alec, Rodrigo<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''' Moritz, Langston<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, Fusion 360, 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''' Connor, TaNia<br />
<br />
== Biology ==<br />
<br />
=== Enzymatic DNA Synthesis Methods === <br />
'''Lead: Gwyn 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 />
Outer space is cold, dark, and dangerous, yet people keep risking lives and spending billions of dollars to venture into its depths. Space projects have historically been some of the most dangerous and time consuming human endeavors ever attempted. So… why do we do it?<br />
<br />
SSI’s Policy Team investigates the politics of space. Whether you are an economist, philosopher, engineer, or anything else, whether you are fascinated by today’s rapidly changing space industry or wish you were around for the first moon landing, Policy Team is the place for you. Join us for our weekly general meetings to discuss the trends and issues of the space industry, or take part in one (or more!) of our subteams below! The future of space is in your hands.<br />
<br />
=== UN Proposal & Citizens for Space Exploration ===<br />
Ever dreamed of visiting the United Nations or meeting with senators in Washington DC to discuss hot topics in outer space? SSI’s Policy Team provides incredible opportunities to delve into the intriguing, controversial, and challenging world of space policy. <br />
<br />
Each year, Policy Team sends members to the Citizens for Space Exploration Conference in Washington, DC, where you — yes, you! — can speak directly with lawmakers and elected officials, lobbying to promote space exploration and determine the role of government in space. <br />
<br />
Last year, eight students from the Policy Team worked with the nonprofit [https://www.forallmoonkind.org/ For All Moonkind] to write a proposal about the preservation of human heritage in space, and the paper is going to be published by the Astrosociology Research Institute. Normally these students would get to travel to Vienna, Austria and present their research to the UN’s Committee on the Peaceful Uses of Outer Space; although we weren’t able to last year due to COVID, we plan on going again this year!<br />
<br />
=== Podcast ===<br />
Space policy is a large, complex, intergenerational conversation — and we want you to join! Our weekly space news podcast “This Week in Space” (check us out on Spotify or iTunes!) addresses what's currently going on in the space industry through discussions among team members and interviews with distinguished members of the space industry. We currently have listeners in 25 countries and are looking to keep expanding!<br />
<br />
=== Book Club ===<br />
Love space related pop culture? Interested in how science fiction eventually becomes science fact? Eager to meet sci-fi authors? Just looking for a place to vibe with really cool people? Come join our book club! We read sci fi novels and discuss them at our biweekly meetings.<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 />
=== Diverssity ===<br />
* Find diverse speakers to bring to campus<br />
* Organize diversity mixers (including with other engineering groups)<br />
* Help {{slack-user|ruqayyatoorawa}} run workshops<br />
<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>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Find_a_Project&diff=4428Find a Project2021-09-30T07:49:20Z<p>Aabdalla: uniform formatting for all teams</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 />
== Mars ==<br />
Team Leads: {{Slack-user|@shreya garg=Shreya Garg|@Kylie=Kylie Holland}}<br />
<br />
In the Mars team, SSI’s newest venture, we believe that humanity is destined to move beyond Earth and settle the Solar System. Our multidisciplinary work combines the fields of materials science, chemical engineering, civil engineering, economics, and anything else that helps our goals! Whether you’re majoring in one of those fields or are undeclared, all you need to be a productive member of our team is a passion for interplanetary exploration. This team is meant to be a great learning opportunity for all its members to become familiar with in situ resource utilization (ISRU) and other technologies that will build our future in space. ISRU promises to produce the resources necessary to sustain human life on other planets. The ability to make potable water, breathable air, and construction materials in situ means that the major constraint on interplanetary missions, the need to bring massive amounts of cargo, can be sidestepped. This would reduce the cost of a Mars mission by orders of magnitude and help expedite it. ISRU also provides the only way for Martian settlements to be truly self-sustaining, allowing humanity to become a multiplanetary species and kickstart a new era of history.<br />
<br />
=== Mars Tractor ===<br />
The tractor subteam is designing and constructing an autonomous roving vehicle dubbed the Mars Tractor that can gather extraterrestrial soil, deposit said soil into the bricks subteam’s brick machine, and manipulate produced bricks to construct simple structures like walls and roads. The machine features a modified rocker-bogie suspension configuration (similar to NASA’s Mars rovers), allowing it to tumble over uneven terrain. Its tools feature a custom soil-gathering drum and forklift-like attachment for carrying bricks. Basic computer vision will allow it to interface with the brick machine using visual tags while avoiding large obstacles. <br />
<br />
<br />
The team has built a first draft of the mechanical and electrical systems, and has also begun work on the control code and computer vision software. Over the summer and into next year, the team will finish the basic tractor and design specialized arms for lifting, scooping, and placing soil and bricks. This project is particularly well suited to people interested in CS, MechE, EE, product design, and robotics!<br />
<br />
=== Mars Simulation ===<br />
The Mars Simulation team works to build a flexible Martian environment and mission architecture simulation platform. This past year, we’ve been building a minimum-viable-product capable of simulating SpaceX’s proposed mission architecture. Going forward, we hope to work with contacts at NASA to refine the system into a realistic, open-source mission planner! This project involves research, coding, visualization design, UX testing and design, and more! Ideal for students interested in CS, mission planning/space exploration strategy, communications, and UX/UI!<br />
<br />
=== Mars Bricks ===<br />
The bricks subteam experiments with methods of turning Martian and lunar soil into building materials for habitats and other structures. The main material we worked with is called biopolymer-bound soil composite (BSC), which is solely composed of an aggregate soil, a protein binder (such as bovine serum albumin), and reclaimable water (which is necessary for mixing and can be recaptured during desiccation). BSC has similar compressive strength as Portland cement concrete, the world’s most common construction material. While concrete production accounts for about 8% of global CO2 emissions, BSC provides a possible carbon-neutral alternative. We are currently designing a prototype device to autonomously produce BSC bricks.<br />
<br />
This subteam won an opportunity to send an experiment to the ISS via SPOCS (Student Payload Opportunity with Citizen Science), a NASA design competition. We will send a payload that will test how BSC dries in microgravity aboard the International Space Station, which will provide valuable data to compare with ground experiments, hopefully shedding light on the material’s usage on the Moon and Mars.<span data-stringify-type="paragraph-break" class="c-mrkdwn__br"></span>Over the next year, we will process data and publish results from our ISS experiment. Additionally, we will finish designing our brick-making machine and start testing and iterating! This project would be particularly well suited for people interested in urban studies/housing, chemical engineering, materials science, MechE, EE, CS, and product design, as well as anyone who loved playing in mud puddles as a kid!<br />
<br />
== Balloons ==<br />
<br />
'''Please see the [[Balloons]] page for more info.'''<br />
<br />
=== HABMC ===<br />
'''Please see the [https://ssi-wiki.stanford.edu/HABMC HABMC] page for more info.'''<br />
<br />
Team Lead: {{slack-user|sunet-id = richchen|display-name=Richard Chen}}<br />
<br />
HABMC is SSI's in-house developed web-based High Altitude Balloon Mission Control (HABMC) platform. From here, we can track our balloons all over the world, streaming live telemetry data from onboard sensors and controlling the balloons altitude and trajectory by sending commands. Infinitely adaptable and expandable, HABMC allows balloons to launch a diverse set of payload types and receive data ''from'' anywhere in the world, ''to'' anywhere in the world. HABMC can be found [https://habmc.stanfordssi.org/flight here.]<br />
=== Cycloon ===<br />
'''Please see the [https://ssi-wiki.stanford.edu/Cycloon Cycloon] page for more info.''' <br />
<br />
Team Lead: {{slack-user|sunet-id = hagop|display-name=Hagop Chinchinian}} <br />
<br />
Balloons launched by SSI from California have flown over three continents and two oceans. What better way to leverage these high-precision, long-endurance flight capabilities than to fly into and collect data from hurricanes, nature’s most awe-inspiring and destructive storms?<br />
<br />
That’s exactly what Cycloon is up to. In just one quarter, our team successfully launched five missions that tested marine tethers, control algorithms, launch maneuvers, and trajectory optimizations to reach storms over the ocean. In the coming year, we’ll be developing radiosondes to drop into weather systems over the continental US, with our eyes set on the big prize: collecting data from an Atlantic or Pacific hurricane in fall 2022 and publishing our results in a conference!<br />
<br />
Our task is exciting and ambitious, and a ton of cool challenges await. Want to design lightweight, power-optimized embedded systems? Have a ham radio license and ideas for scaling up data downlink? Interested in inventing new search and optimization algorithms? Just love meteorology and want to direct engineering efforts for a scientific objective? Can’t wait to see the day when the next NHC advisory means dozens of balloons launched within 48 hours? We can’t either! Join Cycloon to develop cutting-edge technology, perform important scientific research, and create a meaningful impact on the world!<br />
<br />
=== Balloonerang ===<br />
'''Please see the [https://ssi-wiki.stanford.edu/Balloonerang Balloonerang] page for more info.'''<br />
<br />
Team Lead: {{slack-user|sunet-id = rsanda|display-name=Rohan Sanda}}<br />
<br />
Retrieving payloads is just as important as launching them. Balloonerang tackles the challenge of payload recovery with a single, integrated, guided recovery system, simulating when aerodynamics, mechanical, and controls work become inseparable. It is the newest and fastest growing balloons team.<br />
<br />
A Balloonerang payload is launched to near-space and then autonomously glides to land near the outskirts of inhabited areas, reducing time and cost of recovery operations. This stubby glider spends up to a week in the freezing upper atmosphere, ballasting weight, recharging batteries with onboard solar panels, keeping itself and the payload warm, and communicating important data back to Earth with its satellite radio system. When it’s time to terminate the mission, the glider severs its connection to the balloon and zipps back to earth at over 70mph, fighting hundred mile per hour jetstreams, stabilizing itself in high altitude turbulence, and guiding itself to a mission defined recovery site. At 400 feet above the ground, the glider deploys the parachute and descends safely to the ground. Whew! What a journey! And what an adventure for you to go on!<br />
<br />
If you’re interested in CAD design, board fabrication, data visualization, aerodynamics, optimizing flight paths, or anything electronics, Balloonerang has a place for you to shine. Join this tight knit team to experience a little bit of everything: flight control algorithms, complex mechanical design, and hands-on electrical engineering experience.<br />
<br />
=== ValBal ===<br />
'''Note: the below project is no longer active in SSI. Please see the [[Balloons]] page for an updated list of projects.'''<br />
ValBal (Valve and Ballast), is a world record-breaking high-altitude balloon payload that autonomously maintains a set altitude for days of flight by venting helium gas and dropping ballast. If you are interested in MechE, EE, CS, Physics, or even MatSci or ChemE, there's a place for you on the ValBal team!<br />
*MechE -- '''Lead: Paige Brown'''<br />
ValBal's current design is a 3 part 3D printed nylon structure that uses motors to vent helium gas directly from the balloon neck, cut down the payload in the event of an emergency, and turn a wheel to dispense bb pellets as ballast from a lower compartment. The structure supports, at its heart, the avionics, which powers and control the motors and sensors. Contact {{slack-user|paigebrown}} if you're interested in:<br />
*Computer Aided Design (CAD) in SolidWorks<br />
*3D printing<br />
*Messing with dry ice<br />
*Laser cutting<br />
*Random jank manufacturing tricks<br />
*and everything else that goes into making ValBal mechanics run smoothly<br />
<br />
*EE -- '''Lead: Aria Tedjarati''' <br />
ValBal’s current electrical system consists of two compact, low-cost, 4 layer printed circuit boards with a custom avionics platform and a prototype digital radio communication link. The avionics consist of a multitude of sensors, a GPS, a two-way satellite communications system, motor drivers, power regulation, an embedded micro-controller, and much, much more! The digital radio system consists of a 433 MHz GFSK modulated, Reed-Solomon error corrected link that has been proven to reach ranges of 200 km at data-rates significantly greater than that of the Iridium constellation at 1/5th of the power consumption and 1/20th the cost. There are a multitude of ways to join the electrical engineering aspect of ValBal, so if any of this stuff interests you, join! Contact {{slack-user|ariatedjarati}} for more information.<br />
<br />
*CS -- '''Lead: Davy Ragland''' <br />
With ValBal CS, you will learn how to design and build robust, reliable, and flight critical embedded systems code. Since we cannot simply patch the firmware when it is flying, and if something goes wrong we could literally crash, we have to model our system in a way that accounts for complex states, edge cases, and emergent properties. From smart subsystem rebooting to bidirectional comms with parameter tuning, and from a multitude of flight modes to heavily optimized processor and memory behavior, ValBal is the perfect place to hone your skills building something that not only works, but works to industry standards. <br />
Contact {{slack-user|dragland}} to get involved!<br />
<br />
*Physics -- As a physics major, there are plenty of opportunities for you to work on ValBal. It is an insanely complex system; the flight dynamics are not yet completely understood and require simulating atmospheric and thermal effects. Good models are critical to create a good controller, another key component to ValBal that limits our possible endurance. At the same time, you can help with the design of the payload itself, considering how to optimize it for the harsh environment and coming up with good designs. Contact {{slack-user|jcreus}} for more inforation and a good dose of jank.<br />
<br />
*MatSci/ChemE -- '''Lead: Paige Brown'''<br />
ValBal has a '''fatal problem''': latex balloons are quickly weakened by UV radiation and ozone at high altitudes, leading to mission ending failure in just a few days. If this sounds like an interesting problem to you, and you want to be an integral part of helping us circumnavigate the world someday, come help us figure out how to strengthen or alter the latex balloon with s c i e n c e. Contact {{slack-user|paigebrown}} if you're interested!<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, '''Lead: Will'''<br />
** Design and test all airframe hardware<br />
** Design and build tools for integration of the rocket<br />
** Ensure all subsystems are designed and build to correct dimensions<br />
* Payload, '''Lead: WANTED'''<br />
** Design and execute an interesting research project of your choice<br />
** Design a payload of 8.8lbs to be carried to 30,000ft<br />
* Recovery, '''Lead: Saylor'''<br />
** Design and sew a parachute and test it to confirm its Coefficient of Drag<br />
** Design and test a deployment mechanism for our rocket<br />
** Ensure our rocket comes down in one piece<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: Tylor Jilk'''<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, '''Lead: Ruqayya'''<br />
** Develop computer simulations to predict the flight path of our rocket<br />
** Inform the decision making of the team with analysis of motors, weights and design<br />
<br />
== Satellites ==<br />
<br />
===🌲🛰Sequoia 🛰🌲===<br />
We are build a small satellite for earth observation and machine learning. Check out our page for more info! [[Satellites]]<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''' {{slack-user|}}[https://ssi-teams.slack.com/messages/Akasha Akasha], {{slack-user|}}[https://app.slack.com/client/T04HYQ78L/DPXT9NFJ8/details/top Ian]<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''' Alec, Rodrigo<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''' Moritz, Langston<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, Fusion 360, 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''' Connor, TaNia<br />
<br />
== Biology ==<br />
<br />
=== Enzymatic DNA Synthesis Methods === <br />
'''Lead: Gwyn 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 />
Outer space is cold, dark, and dangerous, yet people keep risking lives and spending billions of dollars to venture into its depths. Space projects have historically been some of the most dangerous and time consuming human endeavors ever attempted. So… why do we do it?<br />
<br />
SSI’s Policy Team investigates the politics of space. Whether you are an economist, philosopher, engineer, or anything else, whether you are fascinated by today’s rapidly changing space industry or wish you were around for the first moon landing, Policy Team is the place for you. Join us for our weekly general meetings to discuss the trends and issues of the space industry, or take part in one (or more!) of our subteams below! The future of space is in your hands.<br />
<br />
=== UN Proposal & Citizens for Space Exploration ===<br />
Ever dreamed of visiting the United Nations or meeting with senators in Washington DC to discuss hot topics in outer space? SSI’s Policy Team provides incredible opportunities to delve into the intriguing, controversial, and challenging world of space policy. <br />
<br />
Each year, Policy Team sends members to the Citizens for Space Exploration Conference in Washington, DC, where you — yes, you! — can speak directly with lawmakers and elected officials, lobbying to promote space exploration and determine the role of government in space. <br />
<br />
Last year, eight students from the Policy Team worked with the nonprofit [https://www.forallmoonkind.org/ For All Moonkind] to write a proposal about the preservation of human heritage in space, and the paper is going to be published by the Astrosociology Research Institute. Normally these students would get to travel to Vienna, Austria and present their research to the UN’s Committee on the Peaceful Uses of Outer Space; although we weren’t able to last year due to COVID, we plan on going again this year!<br />
<br />
=== Podcast ===<br />
Space policy is a large, complex, intergenerational conversation — and we want you to join! Our weekly space news podcast “This Week in Space” (check us out on Spotify or iTunes!) addresses what's currently going on in the space industry through discussions among team members and interviews with distinguished members of the space industry. We currently have listeners in 25 countries and are looking to keep expanding!<br />
<br />
=== Book Club ===<br />
Love space related pop culture? Interested in how science fiction eventually becomes science fact? Eager to meet sci-fi authors? Just looking for a place to vibe with really cool people? Come join our book club! We read sci fi novels and discuss them at our biweekly meetings.<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 />
=== Diverssity ===<br />
* Find diverse speakers to bring to campus<br />
* Organize diversity mixers (including with other engineering groups)<br />
* Help {{slack-user|ruqayyatoorawa}} run workshops<br />
<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>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4400Calendar2021-09-08T19:10:59Z<p>Aabdalla: added description of how to edit calendar</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Copy the link to the calendar you want to subscribe to from above<br />
# Open up your Google Calendar and scroll over to the "Other calendars" tab[[File:Cal.PNG|frame|center|kinda weird how GCal just kinda runs my life now]]<br />
# Click the '+' icon and choose "From URL"[[File:Fromlink.PNG|frame|center|it's like i'm a real human for an hour and a half each weekend while putting in all my events]]<br />
# Paste the link to the calendar you chose in step 1 and click "Add Calendar"[[File:Addcal.png|frame|center|and then I'm a mindless drone doing whatever past me thought was best]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===<br />
<br />
<br />
==Editing Calendars==<br />
Only members of the Leadership Workgroup have access to edit Team Calendars. Follow this link to access the Calendars. Once you're there follow these simple steps<br />
<br />
# Select "New Event"[[File:Outlook Calendar.png|center|thumb]]<br />
# Choose the calendar you'd like to apply this event to. Your personal calendar is usually selected by default so this step is important.[[File:Select Calendar.png|center|thumb]]<br />
# Fill out the rest of your event's information and press "Save"<br />
<br />
Your event will automatically appear on Outlook but may take a while to populate on 3rd party apps.</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Select_Calendar.png&diff=4399File:Select Calendar.png2021-09-08T19:08:48Z<p>Aabdalla: </p>
<hr />
<div>New event pane on Outlook with Calendar selection bar open</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Outlook_Calendar.png&diff=4398File:Outlook Calendar.png2021-09-08T19:07:26Z<p>Aabdalla: </p>
<hr />
<div>pic of outlook calendar with new event button indicated</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4396Calendar2021-08-10T16:48:18Z<p>Aabdalla: </p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Copy the link to the calendar you want to subscribe to from above<br />
# [[File:Cal.PNG|frame|center|Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
# [[File:Fromlink.PNG|frame|center|Click the '+' icon and choose "From URL"]]<br />
# [[File:Addcal.png|frame|center|Paste the link to the calendar you chose in step 1 and click "Add Calendar"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===<br />
<br />
<br />
==Editing Calendars==</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=HABSIM&diff=4391HABSIM2021-07-17T01:35:00Z<p>Aabdalla: </p>
<hr />
<div>'''High Altitude Balloon Simulator''' (HABSIM) is a web server ([http://habsim.org/ link]) developed by the SSI [[Balloons]] Team for customizable, ensemble-based, long range trajectory predictions. The aims of the prediction server, in comparison to existing ones, are as follows:<br />
<br />
*Offer probabilistic predictions based on the Monte-Carlo GEFS run set.<br />
*Offer predictions out to the maximum time window permitted by GEFS (+378 hrs).<br />
*Offer finer and broader control over simulation parameters, including ascent rate, duration, simulation step, and drift coefficient.<br />
*Export an intuitive prediction API which can be used to simulate arbitrary flight profiles.<br />
*Offer a web-based UI which captures the functionality and flexibility of the API.<br />
<br />
Primary clients of HABSIM include [[Cycloon]] and [[Spaceshot]]. The project source code may be viewed on [https://github.com/SSI-MC/habsim GitHub]. To get involved, please contact {{slack-user|sunet-id=temp|display-name=Richard Chen}} and {{slack-user|sunet-id=rydwy01|display-name=Ryan Dwyer}} and join {{slack-channel|balloons-habsim}}!<br />
<br />
'''PyHABSIM''' is a Python package which exploits the HABSIM API to offer an intuitive, object-oriented, highly customizable prediction interface, wind and elevation data accession utilities, and trajectory analysis and optimization methods in Python. The package home pages may be found at [https://pypi.org/project/habsim/ PyPI] or [https://github.com/stanford-ssi/habsim_client GitHub]. Please contact {{slack-user|temp|display-name=Richard Chen}} to get involved!</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=HABSIM&diff=4390HABSIM2021-07-17T01:34:28Z<p>Aabdalla: </p>
<hr />
<div>'''High Altitude Balloon Simulator''' (HABSIM) is a web server ([http://habsim.org/ link]) developed by the SSI [[Balloons]] Team for customizable, ensemble-based, long range trajectory predictions. The aims of the prediction server, in comparison to existing ones, are as follows:<br />
<br />
*Offer probabilistic predictions based on the Monte-Carlo GEFS run set.<br />
*Offer predictions out to the maximum time window permitted by GEFS (+378 hrs).<br />
*Offer finer and broader control over simulation parameters, including ascent rate, duration, simulation step, and drift coefficient.<br />
*Export an intuitive prediction API which can be used to simulate arbitrary flight profiles.<br />
*Offer a web-based UI which captures the functionality and flexibility of the API.<br />
<br />
Primary clients of HABSIM include [[Cycloon]] and [[Spaceshot]]. The project source code may be viewed on [https://github.com/SSI-MC/habsim GitHub]. To get involved, please contact {{slack-user|sunet-id=temp|display-name=Richard Chen}} and {{slack-user|sunet-id=rydwy01|display-name=Ryan Dwyer}} and join {{slack-channel|balloons-habsim}}!<br />
<br />
'''PyHABSIM''' is a Python package which exploits the HABSIM API to offer an intuitive, object-oriented, highly customizable prediction interface, wind and elevation data accession utilities, and trajectory analysis and optimization methods in Python. The package home pages may be found at [https://pypi.org/project/habsim/ PyPI] or [https://github.com/stanford-ssi/habsim_client GitHub]. Please contact {{slack-user|bjing}} to get involved!</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=HABSIM&diff=4389HABSIM2021-07-17T01:33:18Z<p>Aabdalla: </p>
<hr />
<div>'''High Altitude Balloon Simulator''' (HABSIM) is a web server ([http://habsim.org/ link]) developed by the SSI [[Balloons]] Team for customizable, ensemble-based, long range trajectory predictions. The aims of the prediction server, in comparison to existing ones, are as follows:<br />
<br />
*Offer probabilistic predictions based on the Monte-Carlo GEFS run set.<br />
*Offer predictions out to the maximum time window permitted by GEFS (+378 hrs).<br />
*Offer finer and broader control over simulation parameters, including ascent rate, duration, simulation step, and drift coefficient.<br />
*Export an intuitive prediction API which can be used to simulate arbitrary flight profiles.<br />
*Offer a web-based UI which captures the functionality and flexibility of the API.<br />
<br />
Primary clients of HABSIM include [[Cycloon]] and [[Spaceshot]]. The project source code may be viewed on [https://github.com/SSI-MC/habsim GitHub]. To get involved, please contact {{slack-user|temp|Richard Chen}} and {{slack-user|rydwy01|Ryan Dwyer}} and join {{slack-channel|balloons-habsim}}!<br />
<br />
'''PyHABSIM''' is a Python package which exploits the HABSIM API to offer an intuitive, object-oriented, highly customizable prediction interface, wind and elevation data accession utilities, and trajectory analysis and optimization methods in Python. The package home pages may be found at [https://pypi.org/project/habsim/ PyPI] or [https://github.com/stanford-ssi/habsim_client GitHub]. Please contact {{slack-user|bjing}} to get involved!</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Category:Mars&diff=4386Category:Mars2021-07-11T19:46:33Z<p>Aabdalla: </p>
<hr />
<div><br />
The ''SSI Mars team'' seeks to push the boundaries of crewed space missions and pave the way for permanent settlement of Mars and other celestial bodies. Our projects are centered on in situ resource utilization (ISRU), a broad group of technologies which make use of the scant resources on Mars for long-term surface missions. We turn Martian air and soil into fuel and concrete, eliminating the need to launch everything from Earth. At the same time, ISRU technologies can sustainably produce fuel and building materials for use on Earth, making our work a crucial step in fighting climate change. If we learn to live on the Red Planet, we can also save the blue one!<br />
<br />
<br />
'''IN SITU RESOURCE UTILIZATION (ISRU)'''<br />
<br />
ISRU is focused on identifying sources of needed elements and materials from one’s immediate surroundings. For example, while the Martian surface is barren and desolate, its carbon dioxide atmosphere provides a source of carbon and oxygen while subsurface water ice provides a source of oxygen and hydrogen. Using electrocatalysis powered by solar panels, these two sources allow for the formation of breathable O2, methane for fueling rocket engines, and carbon monoxide for syngas. Meanwhile, Martian soil can be used as an aggregate base for concrete as well as a source for sulfur and basaltic minerals, whose significance is described in the featured projects below, Mars Bricks and Tractor.<br />
<br />
<br />
==Teams==<br />
<br />
<br />
'''MARS BRICKS'''<br />
<br />
The bricks subteam experiments with methods of turning Martian and lunar soil into building materials for habitats and other structures. The team works with biopolymer-bound soil composite (BSC), which is made of soil, protein binder, and water. BSC has similar compressive strength as Portland cement concrete, the world’s most common construction materia! While concrete production accounts for about 8% of global CO2 emissions, BSC provides a possible carbon-neutral alternative and is also easy to produce from Martian resources. The team is currently designing a prototype device to autonomously produce BSCbricks.<br />
<br />
<br />
<br />
'''MARS TRACTOR'''<br />
<br />
The tractor subteam is designing and constructing an autonomous roving vehicle that goes hand in hand with the Bricks Team machine. When astronauts reach the surface of Mars, their time would be best spent on tasks that require a human touch. To save them time on manual labor, the vehicle, dubbed Mars Tractor, will gather soil, deposit said soil into the Bricks machine, and manipulate produced bricks to construct simple structures like walls and roads!<br />
<br />
<br />
'''MARTIAN MISSION SIMULATION'''<br />
<br />
Are you passionate about humans being an interplanetary species? Do you like thinking about scenarios and ways things could happen, and even apply that to space? Have no CS experience at all but want to help us build the simulation? We have a place just for you at the Simulations Team! We will be offering basic Python programming courses as well as sessions with Adam Raudonis, an AI engineer at Tesla, and a former SSI member, to talk to us about Python in simulations and help us understand what has gone in the project so far! Want to contribute in non-CS ways? We need people like you to help us brainstorm scenarios, document procedures, write papers, and perform research experiments to help us gather more data that will make our simulation better! In the Marsim subteam, there is a place for everyone whatever they want to do! The Mars team is the latest addition to the SSI community. Join us in starting this adventure! We are always open to new ideas for exciting projects that help us move toward our mission. Some ideas to pursue as the team move forward include automated landing pad construction, Martian wind energy, and electrocatalysis for fixation of the Martian atmosphere into useful chemical feedstocks and materials.<br />
<br />
<br />
'''FUTURE PROJECTS'''<br />
<br />
The Mars team is the latest addition to the SSI community. Join us in starting this adventure! We are always open to new ideas for exciting projects that help us move toward our mission. Some ideas to pursue as the team move forward include automated landing pad construction, Martian wind energy, and electrocatalysis for fixation of the Martian atmosphere into useful chemical feedstocks and materials.<br />
<br />
<br />
<br />
==HOW TO JOIN:==<br />
Join SSI, hop on the slack, and join #mars, #mars-sims, #mars-bricks, and #mars-tractor.<br />
<br />
{{Nowrap|Feel free to ping {{Leadership|Mars=True}} if you have any questions or just want to chat!}}</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Category:Mars&diff=4385Category:Mars2021-07-11T19:43:49Z<p>Aabdalla: </p>
<hr />
<div><br />
The ''SSI Mars team'' seeks to push the boundaries of crewed space missions and pave the way for permanent settlement of Mars and other celestial bodies. Our projects are centered on in situ resource utilization (ISRU), a broad group of technologies which make use of the scant resources on Mars for long-term surface missions. We turn Martian air and soil into fuel and concrete, eliminating the need to launch everything from Earth. At the same time, ISRU technologies can sustainably produce fuel and building materials for use on Earth, making our work a crucial step in fighting climate change. If we learn to live on the Red Planet, we can also save the blue one!<br />
<br />
<br />
'''IN SITU RESOURCE UTILIZATION (ISRU)'''<br />
<br />
ISRU is focused on identifying sources of needed elements and materials from one’s immediate surroundings. For example, while the Martian surface is barren and desolate, its carbon dioxide atmosphere provides a source of carbon and oxygen while subsurface water ice provides a source of oxygen and hydrogen. Using electrocatalysis powered by solar panels, these two sources allow for the formation of breathable O2, methane for fueling rocket engines, and carbon monoxide for syngas. Meanwhile, Martian soil can be used as an aggregate base for concrete as well as a source for sulfur and basaltic minerals, whose significance is described in the featured projects below, Mars Bricks and Tractor.<br />
<br />
<br />
==Teams==<br />
<br />
<br />
'''MARS BRICKS'''<br />
<br />
The bricks subteam experiments with methods of turning Martian and lunar soil into building materials for habitats and other structures. The team works with biopolymer-bound soil composite (BSC), which is made of soil, protein binder, and water. BSC has similar compressive strength as Portland cement concrete, the world’s most common construction materia! While concrete production accounts for about 8% of global CO2 emissions, BSC provides a possible carbon-neutral alternative and is also easy to produce from Martian resources. The team is currently designing a prototype device to autonomously produce BSCbricks.<br />
<br />
<br />
<br />
'''MARS TRACTOR'''<br />
<br />
The tractor subteam is designing and constructing an autonomous roving vehicle that goes hand in hand with the Bricks Team machine. When astronauts reach the surface of Mars, their time would be best spent on tasks that require a human touch. To save them time on manual labor, the vehicle, dubbed Mars Tractor, will gather soil, deposit said soil into the Bricks machine, and manipulate produced bricks to construct simple structures like walls and roads!<br />
<br />
<br />
'''MARTIAN MISSION SIMULATION'''<br />
<br />
Are you passionate about humans being an interplanetary species? Do you like thinking about scenarios and ways things could happen, and even apply that to space? Have no CS experience at all but want to help us build the simulation? We have a place just for you at the Simulations Team! We will be offering basic Python programming courses as well as sessions with Adam Raudonis, an AI engineer at Tesla, and a former SSI member, to talk to us about Python in simulations and help us understand what has gone in the project so far! Want to contribute in non-CS ways? We need people like you to help us brainstorm scenarios, document procedures, write papers, and perform research experiments to help us gather more data that will make our simulation better! In the Marsim subteam, there is a place for everyone whatever they want to do! The Mars team is the latest addition to the SSI community. Join us in starting this adventure! We are always open to new ideas for exciting projects that help us move toward our mission. Some ideas to pursue as the team move forward include automated landing pad construction, Martian wind energy, and electrocatalysis for fixation of the Martian atmosphere into useful chemical feedstocks and materials.<br />
<br />
<br />
'''FUTURE PROJECTS'''<br />
<br />
The Mars team is the latest addition to the SSI community. Join us in starting this adventure! We are always open to new ideas for exciting projects that help us move toward our mission. Some ideas to pursue as the team move forward include automated landing pad construction, Martian wind energy, and electrocatalysis for fixation of the Martian atmosphere into useful chemical feedstocks and materials.<br />
<br />
<br />
<br />
==HOW TO JOIN:==<br />
Join SSI, hop on the slack, and join #mars, #mars-sims, #mars-bricks, and #mars-tractor.<br />
<br />
Feel free to ping {{Leadership|Mars=True}} if you have any questions or just want to chat!</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Template:Leadership&diff=4384Template:Leadership2021-07-11T19:42:45Z<p>Aabdalla: </p>
<hr />
<div><onlyinclude><br />
{{nowrap|{{#vardefine:President_1_sunet|aabdalla}}<br />
{{#vardefine:President_1_name|Ahmed Abdalla}}<br />
{{#vardefine:President_2_sunet|mfharris}}<br />
{{#vardefine:President_2_name|Maya Harris}}<br />
{{#vardefine:Balloons_1_sunet|jteoh2}}<br />
{{#vardefine:Balloons_1_name|Janice Teoh}}<br />
{{#vardefine:Balloons_2_name|Matthew Tan}}<br />
{{#vardefine:Balloons_2_sunet|matthtan}}<br />
{{#vardefine:Biology_1_sunet|shrestp}}<br />
{{#vardefine:Biology_1_name|Priyanka Shrestha}}<br />
{{#vardefine:Biology_2_sunet|finsam}}<br />
{{#vardefine:Biology_2_name|Finsam Samson}}<br />
{{#vardefine:Mars_1_sunet|shreya7}}<br />
{{#vardefine:Mars_1_name|Shreya Garg}}<br />
{{#vardefine:Mars_2_sunet|kylholl}}<br />
{{#vardefine:Mars_2_name|Kylie Holland}}<br />
{{#vardefine:Operations_1_sunet|flynnd}}<br />
{{#vardefine:Operations_1_name|Flynn Dreilinger}}<br />
{{#vardefine:Operations_2_sunet|gsocolof}}<br />
{{#vardefine:Operations_2_name|Giulia Socolof}}<br />
{{#vardefine:Policy_1_sunet|jthai}}<br />
{{#vardefine:Policy_1_name|Jocelyn (Fox) Thai}}<br />
{{#vardefine:Policy_2_sunet|gdimop}}<br />
{{#vardefine:Policy_2_name|George Dimopoulos}}<br />
{{#vardefine:Rockets_1_sunet|pmwall}}<br />
{{#vardefine:Rockets_1_name|James Wall}}<br />
{{#vardefine:Rockets_2_sunet|preivers}}<br />
{{#vardefine:Rockets_2_name|Phoenix Reivers}}<br />
{{#vardefine:Satellites_1_sunet|akasha}}<br />
{{#vardefine:Satellites_1_name|Akasha Hayden}}<br />
{{#vardefine:Satellites_2_sunet|ianchang}}<br />
{{#vardefine:Satellites_2_name|Ian Chang}}<br />
{{#vardefine:Spaceshot_1_sunet|zhixinli}}<br />
{{#vardefine:Spaceshot_1_name|Zhi Xin Li}}<br />
{{#vardefine:Spaceshot_2_sunet|lvirsik}}<br />
{{#vardefine:Spaceshot_2_name|Luke Virsik}}<br />
{{#vardefine:Propulsion_1_sunet|newpomax}}<br />
{{#vardefine:Propulsion_1_name|Max Newport}}<br />
{{#vardefine:Propulsion_2_sunet|bhord}}<br />
{{#vardefine:Propulsion_2_name|Blake Hord}}<br />
{{#vardefine:Business_1_sunet|lglik}}<br />
{{#vardefine:Business_1_name|Leo Glikbarg}}<br />
{{#vardefine:Business_2_sunet|ydalmia}}<br />
{{#vardefine:Business_2_name|Yash Dalmia}}<br />
{{#vardefine:Community_1_sunet|gregen}}<br />
{{#vardefine:Community_1_name|Grant Regen}}<br />
{{#vardefine:Community_2_sunet|moserj}}<br />
{{#vardefine:Community_2_name|Joseph Moser}}<br />
{{#vardefine:Data_1_sunet|mfharris}}<br />
{{#vardefine:Data_1_name|Maya Harris}}<br />
{{#vardefine:DEI_1_sunet|tdonatto}}<br />
{{#vardefine:DEI_1_name|TaNia Donatto}}<br />
{{#vardefine:DEI_2_sunet|pmwall}}<br />
{{#vardefine:DEI_2_name|James Wall}}<br />
{{#vardefine:Events_1_sunet|kylholl}}<br />
{{#vardefine:Events_1_name|Kylie Holland}}<br />
{{#vardefine:Events_2_sunet|lbrown27}}<br />
{{#vardefine:Events_2_name|Lucy Brown}}<br />
{{#vardefine:FO_1_sunet|deniselj}}<br />
{{#vardefine:FO_1_name|Denise Lee}}<br />
{{#vardefine:FO_2_sunet|songqipu}}<br />
{{#vardefine:FO_2_name|Steven Songqi Pu}}<br />
{{#vardefine:IT_1_sunet|timv}}<br />
{{#vardefine:IT_1_name|Tim Vrakas}}<br />
{{#vardefine:Marketing_1_sunet|rahma}}<br />
{{#vardefine:Marketing_1_name|Rahma Ali}}<br />
{{#vardefine:Marketing_2_sunet|sophiaj}}<br />
{{#vardefine:Marketing_2_name|Sophia Jones}}<br />
{{#vardefine:Outreach_1_sunet|ajmacias}}<br />
{{#vardefine:Outreach_1_name|Anthony Macias}}<br />
{{#vardefine:Outreach_2_sunet|rsanda}}<br />
{{#vardefine:Outreach_2_name|Rohan Sanda}}<br />
{{#vardefine:Outreach_3_sunet|mfharris}}<br />
{{#vardefine:Outreach_3_name|Maya Harris}}<br />
{{#vardefine:Safety_1_sunet|newpomax}}<br />
{{#vardefine:Safety_1_name|Leo Glikbarg}}<br />
{{#vardefine:Safety_2_sunet|branjz}}<br />
{{#vardefine:Safety_2_name|Brandon Zhang}}<br />
{{#vardefine:Workspace_1_sunet|timv}}<br />
{{#vardefine:Workspace_1_name|Tim Vrakas}}<br />
{{#vardefine:Workspace_2_sunet|aclark22}}<br />
{{#vardefine:Workspace_2_name|Anna Clark}}<br />
{{#vardefine:Website_1_sunet|pritir}}<br />
{{#vardefine:Website_1_name|Priti Rangnekar}}<br />
{{#vardefine:Website_2_sunet|mjturk}}<br />
{{#vardefine:Website_2_name|Matthew Turk}}<br />
{{#vardefine:Current}}<br />
<br />
{{#if:{{{Presidents|}}}|{{#vardefine:Current|President}}{{slack-user|sunet-id = {{#var:{{#var:Current}}_1_sunet}}|display-name = {{#var:{{#var:Current}}_1_name}}}} and {{slack-user|sunet-id={{#var:{{#var:Current}}_2_sunet}}|display-name={{#var:{{#var:Current}}_2_name}}}}}}<br />
{{#if:{{{Balloons|}}}|{{slack-user|sunet-id = {{#var:Balloons_1_sunet}}|display-name = {{#var:Balloons_1_name}}}} and {{slack-user|sunet-id={{#var:Balloons_2_sunet}}|display-name={{#var:Balloons_2_name}}}}}}<br />
{{#if:{{{Biology|}}}|{{slack-user|sunet-id = {{#var:Biology_1_sunet}}|display-name = {{#var:Biology_1_name}}}} and {{slack-user|sunet-id={{#var:Biology_2_sunet}}|display-name={{#var:Biology_2_name}}}}}}<br />
{{#if:{{{Mars|}}}|{{slack-user|sunet-id = {{#var:Mars_1_sunet}}|display-name = {{#var:Mars_1_name}}}} and {{slack-user|sunet-id={{#var:Mars_2_sunet}}|display-name={{#var:Mars_2_name}}}}}}<br />
{{#if:{{{Operations|}}}|{{slack-user|sunet-id = {{#var:Operations_1_sunet}}|display-name = {{#var:Operations_1_name}}}} and {{slack-user|sunet-id={{#var:Operations_2_sunet}}|display-name={{#var:Operations_2_name}}}}}}<br />
{{#if:{{{Policy|}}}|{{slack-user|sunet-id = {{#var:Policy_1_sunet}}|display-name = {{#var:Policy_1_name}}}} and {{slack-user|sunet-id={{#var:Policy_2_sunet}}|display-name={{#var:Policy_2_name}}}}}}<br />
{{#if:{{{Rockets|}}}|{{slack-user|sunet-id = {{#var:Rockets_1_sunet}}|display-name = {{#var:Rockets_1_name}}}} and {{slack-user|sunet-id={{#var:Rockets_2_sunet}}|display-name={{#var:Rockets_2_name}}}}}}<br />
{{#if:{{{Satellites|}}}|{{slack-user|sunet-id = {{#var:Satellites_1_sunet}}|display-name = {{#var:Satellites_1_name}}}} and {{slack-user|sunet-id={{#var:Satellites_2_sunet}}|display-name={{#var:Satellites_2_name}}}}}}<br />
{{#if:{{{Everyone|}}}|<br />
==Presidents==<br />
:* {{slack-user|sunet-id={{#var:President_1_sunet}}|display-name={{#var:President_1_name}}}} and {{slack-user|sunet-id={{#var:President_2_sunet}}|display-name={{#var:President_2_name}}}}<br />
==Balloons Leads== <br />
:* {{slack-user|sunet-id = {{#var:Balloons_1_sunet}}|display-name = {{#var:Balloons_1_name}}}} and {{slack-user|sunet-id={{#var:Balloons_2_sunet}}|display-name={{#var:Balloons_2_name}}}}<br />
==Biology Leads== <br />
:* {{slack-user|sunet-id = {{#var:Biology_1_sunet}}|display-name = {{#var:Biology_1_name}}}} and {{slack-user|sunet-id={{#var:Biology_2_sunet}}|display-name={{#var:Biology_2_name}}}}<br />
==Mars Leads== <br />
:* {{slack-user|sunet-id = {{#var:Mars_1_sunet}}|display-name = {{#var:Mars_1_name}}}} and {{slack-user|sunet-id={{#var:Mars_2_sunet}}|display-name={{#var:Mars_2_name}}}}<br />
==Operations Leads== <br />
:* {{slack-user|sunet-id = {{#var:Operations_1_sunet}}|display-name = {{#var:Operations_1_name}}}} and {{slack-user|sunet-id={{#var:Operations_2_sunet}}|display-name={{#var:Operations_2_name}}}}<br />
==Policy Leads== <br />
:* {{slack-user|sunet-id = {{#var:Policy_1_sunet}}|display-name = {{#var:Policy_1_name}}}} and {{slack-user|sunet-id={{#var:Policy_2_sunet}}|display-name={{#var:Policy_2_name}}}}<br />
==Rockets Leads== <br />
:* {{slack-user|sunet-id = {{#var:Rockets_1_sunet}}|display-name = {{#var:Rockets_1_name}}}} and {{slack-user|sunet-id={{#var:Rockets_2_sunet}}|display-name={{#var:Rockets_2_name}}}}<br />
==Satellites Leads== <br />
:* {{slack-user|sunet-id = {{#var:Satellites_1_sunet}}|display-name = {{#var:Satellites_1_name}}}} and {{slack-user|sunet-id={{#var:Satellites_2_sunet}}|display-name={{#var:Satellites_2_name}}}}<br />
==Spaceshot Leads== <br />
:* {{slack-user|sunet-id = {{#var:Spaceshot_1_sunet}}|display-name = {{#var:Spaceshot_1_name}}}} and {{slack-user|sunet-id={{#var:Spaceshot_2_sunet}}|display-name={{#var:Spaceshot_2_name}}}}<br />
==Propulsion Leads== <br />
:* {{slack-user|sunet-id = {{#var:Propulsion_1_sunet}}|display-name = {{#var:Propulsion_1_name}}}} and {{slack-user|sunet-id={{#var:Propulsion_2_sunet}}|display-name={{#var:Propulsion_2_name}}}}<br />
==Business Leads== <br />
:* {{slack-user|sunet-id = {{#var:Business_1_sunet}}|display-name = {{#var:Business_1_name}}}} and {{slack-user|sunet-id={{#var:Business_2_sunet}}|display-name={{#var:Business_2_name}}}}<br />
==Community Leads== <br />
:* {{slack-user|sunet-id = {{#var:Community_1_sunet}}|display-name = {{#var:Community_1_name}}}} and {{slack-user|sunet-id={{#var:Community_2_sunet}}|display-name={{#var:Community_2_name}}}}<br />
==Data Lead== <br />
:* {{slack-user|sunet-id = {{#var:Data_1_sunet}}|display-name = {{#var:Data_1_name}}}}<br />
==Diversity, Equity, and Inclusion Leads== <br />
:* {{slack-user|sunet-id = {{#var:DEI_1_sunet}}|display-name = {{#var:DEI_1_name}}}} and {{slack-user|sunet-id={{#var:DEI_2_sunet}}|display-name={{#var:DEI_2_name}}}}<br />
==Events Leads== <br />
:* {{slack-user|sunet-id = {{#var:Events_1_sunet}}|display-name = {{#var:Events_1_name}}}} and {{slack-user|sunet-id={{#var:Events_2_sunet}}|display-name={{#var:Events_2_name}}}}<br />
==Financial Officers== <br />
:* {{slack-user|sunet-id = {{#var:FO_1_sunet}}|display-name = {{#var:FO_1_name}}}} and {{slack-user|sunet-id={{#var:FO_2_sunet}}|display-name={{#var:FO_2_name}}}}<br />
==IT Lead== <br />
:* {{slack-user|sunet-id = {{#var:IT_1_sunet}}|display-name = {{#var:IT_1_name}}}}<br />
==Marketing Leads== <br />
:* {{slack-user|sunet-id = {{#var:Marketing_1_sunet}}|display-name = {{#var:Marketing_1_name}}}} and {{slack-user|sunet-id={{#var:Marketing_2_sunet}}|display-name={{#var:Marketing_2_name}}}}<br />
==Outreach Leads== <br />
:* {{slack-user|sunet-id = {{#var:Outreach_1_sunet}}|display-name = {{#var:Outreach_1_name}}}}, {{slack-user|sunet-id={{#var:Outreach_2_sunet}}|display-name={{#var:Outreach_2_name}}}}, and {{slack-user|sunet-id={{#var:Outreach_3_sunet}}|display-name={{#var:Outreach_3_name}}}}<br />
==Safety Leads== <br />
:* {{slack-user|sunet-id = {{#var:Safety_1_sunet}}|display-name = {{#var:Safety_1_name}}}} and {{slack-user|sunet-id={{#var:Safety_2_sunet}}|display-name={{#var:Safety_2_name}}}}<br />
==Workspace Leads== <br />
:* {{slack-user|sunet-id = {{#var:Workspace_1_sunet}}|display-name = {{#var:Workspace_1_name}}}} and {{slack-user|sunet-id={{#var:Workspace_2_sunet}}|display-name={{#var:Workspace_2_name}}}}<br />
==Website Leads== <br />
:* {{slack-user|sunet-id = {{#var:Website_1_sunet}}|display-name = {{#var:Website_1_name}}}} and {{slack-user|sunet-id={{#var:Website_2_sunet}}|display-name={{#var:Website_2_name}}}}}}}}<br />
</onlyinclude><br />
<br />
To use, copy the code below into the desired page, populating the fields that you wish to be displayed (with any text that you want) and feel free to leave the other fields blank or remove.<br />
<br />
<nowiki><br />
{{Leadership<br />
| Everyone = <br />
| Presidents = <br />
| Balloons = <br />
| Biology = <br />
| Mars = <br />
| Operations = <br />
| Policy = <br />
| Rockets = <br />
| Satellites = <br />
}}</nowiki><br />
<br />
An example of proper usage is shown here:<br />
<br />
<nowiki><br />
{{Leadership<br />
| Everyone = true<br />
| Presidents = <br />
| Balloons = <br />
| Biology = <br />
| Mars = <br />
| Operations = <br />
| Policy = <br />
| Rockets = <br />
| Satellites = <br />
}}</nowiki><br />
<br />
or, if you only want the Satellites leads you could do:<br />
<br />
<nowiki><br />
{{Leadership<br />
| Satellites = true<br />
}}</nowiki><br />
<br />
[[Category: Templates]]<br />
<nowiki/></div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_Rockets&diff=4383How to Join Rockets2021-07-11T19:30:30Z<p>Aabdalla: update rockets leadership</p>
<hr />
<div>{{rocket-sidebar}}<br />
<br />
[[File:Pegasus1Launch.JPG | right| 250px | thumb | Pegasus 1 off the pad.]]<br />
<br />
Welcome to rockets! This page is intended to lay out the organization of the group, and let everyone know exactly what they need to do to get started! First of all, the current rockets co-leads are {{Leadership|Rockets=true}} - let us know if you have any questions about the group or about what you are supposed to do.<br />
<br />
SSI tries to introduce new members to High Power Rocketry by guiding them through building a simple rocket, flying it, and earning a Level 1 certification. While not all members have to go through this, it will introduce you to designing, analyzing, building, and then flying a rocket (and you will go to a launch, which are always fun).<br />
<br />
The main rockets page has a lot of information about High Power Rocketry, as well as how we approach it. Reading through the page before attending a meeting is recommended, but certainly not required. This one focuses more on what you have to do to join, which is less about rockets and more about logistics.<br />
<br />
= Basic Info =<br />
<br />
== Meetings ==<br />
<br />
The Rockets Team has general meetings every week; during Fall Quarter of 2017-2018, these meetings are held on Mondays from 8-9pm in Durand 450. They cover all relevant project updates (i.e. Daedalus team updates and launch logistics) and function as work sessions where all of the Rockets Team members are in the same place at once.<br />
<br />
Each project under the Rockets Team umbrella needs to have at least one work session/meeting a week in conjunction with the team-wide meetings.<br />
<br />
'''If you cannot make a project meeting, let your project lead know ahead of time.'''<br />
<br />
== Previous Knowledge ==<br />
<br />
We don’t expect you to know very much about rocketry. If you do, great! But if you don’t, we will spend the time teaching you the fundamentals and give you the opportunities and resources to learn as much about rocketry as you’d like. Working on a project is the best way to exercise and synthesize with the knowledge you gain from working with theory. <br />
<br />
Rocketry is a multi-disciplined topic. Here’s a non-exhaustive list of useful disciplines:<br />
<br />
<ul><br />
<li><blockquote><p>Heat Transfer</p></blockquote></li><br />
<li><blockquote><p>Thermodynamics</p></blockquote></li><br />
<li><blockquote><p>Fluid Mechanics (incompressible and compressible flow)</p></blockquote></li><br />
<li><blockquote><p>Physics</p></blockquote></li><br />
<li><blockquote><p>Material Sciences</p></blockquote></li><br />
<li><blockquote><p>Statics and Dynamics</p></blockquote></li><br />
<li><blockquote><p>Controls</p></blockquote></li><br />
<li><blockquote><p>Circuits</p></blockquote></li><br />
<li><blockquote><p>Amatuer Radio</p></blockquote></li><br />
<li><blockquote><p>Manufacturing</p></blockquote></li></ul><br />
<br />
Introductions to many of these are available on [[So You Want To...]]<br />
<br />
== Safety Training ==<br />
<br />
In order to get access to MC (our room), all members must have completed basic safety training. INSERT DETAILS HERE, IM GOING TO DINNER.<br />
<br />
== Time Commitment ==<br />
<br />
Rocketry is difficult to master, but worth the tedious design process. The more time you put in, the better your project will turn out as well as experience less schedule slip. Building a basic L1 and L2 rocket should not require more than 10 hours combined if done correctly (since they come from kits). L3 projects require much more time since these are designed from scratch and need to go through our NASA-inspired design process.<br />
<br />
== Budget ==<br />
<br />
Rockets has [https://docs.google.com/spreadsheets/d/11LfZaV59FnFJyt4DnnCq2Vj7DgzM_2XfgwEPw27zTdI/edit#gid=0 ''a running budget''] in the Drive (Stanford Student Space Initiative &gt; Teams &gt; Rockets). Please add your purchases to the correct tab so we can have a running tally of what we’re spending.<br />
<br />
== TRA and NAR ==<br />
<br />
[http://www.tripoli.org/ ''Tripoli Rocketry Association (TRA)''] and [http://www.nar.org/ ''National Association of Rocketry (NAR)''] are the two major organizations that organize launches, certify members, and maintain specific standards that govern high power rocketry.<br />
<br />
In order to launch high power rockets, you are required to be a member of either organization ([http://www.tripoli.org/Membership ''Tripoli Membership''] / [http://www.nar.org/join-nar/ ''NAR Membership''])<br />
<br />
The closest Tripoli launch site to Stanford is [http://www.tccrockets.com/ ''Tripoli Central CA''] (near Fresno) and the closest NAR launch site is [http://www.lunar.org/ ''LUNAR''] (somewhat near Stockton). TCC holds HPR launches (max height 16,800’) on the 3rd Saturday of each month. LUNAR holds HPR launches (max height of 15,000’) on the 1st Saturday of each month in addition to low power launches (max height of 1000’) on the 3rd Saturday of each month at Moffett Field.<br />
<br />
== Launches ==<br />
<br />
Here is the launch procedure as lifted from the [https://docs.google.com/document/d/1ItllblKqc9oATIYz2Mf4VrZK0Fh1h3ohmwlDXR33KQM/edit ''Operating Principles and Risk Management''] document.<br />
<br />
Once the team arrives at the launch site, the rules and regulations of the governing body sponsoring the launch will take precedence. Although procedure is likely to vary from site to site, the launch procedure usually occurs in this order:<br />
<br />
<ol style="list-style-type: decimal;"><br />
<li><blockquote><p>Those attempting to fly a rocket approach the Range Safety Officer (RSO) and officers in charge of the launch, sign in (with their member numbers) and usually pay a launch fee. If the flyer is attempting to get a certification, they will fill out relevant forms to declare their intention (these and other useful documentation pertaining to both national rocketry associations are included in the Appendix).</p></blockquote></li><br />
<li><blockquote><p>Depending on the skill level of the flyer, there are two variations of what may occur.</p></blockquote><br />
<ol style="list-style-type: lower-alpha;"><br />
<li><blockquote><p>In the non-certification flight case, the RSO will inspect the rocket and send the flyer to set up the rocket on the launch pad. This requires placing the rocket on the launch rails, placing the igniter in the motor, and checking the launch pad electronics for errors before returning to a safe distance from the launch pad.</p></blockquote></li><br />
<li><blockquote><p>In the case of a certification, the RSO and someone above the flyer’s certification level will inspect the rocket and send the flyer (and another more experienced member) to set up the rocket for launch. The same setup process occurs as stated above.</p></blockquote></li></ol><br />
</li><br />
<li><blockquote><p>After the range has been cleared of spectators/flyers, the RSO announces each rocket and launches them one at a time (unless otherwise specified; an example of an exception is a drag race between two rockets).</p></blockquote></li><br />
<li><blockquote><p>Once the range is cleared of rockets, flyers recover their rockets.</p></blockquote></li><br />
<li><blockquote><p>If the flight is not a certification, the procedure ends here. Otherwise, the flyer shows his or her rocket to the RSO and has them sign off on the flyer’s paperwork if the flight is successful. The paperwork is then sent off to the headquarters of the organization and processed.</p></blockquote></li></ol><br />
<br />
== Rocket Naming Conventions ==<br />
<br />
For mass certs:<br />
<br />
SSI-R# will be the designation for general rocket launches (blanket certification launches).<br />
<br />
Your rocket’s name can be whatever you would like it to be. Examples in the past are: ''Cardinal I'', ''Flamos'', ''Chris May'', etc.<br />
<br />
For Daedalus:<br />
<br />
SSI-[Level][three letter code denoting name][Launch number] ex. SSI-L3TAL1. These will not affect the number of SSI-R launches. They will have separate counts. The launch number will be useful if the same rocket goes flying again (which should be plausible if you don't mash it).<br />
<br />
If the rocket is Class 3, no Level number is required.<br />
<br />
== Rockets Leadership ==<br />
<br />
The logistics required to run a fully operational Rockets team can be too much for just two co-leads to handle. The Rockets Leadership is a group of people who care about organizing the logistics behind launches and projects that the team is working on. If you show that you care and put in an exceptional amount of effort into your project, you can choose to be a part of this group.<br />
<br />
[https://docs.google.com/a/stanford.edu/document/d/1-J5TS0MRgHi0HFTyPhYzzF6VZBa3dqO-WpxrCLgJIpQ/edit?usp=sharing ''Here is a document with all the roles on Rockets Leadership.'']<br />
<br />
= Resources =<br />
<br />
Other members are one of your best resources if you have any questions about rocketry. Other fantastic resources are laid out below.<br />
<br />
== Rockets Drive ==<br />
<br />
There are tons of useful things in the Rockets folder!!!!! Here are descriptions of a few of those folders.<br />
<br />
=== [http://wiki.stanfordssi.org/Stanford_Student_Space_Initiative_(SSI) ''Wiki''] ===<br />
<br />
Go here first for finding useful data on L1 certification procedures! You should add as much to the wiki as possible.<br />
<br />
=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVUFUcEpWRGt2M00 ''Archive''] ===<br />
<br />
This holds all the older Rockets plans/documents/etc. Usually these documents are not particularly useful (which is why they are in the archive).<br />
<br />
=== [https://drive.google.com/open?id=0B_uGMv8pu2KgU3Rsbi1KOFpuSzA ''Daedalus''] ===<br />
<br />
This holds all the information for Daedalus, like team folders, L3 requirements, and PDRs &amp; CDRs. Snoop around to see what they’ve done so far and steal information for your project (citing is always a good idea when you do take information).<br />
<br />
=== [https://drive.google.com/open?id=0B_uGMv8pu2KgVkdjcGQtWTNsZU0 ''Getting Nerdy: Textbooks and Manuals''] ===<br />
<br />
This folder holds a collection of useful texts ranging from textbooks, manuals, NASA articles and technical reports. If you need to learn things, [https://docs.google.com/a/stanford.edu/document/d/18PSjKqlVLTQzfJLG7ggiWY61W3ZcaD9kCcEePinAJw0/edit?usp=drive_web ''check out this document''].<br />
<br />
=== [https://drive.google.com/open?id=0ByRlIAW5-8GqcUcyckNmZlFfN1U ''Launch Documentation''] ===<br />
<br />
This holds all the launch documentation for upcoming launches and things like build slot signups, ride signups, rocket building instructions, required reading, pre-flight checklists, etc. Read through this folder and you’ll have a pretty damn good idea of launch logistics.<br />
<br />
=== [https://drive.google.com/open?id=0B-5MRX1wVAAdNXQxUzdNVGNRRWc ''Rockets Operating Principles''] ===<br />
<br />
This folder houses all of the operating principles, risk mitigation planning, and miscellaneous safety codes, documentation, and literally anything Stanford’s lawyers could possibly want from us. If you read the document you will have a very good understanding of how the team operates on an administrative level.<br />
<br />
=== [https://drive.google.com/open?id=0B_uGMv8pu2KgdXo4YVJEV1duRlU ''The Design Process''] ===<br />
<br />
This folder houses all you need to know to design, fabricate and launch a rocket from a documentation standpoint. Read it.<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 #rockets), which allow us to push out general updates to everyone interested in the rockets team and direct messages in order to communicate with one person - although Slack has recently added a group messaging feature if you don’t want to make an entire channel for a 4 person chat - at a time. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!<br />
<br />
[https://ssi-teams.slack.com/signup ''Join the SSI Slack here.'']<br />
<br />
== End Station III/ISS ==<br />
<br />
ISS can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. Located in End Station III, ISS houses work sessions and project storage. Note: keycard access is required to the building. For specific questions, contact our workspace manager (see our website). Meetings or work sessions can also be conducted in the conference room, Durand 393 (often available), the floor of End Station III (known as Dragon), or Durand 450 (with prior reservation through AA Department Office on the second floor of Durand).<br />
<br />
<br />
<br />
<noinclude>[[Category:Rockets]]</noinclude> [[Category: Rockets Guides]]</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Template:Leadership&diff=4382Template:Leadership2021-07-06T02:36:06Z<p>Aabdalla: </p>
<hr />
<div><onlyinclude><br />
{{nowrap|{{#vardefine:President_1_sunet|aabdalla}}<br />
{{#vardefine:President_1_name|Ahmed Abdalla}}<br />
{{#vardefine:President_2_sunet|mfharris}}<br />
{{#vardefine:President_2_name|Maya Harris}}<br />
{{#vardefine:Balloons_1_sunet|jteoh2}}<br />
{{#vardefine:Balloons_1_name|Janice Teoh}}<br />
{{#vardefine:Balloons_2_name|Matthew Tan}}<br />
{{#vardefine:Balloons_2_sunet|matthtan}}<br />
{{#vardefine:Biology_1_sunet|luciam}}<br />
{{#vardefine:Biology_1_name|Lucia Riley Morris}}<br />
{{#vardefine:Biology_2_sunet|finsam}}<br />
{{#vardefine:Biology_2_name|Finsam Samson}}<br />
{{#vardefine:Mars_1_sunet|rahma}}<br />
{{#vardefine:Mars_1_name|Rahma Ali}}<br />
{{#vardefine:Mars_2_sunet|kylholl}}<br />
{{#vardefine:Mars_2_name|Kylie Holland}}<br />
{{#vardefine:Operations_1_sunet|flynnd}}<br />
{{#vardefine:Operations_1_name|Flynn Dreilinger}}<br />
{{#vardefine:Operations_2_sunet|gsocolof}}<br />
{{#vardefine:Operations_2_name|Giulia Socolof}}<br />
{{#vardefine:Policy_1_sunet|jthai}}<br />
{{#vardefine:Policy_1_name|Jocelyn Thai}}<br />
{{#vardefine:Policy_2_sunet|lglik}}<br />
{{#vardefine:Policy_2_name|Leo Glikbarg}}<br />
{{#vardefine:Rockets_1_sunet|jsbell39}}<br />
{{#vardefine:Rockets_1_name|Spencer Bell}}<br />
{{#vardefine:Rockets_2_sunet|mfharris}}<br />
{{#vardefine:Rockets_2_name|Maya Harris}}<br />
{{#vardefine:Satellites_1_sunet|akasha}}<br />
{{#vardefine:Satellites_1_name|Akasha Hayden}}<br />
{{#vardefine:Satellites_2_sunet|ianchang}}<br />
{{#vardefine:Satellites_2_name|Ian Chang}}<br />
{{#vardefine:Spaceshot_1_sunet|zhixinli}}<br />
{{#vardefine:Spaceshot_1_name|Zhi Xin Li}}<br />
{{#vardefine:Spaceshot_2_sunet|lvirsik}}<br />
{{#vardefine:Spaceshot_2_name|Luke Virsik}}<br />
{{#vardefine:Propulsion_1_sunet|newpomax}}<br />
{{#vardefine:Propulsion_1_name|Max Newport}}<br />
{{#vardefine:Propulsion_2_sunet|bhord}}<br />
{{#vardefine:Propulsion_2_name|Blake Hord}}<br />
{{#vardefine:Business_1_sunet|lglik}}<br />
{{#vardefine:Business_1_name|Leo Glikbarg}}<br />
{{#vardefine:Business_2_sunet|ydalmia}}<br />
{{#vardefine:Business_2_name|Yash Dalmia}}<br />
{{#vardefine:Community_1_sunet|gregen}}<br />
{{#vardefine:Community_1_name|Grant Regen}}<br />
{{#vardefine:Community_2_sunet|moserj}}<br />
{{#vardefine:Community_2_name|Joseph Moser}}<br />
{{#vardefine:Data_1_sunet|mfharris}}<br />
{{#vardefine:Data_1_name|Maya Harris}}<br />
{{#vardefine:DEI_1_sunet|sebamq}}<br />
{{#vardefine:DEI_1_name|Seba Marin-Quiros}}<br />
{{#vardefine:DEI_2_sunet|tdonatto}}<br />
{{#vardefine:DEI_2_name|TaNia Donatto}}<br />
{{#vardefine:DEI_3_sunet|pmwall}}<br />
{{#vardefine:DEI_3_name|James Wall}}<br />
{{#vardefine:Events_1_sunet|kylholl}}<br />
{{#vardefine:Events_1_name|Kylie Holland}}<br />
{{#vardefine:Events_2_sunet|lbrown27}}<br />
{{#vardefine:Events_2_name|Lucy Brown}}<br />
{{#vardefine:FO_1_sunet|deniselj}}<br />
{{#vardefine:FO_1_name|Denise Lee}}<br />
{{#vardefine:FO_2_sunet|songqipu}}<br />
{{#vardefine:FO_2_name|Steven Songqi Pu}}<br />
{{#vardefine:IT_1_sunet|timv}}<br />
{{#vardefine:IT_1_name|Tim Vrakas}}<br />
{{#vardefine:Marketing_1_sunet|rahma}}<br />
{{#vardefine:Marketing_1_name|Rahma Ali}}<br />
{{#vardefine:Marketing_2_sunet|sophiaj}}<br />
{{#vardefine:Marketing_2_name|Sophia Jones}}<br />
{{#vardefine:Outreach_1_sunet|ajmacias}}<br />
{{#vardefine:Outreach_1_name|Anthony Macias}}<br />
{{#vardefine:Outreach_2_sunet|rsanda}}<br />
{{#vardefine:Outreach_2_name|Rohan Sanda}}<br />
{{#vardefine:Outreach_3_sunet|mfharris}}<br />
{{#vardefine:Outreach_3_name|Maya Harris}}<br />
{{#vardefine:Safety_1_sunet|newpomax}}<br />
{{#vardefine:Safety_1_name|Leo Glikbarg}}<br />
{{#vardefine:Safety_2_sunet|branjz}}<br />
{{#vardefine:Safety_2_name|Brandon Zhang}}<br />
{{#vardefine:Workspace_1_sunet|timv}}<br />
{{#vardefine:Workspace_1_name|Tim Vrakas}}<br />
{{#vardefine:Workspace_2_sunet|aclark22}}<br />
{{#vardefine:Workspace_2_name|Anna Clark}}<br />
{{#vardefine:Website_1_sunet|pritir}}<br />
{{#vardefine:Website_1_name|Priti Rangnekar}}<br />
{{#vardefine:Website_2_sunet|mjturk}}<br />
{{#vardefine:Website_2_name|Matthew Turk}}<br />
{{#vardefine:Current}}<br />
<br />
{{#if:{{{Presidents|}}}|{{#vardefine:Current|President}}{{slack-user|sunet-id = {{#var:{{#var:Current}}_1_sunet}}|display-name = {{#var:{{#var:Current}}_1_name}}}} and {{slack-user|sunet-id={{#var:{{#var:Current}}_2_sunet}}|display-name={{#var:{{#var:Current}}_2_name}}}}}}<br />
{{#if:{{{Balloons|}}}|{{slack-user|sunet-id = {{#var:Balloons_1_sunet}}|display-name = {{#var:Balloons_1_name}}}} and {{slack-user|sunet-id={{#var:Balloons_2_sunet}}|display-name={{#var:Balloons_2_name}}}}}}<br />
{{#if:{{{Biology|}}}|{{slack-user|sunet-id = {{#var:Biology_1_sunet}}|display-name = {{#var:Biology_1_name}}}} and {{slack-user|sunet-id={{#var:Biology_2_sunet}}|display-name={{#var:Biology_2_name}}}}}}<br />
{{#if:{{{Mars|}}}|{{slack-user|sunet-id = {{#var:Mars_1_sunet}}|display-name = {{#var:Mars_1_name}}}} and {{slack-user|sunet-id={{#var:Mars_2_sunet}}|display-name={{#var:Mars_2_name}}}}}}<br />
{{#if:{{{Operations|}}}|{{slack-user|sunet-id = {{#var:Operations_1_sunet}}|display-name = {{#var:Operations_1_name}}}} and {{slack-user|sunet-id={{#var:Operations_2_sunet}}|display-name={{#var:Operations_2_name}}}}}}<br />
{{#if:{{{Policy|}}}|{{slack-user|sunet-id = {{#var:Policy_1_sunet}}|display-name = {{#var:Policy_1_name}}}} and {{slack-user|sunet-id={{#var:Policy_2_sunet}}|display-name={{#var:Policy_2_name}}}}}}<br />
{{#if:{{{Rockets|}}}|{{slack-user|sunet-id = {{#var:Rockets_1_sunet}}|display-name = {{#var:Rockets_1_name}}}} and {{slack-user|sunet-id={{#var:Rockets_2_sunet}}|display-name={{#var:Rockets_2_name}}}}}}<br />
{{#if:{{{Satellites|}}}|{{slack-user|sunet-id = {{#var:Satellites_1_sunet}}|display-name = {{#var:Satellites_1_name}}}} and {{slack-user|sunet-id={{#var:Satellites_2_sunet}}|display-name={{#var:Satellites_2_name}}}}}}<br />
{{#if:{{{Everyone|}}}|<br />
==Presidents==<br />
:* {{slack-user|sunet-id={{#var:President_1_sunet}}|display-name={{#var:President_1_name}}}} and {{slack-user|sunet-id={{#var:President_2_sunet}}|display-name={{#var:President_2_name}}}}<br />
==Balloons Leads== <br />
:* {{slack-user|sunet-id = {{#var:Balloons_1_sunet}}|display-name = {{#var:Balloons_1_name}}}} and {{slack-user|sunet-id={{#var:Balloons_2_sunet}}|display-name={{#var:Balloons_2_name}}}}<br />
==Biology Leads== <br />
:* {{slack-user|sunet-id = {{#var:Biology_1_sunet}}|display-name = {{#var:Biology_1_name}}}} and {{slack-user|sunet-id={{#var:Biology_2_sunet}}|display-name={{#var:Biology_2_name}}}}<br />
==Mars Leads== <br />
:* {{slack-user|sunet-id = {{#var:Mars_1_sunet}}|display-name = {{#var:Mars_1_name}}}} and {{slack-user|sunet-id={{#var:Mars_2_sunet}}|display-name={{#var:Mars_2_name}}}}<br />
==Operations Leads== <br />
:* {{slack-user|sunet-id = {{#var:Operations_1_sunet}}|display-name = {{#var:Operations_1_name}}}} and {{slack-user|sunet-id={{#var:Operations_2_sunet}}|display-name={{#var:Operations_2_name}}}}<br />
==Policy Leads== <br />
:* {{slack-user|sunet-id = {{#var:Policy_1_sunet}}|display-name = {{#var:Policy_1_name}}}} and {{slack-user|sunet-id={{#var:Policy_2_sunet}}|display-name={{#var:Policy_2_name}}}}<br />
==Rockets Leads== <br />
:* {{slack-user|sunet-id = {{#var:Rockets_1_sunet}}|display-name = {{#var:Rockets_1_name}}}} and {{slack-user|sunet-id={{#var:Rockets_2_sunet}}|display-name={{#var:Rockets_2_name}}}}<br />
==Satellites Leads== <br />
:* {{slack-user|sunet-id = {{#var:Satellites_1_sunet}}|display-name = {{#var:Satellites_1_name}}}} and {{slack-user|sunet-id={{#var:Satellites_2_sunet}}|display-name={{#var:Satellites_2_name}}}}<br />
==Spaceshot Leads== <br />
:* {{slack-user|sunet-id = {{#var:Spaceshot_1_sunet}}|display-name = {{#var:Spaceshot_1_name}}}} and {{slack-user|sunet-id={{#var:Spaceshot_2_sunet}}|display-name={{#var:Spaceshot_2_name}}}}<br />
==Propulsion Leads== <br />
:* {{slack-user|sunet-id = {{#var:Propulsion_1_sunet}}|display-name = {{#var:Propulsion_1_name}}}} and {{slack-user|sunet-id={{#var:Propulsion_2_sunet}}|display-name={{#var:Propulsion_2_name}}}}<br />
==Business Leads== <br />
:* {{slack-user|sunet-id = {{#var:Business_1_sunet}}|display-name = {{#var:Business_1_name}}}} and {{slack-user|sunet-id={{#var:Business_2_sunet}}|display-name={{#var:Business_2_name}}}}<br />
==Community Leads== <br />
:* {{slack-user|sunet-id = {{#var:Community_1_sunet}}|display-name = {{#var:Community_1_name}}}} and {{slack-user|sunet-id={{#var:Community_2_sunet}}|display-name={{#var:Community_2_name}}}}<br />
==Data Lead== <br />
:* {{slack-user|sunet-id = {{#var:Data_1_sunet}}|display-name = {{#var:Data_1_name}}}}<br />
==Diversity, Equity, and Inclusion Leads== <br />
:* {{slack-user|sunet-id = {{#var:DEI_1_sunet}}|display-name = {{#var:DEI_1_name}}}}, {{slack-user|sunet-id={{#var:DEI_2_sunet}}|display-name={{#var:DEI_2_name}}}}, and {{slack-user|sunet-id={{#var:DEI_3_sunet}}|display-name={{#var:DEI_3_name}}}}<br />
==Events Leads== <br />
:* {{slack-user|sunet-id = {{#var:Events_1_sunet}}|display-name = {{#var:Events_1_name}}}} and {{slack-user|sunet-id={{#var:Events_2_sunet}}|display-name={{#var:Events_2_name}}}}<br />
==Financial Officers== <br />
:* {{slack-user|sunet-id = {{#var:FO_1_sunet}}|display-name = {{#var:FO_1_name}}}} and {{slack-user|sunet-id={{#var:FO_2_sunet}}|display-name={{#var:FO_2_name}}}}<br />
==IT Lead== <br />
:* {{slack-user|sunet-id = {{#var:IT_1_sunet}}|display-name = {{#var:IT_1_name}}}}<br />
==Marketing Leads== <br />
:* {{slack-user|sunet-id = {{#var:Marketing_1_sunet}}|display-name = {{#var:Marketing_1_name}}}} and {{slack-user|sunet-id={{#var:Marketing_2_sunet}}|display-name={{#var:Marketing_2_name}}}}<br />
==Outreach Leads== <br />
:* {{slack-user|sunet-id = {{#var:Outreach_1_sunet}}|display-name = {{#var:Outreach_1_name}}}}, {{slack-user|sunet-id={{#var:Outreach_2_sunet}}|display-name={{#var:Outreach_2_name}}}}, and {{slack-user|sunet-id={{#var:Outreach_3_sunet}}|display-name={{#var:Outreach_3_name}}}}<br />
==Safety Leads== <br />
:* {{slack-user|sunet-id = {{#var:Safety_1_sunet}}|display-name = {{#var:Safety_1_name}}}} and {{slack-user|sunet-id={{#var:Safety_2_sunet}}|display-name={{#var:Safety_2_name}}}}<br />
==Workspace Leads== <br />
:* {{slack-user|sunet-id = {{#var:Workspace_1_sunet}}|display-name = {{#var:Workspace_1_name}}}} and {{slack-user|sunet-id={{#var:Workspace_2_sunet}}|display-name={{#var:Workspace_2_name}}}}<br />
==Website Leads== <br />
:* {{slack-user|sunet-id = {{#var:Website_1_sunet}}|display-name = {{#var:Website_1_name}}}} and {{slack-user|sunet-id={{#var:Website_2_sunet}}|display-name={{#var:Website_2_name}}}}}}}}<br />
</onlyinclude><br />
<br />
To use, copy the code below into the desired page, populating the fields that you wish to be displayed (with any text that you want) and feel free to leave the other fields blank or remove.<br />
<br />
<nowiki><br />
{{Leadership<br />
| Everyone = <br />
| Presidents = <br />
| Balloons = <br />
| Biology = <br />
| Mars = <br />
| Operations = <br />
| Policy = <br />
| Rockets = <br />
| Satellites = <br />
}}</nowiki><br />
<br />
An example of proper usage is shown here:<br />
<br />
<nowiki><br />
{{Leadership<br />
| Everyone = true<br />
| Presidents = <br />
| Balloons = <br />
| Biology = <br />
| Mars = <br />
| Operations = <br />
| Policy = <br />
| Rockets = <br />
| Satellites = <br />
}}</nowiki><br />
<br />
or, if you only want the Satellites leads you could do:<br />
<br />
<nowiki><br />
{{Leadership<br />
| Satellites = true<br />
}}</nowiki><br />
<br />
[[Category: Templates]]<br />
<nowiki/></div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4358Calendar2021-04-30T22:50:48Z<p>Aabdalla: /* Google Calendar */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Copy the link to the calendar you want to subscribe to from above<br />
# [[File:Cal.PNG|frame|center|Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
# [[File:Fromlink.PNG|frame|center|Click the '+' icon and choose "From URL"]]<br />
# [[File:Addcal.png|frame|center|Paste the link to the calendar you chose in step 1 and click "Add Calendar"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Addcal.png&diff=4357File:Addcal.png2021-04-30T22:50:05Z<p>Aabdalla: </p>
<hr />
<div></div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Fromlink.PNG&diff=4356File:Fromlink.PNG2021-04-30T22:49:39Z<p>Aabdalla: </p>
<hr />
<div></div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Cal3.PNG&diff=4355File:Cal3.PNG2021-04-30T22:47:48Z<p>Aabdalla: Aabdalla uploaded a new version of File:Cal3.PNG</p>
<hr />
<div>== Summary ==<br />
google calendar snapshot</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Cal3.PNG&diff=4354File:Cal3.PNG2021-04-30T22:47:03Z<p>Aabdalla: Aabdalla reverted File:Cal3.PNG to an old version</p>
<hr />
<div>== Summary ==<br />
google calendar snapshot</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Cal3.PNG&diff=4353File:Cal3.PNG2021-04-30T22:42:33Z<p>Aabdalla: Aabdalla uploaded a new version of File:Cal3.PNG</p>
<hr />
<div>== Summary ==<br />
google calendar snapshot</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Cal2.PNG&diff=4352File:Cal2.PNG2021-04-30T22:41:01Z<p>Aabdalla: Aabdalla uploaded a new version of File:Cal2.PNG</p>
<hr />
<div>== Summary ==<br />
google calendar snapshot</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4351Calendar2021-04-30T22:38:40Z<p>Aabdalla: /* Google Calendar */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Copy the link to the calendar you want to subscribe to from above<br />
# [[File:Cal.PNG|frame|center|Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
# [[File:Cal2.PNG|frame|center|Click the '+' icon and choose "From URL"]]<br />
# [[File:Cal3.PNG|frame|center|Paste the link to the calendar you chose in step 1 and click "Add Calendar"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4350Calendar2021-04-30T06:48:51Z<p>Aabdalla: /* Google Calendar */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Download your desired ics file from the links above<br />
# [[File:Cal.PNG|frame|center|Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
# [[File:Cal2.PNG|frame|center|Click the '+' icon and choose "Import"]]<br />
# [[File:Cal3.PNG|frame|center|Select the file you downloaded from your file explorer and press "Import"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4349Calendar2021-04-30T06:45:14Z<p>Aabdalla: /* Google Calendar */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
Download your desired ics file from the links above<br />
[[File:Cal.PNG|thumb|left|Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
[[File:Cal2.PNG|thumb|left|Click the '+' icon and choose "Import"]]<br />
[[File:Cal3.PNG|thumb|left|Select the file you downloaded from your file explorer and press "Import"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4348Calendar2021-04-30T06:42:03Z<p>Aabdalla: /* Google Calendar */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Download your desired ics file from the links above<br />
# [[File:Cal.PNG||Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
# [[File:Cal2.PNG||Click the '+' icon and choose "Import"]]<br />
# [[File:Cal3.PNG||Select the file you downloaded from your file explorer and press "Import"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4347Calendar2021-04-30T06:41:37Z<p>Aabdalla: /* Subscribing to Calendars */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Download your desired ics file from the links above<br />
# [[File:Cal.PNG|Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
# [[File:Cal2.PNG|Click the '+' icon and choose "Import"]]<br />
# [[File:Cal3.PNG|Select the file you downloaded from your file explorer and press "Import"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.<br />
<br />
===Outlook Calendar===<br />
<br />
===Apple Calendar===<br />
<br />
===Calendly===</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4346Calendar2021-04-30T06:40:43Z<p>Aabdalla: /* Google Calendar */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
# Download your desired ics file from the links above<br />
# [[File:Cal.PNG|Open up your Google Calendar and scroll over to the "Other calendars" tab]]<br />
# [[File:Cal2.PNG|Click the '+' icon and choose "Import"]]<br />
# [[File:Cal3.PNG|Select the file you downloaded from your file explorer and press "Import"]]<br />
<br />
Sometimes this process doesn't work the first time, not really sure why. Don't panic just try it again.</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4345Calendar2021-04-30T06:36:22Z<p>Aabdalla: /* Google Calendar */</p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===<br />
[[File:Cal.PNG]]<br />
[[File:Cal2.PNG]]<br />
[[File:Cal3.PNG]]</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Cal3.PNG&diff=4344File:Cal3.PNG2021-04-30T06:33:43Z<p>Aabdalla: google calendar snapshot</p>
<hr />
<div>== Summary ==<br />
google calendar snapshot</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Cal2.PNG&diff=4343File:Cal2.PNG2021-04-30T06:33:30Z<p>Aabdalla: google calendar snapshot</p>
<hr />
<div>== Summary ==<br />
google calendar snapshot</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=File:Cal.PNG&diff=4342File:Cal.PNG2021-04-30T06:30:55Z<p>Aabdalla: google calendar snippet</p>
<hr />
<div>== Summary ==<br />
google calendar snippet</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4341Calendar2021-04-30T06:28:54Z<p>Aabdalla: </p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
==Subscribing to Calendars==<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
===Google Calendar===</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4340Calendar2021-04-30T06:28:21Z<p>Aabdalla: </p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]<br />
<br />
=Subscribing to Calendars=<br />
Whatever calendar app you use will give you the option to subcribe to an outside calendar using an ics file. The links above take you to an ics file for each subteam's calendar. These calendars are hosted on Outlook for a host of bureacratic reasons that aren't very pertinent to this page. Below you can find guidelines on how to add that ics file to the calendar app of your choosing.<br />
==Google Calendar==</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Calendar&diff=4339Calendar2021-04-30T06:01:05Z<p>Aabdalla: </p>
<hr />
<div>There once was a time when SSI was small enough for a single calendar, in the days before the rift. Now, there are 8, one for each team in SSI and a calendar devoted entirely to events (to rule them all and in the darkness bind them, so-to-speak). You can view them on the website, at https://stanfordssi.org/events, or add them to your personal calendar (iCal, Google Calendar, Outlook, etc.) with the .ics links provided here.<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/ca7bf600b2ff47278da7400e9415a7ce17005022238289599526/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Events]<br />
<br />
'''Teams:'''<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/735e3e50b3b748f5a302964eb93becd37480700993753267689/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Balloons]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/3f988b5a3ad74181b5bfa595fb66d61d17439656288001954590/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Biology]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/c12e1fdd69484a04bf69992e946cea326770383156545951962/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Mars]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/a3ec72eeab12479c9e2f5285277b775c8758137961323794290/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Operations]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/550548b74b264837b7e2de6bbe0bd22016904862627457384984/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Policy]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/80d34ce3e0e748caae8e1300cb856a8613993566167978815063/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Rockets]<br />
<br />
[https://outlook.office365.com/owa/calendar/2011ea4cbe914f4989a4a2cd8137b3ad@stanford.edu/6c9c351c7b514adb9286a6fbeb55227411172247604092841466/S-1-8-27252731-3175038331-2327072536-1781927242/reachcalendar.ics Satellites]</div>Aabdallahttps://ssi-wiki.stanford.edu/w/index.php?title=Spaceshot&diff=4300Spaceshot2021-02-28T07:04:13Z<p>Aabdalla: </p>
<hr />
<div>Spaceshot!<br />
Project Spaceshot was started in 2018 but Thomas White...</div>Aabdalla