https://ssi-wiki.stanford.edu/w/api.php?action=feedcontributions&user=Ceglikbarg&feedformat=atomStanford SSI Wiki - User contributions [en]2024-03-28T11:04:12ZUser contributionsMediaWiki 1.35.0https://ssi-wiki.stanford.edu/w/index.php?title=Spaceshot&diff=3784Spaceshot2020-02-17T02:37:37Z<p>Ceglikbarg: needs work</p>
<hr />
<div>Spaceshot!</div>Ceglikbarghttps://ssi-wiki.stanford.edu/w/index.php?title=How_to_Join_SSI&diff=3523How to Join SSI2018-10-28T23:12:45Z<p>Ceglikbarg: /* Becoming an official member */</p>
<hr />
<div>Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member.<br />
<br />
=Becoming an official member=<br />
<br />
# Pay dues ($10 in exchange for a t-shirt) to our financial officers - any leadership team member can accept these in cash, or you can Venmo our Financial Officer, Chloe Glikbarg, directly. Message her on Slack for details ({{slack-user|chloe}}). If dues present a financial hardship, message {{slack-user|tucks}}, {{slack-user|kai}}, or {{slack-user|chloe}}, and we'll waive them.<br />
# Fill out this 30-second form: [https://stanfordssi.org/q https://stanfordssi.org/q]<br />
# Join the SSI Slack [https://ssi-teams.slack.com/signup here].<br />
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].<br />
# In order to allow you access to our workspace, [[End Station III]], you need to do the following things:<br />
##Log into [https://axess.sahr.stanford.edu/ AXESS] and click "STARS" at the top<br />
##Using either the "All Learning" list, or the Search Catalog, complete the following three safety trainings: '''EHS-4200: General Safety, Injury Prevention (IIPP), and Emergency Preparedness, EHS-1900: Chemical Safety for Laboratories, and EHS-2200: Compressed Gas Safety.''' If you've completed any of these previously for a laboratory class or other university purpose, you don't need to repeat them.<br />
##Some time after completion, you will receive an email for each of these (can take up to 24 hours) certifying your completion. Save each e-mail as a PDF, or, less preferably, screenshot it. This PDF or screenshot '''must''' have your name on it. Ask in {{slack-channel|welcome-to-ssi}} if you have questions about EH&S training - mentioning {{slack-user|mc-safety}} in your question will notify people who can help.<br />
##Sign into the [http://internal.stanfordssi.org internal site] using your Stanford email and under EH&S Safety Training, upload PDFs or screenshots proving your completion of the safety trainings.<br />
##Attend a safety tour of ES3. Ask in {{slack-channel|welcome-to-ssi}} to coordinate a time.<br />
##While in ES3, make sure to sign a copy of the Space Usage Agreement and leave it in the binder by the door. This is your record of completing the workspace safety tour.<br />
##Send a message in Slack to our workspace manager {{slack-user|smaldonado}} that you've completed everything!<br />
<br />
=Resources=<br />
<br />
== [https://ssi-teams.slack.com/ Slack] ==<br />
<br />
Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!<br />
<br />
To see what a list of what channels there are to join, check out the [[Slack Directory]].<br />
<br />
[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']<br />
<br />
==[https://calendar.google.com/calendar/embed?src=5or10qu0uhtfqcdqb3knrpn3r8@group.calendar.google.com&ctz=America/Los_Angeles SSI Calendar]==<br />
Home to all of our events across all our teams.<br />
<br />
== [https://stanfordssi.org/leadership SSI Leadership] ==<br />
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.<br />
<br />
==The Wiki==<br />
<br />
This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.<br />
<br />
==[https://drive.google.com/open?id=0B5ethK6WQZfAWXgtR25KOEloN2M SSI Drive]==<br />
<br />
The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage. <br />
<br />
== [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>Ceglikbarghttps://ssi-wiki.stanford.edu/w/index.php?title=Getting_Reimbursed&diff=3466Getting Reimbursed2018-08-06T17:57:30Z<p>Ceglikbarg: </p>
<hr />
<div>Congratulations! You have done a great service to SSI by spending your own hard-earned money on buying something we need. Thanks for that. The reimbursement system is absolutely key to our functionality as an organization - without it, it would take months of lead time to buy anything, and what we do would become almost impossible. Now, let's get your money back, as quickly as possible.<br />
<br />
<br />
= Step 1: Keep you receipt! =<br />
<br />
The importance of this cannot be overstated. Without a receipt, it's very difficult to reimburse. If you're buying things at home, save your receipt and try to submit it as soon as you can; if you're traveling with SSI, take a picture of your receipt in case you forget it or accidentally lose it. And when you get your receipt, check two things:<br />
- Is it an invoice? If so, it's not quite enough - you also need to attach a bank statement. <br />
- Is it itemized? Restaurants are especially notorious for this, but if a place doesn't list a breakdown of what you spent, it doesn't count. If you get one of these, go back and ask for an itemized one. <br />
<br />
<br />
= Step 2: Go to the SSI Internal Site =<br />
<br />
It's at https://internal.stanfordssi.org/. You can log on with your Stanford ID. If all goes well, you should see this page: <br />
<br />
<br />
<br />
If not, go to #operations-website and complain. <br />
<br />
<br />
= Step 3: Click on the reimbursements tab =<br />
<br />
Once you're there, click on New Reimbursement<br />
<br />
<br />
<br />
= Step 4: Fill out the fields and submit! = <br />
<br />
If you're confused by a field or unsure what to put, please contact @chloe or @Peter Maldonado.<br />
<br />
<br />
<br />
<br />
= Step 5: (Rockets Team Only) Fill Out an Expense Report = <br />
<br />
Some teams require <br />
<br />
<br />
<br />
= Step 6: Track your process and make changes if necessary =<br />
<br />
When you submit your reimbursement, slackbot will message you to let you know! After that, it's up to the financial officers to process it, and slackbot will update you as they do so. If there's something wrong with your reimbursement, they'll also let you know! If you get a message saying your reimbursement was rejected, don't despair. There are plenty of ways to fix it and resubmit it--check the message from either the FOs, team co-leads, or SSE (Stanford Student Enterprises, the people who make the final call on the validity of a reimbursement) and make the necessary changes. If you're unsure what the message means or want clarification, contact either @chloe or @Peter Maldonado.<br />
<br />
<br />
<br />
= Step 7: Pick up your reimbursement = <br />
<br />
Within a few weeks, you should get an email from ASSU saying that a payment is available! You can go pick up your check from the ASSU office on the first floor of Old Union, behind the Axe and Palm (TAP).<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Operations]]</div>Ceglikbarghttps://ssi-wiki.stanford.edu/w/index.php?title=Getting_Reimbursed&diff=3464Getting Reimbursed2018-07-26T23:17:27Z<p>Ceglikbarg: </p>
<hr />
<div>Congratulations! You have done a great service to SSI by spending your own hard-earned money on buying something we need. Thanks for that. The reimbursement system is absolutely key to our functionality as an organization - without it, it would take months of lead time to buy anything, and what we do would become almost impossible. Now, let's get your money back, as quickly as possible.<br />
<br />
<br />
= Step 1: Keep you receipt! =<br />
<br />
The importance of this cannot be overstated. Without a receipt, it's very difficult to reimburse. If you're buying things at home, save your receipt and try to submit it as soon as you can; if you're traveling with SSI, take a picture of your receipt in case you forget it or accidentally lose it. And when you get your receipt, check two things:<br />
- Is it an invoice? If so, it's not quite enough - you also need to attach a bank statement. <br />
- Is it itemized? Restaurants are especially notorious for this, but if a place doesn't list a breakdown of what you spent, it doesn't count. If you get one of these, go back and ask for an itemized one. <br />
<br />
<br />
= Step 2: Go to the SSI Internal Site =<br />
<br />
It's at https://internal.stanfordssi.org/. You can log on with your Stanford ID. If all goes well, you should see this page: <br />
<br />
<br />
<br />
If not, go to #operations-website and complain. <br />
<br />
<br />
= Step 3: Click on the reimbursements tab =<br />
<br />
Once you're there, click on New Reimbursement<br />
<br />
<br />
<br />
= Step 4: Fill out the fields and submit! = <br />
<br />
<br />
<br />
<br />
<br />
= Step 5: (Rockets Team Only) Fill Out an Expense Report = <br />
<br />
Some teams require <br />
<br />
<br />
<br />
= Step 6: Track your process and make changes if necessary =<br />
<br />
When you submit your reimbursement, slackbot will message you to let you know! After that, it's up to the financial officers to process it, and slackbot will update you as they do so. If there's something wrong with your reimbursement, they'll also let you know!<br />
<br />
<br />
<br />
= Step 7: Pick up your reimbursement = <br />
<br />
Within a few weeks, you should get an email from ASSU saying that a payment is available! You can go pick up your check from the ASSU office on the first floor of Old Union, behind the Axe and Palm (TAP). <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Operations]]</div>Ceglikbarghttps://ssi-wiki.stanford.edu/w/index.php?title=IREC_2018&diff=3422IREC 20182018-07-10T00:35:59Z<p>Ceglikbarg: recovery updates</p>
<hr />
<div>[[File: IREC2018pose.jpg|400px|thumb|right|frame|The team posing with the fully integrated rocket before launching it at the competition.]]<br />
<br />
IREC 2018 was the second SSI IREC team to participate in the [[Intercollegiate Rocketry Engineering Competition]], placing second in the 30k commercial off-the-shelf motor category. The rocket was named Redshift and featured an avionics bay with a long-distance radio system, a reduced-diameter recovery system, a fiberglass airframe with a carbon fiber fin lay-up, a powered decoupling mechanism, and a software-defined GPS payload.<br />
<br />
=Overview=<br />
<br />
At four inches in diameter and 128 inches long, the rocket design used a minimum diameter airframe to house the Cessaroni Technology N2900 motor. With a wet mass of 58 pounds (dry mass of 27.8 lbs + 1-7 lbs lead shot ballast), the rocket was built to fly to 30,000 feet.<br />
<br />
=Goals and Requirements=<br />
<br />
The goal of the rocket design was to be capable of delivering an 8.8 pound payload to an altitude of 30,000 feet while employing as much student innovation as possible.<br />
<br />
=System Design=<br />
<br />
[[File:IREC2018cad.png|800px|thumb|center|frame|CAD model of the rocket, displaying subsystem layout.]]<br />
<br />
The system went through a few key iterations: at first, a full staging system was considered, then a boosted dart system. After those options turned out to be relatively infeasible due to manpower and expertise issues, as well as the full system redesign that it would have required to conform to smaller airframe diameters, a move was made to a powered decoupling system. <br />
<br />
==Avionics==<br />
<br />
The avionics system consisted of multiple custom printed circuit board assemblies (PCBAs), which used direct board-to-board interconnects to eliminate the use of wires.<br />
<br />
The main boards in the avionics system were:<br />
<br />
* [[Skybass]], an altimeter developed by [[User:Johnldean|John Dean]]<br />
* Motherboard, which was the main interface between all other boards and contained the power distribution, arming systems, and e-match firing pathways.<br />
* Daughtership, a board for mounting the StratoLogger and Raven COTS altimeters.<br />
<br />
==Recovery==<br />
<br />
At apogee, the recovery system deployed a small (32") SRAD drogue parachute for a swift, controlled descent (~70 ft/s) that minimized horizontal drift. The deployment of the drogue was triggered by a CO2 canister deployment mechanism.<br />
<br />
When the rocket reached an apogee of 1,500 feet, the main SRAD chute (90"), which was retained in the recovery bay by the Tender Retention System, was aimed to deploy for a soft landing. Due to compact packing, the main chute did not successfully deploy.<br />
<br />
The recovery bay was selected to have a restricted diameter (2.65"), smaller than that of the rocket airframe (3.9"). This reduced diameter was chosen so that the parachutes would be able to deploy through the restriction in the airframe size caused by the staging ring.<br />
<br />
==Structures==<br />
<br />
The structure of the rocket was constructed using COTS fiberglass tubing, with a student-built carbon-fiber fin lay-up. The structures team attempted to build a custom airframe using the [[X-Winder]] filament winder, but was unable to produce a usable airframe in time using this method.<br />
<br />
==Payload==<br />
<br />
The payload flown on the rocket was a software-define GPS experiment. The goal was to use a COTS software defined radio USB dongle (RTL-SDR), connected to a Raspberry Pi Zero, to capture raw samples from the GPS L1 spectrum. One the rocket is recovered, the raw samples could be downloaded from the Raspberry Pi's SD card and run through tracking algorithms to solve for the rocket's position throughout the flight. The advantages of such a system were specifically for rocketry applications, namely that such a system could be more resistant to losing lock with satellites during high accelerations during flight due to high rates of doppler shift, and that it could provide a way around the GPS COCOM restrictions. The COCOM restrictions limit consumer GPS operation under high velocities and altitudes, which poses an issue for SSI's [[Spaceshot]] project.<br />
<br />
==Staging==<br />
<br />
The staging project was a decoupling mechanism developed for high-speed decoupling. A stepper motor drives a lead screw, on which a nut rides, lifting and lowering a set of lever arms that turn the vertical motion of the nut into horizontal motion. This horizontal motion actuates a set three clamps which affix two metal rings together. These rings are each mounted on one half of the airframe. By backing off the clamps, the rings, and consequently the airframes, are free to separate.<br />
<br />
Issues with the staging system arose when it was near to its completion. The greatest problem was that the stepper motor would have to provide a constant holding torque in order to keep the rocket rigid during the period of time between integration and when separation was required during launch. This application of holding torque required a significant amount of power, and the original battery size resulted in a 20 minute maximum lifetime. Given the lack of adequate space to add enough batteries for a multi-hour lifetime, required in the event of launch delays, and uncertainty about the speed with which the system would drain the battery, it was decided before test launch three that the project should be cut from the final rocket design.<br />
<br />
==Launch Operations==<br />
<br />
Launch Operations handled all launch logistics, including food at the launch, lodging for multi-day launches, checklist organization, pre-launch packing, and transportation.<br />
<br />
=Test Launches=<br />
<br />
==Launch 1==<br />
<br />
TODO: Attach launch stats and a link to the data? <br />
<br />
==Launch 2==<br />
<br />
==Launch 3==<br />
<br />
=The Competition=<br />
<br />
=Documentation=<br />
<br />
* [https://drive.google.com/file/d/1B-4ndZNTqcyyGEI-J9Cef_EhLjfIpOm6/view?usp=sharing Project Technical Report]<br />
* [https://drive.google.com/file/d/1JBI0Ohp3OFxwmPIfnDCpdROMip6v7sKL/view?usp=sharing Poster]<br />
* [https://docs.google.com/drawings/d/1FZ-EO2cmcVqKG4EX4ICNpjDG-7YpyGjMEO3sUQ1J7eA/edit?usp=sharing Fast Facts Card]<br />
* [https://drive.google.com/file/d/11V0K0Fe9YUkwESrhL8_F12ssUUUeGvvl/view?usp=sharing SRADio Podium Presentation Slides]<br />
* [https://drive.google.com/file/d/1nuDhLZtP00u9kX1kKX7aCkomgPamfNCM/view?usp=sharing SRADio Podium Presentation Proposal]<br />
<br />
[[Category:Rockets]]</div>Ceglikbarg