Observation 4387213: NOAA 9 (15427)

Regarding Observation 4387213

And sudo journalctl -f -u satnogs-client.service generate this.

OOOOOOOOOOOOOOOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:08:55 cceres _team satnogs-client[516]: OOOOOOOOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:08:55 cceres_team satnogs-client[516]: satnogsclient.scheduler.tasks - INFO - Post data started
juil. 07 16:09:55 cceres _team satnogs-client[516]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:10:55 cceres _team satnogs-client[516]: OOOOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:11:55 cceres _team satnogs-client[516]: OOOOOOOOOOOOOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:11:55 cceres _team satnogs-client[516]: satnogsclient.scheduler.tasks - INFO - Post data started
juil. 07 16:12:55 cceres _team satnogs-client[516]: OOOOOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:13:55 cceres _team satnogs-client[516]: OOOOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:14:55 cceres _team satnogs-client[516]: OOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:14:55 cceres _team satnogs-client[516]: satnogsclient.scheduler.tasks - INFO - Post data started
juil. 07 16:15:56 cceres _team satnogs-client[516]: Osatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:16:55 cceres _team satnogs-client[516]: OOOOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:17:55 cceres _team satnogs-client[516]: satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:17:55 cceres _team satnogs-client[516]: satnogsclient.scheduler.tasks - INFO - Post data started
juil. 07 16:18:55 cceres _team satnogs-client[516]: Osatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:19:55 cceres _team satnogs-client[516]: Osatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:20:55 cceres _team satnogs-client[516]: Osatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:20:55 cceres _team satnogs-client[516]: satnogsclient.scheduler.tasks - INFO - Post data started
juil. 07 16:21:55 cceres _team satnogs-client[516]: OOsatnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
juil. 07 16:22:23 cceres _team satnogs-client[516]: OOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsOsatnogsclient.observer.observer - INFO - Tracking stopped.

Someone known what is mean ?
cheers!

The O’s mean that you have lost samples, samples that SDR sends but CPU is too busy to edit and it drops them. This is why the audio in the observations has shorter duration than the scheduled one, and is automatically set as failed. This can happen for different reasons, the two most frequent are:

  1. The temperature of CPU/RPi is too high so the software/firmware drops the frequency of CPU ending up with less CPU power
  2. Sample rate is set to a value that CPU can not handle.

In the first case, using a way to cool CPU/RPi could help. In both cases setting a lower sample rate in satnogs-setup could also help.

My station does the same. But looking through all the NOAA-9 observations shows that a lot of stations have this problem. See SatNOGS Network - Observations

Something fishy is going on…