Updating claude with comms

CLAUDE.md

@@ -78,6 +78,8 @@ Here are the controls that I am proposing
 12. Off-centering
 13. Graticule brilliance 
 14. Reset (in case kids really mess things up)
+15. Pulse length selection (short pulse for better range resolution,
+    long pulse for better sensitivity at distance; operator selectable)
 
 
 (Please suggest other controls I may have missed.)
@@ -100,8 +102,9 @@ be expensive, especially robust ones that kids cannot break.
 
 Shaders:
 
-Please read and suggest what different shaders set to be used for reliability
+Each of the following is a separate shader set. Keeping them separate is
-and make approprate changes to this file. At least the following shader sets
+intentional for easier debugging — each layer can be disabled, modified,
+or tested independently without affecting the others. At least the following shader sets
 
 1. PPI targets, current, in white blue
 2. clutter for rain, in white blue
@@ -161,12 +164,31 @@ The PPI display will need shaders for the following:
 Communication:
 
 All I know now is that I plan to use a combination of raspberry pi 4 and a Airspy 
-SDR for each of ais, ads-b, and uat. I need comments on uat; does it need separate
+SDR for each of ais, ads-b, and uat. UAT (978 MHz) and ADS-B (1090 MHz) are different
-SDR and raspberry PI? I am hoping that each raspberry pi would act as a server to field
+frequencies and require separate SDRs, but a single Raspberry Pi 4 is powerful enough
-requests from this program I plan to use a separate git repository and a CLAUDE.md of its own
+to run both dump1090 (ADS-B) and dump978 (UAT) simultaneously with two SDRs on its USB
-since the build is for a different architecture and its own CMakeFile.txt file. Any comments?
+ports. AIS requires a separate Raspberry Pi with its own SDR tuned to VHF 161/162 MHz.
-Can I put the raspberry pi stuff in this same file heirarchy but with separate CMakeFile.txt,
+
-includes, etc.
+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
+called raspberry pi. Those classes will use a common data structure:
+
+1. float longitude
+2. float latitude
+3. char *vessel_name
+4. char *registration
+5. char *vessel_size
+
+Looking for suggesions
+
+Each of these raspberry pis will called by a main function (running as its own thread)
+to gather this data structure if there are any  targets received since the last
+call.
+
+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
+a different toolchain and dependencies. Do not mix it into this repository hierarchy.
 
 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