tomwalters@0: /*!
tomwalters@0: \mainpage AIM-C developer documentation
tomwalters@0: 
tomwalters@9: \section intro_sec Introduction
tomwalters@0: AIM-C is a real-time version of the the auditory image model (AIM)
tomwalters@0: developed at the <a href="http://www.pdn.cam.ac.uk/groups/cnbh/">
tomwalters@0: Centre for the Neural Basis of Hearing</a>.
tomwalters@0: 
tomwalters@9: The main development site for AIM-C is at http://aimc.acousticscale.org/. The 
tomwalters@9: code is available at http://code.google.com/p/aimc/.
tomwalters@9: 
tomwalters@9: \section design_sec Design
tomwalters@0: AIM-C uses a block-based processing scheme. A mono input signal is
tomwalters@0: split into short segments, which are sequentially 'pushed' through the
tomwalters@0: processing pipeline. The pipeline consists of a number of modules in a
tomwalters@0: tree structure.
tomwalters@0: 
tomwalters@0: The basic unit of data in AIM-C is the signal bank, and the basic
tomwalters@0: processing unit is the module. A signal bank represents a short
tomwalters@0: segment, or 'frame', of an audio signal with multiple
tomwalters@0: channels. Modules generally take a frame (represented as a signal
tomwalters@0: bank) as input, and generate zero, one, or more signal bank frames as
tomwalters@9: output. Each module maintains a list of 'target' modules, to which
tomwalters@9: it 'pushes' the frames that it generates. Each module
tomwalters@0: performs processing on the output of the previous module, and in turn,
tomwalters@0: push the output that they produce to their targets.
tomwalters@0: 
tomwalters@9: This feed-forward, tree-like system allows modules to generate as many output
tomwalters@9: frames as necessary for each input frame. It also allows for easy 'rewiring'
tomwalters@9: of chains of modules. For example, a 'viewer' module could be temporarily 
tomwalters@9: added as a target of another module while the user was interested in seeing
tomwalters@9: that module's output.
tomwalters@0: 
tomwalters@9: Since each module is an instance of a class, it can retain the necessary state
tomwalters@9: variables within the class between calls.
tomwalters@0: 
tomwalters@9: \section style_sec Coding style
tomwalters@0: 
tomwalters@0: For the most part, AIM-C now follows the <a
tomwalters@0: href="http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml">
tomwalters@0: Google C++ style guide</a>. The original (2006-2009) AIM-C codebase
tomwalters@0: used a different style, and so you may find some files which still
tomwalters@0: follow the older conventions. New code should adhere to the Google style
tomwalters@0: guide.
tomwalters@0: 
tomwalters@0: 
tomwalters@0: */