Satnogs Scheduler non_field_errors

SatNOGS Software
1

I’ve been trying to get the auto scheduler running on my ground station and I am getting permission errors. Running the command from the crontab example in a shell:

sudo ~/env/bin/python ~/env/bin/schedule_single_station.py -s 3132 -d 1.2 -P ~/env/bin/priorities_3132.txt -f -z

I get this result:

2023-07-15 22:44:20,670 - auto_scheduler.satnogs_client - INFO - Requesting information for ground station 3132
2023-07-15 22:44:21,266 - auto_scheduler.satnogs_client - INFO - Ground station information retrieved!
2023-07-15 22:44:21,823 - root - INFO - Finding all passes for 840 satellites:
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 840/840 [00:32<00:00, 25.67it/s]
2023-07-15 22:44:54,574 - auto_scheduler.satnogs_client - INFO - Requesting scheduled passes for ground station 3132
2023-07-15 22:44:55,543 - auto_scheduler.satnogs_client - INFO - Scheduled passes for ground station 3132 retrieved!
2023-07-15 22:44:55,558 - root - INFO - Found 0 scheduled passes between 2023-07-15 22:54:20 and 2023-07-16 00:06:20 on ground station 3132
2023-07-15 22:44:55,560 - root - INFO - 2 passes selected out of 71, 1463 s out of 2733 s at 53.526% efficiency
2023-07-15 22:44:55,561 - root - INFO - GS | Sch | NORAD | Start time | End time | Duration | El | Priority | Transmitter UUID | Mode | Satellite name
2023-07-15 22:44:55,562 - root - INFO - 3132 | N | 56745 | 2023-07-15T23:08:18 | 2023-07-15T23:19:52 | 0:11:34 | 25 | 1.000000 | fDywUVLPJc2FMkFoYv7EeV | MSK | {‘name’: ‘SNIPE 2’}
2023-07-15 22:44:55,562 - root - INFO - 3132 | N | 40014 | 2023-07-15T23:41:02 | 2023-07-15T23:53:50 | 0:12:48 | 68 | 1.000000 | NSXo8tGxmxpTUMsmSH34FF | FSK | {‘name’: ‘BUGSAT-1 (TITA)’}
2023-07-15 22:44:55,563 - root - INFO - Scheduling all unscheduled passes listed above.
2023-07-15 22:44:56,522 - auto_scheduler.satnogs_client - ERROR - Failed to batch-schedule the passes. Reason: {‘non_field_errors’: [‘No permission to schedule observations on station: 3132’]}
2023-07-15 22:44:56,522 - auto_scheduler.satnogs_client - ERROR - Fall-back to single-pass scheduling.
2023-07-15 22:44:57,244 - auto_scheduler.satnogs_client - ERROR - Failed to schedule the pass at 2023-07-15 23:19:52. Reason: {‘non_field_errors’: [‘No permission to schedule observations on station: 3132’]}
2023-07-15 22:44:58,020 - root - INFO - Done.

Any ideas on what I can check to resolve the “No Permission” errors?

George

2

The error message could be more specific, but I think the reason for the failure is that Snipe-2 is recorded as misusing their frequency. See SatNOGS DB - SNIPE B

More info: No permission to schedule observation on satellites with Frequency Misuse

1 Like
3

Looks like a older version ?
The current version has another column in the table (freq misuse), example from my station:

4 passes selected out of 11, 1548 s out of 3572 s at 43.339% efficiency
  GS | Sch | NORAD | Start time          | End time            | Duration |  El | Priority | Transmitter UUID       | Mode       | Freq   | Satellite name
                                                                                                                                 | misuse | 
1888 | Y   | 43485 | 2023-07-16T10:26:04 | 2023-07-16T10:32:11 | 0:06:07 |  81 | 1.000000 | srRymFH6KNvisXgchfnf77 |            | N      | Luojia-1
1888 | Y   | 40380 | 2023-07-16T10:35:04 | 2023-07-16T10:40:10 | 0:05:06 |  80 | 1.000000 | eJs9KnfVMdL5At8igBjqLS |            | N      | EXOCUBE
1888 | N   | 52175 | 2023-07-16T10:47:33 | 2023-07-16T10:52:01 | 0:04:28 |  85 | 0.217222 | YeTsm29mcydZCXFVWDAZ4M | GFSK       | N      | BDSat
1888 | Y   | 99084 | 2023-07-16T11:15:29 | 2023-07-16T11:25:36 | 0:10:07 |  12 | 1.000000 | 4T8D7kLMyV8rF5r4rpBnfd |            | Y      | SATURN
Scheduling all unscheduled passes listed above.

doing a git pull --ff-only perhaps ?

2 Likes
4

Thank you for the informative replies. That makes sense and after letting it run overnight it scheduled observations on my station successfully. Also I just followed the instructions for installation on the repository page without checking for a new version. I will update that today.

Thanks again for the help!

George

2 Likes
5

When I check --version I get 0.2, I believe that is the current version. Not sure why it didn’t show the misuse column.

How did you paste that text in your reply so it shows the proper formatting with the horizontal scroll bar?

1 Like
6

The 0.2 tag is quite old, we made a bunch of improvements since then, but it’s still in the readme… updating to latest is what I would recommend. Also a bit funny that the readme of tag 0.2 does not specify version in the clone, but the master branch does point to 0.2 :stuck_out_tongue:
Depending on how it was cloned, may need git checkout master and then pulling.

The format is using backticks, available with Ctrl-E.

2 Likes