Adding to description file
This commit is contained in:
46
CLAUDE.md
46
CLAUDE.md
@@ -3,6 +3,31 @@ days of digital electronics and we had to use a cathode ray tube with p7 phospho
|
||||
|
||||
I plan to use c++ and opengl and shaders for access to a GPU. I am in ubuntu 25.10.
|
||||
|
||||
I wish the c++ be arranged as follows:
|
||||
|
||||
All code in the src subdirectory
|
||||
|
||||
The main program and the binary would be called radar-simulation.
|
||||
|
||||
We need to use classes. For now, I can see one class for all things
|
||||
having to do with putting stuff on the screen. Includes initializing
|
||||
OpenGL and put up two windows on the screen. One is for the PPI display,
|
||||
locate on the right hand side of the screen with margins for the sides of
|
||||
the monitor. The A Scope is a smaller window on the center of the left
|
||||
side of the display.
|
||||
|
||||
All inputs to either display will be performed in that class. Data fields
|
||||
for the methods of that class should be put into a header file in the
|
||||
headers directory.
|
||||
|
||||
Another class would be used to communicate with the raspberry pies that
|
||||
will obtain data from the ais and ads-b software defined radios.
|
||||
|
||||
Another class would be used for simulating targets, like for example
|
||||
a sailboat regatta race.
|
||||
|
||||
There may be more classes TBD
|
||||
|
||||
The platform is a Geekom GEEKOM A8 Max, AMD Ryzen 9 8945HS 5.2GHz 32GB RAM
|
||||
|
||||
Now here is the overall project and proposed architecture
|
||||
@@ -19,5 +44,24 @@ how to impliment the bearing control. Just put the display up on the screen.
|
||||
The main ppi scope will take up the right hand side of the screen. You need to leave about
|
||||
a 1/2 inch margin around the sides of the circular scope.
|
||||
|
||||
Details for A scope (predescor to the PPI scope)
|
||||
|
||||
The a scope will have pulse amplitude on the vertical axis and the range on the horizontal
|
||||
axis. There will be a graticule for the a scope.
|
||||
axis. There will be a graticule for the a scope. This will show range markings. In the
|
||||
day, the operator would physically change the graticule overlay. What we can do is to
|
||||
electronically change the overlay and put a brief message saying operator changes
|
||||
the graticule.
|
||||
|
||||
The graticle was illuminated with #47 incandescent dial lights, we need to have that
|
||||
graticule lit with an equivalent color. Horizontal is range, verticle is strength
|
||||
of the return blip. The phosphor of the A scope is green, similar to P1, which was
|
||||
used on oscillosopes.
|
||||
|
||||
Please note that there will be two sets of shaders. Once for the actual trace and the
|
||||
other is used for the graticule. It will be used to change the graticle range and
|
||||
briefly display the message "operator inserts new graticule manually". If possible for
|
||||
realism, have the old graticule move up and off the screen and then the new graticule move
|
||||
onto and down the screen until it is in place, simulating the operator changing the
|
||||
graticule.
|
||||
|
||||
PPI display will be done later.
|
||||
|
||||
Reference in New Issue
Block a user