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

Fix typos

Browse Source
This commit is contained in:
Mark Allyn
2026-04-21 08:03:05 -07:00
parent 8c3f5e67a9
commit 83ebd11ea5
2 changed files with 58 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
additions
View File

@@ -9,22 +9,28 @@ a postgresql user named radar with password radar with full priveleges to databa
DATABASE Schema:
1. Type of target (Enumeration AIS, ADS-B, Local (simulator)
2. ID a. MMID for marine; b. ICAO 24 bit aircraft address; for simulator we can use the same MMID
2. ID a. MMSI for marine; b. ICAO 32 bit aircraft address; for simulator we can use the same MMSI
and aircraft address
3. width (24 bits)
4. length (24 bits)
5. Height above water (24 bits)
3. width (32 bits) in meters (float data type)
4. length (32 bits) in meters (float data type)
5. Height above water (32 bits) in meters (float data type)
6. Material (Enumeration fiberglass, wood, aluminum, steel
7. Enumeration: need update for size and material, does not need update for size and material
7. boolean: need update for size and material, does not need update for size and material
8. ISO 8601 timestamp for last used
9. ISO 8601 timestamp for last updated
10. Track / position history (to be used if I want newer track prediction radars
Keep a copy of the data in the shaders. Don't just copy the entire database; when the
system starts up, there would be nothing in the copy; but as we get targets, either from
AIS, ADS-B, or simulator, add each target encountered to the copy in the shaders. This means
that we don't have to copy all of the data into the database. It will grow to a size up to the
current target count in a simulation session.
For performance, we can keep id, width, length, and height, and material
inside the shaders as fixed data; but have location, heading, and altitude (aircraft)
The items in the database (to start with) would be the Enumeration, The ID, width, height,
and material.
and material. Suggestion: Uniform Buffer Object for the id, width, height, material
The items that are updated per data coming in from the raspberry pis and the simulator
are orientation / RCS (based on heading), location (in longitude and latitude) and ID ; Suggestion
vertex objects or SSBO
Suggest that CPU compute the RCS based on heading and dimensions and altitude (aircraft)
Maybe, if I simulate a modern system, I may want a field to describe the target (passenger, cargo,
oil, fishing; and maybe specifics for the targets. I know that the coast guard has a lot of
@@ -49,7 +55,7 @@ END OF PROPOSAL
Marine radar equation stuff:
For this purpose, the marine radar will use the X Band (9225 MHZ) and 30 KW power for
maratime traffic system radar (our a-scope marine and PPI scope marine)
maritime traffic system radar (our a-scope marine and PPI scope marine)
For Marine, horizontal beam width is 0.5 degrees; vertical beam width is 20 degrees.
For Marine, the antenna size is 15 feet in length.
@@ -70,12 +76,12 @@ Chain Home radar equation stuff:
For Chain Home, this will be a bit different: (this is AMES type 1)
Frequency is 30 MHZ
Powwer is 500 KW
Power is 500 KW
Pulse width is 20 US
TRANSMIT GAIN (Gt)
Note that the transmit beam is not a beam, but a floodlight.
Pulse repitation frequency is 25 HZ or 12 HZ as selected by operator
Pulse repetition frequency is 25 Hz or 12.5 Hz as selected by operator
Use Transmit G from beam width (floodlight) something like
G = 30000/100 degrees * 40 degrees
about 8.7 dBI (linear value of 7.5
@@ -93,7 +99,7 @@ Precision Approach Radar Equation Stuff:
Peak power is about 100 kw
Very high antenna gain
X Band (3 cm for wavelength) Operation allow higher antenna gain
PAR must reliably small aircraft
PAR must reliably detect small aircraft
High pule repition rate
Sweep about 20 degrees horizontal and 10 degress vertical
Short pulse width for range resolution