Skip to content Skip to navigation

Connexions

You are here: Home » Content » The Team

Navigation

Content Actions

Lenses

What is a lens?

Definition of a lens

Lenses

A lens is a custom view of Connexions content. You can think of it as a fancy kind of list that will let you see Connexions through the eyes of organizations and people you trust.

What is in a lens?

Lens makers point to Connexions materials (modules and collections), creating a guide that includes their own comments and descriptive tags about the content.

Who can create a lens?

Any individual Connexions member, a community, or a respected organization.

This content is ...

Affiliated with (What does "Affiliated with" mean?)

This content is either by members of the organizations listed or about topics related to the organizations listed. Click each link to see a list of all content affiliated with the organization.
  • Rice University ELEC 301 Projects

    This module is included inLens: Rice University ELEC 301 Project Lens
    By: Rice University ELEC 301As a part of collection:"ELEC 301 Projects Fall 2004"

    Click the "Rice University ELEC 301 Projects" link to see all content affiliated with them.

  • Rice University OCW

    This module is included inLens: Rice University OpenCourseWare
    By: OpenCourseWare ConsortiumAs a part of collections:"Array Signal Processing", "ELEC 301 Projects Fall 2004"

    Click the "Rice University OCW" link to see all content affiliated with them.

Tags

(What is a tag?)

These tags come from the endorsement, affiliation, and other lenses that include this content.

The Team

Module by: Jeremy Bass, James Finnigan, Edward Rodriguez, Claiborne McPheeters

Summary: This lists the team members and their responsibilities.

Group Members

The group work was distributed to follow the strengths of the individual members. Jim Finnigan was responsible for most of the LabVIEW code, while Clay McPheeters and Jeremy Bass worked on a couple of supplementary VIs. Ed Rodriguez built the actual hardware microphone array and the filters for the microphone signals going into the DAQ. In addition, we all got together and tested the hardware and software to make sure it worked. Jeremy and Clay created the poster for the presentation, while all members of the group worked on the Connexions modules. We all spent many hours and exchanged uncountable blank stares trying to understand array theory. Many thanks to Dr. Don H. Johnson for helping us along the way. Dr. Richard Baraniuk also gave us helpful ideas and LabVIEW, which we could never have afforded.

Figure 1
Jim Finnigan (finnigan@rice.edu)
Jim Finnigan (finnigan@rice.edu) (Jim.jpg)
Figure 2
Ed Rodriguez (edrod@rice.edu)
 Ed Rodriguez (edrod@rice.edu) (Ed.jpg)
Figure 3
Clay McPheeters (claym@rice.edu)
 Clay McPheeters (claym@rice.edu) (Clay.jpg)
Figure 4
Jeremy Bass (jbass1@rice.edu)
 Jeremy Bass (jbass1@rice.edu) (Jeremy.jpg)

Acknowledgements

Dr. Don H. Johnson for consultation & book: Array Signal Processing: Concepts & Techniques

Dr. Richard Baraniuk for LabVIEW and direction

Varma, Krishnaraj: “Time-Delay-Estimate Based Direction-of-Arrival Estimation for Speech in Reverberant Environments”

Comments, questions, feedback, criticisms?

Send feedback