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

Add detail for comms and references

Browse Source
This commit is contained in:
Mark Allyn
2026-04-01 10:13:45 -07:00
parent 6cabf29934
commit ce226dc4ce
1 changed files with 32 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
CLAUDE.md
View File

@@ -56,6 +56,19 @@ for the a scope. The ppi scope
will be on the right side of the screen and the a scope will be on the left will be on the right side of the screen and the a scope will be on the left
hand side of the screen. hand side of the screen.
Suggest one window with viewports. Lets have window the entire screen. For develpment
I would need some sort of escape the esscape the full screen and go back to the
desktop.
Suggest that the radar itself is at the location of the Community Boating
Center dock in Bellingham, Washington, That should be 0,0 in local cartesian
coordinates or 0 in range for vectoring. North on radar needs to be north in
reality.
GPS for tagets should be converted to local cartesian reference to this
location. I don't know if I have to be concerned with vector data. Please
comment.
Notes for controls the user can play with Notes for controls the user can play with
Here are the controls that I am proposing Here are the controls that I am proposing
@@ -159,7 +172,11 @@ The PPI display will need shaders for the following:
4. facility to include shore lines. This will change with range settings. If possible, can 4. facility to include shore lines. This will change with range settings. If possible, can
we include docks and tall buildings? Immediate is blue white same as targets. we include docks and tall buildings? Immediate is blue white same as targets.
5. Persistance (green yellow) for targets, clutter, and shore lines. 5. Persistance (green yellow) for targets, clutter, and shore lines. Persistance should
be ping pong. Lets suggest for persistance to be about 3 seconds.
6. The pulse repitition time should be the same as a multiple of the screen update rate
so that we would have no aliasing.
Communication: Communication:
@@ -174,11 +191,16 @@ Each Raspberry Pi will act as a server fielding requests from this program.
Lets try to have each raspberry pi as a separate instantiation of a class Lets try to have each raspberry pi as a separate instantiation of a class
called raspberry pi. Those classes will use a common data structure: called raspberry pi. Those classes will use a common data structure:
1. float longitude 1. double longitude
2. float latitude 2. double latitude
3. char *vessel_name 3. std::string *vessel_name
4. char *registration 4. std::string *registration
5. char *vessel_size 5. float *vessel_size
6. float course
7. float speed
8. time_t timestame
9. float altitude (0 for boats)
10. Target type
Looking for suggesions Looking for suggesions
@@ -189,6 +211,10 @@ call.
The Raspberry Pi code will live in a separate git repository with its own CLAUDE.md The Raspberry Pi code will live in a separate git repository with its own CLAUDE.md
and its own CMakeLists.txt, since it targets a different architecture (ARM) and has 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. a different toolchain and dependencies. Do not mix it into this repository hierarchy.
The code will work on a blocking basis to block until something becomes available
It should be up to this piece to convert the global latitude and longitude to
cartesian coordinates for the display. Unless you suggest otherwise
Right now, I just want to make sure that the structure is okay and that the CMakeFile.txt Right now, I just want to make sure that the structure is okay and that the CMakeFile.txt
looks okay. I am not ready to ask you to create any code looks okay. I am not ready to ask you to create any code