Operation

Scheduling your first test observation

Prerequisites

You've set up your SatNOGS client successfully
You've created an account on the Network, created a ground station, and it's showing up as "online"

If you've run into any problems with those steps, check out the Troubleshooting page or ask for help in the community forum, the Matrix room, or on IRC at #satnogs on Libera Chat.

SatNOGS Network

Navigate your ground station page in the Network Environment (user name -> "My Profile" -> click on the name of your ground station).
Select the "Upcoming passes" tab.
Look for a pass with a "schedule" button that isn't greyed out, and click it. Ensure it is a good (high) pass of an operational satellite (check the color bar on the satellite)
In the "New Observation" page that comes up, click the "Calculate" button, then click "Schedule".
You should now see a page for that observation; in the "Waterfall" tab, you should see "Waiting for waterfall".
You can also schedule multiple observations at once for a single satellite via the "Observation new page".

Ground Station

Now SSH to your ground station computer and run these steps:

Follow the satnogs-client logs. This can be done with sudo docker logs satnogs_satnogs-client -ft
At the scheduled time for the observation, you should see the client start the SDR capture:

2026-04-27T14:12:22.668909000Z Found Rafael Micro R820T tuner
2026-04-27T14:12:22.823425000Z [INFO] Opening Generic RTL2832U OEM :: 00000001...
2026-04-27T14:12:23.089070000Z Found Rafael Micro R820T tuner
2026-04-27T14:12:24.756358000Z [INFO] Using format CF32.
2026-04-27T14:12:24.779741000Z Allocating 15 zero-copy buffers

After the observation is over, the client submits the data to the SatNOGS network.

In the SatNOGS Stage Environment, refresh the Observation page. You should now see a waterfall plot for your data.

If that all worked -- congratulations! You've just successfully completed your first SatNOGS observation.

If it didn't work, don't feel bad -- it can take a few attempts before you get it right. Have a look at the Troubleshooting page for tips, and don't forget to contact the community if you need help.

Observations ratings

The main purpose of rating observations is to know if the satellite/transmitter is alive, if it transmits in the listed frequency/ies, and if the TLEs we have are accurate.

Observations are rated automatically by algorithm based on specific criteria that depend on Artifacts. There are 4 different statuses:

Unknown
- "Unknown" status means that algorithm wasn't able to determine automatically how to rate the observation. In this case user needs to give feedback by vetting the artifacts of the observation.
Good
- "Good" status means that algorithm was able to determine the presence of the satellite in one of the artifacts of the observation.
Bad
- "Bad" status means that algorithm wasn't able to determine the presence of the satellite in one of the artifacts of the observation.
Failed
- "Failed" status means that algorithm was able to determine that something went wrong during the observation. There are two cases that fall under this category:
  - Absence of artifacts: In this case there are no uploaded artifacts by the station in a defined time period.
  - Malformed artifacts: In this case there are uploaded artifacts but with malformed or unexpected format, for example Audio artifact duration is different than the scheduled one.

Improving algorithm for automated rating is a work in progress. If you find an inconsistency you can open an issue about it or fix it in SatNOGS Network repository. Meanwhile, a third-party python program (MIT License) for high-accuracy waterfall classification that is readily deployable may be found and used at this GitHub repository.

Vetting artifacts

Currently, artifact vetting is only implemented for Waterfall artifacts.

Waterfall

Status

Once waterfall is posted back in the Network by SatNOGS Client, by default, would be unvetted. User can manually vet waterfall, in waterfall tab, using one of the next choices:

With Signal
- You should vet waterfall as "With Signal" when it is clear from the waterfall that the observed satellite is present. Keyboard Shortcut 'g'.
Without Signal
- You should vet waterfall as "Without Signal" when by examining the waterfall it is obvious that the observed satellite isn't present. Keyboard Shortcut 'b'.
Unknown
- You should leave or vet waterfall as "Unknown" when by examining the waterfall it is not clear if there is or not presence of the observed satellite. Keyboard Shortcut 'u'.

The expected signal in the majority of the cases, should be in the center of the waterfall following a vertical straight line. Exceptions could be satellites that are recently deployed and we don't have accurate TLE or satellites that have a misbehaving transmitter.

If you are unsure about an observation, click the "Discuss" button, near the top right of the observation's page; that will post a link to it on the Observations forum, where you can ask for feedback.

Click the "Discuss" button to post in our web forum. (Note: this will only appear in the SatNOGS Network.)

Examples

Below is a collection of waterfalls with possible results of observations:

With Signal: Satellite is visible (bars-bursts of data in the middle). Note that the tangent-shaped lines are local noise
Without Signal: Typical empty waterfall with no visible signals.
With Signal: Although drifting, satellite is clearly visible around the center.
With Signal: Faint CW signal around center-left. Note you might have to expand image to notice it
With Signal: Clearly visible FM transmission. Note that the swinging lines are terrestrial noise
With Signal: Straight line in the center bottom is a satellite. Note transmission on left bottom is the same satellite on a different frequency
With Signal: Packets clearly seen in the middle of the observation. Note transmission starting middle bottom then moving to left and back to right *is* a space object (satellite). It is not the one we are tracking though (different TLE, thus this type if curve).

You can see more in Taxonomy_of_Observations.

Network Station Status

There are three different properties that define the station status:

If the station is connected with the Network or not (online/offline), this is set in the is_connected field. The field value is calculated automatically after Network checking if there is any recent "new jobs" request from the station.

If the station is available for being used (for scheduling) by the Network or not, this is set in the is_available field. Station owner can set the value of this field by editing the station's, specifically in the Settings section by using the Available checkbox.

If the station is under testing (functionality, performance or configuration), this is set in the testing field. Station owner can set the value of this field by editing the station's, specifically in the Settings section by using the Testing checkbox.

Colour	Status
Green	Station is online, available and not in testing mode
Yellow	Station is online, available and in testing mode
Black	Station is online but unavailable
Red	Station is offline

The values of these three properties define the permissions of the station owners, which can be read in the permissions matrix.

Network Permissions Matrix

User	View and discuss observation	Vet artifacts (currently only waterfall image)	Delete future observation	Schedule observation
Non Authenticated	All	None	None	None
Authenticated	All	None	None	None
Station Owner (Future)	All	None	None	None
Station Owner (Offline)	All	Own (stations or observations)	Own (stations or observations)	None
Station Owner (Online & Unavailable)	All	Own (stations or observations)	Own (stations or observations)	Own (stations)
Station Owner (Online, Available & Testing)	All	Own (stations or observations)	Own (stations or observations)	Own (stations)
Station Owner (Online, Available & Non-testing)	All	All	Own (stations or observations)	All (online & available stations)
Operator	All	All	Own (stations or observations)	All (online & available stations)
Moderator	All	All	All	All (for unavailable stations after an agreement with the station owner)
Admin	All	All	All	All (for unavailable stations after an agreement with the station owner)

Examples:

Authenticated user can view and discuss on all the observations but can not vet artifacts, delete an observation and schedule observation.

Station Owner with at least one online and available station can view and discuss on all observations, can vet artifacts, delete observations on stations that owns or have scheduled and schedule observations to all online an available stations.