Difference between revisions of "SatNOGS Network"

From SatNOGS
(Remove production wording)
m (Librespace1 moved page Network to SatNOGS Network: Actually, full name is better for main websites...)
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Scope==
+
== Introduction ==
  
 
SatNOGS Network website is where the scheduling, reviewing and operations happen for the SatNOGS project. The instance can be found in [https://network.satnogs.org network.satnogs.org]
 
SatNOGS Network website is where the scheduling, reviewing and operations happen for the SatNOGS project. The instance can be found in [https://network.satnogs.org network.satnogs.org]
 +
 +
[[File:Satnogs-network-cap.png|800px|SatNOGS Network Screen capture]]
  
 
==Getting started==
 
==Getting started==
Line 23: Line 25:
 
All this information is then saved by the network, and used to determine which satellites can be received by your station. This will help other users to schedule passes on your ground station, but it can also help you improve your station. For example, perhaps you would like to receive the latest [https://en.wikipedia.org/wiki/Automatic_picture_transmission NOAA APT weather images] which are VHF transmissions. You could schedule an observation with your ground station and multiple other ground stations in order to determine if your set up has comparable performance. Without the station detail, this would not be possible.  
 
All this information is then saved by the network, and used to determine which satellites can be received by your station. This will help other users to schedule passes on your ground station, but it can also help you improve your station. For example, perhaps you would like to receive the latest [https://en.wikipedia.org/wiki/Automatic_picture_transmission NOAA APT weather images] which are VHF transmissions. You could schedule an observation with your ground station and multiple other ground stations in order to determine if your set up has comparable performance. Without the station detail, this would not be possible.  
  
* Finally, head to your client and [[Raspberry_Pi_3#Setup|complete its setup]], using the information you supplied on the Network, plus the API key and the ID you were assigned.
+
* Finally, head to your client and [[Raspberry_Pi#Setup|complete its setup]], using the information you supplied on the Network, plus the API key and the ID you were assigned.
  
 
The image below shows the web page for a typical ground station:
 
The image below shows the web page for a typical ground station:
Line 38: Line 40:
 
The Network needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and in line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.
 
The Network needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and in line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.
  
Once you feel that your station has been performing well for a period of time under the "Testing" flag then you should go ahead and edit the station, remove the testing flag and announce the availability of a new station in our community channels!
+
Once you feel that your station has been performing well for a period of time under the "Testing" flag then remove the flag. Select the ground station press edit and remove the testing flag under settings. Then announce the availability of a new station in our community channels!
  
 
The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable.
 
The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable.
Line 51: Line 53:
  
 
The SatNOGS Network application is a project by itself with constant development. We  test the Network application in our [[Development Environment|development environment]], and [[Software contribution|always welcome python/javascript developers to help us]]!
 
The SatNOGS Network application is a project by itself with constant development. We  test the Network application in our [[Development Environment|development environment]], and [[Software contribution|always welcome python/javascript developers to help us]]!
 +
 +
[[Category:Infrastructure]]
 +
[[Category:Hardware]]
 +
[[Category:Software]]
 +
[[Category:Build]]
 +
[[Category:Operate]]
 +
[[Category:Develop]]

Latest revision as of 23:11, 20 January 2020

Introduction

SatNOGS Network website is where the scheduling, reviewing and operations happen for the SatNOGS project. The instance can be found in network.satnogs.org

SatNOGS Network Screen capture

Getting started

Now you're ready to create a ground station!

Creating a ground station

  • On your user page, click on "Add Ground Station"
  • Fill out all the information. You'll need to provide some essential information about your ground station:
  • Where is the station? We'll need the height above ground level and maidenhead locator
  • Is the antenna static, or does it have a rotator?
  • What type of antennas does the station have?

All this information is then saved by the network, and used to determine which satellites can be received by your station. This will help other users to schedule passes on your ground station, but it can also help you improve your station. For example, perhaps you would like to receive the latest NOAA APT weather images which are VHF transmissions. You could schedule an observation with your ground station and multiple other ground stations in order to determine if your set up has comparable performance. Without the station detail, this would not be possible.

  • Finally, head to your client and complete its setup, using the information you supplied on the Network, plus the API key and the ID you were assigned.

The image below shows the web page for a typical ground station:

Dev ground station.PNG

Observing a pass

The central point of the system is the ability to schedule a pass. You'll find all the information about scheduling and how to assess the quality of the observation as part of scheduling your first observation.

Your station should now appear on the Ground Stations list marked as yellow "Testing".

Moving out of testing

The Network needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and in line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.

Once you feel that your station has been performing well for a period of time under the "Testing" flag then remove the flag. Select the ground station press edit and remove the testing flag under settings. Then announce the availability of a new station in our community channels!

The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable.

What's next?

  • Keep your station busy! Schedule observations or reach out to the community for scheduling help.
  • Keep reviewing your ground station performance.
  • Reach out to others in community for help on any issue.

Development

The SatNOGS Network application is a project by itself with constant development. We test the Network application in our development environment, and always welcome python/javascript developers to help us!