2.5e-3 Ramp rise time for stimuli (s)
# Module Specifications
PureTone < PTone1.par
PreEmphasis_BandPass < PreEmph1.par
IHC_Meddis86 < Meddis86.par
Figure  Meddis86.sim Simulation Specification Each of the lines after the begin specifies the module to use, e.g.. the PureTone module is set from the PTone1.par parameter file. Additional lines may be added or different modules or parameter files may be used.
Simulation specifcations are run using the same procedure as outlined in the section "The Standard Program Format" (page 17) above. However, most of the steps outlined by that section are carried out automatically or are implicit in the way the simulation specification is set out. The declaration of the data structure pointers (step i) and the initialisation of the data structures (step ii) is carried out automatically for each line in the simulation specification. The order of the lines defines the connections between the module processes (step iv). The driving program calls the routine for reading the module parameters for the simulation specification (step v). In the output shown above the lines beginning, "ReadPars_..." show the diagnostics messages for this operation. The driving program also calls the routines which run the main simulation process (step vi) and carries out the house keeping operations (step vii). It is useful to note that simulation specifications are accessed using a module the same as any other process in the CRL, and can thus be used nested within other simulation specifications.
The simulation run by the AudPerSS.c example program can be change by simply changing the module specification in the "Meddis86.sim" file, or using a different file altogether. In the "Meddis86.sim" file the PureTone stimulus can be changed by adjusting the parameters in the file, "Ptone1.par" or other stimulus modules such as a harmonic series or pulse train can be used. By using the DataFile module as the stimulus, sound files such as AIFF, WAV, ASCII or raw binary files can be used as stimuli. All these changes use the same driving program, and are made by changing the PureTone < Ptone1.par line of the simulation specification. By changing the other lines the Meddis model can be replaced by other available models. Additional modules, including analysis processing, can also be added. In addtion simple processing loops can be used.
More detailed information about using simulation specifications is given in section ?? on page ??.