Make the nonlinear beamformer steerable

webrtc/modules/audio_processing/test/audioproc_float.cc

Index: webrtc/modules/audio_processing/test/audioproc_float.cc
diff --git a/webrtc/modules/audio_processing/test/audioproc_float.cc b/webrtc/modules/audio_processing/test/audioproc_float.cc
index 9c44d76ecc29fb404a91630fd7f5efe1247fe988..d5b07079b8388bd5c8ef886c2748061de4f586bd 100644
--- a/webrtc/modules/audio_processing/test/audioproc_float.cc
+++ b/webrtc/modules/audio_processing/test/audioproc_float.cc
@@ -37,6 +37,9 @@ DEFINE_string(mic_positions, "",
     "Space delimited cartesian coordinates of microphones in meters. "
     "The coordinates of each point are contiguous. "
     "For a two element array: \"x1 y1 z1 x2 y2 z2\"");
+DEFINE_double(target_angle_degrees,
+              90,
+              "The azimuth of the target in radians");
 
 DEFINE_bool(aec, false, "Enable echo cancellation.");
 DEFINE_bool(agc, false, "Enable automatic gain control.");
@@ -107,7 +110,10 @@ int main(int argc, char* argv[]) {
         ParseArrayGeometry(FLAGS_mic_positions, num_mics);
     RTC_CHECK_EQ(array_geometry.size(), num_mics);
 
-    config.Set<Beamforming>(new Beamforming(true, array_geometry));
+    config.Set<Beamforming>(new Beamforming(
+        true,
+        array_geometry,
+        M_PI * FLAGS_target_angle_degrees / 180.f));

[peah-webrtc, 2015/10/13 12:53:41]

Since the usage is done using degrees, it would make sense for the beamformer to
accept the target angle in degrees instead of radians.

[aluebs-webrtc, 2015/10/20 00:04:20]

I only think this user will user degrees, since it is a user input and, as you
said, degrees are easier to think about. The localizers work with radians, all
trigonometrics functions in C++ do, so I don't find a strong point for changing
the interface to degrees.

[peah-webrtc, 2015/10/20 21:22:33]

Acknowledged.

   }
 
   rtc::scoped_ptr<AudioProcessing> ap(AudioProcessing::Create(config));