BeamForm different results for azimuth array vs scalar

[jegestrich]

The function BeamForm generates different data when entering a scalar azimuth or an array filled with the same scalar value.
I realized that when plotting the spectrum of both, where the input of an azimuth array causes a dip in the spectrum at 2-5 Hz. An example plot is shown below.

[jwbishop]

An array passed to 'beamForm' in the generic module is interpreted as a back-azimuth angle and an elevation angle.

For the sake of curiosity, what is the aperture of your array?

[davidfee5]

We just talked about it during our meeting and agree. We should implement some error-checking to confirm a realistic back-azimuth and angle are provided.

[jwbishop]

This issue seems resolved now.

[liamtoney]

This issue seems resolved now.

@jwbishop was the error-checking above implemented?

[jwbishop]

We should implement some error-checking to confirm a realistic back-azimuth and angle are provided.

Perhaps this issue can be avoided by rewriting the function arguments to accept separate back-azimuth and incidence angle arguments. Moreover, we can make sure the incidence angle is between 0 and 90 degrees.

Should this not be a separate issue, a enhancement? The original issue itself concerning the array vs scalar arguments was resolved.