Remarks on auto-scheduler priorities text file

Hi,
I’m setting up the autoscheduler on my SATNOGS station and would like to know if there is a way to insert remarks on autoscheduler’s priorities text file in order to know to what satellite and transmitter each line refers to?, this would be very handy when adding and removing satellites and transmitters on the file.
Thanks & Regards de Xe3adc, Abraham.

1 Like

I just tried the following and it doesn’t give an error, give it a try and share your experience.

32789 1.0 RGrApAMv8gLbweTgXRhZGa # Delfi-C3
39428 1.5 aRboijNaKGSDZu3ZVyTFX2
39444 1.5 Pt4MFHSC8UFHu3aTQTLz9K
42017 1.5 msnC2ijNNoQ2ECKunbpAkm
43137 1.0 3rLGJWqj3XZ6Z8vADCRwiW
43770 1.0 bxfwWfvm9UaXRvVfyhcjt6
43803 0.4 ocoEf6MEZtiZgvEWSWsqtY
47311 0.4 kFjfKquGRZ4PVGp93siPgq
47950 1.0 gQfXoAeK5xak5zNaQCpGJo

Hello,
Thanks for your response, I tried the following priorities file:

40014 1.0 NSXo8tGxmxpTUMsmSH34FF # bugsat
40379 1.0 PMnr7eXunTq4zsS3WnbqxV # grifex
30776 1.0 rjz4x8XfpQCvmM8qgArr9Z # falconsat3
44103 1.0 TGP8nqLVquNWuYYytpbQ7A # aistechsat3
41460 1.0 HhPiuNj3whyDNCFCYBDykV # aausat4
41460 1.0 JLNq6FzBfaCvK7H5neMKiC # aausat4
99943 1.0 3cRwEsgyxi2ju3keP9Yfb2 # cubesail1
47952 1.0 etxVG5sC2U68VFR3iSNehr # cubesx-hse
44352 1.0 KvhPyZKYATt2gso5y3mPPU # armadillo 19.2k
43855 1.0 ovpmeNWQar69dTqXcZ4nMi # chompp afsk1200
40968 1.0 9KeB2ZXuBaUMjcK6TtvUdh # bisonsat fsk 9.6
42790 1.0 AX8jbngoyxRsg58hKJxo42 # vzlusat afsk 4.8
41168 1.0 XsKJgznKU3tFxKKVsNRXGY # athenoxat gmsk2.4

Although there were no errors during the process there were no additional observation scheduled on my satnogs station:

2021-11-06 18:21:01,082 - root - INFO - Found 3 scheduled passes between 2021-11-07 00:27:45 and 2021-11-07 12:27:45 on ground station 1650
2021-11-06 18:21:01,083 - root - INFO - 3 passes selected out of 399, 783 s out of 11243 s at 6.964% efficiency
2021-11-06 18:21:01,083 - root - INFO - GS   | Sch | NORAD | Start time          | End time            | Duration |  El | Priority | Transmitter UUID       | Mode       | Satellite name 
2021-11-06 18:21:01,083 - root - INFO - 1650 |   Y | 44365 | 2021-11-07T01:29:37 | 2021-11-07T01:33:37 | 0:04:00  |  40 | 1.000000 | BPCnonMHkQ2hdnPeN48g3L |            | 
2021-11-06 18:21:01,083 - root - INFO - 1650 |   Y | 47924 | 2021-11-07T03:17:52 | 2021-11-07T03:22:00 | 0:04:08  |  86 | 1.000000 | ad9SYnYhRYHBKjFKPBAaEU |            | 
2021-11-06 18:21:01,083 - root - INFO - 1650 |   Y | 47701 | 2021-11-07T04:32:05 | 2021-11-07T04:37:00 | 0:04:55  |  90 | 1.000000 | Tk3gzpqQcC5U3KhEyku9dy |            | 
2021-11-06 18:21:01,084 - root - INFO - Done.

Afterwards I ran the auto-scheduler with the same file with no remarks and same parameters obtaining 12 additional observations scheduled as follows:

