maallyn/radar-simulation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Adding changing notifier and quickened graticule change

Browse Source
This commit is contained in:
Mark Allyn
2026-04-07 08:02:33 -07:00
parent 337d423639
commit 7db6259b06
4 changed files with 291 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
CLAUDE.md
View File

@@ -276,6 +276,36 @@ The Raspberry Pi code will live in a separate git repository with its own CLAUDE
and its own CMakeLists.txt, since it targets a different architecture (ARM) and has
a different toolchain and dependencies. Do not mix it into this repository hierarchy
NEW suggestions =======
1. The a scope bearing must not follow the rotating sweep on the ppi scope. The A scope
during the time they were popular before the ppi scope used a manual control to set the
bearing. The bearing setting uses a servo motor to rotate the dish antenna to the bearing
desired by the operator. We need to simulate that by not a scope not to follow the bearing
shown on the ppi scope. This bearing must be controled by control 7.
2. Add two more controls; Range for ppi scope cursor and Bearing for the PPI scope cursor
3. Pleae add a small window under the A scope to show the setting of the A scope bearnig.
4. Temporary: Have the bearing for a scope set to the location of one of the current targets.
5. Have the cursor on the ppi scope follow one of the targets and not move around.
New update 1
1. I notice that the height of the pulse on the A scope seems to be going up and down in sync
with the ppi scope rotating.
2. Add a range figure in the small box under the A scope
3. Have the a scope graticules change a little faster
4. it appears that the cursor range ring sometimes appears outside the boundary of the scope
New update 2
1. Add small text window above that a scope that says "Operator Manually Changing Range Graticule"
This appears only when the graticule is changing
NOTE on my plan for coding
1. I want to test and debug the code feature by feature.
@@ -305,10 +335,5 @@ Order of testing features.
========================================================
Generate code for testiong feature 1 and 2 and 3 only;
1. General initialization and set up basic boundaries of the two scopes
on the screen. No features on each scope yet.
2. Edge graticule on ppi scope (Bearing ticks and numbers)
3. replaceable graticules for A scope
Do not generate any other code
Generate code the run this and hold for 10 seconds and exit
Generate code for testiong feature 1,2,3,4,5,6 nly;