Antenna Control: Track and flip past 360° Az or 90° El
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
The payload names no source files, so begin by finding where GPredict computes the azimuth and elevation values sent to the rotator. Check how azimuth wraps at 360° and whether any flip logic already exists. Done means the rotator can be commanded past 360° azimuth and past 90° elevation, with the behaviour choosable, and the existing tracking behaviour is unchanged. Expect design questions about the rotator protocol, so confirm the approach with the maintainer first.
Written by the indexing model from the issue text.
Description
Currently, GPredict tracks a satellite and sends commands only using direct astronomical value.
For example, when a satellite crosses 360°, it will go back to 0° and flip the rotator 360° even though it can go further until 450° and prevent this flip. SatDump for example supports this.
Another example is the Flip method used by SatNOGS to flip the rotator over 90° and prevent the Az control to go too fast for high passes over 70°.
It would be great for GPredict to benefits from rotator that can go beyond 360° in Az and 90° in El to prevent go-arounds and flip values if possible.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 305
- Avg merge
- 8h 48m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from csete/gpredict
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 Under an hour Newbie friendliness 60/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 78/100
Similar issues
-
mewencode: base256[] and base128[] are indexed out of bounds by a non-ASCII octetPossibly taken @kazu-yamamoto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kazu-yamamoto/Mew#276 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
FujiNetWIFI/fujinet-firmware#2045 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
[Performance]: Qwen-Image-2.1 CPU-only on i5-10500H (6C AVX2, 32 GB): 512x512 in 7.7 min at 8 stepsOpen
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:gates area:gfx found-by:critic kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
InauguralSystems/EigenScript#1825 ·
Maintainers usually reply within 1 day