2021-11-06 18:21:33,343 - root - INFO - 15 passes selected out of 402, 3956 s out of 35545 s at 11.131% efficiency
2021-11-06 18:21:33,343 - root - INFO - GS   | Sch | NORAD | Start time          | End time            | Duration |  El | Priority | Transmitter UUID       | Mode       | Satellite name 
2021-11-06 18:21:33,344 - root - INFO - 1650 |   Y | 44365 | 2021-11-07T01:29:37 | 2021-11-07T01:33:37 | 0:04:00  |  40 | 1.000000 | BPCnonMHkQ2hdnPeN48g3L |            | 
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 41168 | 2021-11-07T02:23:23 | 2021-11-07T02:27:56 | 0:04:33  |  39 | 1.000000 | XsKJgznKU3tFxKKVsNRXGY | GMSK       | ATHENOXAT 1
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 42790 | 2021-11-07T02:41:43 | 2021-11-07T02:46:21 | 0:04:38  |  70 | 1.000000 | AX8jbngoyxRsg58hKJxo42 | AFSK       | VZLUSAT-1
2021-11-06 18:21:33,344 - root - INFO - 1650 |   Y | 47924 | 2021-11-07T03:17:52 | 2021-11-07T03:22:00 | 0:04:08  |  86 | 1.000000 | ad9SYnYhRYHBKjFKPBAaEU |            | 
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 44352 | 2021-11-07T03:36:04 | 2021-11-07T03:40:20 | 0:04:15  |  75 | 1.000000 | KvhPyZKYATt2gso5y3mPPU | GFSK       | Armadillo
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 44103 | 2021-11-07T04:04:34 | 2021-11-07T04:07:45 | 0:03:11  |  27 | 1.000000 | TGP8nqLVquNWuYYytpbQ7A | FSK        | AISTechSat 3
2021-11-06 18:21:33,344 - root - INFO - 1650 |   Y | 47701 | 2021-11-07T04:32:05 | 2021-11-07T04:37:00 | 0:04:55  |  90 | 1.000000 | Tk3gzpqQcC5U3KhEyku9dy |            | 
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 47952 | 2021-11-07T04:56:18 | 2021-11-07T05:01:00 | 0:04:42  |  45 | 1.000000 | etxVG5sC2U68VFR3iSNehr | GMSK       | CubeSX-HSE
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 40968 | 2021-11-07T05:17:44 | 2021-11-07T05:23:50 | 0:06:05  |  44 | 1.000000 | 9KeB2ZXuBaUMjcK6TtvUdh | FSK        | BISONSAT
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 41168 | 2021-11-07T05:45:30 | 2021-11-07T05:50:28 | 0:04:58  |  48 | 1.000000 | XsKJgznKU3tFxKKVsNRXGY | GMSK       | ATHENOXAT 1
2021-11-06 18:21:33,344 - root - INFO - 1650 |   N | 30776 | 2021-11-07T06:02:53 | 2021-11-07T06:06:48 | 0:03:54  |  38 | 1.000000 | rjz4x8XfpQCvmM8qgArr9Z | FSK        | FALCONSAT-3
2021-11-06 18:21:33,345 - root - INFO - 1650 |   N | 41168 | 2021-11-07T07:27:18 | 2021-11-07T07:30:55 | 0:03:37  |  28 | 1.000000 | XsKJgznKU3tFxKKVsNRXGY | GMSK       | ATHENOXAT 1
2021-11-06 18:21:33,345 - root - INFO - 1650 |   N | 41460 | 2021-11-07T09:54:57 | 2021-11-07T09:59:37 | 0:04:39  |  44 | 1.000000 | JLNq6FzBfaCvK7H5neMKiC | GMSK       | AAUSAT 4
2021-11-06 18:21:33,345 - root - INFO - 1650 |   N | 45261 | 2021-11-07T10:31:40 | 2021-11-07T10:34:53 | 0:03:12  |  69 | 1.000000 | MwBGcd7pTZQjn7YSFTLj87 | FSK        | AztechSat-1
2021-11-06 18:21:33,345 - root - INFO - 1650 |   N | 40014 | 2021-11-07T11:16:56 | 2021-11-07T11:22:01 | 0:05:04  |  45 | 1.000000 | NSXo8tGxmxpTUMsmSH34FF | FSK        | BUGSAT-1 (TITA)
2021-11-06 18:21:33,345 - root - INFO - Scheduling all unscheduled passes listed above.
2021-11-06 18:21:38,022 - root - INFO - Done.
(env) abraham@lap:~/satnogs-auto-scheduler$
1 Like

Thanks for sharing your experience, so this doesn’t seem to work, then we will need the developer to add this option. If I am correct the is @kerel

I’ve tried this in the past as well and encountered the same result as @ xe3adc.That is, no error but nothing gets scheduled until the comment is removed.

1 Like

I opened an enhancement request

2 Likes

Implemented.

Thanks again @PE0SAT for testing!

3 Likes

Thanks Kerel,

I have tested the latest update and worked like a charm, can others also update and share there experience.

1 Like

Hi, many thanks, that was fast…
Just two questions:
1-What is the correct procedure to update?, I’m using ubuntu 18.04 lts,
will the following commands work:

cd satnogs-auto-scheduler
git pull origin master

Is there something else to do?

2-To launch auto-scheduler, should I use the same CLI command as before with the priorities.txt file commented as shown in past messages?

best regards, Abraham - xe3adc

Good day Abraham,

I used to development fork that was created by @kerel but now with all the code merged a git pull should be enough. All the commands stayed the same.

After removing observation and then adding remarks to my priority file and re run the schedular I found that the observations where created again.

Maybe @kerel can add something to the README file on the repository on how remarks can be used.

All the best Jan - PE0SAT

Hello Jan,
Many thanks for your support…!!
I updated the auto-scheduler as you suggested without any problems, afterwards I obtained observations correctly scheduled using the auto-scheduler with the commented priorities file.
Also many thanks to @kerel for the expedite response.
Best regards, Abraham - xe3adc

1 Like