Difference between revisions of "Operation"

From SatNOGS
(Network permissions matrix)
m (change docs to reflect new deletion restriction)
Line 1: Line 1:
 
__TOC__
 
__TOC__
  
== Scheduling your first test observation ==
+
==Scheduling your first test observation==
  
 
'''Assumptions:'''
 
'''Assumptions:'''
  
* You've set up your [[Raspberry Pi 3|SatNOGS client successfully]]
+
*You've set up your [[Raspberry Pi 3|SatNOGS client successfully]]
* You've created an account on the [[Network]], created a ground station, and it's showing up as "online"
+
*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 [https://community.libre.space/c/satnogs the community forum], [https://riot.im/app/#/room/#satnogs:matrix.org the Matrix room], or on IRC at #satnogs on Freenode.
 
If you've run into any problems with those steps, check out the [[Troubleshooting]] page or ask for help in [https://community.libre.space/c/satnogs the community forum], [https://riot.im/app/#/room/#satnogs:matrix.org the Matrix room], or on IRC at #satnogs on Freenode.
Line 12: Line 12:
 
'''SatNOGS Network:'''
 
'''SatNOGS Network:'''
  
* Navigate your ground station page in the [https://network.satnogs.org Network Environment] (user name -> "My Profile" -> click on the name of your ground station).
+
*Navigate your ground station page in the [https://network.satnogs.org Network Environment] (user name -> "My Profile" -> click on the name of your ground station).
* Select the "Upcoming passes" tab.
+
*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)
+
*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".
+
*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 should now see a page for that observation; in the "Waterfall" tab, you should see "Waiting for waterfall".
  
 
'''Ground Station'''
 
'''Ground Station'''
Line 22: Line 22:
 
Now SSH to your ground station computer and run these steps:
 
Now SSH to your ground station computer and run these steps:
  
* Follow the satnogs-client logs. Depending on your setup, this might be done with <code>journalctl -f -u satnogs-client.service</code>, or <code>tail -F /var/log/supervisor/satnogs.log</code>
+
*Follow the satnogs-client logs. Depending on your setup, this might be done with <code>journalctl -f -u satnogs-client.service</code>, or <code>tail -F /var/log/supervisor/satnogs.log</code>
* Before the observation is scheduled to start, you should see your client wake up once per minute to check for new jobs:
+
*Before the observation is scheduled to start, you should see your client wake up once per minute to check for new jobs:
  
 
<pre>
 
<pre>
Line 37: Line 37:
 
</pre>
 
</pre>
  
* At the scheduled time for the observation, you should see the client kick off the observation:
+
*At the scheduled time for the observation, you should see the client kick off the observation:
  
 
<pre>
 
<pre>
Line 55: Line 55:
 
</pre>
 
</pre>
  
* After the observation is over, you should see the client submit the data to the SatNOGS network
+
*After the observation is over, you should see the client submit 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.
 
In the SatNOGS Stage Environment, refresh the Observation page.  You should now see a waterfall plot for your data.
Line 63: Line 63:
 
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.
 
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.
  
== Rating observations ==
+
==Rating observations==
  
 
Once your observation results are posted back in the Network by your satnogs-client, you should go to Network to rate your observations. Any orange marked observations need vetting by users.
 
Once your observation results are posted back in the Network by your satnogs-client, you should go to Network to rate your observations. Any orange marked observations need vetting by users.
Line 73: Line 73:
 
Categories of observations:
 
Categories of observations:
  
* '''Good'''
+
*'''Good'''
** You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
+
**You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
* '''Bad'''
+
*'''Bad'''
** You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.
+
**You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.
* '''Failed'''
+
*'''Failed'''
** You should mark observations as "Failed" when the station failed entirely: the waterfall and/or audio is empty or not present, or there's too much noise.
+
**You should mark observations as "Failed" when the station failed entirely: the waterfall and/or audio is empty or not present, or there's too much noise.
  
  
Line 94: Line 94:
 
[[File:Observation_with_discuss_button_highlighted.png|thumb|frame|Click the "Discuss" button to post in our web forum. (Note: this will only appear in the SatNOGS network.)]]
 
[[File:Observation_with_discuss_button_highlighted.png|thumb|frame|Click the "Discuss" button to post in our web forum. (Note: this will only appear in the SatNOGS network.)]]
  
=== Discuss ===
+
===Discuss===
 
If you're still 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 [https://community.libre.space/c/observations the Observations forum], where you can ask for feedback.
 
If you're still 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 [https://community.libre.space/c/observations the Observations forum], where you can ask for feedback.
  
== Scheduling observations in standalone mode ==
+
==Scheduling observations in standalone mode==
  
=== Scheduling a NOAA observation in standalone mode ===
+
===Scheduling a NOAA observation in standalone mode===
  
 
Instructions for scheduling a NOAA observation, including decoding of the APT images, can be found [http://ixion.csd.uoc.gr/vardakis/index.php/satnogs-noaa-apt-decoder-walkthrough/ here].
 
Instructions for scheduling a NOAA observation, including decoding of the APT images, can be found [http://ixion.csd.uoc.gr/vardakis/index.php/satnogs-noaa-apt-decoder-walkthrough/ here].
  
  
 
+
==Network permissions matrix==
== Network permissions matrix ==
 
  
 
{| class="wikitable" style="text-align:center"
 
{| class="wikitable" style="text-align:center"
 
|-
 
|-
! scope="col" | User
+
! scope="col" |User
! scope="col" | View and discuss observation
+
! scope="col" |View and discuss observation
! scope="col" | Vet observation
+
! scope="col" |Vet observation
! scope="col" | Delete observation
+
! scope="col" |Delete future observation
! scope="col" | Schedule observation
+
! scope="col" |Schedule observation
 
|-
 
|-
 
|Non Authenticated
 
|Non Authenticated
Line 121: Line 120:
 
|None
 
|None
 
|-
 
|-
| Authenticated
+
|Authenticated
| All
+
|All
| None
+
|None
| None
+
|None
 
|None
 
|None
 
|-
 
|-
Line 145: Line 144:
 
|Own(stations)
 
|Own(stations)
 
|-
 
|-
| Station Owner (Online)
+
|Station Owner (Online)
| All
+
|All
| All
+
|All
| Own(stations or observations)
+
|Own(stations or observations)
| All(online stations)
+
|All(online stations)
 
|-
 
|-
| Moderator
+
|Moderator
| All
+
|All
| All
+
|All
| All
+
|All
| All
+
|All
 
|-
 
|-
| Admin
+
|Admin
| All
+
|All
| All
+
|All
| All
+
|All
| All
+
|All
 
|}
 
|}
 
Examples:
 
Examples:
* Authenticated user can view and discuss on all the observation. User can not vet or delete an observation. User can not schedule observation in any station.
 
  
* Station Owner with at least one online station can view and discuss on all observations. Online station owner can vet or delete observations on stations that owns. Online station owner can vet or delete observation that has scheduled. Online station owner can schedule observations on all online stations.
+
*Authenticated user can view and discuss on all the observation. User can not vet or delete an observation. User can not schedule observation in any station.
 +
 
 +
*Station Owner with at least one online station can view and discuss on all observations. Online station owner can vet or delete observations on stations that owns. Online station owner can vet or delete observation that has scheduled. Online station owner can schedule observations on all online stations.

Revision as of 23:57, 10 July 2019

Scheduling your first test observation

Assumptions:

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 Freenode.

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".

Ground Station

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

  • Follow the satnogs-client logs. Depending on your setup, this might be done with journalctl -f -u satnogs-client.service, or tail -F /var/log/supervisor/satnogs.log
  • Before the observation is scheduled to start, you should see your client wake up once per minute to check for new jobs:
Oct 02 00:16:02 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:02,477 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 02 00:16:02 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:02,479 - satnogsclient - DEBUG - Sending message: [{"origin": "network", "transmitter": "uXJ8NQNcH8b9osRc
Oct 02 00:16:02 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:02,488 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2
Oct 02 00:16:59 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:59,615 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next r
Oct 02 00:16:59 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:59,661 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next 
Oct 02 00:16:59 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:59,668 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 
Oct 02 00:17:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:17:00,906 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 02 00:17:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:17:00,908 - satnogsclient - DEBUG - Sending message: [{"origin": "network", "transmitter": "uXJ8NQNcH8b9osRc
Oct 02 00:17:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:17:00,912 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2
  • At the scheduled time for the observation, you should see the client kick off the observation:
Oct 02 00:18:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:00,774 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 02 00:18:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:00,776 - satnogsclient - DEBUG - Sending message: [{"origin": "network", "transmitter": "uXJ8NQNcH8b9osRc
Oct 02 00:18:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:00,781 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,022 - apscheduler.executors.default - INFO - Running job "spawn_observer (trigger: date[2017-10-02 00:
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,082 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:4533
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,109 - satnogsclient - DEBUG - Sending message: p
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,110 - satnogsclient - DEBUG - Received message: 0.000000
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 0.000000
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,111 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:4532
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,115 - satnogsclient - DEBUG - Sending message: P 188.276951189 -0.0155264223734
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,119 - satnogsclient - DEBUG - Received message: RPRT -1
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,143 - satnogsclient - DEBUG - Sending message: F 436038107
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,144 - satnogsclient - DEBUG - Received message: RPRT 0
  • After the observation is over, you should see the client submit 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.

Rating observations

Once your observation results are posted back in the Network by your satnogs-client, you should go to Network to rate your observations. Any orange marked observations need vetting by users.

Idea.png
The main purpose of validating 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.
Idea.png
The functionality may change in the future, but for now even a faint sign on the waterfall is enough to make it valid.
Orange need your rating!

Categories of observations:

  • Good
    • You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
  • Bad
    • You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.
  • Failed
    • You should mark observations as "Failed" when the station failed entirely: the waterfall and/or audio is empty or not present, or there's too much noise.


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

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

Discuss

If you're still 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.

Scheduling observations in standalone mode

Scheduling a NOAA observation in standalone mode

Instructions for scheduling a NOAA observation, including decoding of the APT images, can be found here.


Network permissions matrix

User View and discuss observation Vet observation 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 (Testing) All Own(stations or observations) Own(stations or observations) Own(stations)
Station Owner (Online) All All Own(stations or observations) All(online stations)
Moderator All All All All
Admin All All All All

Examples:

  • Authenticated user can view and discuss on all the observation. User can not vet or delete an observation. User can not schedule observation in any station.
  • Station Owner with at least one online station can view and discuss on all observations. Online station owner can vet or delete observations on stations that owns. Online station owner can vet or delete observation that has scheduled. Online station owner can schedule observations on all online stations.