Difference between revisions of "SatNOGS Network"

From SatNOGS Wiki
(Development: Fix/add links)
(Migrate some content from dev page, including details needed to create ground station)
Line 8: Line 8:
 
* Head to https://network.satnogs.org/accounts/signup/ to create a new account
 
* Head to https://network.satnogs.org/accounts/signup/ to create a new account
 
* Verify your email
 
* Verify your email
 +
 +
Now you're ready to create a ground station!
 +
 +
===Creating a ground station===
 +
 
* On your user page, click on `Add Ground Station`
 
* On your user page, click on `Add Ground Station`
* Fill out all the information
+
* Fill out all the information.  You'll need to provide some essential information about your ground station:
* Head to your client and complete the setup of it using the information you supplied on the Network, plus you API key and the ID you got assigned.
+
 
 +
<ul>
 +
<li>Where is the station?  We'll need the height above ground level and [https://en.wikipedia.org/wiki/Maidenhead_Locator_System maidenhead locator]</li>
 +
<li>Is the antenna static, or does it have a rotator?</li>
 +
<li>What type of antennas does the station have?</li>
 +
</ul>
 +
 
 +
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 complete the setup of it 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:
 +
<p>[[File:Dev_ground_station.PNG|center|800px]]</p>
 +
 
 +
===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 [[Operation|scheduling your first observation]].
  
 
Your station should now appear on the [https://network.satnogs.org/stations/ Ground Stations list] marked as yellow "Testing".
 
Your station should now appear on the [https://network.satnogs.org/stations/ Ground Stations list] marked as yellow "Testing".
  
 
==Moving out of testing==
 
==Moving out of testing==
The production environment 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 it line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.
+
 
 +
The production environment 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 you should go ahead and edit the station, remove the testing flag and 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. If you're ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.
+
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. If your ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.
  
==What is next==
+
==What's next?==
  
 
* Keep your station busy! Schedule observations or reach out to the community for scheduling help.
 
* Keep your station busy! Schedule observations or reach out to the community for scheduling help.
Line 28: Line 50:
  
 
==Development==
 
==Development==
 +
 
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]]!

Revision as of 04:02, 13 March 2018

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

Purpose

The production environment is the default place to get started on creating and connecting a ground station client. All SatNOGS operations (scheduling and reviewing satellite observations) happen in the production instance of our Network.

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 the setup of it 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 production environment 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!

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. If your ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.

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!