Sphere lab

Location

floor plan Biophysics Labs

The Sphere lab is located at the underground corridor (floor -2) between the Huygens Building and the Goudsmitpaviljoen (NMR). The entrance from the corridor is has the number W36A -2.002a. The Lab itself has the number -2.002d.

The entrance code of the door lock is 2971.

Experiment

TDT programming

Basic information on TDT programming can be found in the RPvdsEx manual For everyone: read this first! (several examples: tones)

Basic sound localization experiment software

A basic sound localization experiment consists of several software components:

• xxxxxx.rcx for sound generation and data acquisition using TDT
• xxxxxx.m to input parameters, acting as a GUI

Sound generation

With the TDT system we can create and control sound stimuli in realtime. Stimulus parameters such as loudness, duration and onset timing can be controlled using the circuit components of the RPvdsex software. To create a stimulus, a relevant circuit has to be loaded onto the RP2 Realtime Processing unit. These files are called .rcx/.rpx files and can be found on the C:\MATLAB\experiment\RPvdsex drive on the experimental pc in the Biophysics lab.

Let's start with an example of gaussian white noise to see what is needed to present a stimulus.

In the circuit shown above, we can see that there is a separate component called "GaussNoise". This generates random numbers that can be used to produce whitenoise through a speaker. After the GaussNoise component, there are two "Biquad" components in serie. The Biquad components both have input from "ButCoef1"; Butterworth filter coefficient generators. The result is a sound that is Lowpass filtered with cutoff frequency "LPFreq" and highpass filtered with "HPfreq". Both LPfreq and HPfreq are so called parameter tags, wich can be controlled via matlab with the command RP2.SetTagVal('HPfreq',MatlabHPfreq) where MatlabHPfreq is the Matlab variable with the value you want to assign to HPfreq in the circuit.

The filtered noise signal is passed to "BPGwn" (bandpassed Gaussian White noise) which is a simple linker component to create a clear flow in the circuit. The BPGwn reappears in the lower left part of the circuit, where it functions as input for a gating component "Cos2Gate". The gating component makes sure that the signal onset is a smooth transition from 0 to maximum amplitude, to prevent highfrequency onset artefacts. The Cos2Gate has additional green input in the form of Ctrl=Open, meaning that this is a digital (0 or 1) value. Likewise, the main input of Cos2Gate is light blue, meaning that it is a floating point value. When you create and compile your own circuits, the software checks if the input type matches the type of signal you connected. The Ctrl=Open port gets its input from the "Schmitt" component which creates a digital pulse of length "Thi" milliseconds. This is the stimulus duration, which you can change by altering the "StimLength" tag value. The Schmitt pulse is triggered by a linker called "Engage" which you can trace back to the top of the circuit. There and "EdgeDetect" looks for sharp positive change in the external trigger labeled "Src=Extern". This is the trigger input on the RP2 machine, usually you connect a button that the participant presses.

The output of the Cos2Gate is multiplied by "GWNAmp" to create a fixed loudness change. Note that you can also change the loudness by altering the "Amp" parameter in the GaussNoise component. After the multiplier, there are two components called "Ch=1" and "Ch=2". These are Digital to Analog Converters (DAC outputs) and they correspond to the two output channels on the RP2.

After the RP2, the sound signal is led through a PM2relay ("MUX machines" or Multiplexers) to assign which speaker should present the sound.

In this part of the circuit, we will start with the output instead of the input. Output here is the "WordBitOut" on the right with "M=-1" written inside. The wordbitout is a digital output with 8 bits. From the TDT system manual: Bits 0 - 3 identify the channel number. Integer 0, or bitpattern (xxxx 0000), is channel 0 and integer 15, or bitpattern (xxxx 1111), is channel 15. Bits 4 and 5 identify the device number. Integer value 0, or bit pattern (xx00xxxx), is device number 0 and integer value 48, or bit pattern (xx11xxxx), is device number 3. The device number is set internally for each PM2R and allows for an RP2 to control up to four PM2R modules. If only one PM2R is being used, it should have device number 0. Bit 6 is the set-bit. When this bit is set high, the channel and device from the previous six bits is activated. Bit 7 deactivates all channels across only the specified device.

This means that you need to add several integer values to switch on the speaker you want. To select the channel (0-15) on a multiplexer, you can change the "GwnChan" tag. To select a multiplexer device, change the "DeviceSelect" tag value. Finally, to switch on the selected speaker, choose value 64 for "SetReset" and trigger the software trigger (the "Src=Soft1" component) via matlab. To know which speaker (azymuth, elevation location) belongs to which configuration of multiplexerindex and channel, use the SoundSpeakerLookUp function in matlab (more on this function and other matlab functions in another section).

Timing of sounds The timing of sound playback is an important factor in an auditory experiment. Humans can detect onset differences at millisecond level, so knowing when your sound was presented and when it ended is crucial for analysis. A specific part of the sound presentation RP2 circuit is designed to measure and store onset/offset timings for sounds. This part of the circuit is shown in the figure below:

The timings of sound onset and offset are based on the change in WriteSound. Once SoundOn or SoundOff is high, the Schmitt2 sends a single sample pulse to the SerStore buffer component. The buffer stores the value in the Counter (the Clock value). The counter can be set at any time before stimulus presentation, because only the relative timings between different events in a trial (button presses, LED timings, data acquiring) matter. In the circuit above, the counter is switched on with a zBusA trigger. This has the advantage that multiple circuits on different machines can be triggered simultaneously. The tags OnsetTimings and OffsetTimings can be read using the matlab command RP2.ReadTagV('OnsetTimings',0,1) (or 'OffsetTimings').

Technical information

Sound booth

Acoustics

...todo...

Electronics rack

The electronics rack contains 10 TDT Zbus devices chassis, each containing two TDT series 3 devices. Furthermore it contains the Field coil amplifier and the Femto LockinAmplifier as part of the head tracking electronics.

The zBus Monitor program has control functions for the optical bus. It shows all the connected zBus chassis and the TDT devices that are installed in each chassis. It also shows the version number of the installed firmware on the devices.

zBus Monitor

The following table shows all the zBus chassis from top to bottom, with the installed devices.

Chassis	Front left	Front right	Back
Zbus	MS2 Monitor speaker	<empty>
Zbus	PA5 Attenuator	PA5 Attenuator	F05 optibit bus #1
Zbus	PA5 Attenuator	PA5 Attenuator	F05 optibit bus #2
Zbus	SA1 Speaker amplifier	SA1 Speaker amplifier
Zbus	RP2.1 Sound processor	RP2.1 Sound processor	F05 optibit bus #3
Zbus	PM2R Multiplexer	PM2R Multiplexer
Zbus	PM2R Multiplexer	PM2R Multiplexer
Zbus	PM2R Multiplexer	PM2R Multiplexer
Zbus	PM2R Multiplexer	PM2R Multiplexer
Zbus	RA16ba base station	RA8GA2 multi DAC	F05 optibit bus #4

upper half of electronics rack

The next table shows all other electronics in the lower half of the rack from top to bottom.

PP16 Patch panel for Medusa Base Station

PP16 Patch panel for Medusa Base Station

Digital event recorder

Junction box panel (connects to junction box in sound boot)

Trigger distribution panel

Femto Lockin amplifiers

Tektronics Oscilloscope

Field coil amplifier

Rack main power switch

Patch panel for XLR output to Tannoy speakers

lower half of electronics rack