251
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + Line 15:
Line 15: − + Line 28:
Line 28: − + Line 37:
Line 37: + + + + + + + Line 49:
Line 56: − + − +
Changed download links for Git (to the official Git website, so they will probably last longer)
1. Join the SSI slack, and the #satellites and #satellites-software channels. Joining #satellites-systems is optional, if you want to receive info on systems-level discussions.
1. Join the SSI slack, and the #satellites and #satellites-software channels. Joining #satellites-systems is optional, if you want to receive info on systems-level discussions.
2. Come to meetings Thursdays at 6:30 PST.
2. Come to meetings Thursdays at 10:00 am PST.
3. Create a github account (www.github.com) and DM @langston and @moritz (the software co-leads) your username
3. Create a github account (www.github.com) and DM @langston and @moritz (the software co-leads) your username
6. Take a look at the projects below, and see which ones interest you. Message @langston and @moritz which one you want to do, or if you have any questions.
6. Take a look at the projects below, and see which ones interest you. Message @langston and @moritz which one you want to do, or if you have any questions.
7. Setup your workspace (see below). Some tools are only required for certain projects, but some are required for almost everything, like Git and Pycharm.
7. Setup your workspace (see below). Some tools are only required for certain projects, but some are required for almost everything, like Git and Pycharm.
== Onboarding Projects ==
== Onboarding Projects ==
| Experiment with existing code base || The current setup includes the Raspberry Pi as well as our PyCubed flight controller. This task is about looking at our existing software, actually running it on our hardware and playing around with it to get a better sense of what direction you want to take this project. This task will involve lots of close contact with the existing team members, who will help you get set up and explain any open questions. || Medium || Python, CircuitPython, Redis, Microservices, PyCharm, SSH, Terminal || [https://docs.google.com/document/d/1ZWL9MvW_2tVnGzFI_tQNpB-c1mfshqX5QQEkKCeFUYI Specification]
| Experiment with existing code base || The current setup includes the Raspberry Pi as well as our PyCubed flight controller. This task is about looking at our existing software, actually running it on our hardware and playing around with it to get a better sense of what direction you want to take this project. This task will involve lots of close contact with the existing team members, who will help you get set up and explain any open questions. || Medium || Python, CircuitPython, Redis, Microservices, PyCharm, SSH, Terminal || [https://docs.google.com/document/d/1ZWL9MvW_2tVnGzFI_tQNpB-c1mfshqX5QQEkKCeFUYI Specification]
|-
|-
| Connect sensors to flight computer || Our sensors (sun sensors, altitude sensors, etc.) are connected to the board with various hardware mechanisms (like I2C). Some of them need to be configured to be able to use them with our software. You will be writing the code to interact with these sensors. || Medium || Circuitpython, PyCharm, Terminal, Hardware || [https://docs.google.com/document/d/1VB5gb-bnp_UFKpjpO19iZd7fr1wIAzVZ1ZSG1nAKx44 Specification]
| Connect sensors to flight computer || Our sensors (e.g. sun sensor) are connected to the board with various hardware mechanisms (like I2C). Some of them need to be configured to be able to use them with our software. You will be writing the code to interact with these sensors. || Medium || Circuitpython, PyCharm, Terminal, Hardware || [https://docs.google.com/document/d/1VB5gb-bnp_UFKpjpO19iZd7fr1wIAzVZ1ZSG1nAKx44 Specification]
|-
|-
| Define Radio Message-Passing Format || We have a working radio, but we still need to the format of the data we send and the commands we receive. This will also involve researching existing satellites and protocols. || Medium || Circuitpython, PyCharm, Radio, LoRa|| [https://docs.google.com/document/d/1vPeG-qkxTSYBcFwMqxWHhPL9Y8wMy-m9YjU5WEven1A Specification]
| Define Radio Message-Passing Format || We have a working radio, but we still need to the format of the data we send and the commands we receive. This will also involve researching existing satellites and protocols. || Medium || Circuitpython, PyCharm, Radio, LoRa|| [https://docs.google.com/document/d/1vPeG-qkxTSYBcFwMqxWHhPL9Y8wMy-m9YjU5WEven1A Specification]
|}
|}
== Points of Contact ==
These are people you should talk to when you have questions about a part of the software codebase, and also request reviews from when you create a PR.
* PyCubed (i.e. flight_computer/): Langston Nashold (@lgnashold on Github)
* Raspberry Pi (i.e. Payload/): Moritz (@austrian_code_wizard)
* Radio Telemetry on PyCubed: Zach Witzel (@zachwitz)
* Modeling (sequoia-modeling repo): Langston Nashold, Rayan Krishnan (@rayank)
== Workspace Setup ==
== Workspace Setup ==
3. Install either git on the command line, if you are comfortable with the terminal, or github desktop, if you prefer a GUI. These steps focus on using git from the terminal.
3. Install either git on the command line, if you are comfortable with the terminal, or github desktop, if you prefer a GUI. These steps focus on using git from the terminal.
* Instructions to install Git: https://www.atlassian.com/git/tutorials/install-git
* Instructions to install Git: https://git-scm.com/downloads
* Instructions to install the desktop GUI: https://desktop.github.com/
* Instructions to install the desktop GUI: https://git-scm.com/downloads/guis
4. Try checking out the codebase! Go [https://github.com/stanford-ssi/sequoia-software the repository] and press clone. In the terminal, run the following command (if you are using the CLI)
4. Try checking out the codebase! Go [https://github.com/stanford-ssi/sequoia-software the repository] and press clone. In the terminal, run the following command (if you are using the CLI)