Difference between revisions of "SatNOGS Operations Manual"
(wip) (Tag: Visual edit) |
(Tag: Visual edit) |
||
| Line 1: | Line 1: | ||
{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}} | {{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}} | ||
| − | === Requirements === | + | ===Requirements=== |
his manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations! | his manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations! | ||
| − | === Adding a new Satellite === | + | ===Adding a new Satellite=== |
| − | ==== 0. Should we add it? ==== | + | ====0. Should we add it?==== |
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible. | In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible. | ||
| − | 1. Find new satellites | + | ==== 1. Find new satellites ==== |
| + | Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches: | ||
| − | + | * https://space.skyrocket.de/doc_chr/lau2020.htm | |
| + | * https://spaceflightnow.com/launch-schedule/ | ||
| + | * https://www.space.com/32286-space-calendar.html | ||
| + | |||
| + | Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc) | ||
| + | <br /> | ||
| + | |||
| + | ==== 2. File the issues in satnogs-ops ==== | ||
| + | Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed. Some websites and online resources for digging up information (if not already provided by the mission teams): | ||
| + | |||
| + | * http://nanosats.eu/ | ||
| + | * http://www.amsatuk.me.uk/iaru/index.php | ||
| + | * https://fcc.report/ | ||
| + | * https://apps.fcc.gov/oetcf/els/index.cfm | ||
| + | * Search Google and Twitter for mission posted information! | ||
| + | |||
| + | ==== 3. Add satellite in DB ==== | ||
| + | <br /> | ||
| + | |||
| + | ==== 4. Add and approve transmitters in DB ==== | ||
| + | <br /> | ||
| + | |||
| + | ==== 5. Update provisional TLEs (~12 hours before launch) ==== | ||
| + | <br /> | ||
| + | |||
| + | ==== 6. Sync SatNOGS Network ==== | ||
| + | <br /> | ||
| + | |||
| + | ==== 7. Schedule LEOP ==== | ||
| + | <br /> | ||
| + | |||
| + | ==== 8. Review results ==== | ||
| + | |||
| + | |||
| + | |||
| + | <br /> | ||
Revision as of 16:32, 19 June 2020
Contents
Requirements
his manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!
Adding a new Satellite
0. Should we add it?
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.
1. Find new satellites
Besides the missions that will actively reach out to us by filling issues in satnogs-ops repo, we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:
- https://space.skyrocket.de/doc_chr/lau2020.htm
- https://spaceflightnow.com/launch-schedule/
- https://www.space.com/32286-space-calendar.html
Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)
2. File the issues in satnogs-ops
Once you have the information it is needed then navigate to satnogs-ops repo and open new issues containing all the information needed. Some websites and online resources for digging up information (if not already provided by the mission teams):
- http://nanosats.eu/
- http://www.amsatuk.me.uk/iaru/index.php
- https://fcc.report/
- https://apps.fcc.gov/oetcf/els/index.cfm
- Search Google and Twitter for mission posted information!
3. Add satellite in DB
4. Add and approve transmitters in DB
5. Update provisional TLEs (~12 hours before launch)
6. Sync SatNOGS Network
7. Schedule LEOP
8. Review results
