Any development into any facility or API that can be used to write our own scripts to perform the schedulling? It doesn’t really need to be fancy or elaborate, just some way to define the satellite, elevation limits perhaps and a max of 2 days into the future. Then We can write our scripts to perform the schedulling without the need to resort to a time consuming manual task. Perhaps just limited to our own station.
I can gladly contribute either to write code or to test code.
The execution seems to work successfully but it didn’t schedule anything in the system even if it says that 218 passes were selected within the windows stated based on the station capabilities.
Running the tool with -l INFO a comprehensive list of the actions are listed, but a suggestive message does appear (see log excerpt below), despite it no additional error message is given.
I did use as -u the username I use to login into SatNOGS and as -p the password I use for the same.
I didn’t include any priority file for the run.
Thank you in advance for any help.
73 de Pedro LU7DID
2019-04-18 21:13:57,147 - root - INFO - Requesting information for ground station 499
2019-04-18 21:13:58,364 - root - INFO - Ground station information retrieved!
2019-04-18 21:13:58,407 - root - INFO - Finding all passes for 133 satellites:
100%|██████████| 133/133 [01:20<00:00, 1.67it/s]
2019-04-18 21:15:18,743 - root - INFO - Requesting scheduled passes for ground station 499
2019-04-18 21:15:21,262 - root - INFO - Scheduled passes for ground station 499 retrieved!
2019-04-18 21:15:21,272 - root - INFO - Found 57 scheduled passes between 2019-04-19 00:13:57 and 2019-04-22 00:13:57 on ground station 499
2019-04-18 21:15:25,184 - root - INFO - 218 passes scheduled out of 1500, 147069 s out of 259128 s at 56.755% efficiency
2019-04-18 21:15:25,186 - root - INFO - GS | Sch | NORAD | Start time | End time | El | Priority | Transmitter UUID | Satellite name
2019-04-18 21:15:25,188 - root - INFO - 499 | 1 | 43590 | 2019-04-19T00:26:09 | 2019-04-19T00:31:51 | 23 | 1.000000 | vcSqoKHZe6KYHoKqhTiytH |
… [many satellites are listed here] …
2019-04-18 21:15:25,268 - root - INFO - 499 | | 42759 | 2019-04-22T00:12:33 | 2019-04-22T00:24:56 | 30 | 0.313333 | qPbeGpVSxXnJ4YMfBRfG92 | ZHUHAI-1 02 (CAS-4B) 2019-04-18 21:15:26,682 - root - INFO - Authentication failed
2019-04-18 21:15:26,684 - root - INFO - Checking and scheduling passes as needed.
100%|██████████| 218/218 [04:04<00:00, 1.46s/it]
2019-04-18 21:19:31,196 - root - INFO - All passes are scheduled. Exiting!
The auto-scheduler uses an old authentication method for the SatNOGS network, not the AUTH0 approach that is used across all SatNOGS platforms (network, forums, db etc). If you have your old login information, use that.
If you are a relatively new user you would not have an old login information, which would mean we would have get our act together and fix the auto-scheduler code (I’m sorry we haven’t gotten around to that yet).
Is there any workaround with the present code enabling me to execute it with the current Id/password? Furthermore, is there a way I can use to get an old userid/password combination?
It’s also advisable if the code is modified that if it found a severe execution condition to end with some form of exception or failure condition, otherwise it’s ending normally but the actual result is abnormal, only with a higher log level provide some clues on the subject.