Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitf5327e0

Browse files
committed
fix links and XZ plane
1 parent9776d1d commitf5327e0

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

‎content/2d_beamforming.rst‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -73,12 +73,12 @@ Now let's move on to the 2D case. We will place our array in the X-Z plane, wit
7373
# Now let's switch to 2D, using a 4x4 array with half wavelength spacing, so 16 elements total
7474
Nr=16
7575
76-
# Element positions, still as a list of x,y,z coordinates in meters
76+
# Element positions, still as a list of x,y,z coordinates in meters, we'll place the array in the X-Z plane
7777
pos= np.zeros((Nr,3))
7878
for iinrange(Nr):
7979
pos[i,0]= d* (i%4)# x position
80-
pos[i,1]=d* (i//4)# y position
81-
pos[i,2]=0# z position
80+
pos[i,1]=0# y position
81+
pos[i,2]=d* (i//4)# z position
8282
8383
The top-down view of our rectangular 4x4 array:
8484

@@ -202,6 +202,8 @@ This outputs 0 dB, which is what we expect because MVDR's goal is to achieve uni
202202

203203
Your results may vary due to the random noise being used to calculate the received samples, which get used to calculate:code:`R`. But the main take-away is that the jammers will be in a null and very low power, the 1 degree off from:code:`dir` will be slightly below 0 dB, but still in the main lobe, and then a random direction is going to be lower than 0 dB but higher than the jammers, and very different every run of the simulation. Note that with MVDR you get a gain of 0 dB for the main lobe, but if you were to use the conventional beamformer, you would get:math:`10\log_{10}(Nr)`, so about 12 dB for our 16-element array, showing one of the trade-offs of using MVDR.
204204

205+
The code for this section can be found `here<https://github.com/777arc/PySDR/blob/master/figure-generating-scripts/doa_2d.py>`_.
206+
205207
**********************************************
206208
Processing Signals from an Actual 2D Array
207209
**********************************************
@@ -396,7 +398,7 @@ Using this 2D plot we can easily read off the estimated azimuth and elevation of
396398

397399
As an exercise, try using the conventional beamformer, as well as MVDR, and compare the results to MUSIC.
398400

399-
This code in its entirety can be found `here<https://github.com/777arc/RADAR-2025-Beamforming-Labs/blob/refs/heads/main/figure-generating-scripts/2d_array_recording.py>`_.
401+
This code in its entirety can be found `here<https://github.com/777arc/PySDR/blob/master/figure-generating-scripts/2d_array_recording.py>`_.
400402

401403
***********************
402404
Interactive Design Tool

‎figure-generating-scripts/doa_2d.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ def get_unit_vector(theta, phi): # angles are in radians
179179

180180
# 2D plot that makes more sense
181181
# This seems to be making a UV plot
182-
ifFalse:
182+
ifTrue:
183183
resolution=100# number of points in each direction
184184
theta_scan=np.linspace(-np.pi/2,np.pi/2,resolution)# azimuth angles
185185
phi_scan=np.linspace(-np.pi/4,np.pi/4,resolution)# elevation angles

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp