113 lines
4.8 KiB
Plaintext
113 lines
4.8 KiB
Plaintext
I would like to have this project use the radar equation to determine
|
||
brightness and possible blooming on targets.
|
||
|
||
I want the radar equation to be implemented within the shaders.
|
||
|
||
I want a postgres database (I did install postgresql and set up a database named radar with
|
||
a postgresql user named radar with password radar with full priveleges to database radar.
|
||
|
||
DATABASE Schema:
|
||
|
||
1. Type of target (Enumeration AIS, ADS-B, Local (simulator)
|
||
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 (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. 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
|
||
|
||
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 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)
|
||
In doing this, keep this work outside of any mutex lock of any shared data
|
||
|
||
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
|
||
contextual data on targets that are from external sources. For now, let's not worry about this.
|
||
|
||
PROPOSAL:
|
||
|
||
Since ADS-b and AIS may not have material and size data, I would like to propose
|
||
That the initial running of the system upon detecting a target that has no size
|
||
determination, we use a default size, say, 20 feet long 20 feet wide and fiberglass
|
||
for boats; 50 feet long 10 feet wide fusalage for planes; and set the need update parameter
|
||
to need update.
|
||
|
||
Add an option (command line option) for system. Command line options would be 'database'
|
||
which would open a graphical panel suitable for updating the postgres database.
|
||
At the beginning of the life of this project, almost all targets seen except for those
|
||
from the simulator will need database updating; as life of the system gets older there would
|
||
be fewer targets that need operation. For this option; none of the main radar screens
|
||
will be available. So we do not have to to have the opengl and shader stuff. Use a regular
|
||
desktop based application non opengl shader database updating application. This would be ended with quit
|
||
and then the main radar application can be started.
|
||
|
||
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
|
||
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.
|
||
For Marine, the antenna height is 50 feet off surface
|
||
|
||
Air traffic radar equation stuff:
|
||
|
||
For this purpose, the air traffic control radar at BLI frequency 3 ghz or S Band;
|
||
power 25 KW
|
||
|
||
For Air Traffic Control, the beam width is 1.4 degrees for horizontal and 5 degrees for vertical
|
||
For Air Traffic Control, the antenna size is 20 feet wide
|
||
For Air Traffic Control, the antenna is on a tower 50 feet high from the runway. It is not
|
||
mounted on the control tower.
|
||
|
||
Chain Home radar equation stuff:
|
||
|
||
For Chain Home, this will be a bit different: (this is AMES type 1)
|
||
|
||
Frequency is 30 MHZ
|
||
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 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)
|
||
|
||
Note that this is Bistatic; we need both Gt and Gr
|
||
|
||
RECEIVE GAIN (Gr) is about 4 to 10 (6–10 dBi)
|
||
|
||
System loss due to transmission line about 8 DB
|
||
|
||
Target RCS larger RCS due to resonant scattering (I need help; please lookup
|
||
|
||
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 detect small aircraft
|
||
High pulse repetition rate
|
||
Sweep about 20 degrees horizontal and 10 degrees vertical
|
||
Short pulse width for range resolution
|
||
Beamwidth is determined by wavelength/antenna size with antenna size of about 5 meters.
|
||
|
||
GENERAL NOTE FOR EQUATION STUFF
|
||
|
||
We will need these key variables to be able to be changed via the settings.h file
|
||
and DESIGN.md and CLAUDE.md
|