fix typos and add gain and clutter controls on keyboard
This commit is contained in:
23
additions
23
additions
@@ -23,32 +23,33 @@ DATABASE Schema:
|
||||
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. 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)
|
||||
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, lets now worry about this.
|
||||
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
|
||||
determinatioin, we use a default size, say, 20 feet long 20 feet wide and fiberglass
|
||||
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 begining of the life of this project, almost all targets seen except for those
|
||||
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.
|
||||
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
|
||||
|
||||
@@ -84,7 +85,7 @@ 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
|
||||
about 8.7 dBi (linear value of 7.5)
|
||||
|
||||
Note that this is Bistatic; we need both Gt and Gr
|
||||
|
||||
@@ -100,8 +101,8 @@ 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 pule repition rate
|
||||
Sweep about 20 degrees horizontal and 10 degress vertical
|
||||
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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user