Size: 15647
Comment:
|
Size: 18214
Comment: Remove outdated references
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
From Eprime and VB, you may use the parallel port to synchronise, and to collect button box responses. From Matlab, National Instruments PCI 6503 card is used to capture all pulses (scanner synch pulse and button pulses alike). You can access its functions via ScannerSynch. |
* From '''Eprime''' and '''VB''', you may use the parallel port to synchronise, and to collect button box responses. * From '''Matlab''', National Instruments PCI 6503 card is used to capture all pulses (scanner synch pulse and button pulses alike). You can access its functions via ScannerSynch and [[http://imaging.mrc-cbu.cam.ac.uk/meg/MEGSynch|MEGSynch]]. |
Line 16: | Line 16: |
There's now also the possibility of using the parallel port as an input/output device in your experiment. For the moment only the leftmost stimulus presentation machine has this option. All signals will be send to both the Keithly PIO card and the parallel port. |
There's now also the possibility of using the parallel port as an input/output device in your experiment. For the moment only the leftmost stimulus presentation machine has this option. All signals will be send to both the Keithly PIO card and the parallel port. |
Line 21: | Line 18: |
BEWARE!! All signals coming from the parallel port are inverted as compared to the PIO signals. This means that a button press will show as a button release! This can be solved quite simply by setting the 'Invert' property in the port device properties dialog in E-Prime. |
BEWARE!! All signals coming from the parallel port are inverted as compared to the PIO signals. This means that a button press will show as a button release! This can be solved quite simply by setting the 'Invert' property in the port device properties dialog in E-Prime. |
Line 26: | Line 20: |
As the scanner pulse is inverted compared to the other buttons, this will now still be the wrong way around, sadly. The simplest way to solve this is to enable two 'Port' devices in E-Prime, one inverted for the buttons and one not inverted for the scanner pulses. |
As the scanner pulse is inverted compared to the other buttons, this will now still be the wrong way around, sadly. The simplest way to solve this is to enable two 'Port' devices in E-Prime, one inverted for the buttons and one not inverted for the scanner pulses. |
Line 31: | Line 22: |
The parallel port can be used with E-Prime, without the need for extra libraries or explicit coding in your scripts. There's also a little test program on the machines, called '!PortTest', which will show all incoming signals from both PIO and parallel port. |
The parallel port can be used with E-Prime, without the need for extra libraries or explicit coding in your scripts. There's also a little test program on the machines, called '!PortTest', which will show all incoming signals from both PIO and parallel port. |
Line 42: | Line 30: |
Configuring E-Prime is relatively easy (this was done with a release candidate for E-Prime2). Say you want to configure E-Prime to get input from the parallel port for both response box and scanner pule. First, enable in your project 2 ParallelPort devices (apprently EPrime is touchy about the names you give to devices, so if possible just leave the default names, i.e. ParallelPort and ParallelPort2). For both devices set the port mode to be on Input and the address to be &H379 (not 378 -- this will make the input numbering easier to use in E-Prime). The device you want to use for the ButtonBox should also be inverted (as mentioned above). Now that you have two parallel port devices enabled, all you need to know is that the scanner pulse will be received as a number 8, while the four fingers of the right hand will be (from index to pinky) 7,6,5,4. |
Configuring E-Prime is relatively easy (this was done with a release candidate for E-Prime2). Say you want to configure E-Prime to get input from the parallel port for both response box and scanner pule. First, enable in your project 2 ParallelPort devices (apprently EPrime is touchy about the names you give to devices, so if possible just leave the default names, i.e. ParallelPort and ParallelPort2). For both devices set the port mode to be on Input and the address to be &H379 (not 378 -- this will make the input numbering easier to use in E-Prime). The device you want to use for the ButtonBox should also be inverted (as mentioned above). Now that you have two parallel port devices enabled, all you need to know is that the scanner pulse will be received as a number 8, while the four fingers of the right hand will be (from index to pinky) 7,6,5,4. |
Line 65: | Line 49: |
'''Size:''' Distance between MRI screen and mid-point of mirror = 823mm Approx distance between eyes and mid-point of mirror ~ 90mm Width of full-screen display on MRI screen = 268mm |
'''Size:''' Distance between MRI screen and mid-point of mirror = 823mm Approx distance between eyes and mid-point of mirror ~ 90mm Width of full-screen display on MRI screen = 268mm |
Line 71: | Line 53: |
There are Matlab functions available for [[TransformingVisualAngleAndPixelSize|transforming visual angle to stimulus size]], or the other way around. | There are Matlab functions available for [[TransformingVisualAngleAndPixelSize|transforming visual angle to stimulus size]], or the other way around. |
Line 89: | Line 71: |
Note that if you are using the new LCD screen with anything other than the native resolution (1920x1080) Psychtoolbox's sync tests will fail, causing some fairly cryptic crashes when you attempt to Screen('OpenWindow'). The workaround is to include Screen('Preference','SkipSyncTests',1) in your script before opening the screen. But before applying this, please be very sure that your experiment really doesn't require any kind of reasonable display timing. Speak to Johan about this issue if unsure. | Note that if you are using the new LCD screen with anything other than the native resolution (1920x1080) Psychtoolbox's sync tests will fail, causing some fairly cryptic crashes when you attempt to Screen('OpenWindow'). The workaround is to include Screen('Preference','SkipSyncTests',1) in your script before opening the screen. But before applying this, please be very sure that your experiment really doesn't require any kind of reasonable display timing. Speak to Johan Carlin about this issue if unsure. |
Line 92: | Line 74: |
All machines should contain a small DMDX testscript, which should be used to check the proper functioning of the button box, the headphones and the projection system. | |
Line 93: | Line 76: |
All machines should contain a small DMDX testscript, which should be used to check the proper functioning of the button box, the headphones and the projection system. |
There are three video modes available for DMDX: ||1024 * 768 ||16 bit ||0 Hz || ||1024 * 768 ||16 bit ||60 Hz || ||1024 * 768 ||32 bit ||60 Hz || |
Line 98: | Line 82: |
There are three video modes available for DMDX: | |
Line 100: | Line 83: |
|| 1024 * 768 || 16 bit || 0 Hz || || 1024 * 768 || 16 bit || 60 Hz || || 1024 * 768 || 32 bit || 60 Hz || |
|
Line 104: | Line 84: |
The first mode is only installed for compatibility. It should not be used. The 0 Hz indicates that the 'default' refresh rate is used, which is usually the refresh rate that is set for Windows. This will always be 60 Hz too, so identical to the second mode. But it is still better to explicitly set the refresh rate. People have had trouble with this before, when someone changed the Windows display settings. People do fiddle. |
The first mode is only installed for compatibility. It should not be used. The 0 Hz indicates that the 'default' refresh rate is used, which is usually the refresh rate that is set for Windows. This will always be 60 Hz too, so identical to the second mode. But it is still better to explicitly set the refresh rate. People have had trouble with this before, when someone changed the Windows display settings. People do fiddle. |
Line 113: | Line 88: |
The third one will give better colour, so should be used when pictures are being presented. It also has the advantage that it is completely identical to the Windows settings, meaning that there will be no mode switching, which could prevent problems, certainly with flat screens and projectors. |
The third one will give better colour, so should be used when pictures are being presented. It also has the advantage that it is completely identical to the Windows settings, meaning that there will be no mode switching, which could prevent problems, certainly with flat screens and projectors. |
Line 118: | Line 90: |
So, to summarise, the best mode to use is the last one, which should be specified in your DMDX script like this: |
So, to summarise, the best mode to use is the last one, which should be specified in your DMDX script like this: |
Line 124: | Line 95: |
or | |
Line 125: | Line 97: |
or {{{ |
{{{ |
Line 130: | Line 100: |
Additionally, I would like to repeat the need to use QPIO12 with the current setup, instead of PIO12. |
Additionally, I would like to repeat the need to use QPIO12 with the current setup, instead of PIO12. |
Line 137: | Line 105: |
or | |
Line 138: | Line 107: |
or {{{ |
{{{ |
Line 143: | Line 110: |
Line 145: | Line 111: |
Line 156: | Line 121: |
||<tablewidth="37%"19%>'''Freq (Hz)''' ||<28%>'''H1''' ||<25%>'''H2''' ||<28%>'''H3''' || ||<19%>250 ||<28%>92.97 ||<25%>73.86 ||<28%>74.39 || ||<19%>500 ||<28%>98.07 ||<25%>74.34 ||<28%>65.58 || ||<19%>1000 ||<28%>98.10 ||<25%>59.20 ||<28%>27.16 || ||<19%>2000 ||<28%>68.61 ||<25%>32.10 ||<28%>9.38 || ||<19%>3000 ||<28%>47.24 ||<25%>5.0 ||<28%>15.82 || ||<19%>4000 ||<28%>49.99 ||<25%>5.05 ||<28%>13.53 || ||<19%>6000 ||<28%>27.88 ||<25%>11.57 ||<28%>7.97 || ||<19%>8000 ||<28%>23.03 ||<25%>8.50 ||<28%>7.78 || |
|
Line 157: | Line 131: |
||<tablewidth="37%"19%>'''Freq (Hz)'''||<28%>'''H1'''||<25%>'''H2'''||<28%>'''H3'''|| ||<19%>250||<28%>92.97||<25%>73.86||<28%>74.39|| ||<19%>500||<28%>98.07||<25%>74.34||<28%>65.58|| ||<19%>1000||<28%>98.10||<25%>59.20||<28%>27.16|| ||<19%>2000||<28%>68.61||<25%>32.10||<28%>9.38|| ||<19%>3000||<28%>47.24||<25%>5.0||<28%>15.82|| ||<19%>4000||<28%>49.99||<25%>5.05||<28%>13.53|| ||<19%>6000||<28%>27.88||<25%>11.57||<28%>7.97|| ||<19%>8000||<28%>23.03||<25%>8.50||<28%>7.78|| |
|
Line 170: | Line 138: |
'''Headphone simulator/pre-emphasis tool ''' Here is a tool that allows you to do two things: (1) approximately simulate what your stimuli will sound like in the scanner (2) pre-emphasise your stimuli, boosting the frequencies that will be reduced by the presentation system |
'''Headphone simulator/pre-emphasis tool ''' Here is a tool that allows you to do two things: (1) approximately simulate what your stimuli will sound like in the scanner (2) pre-emphasise your stimuli, boosting the frequencies that will be reduced by the presentation system |
Line 178: | Line 143: |
Line 186: | Line 150: |
||<tablewidth="577px"11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''LEFT''' ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''RIGHT''' ||<11% height="20px" style="vertical-align:top"> || ||<11% height="19px" style="vertical-align:top"> ||||<22% height="19px" style="text-align:center;vertical-align:top">Amplitude dB SPL ||<11% height="19px" style="vertical-align:top"> ||<11% height="19px" style="vertical-align:top"> ||<11% height="19px" style="vertical-align:top"> ||||<22% height="19px" style="text-align:center;vertical-align:top">Amplitude dB SPL ||<11% height="19px" style="vertical-align:top"> || ||<11% height="20px" style="vertical-align:top">Freq (Hz) ||<11% height="20px" style="vertical-align:top">H1 ||<11% height="20px" style="vertical-align:top">H2 ||<11% height="20px" style="vertical-align:top">H3 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">Freq (Hz) ||<11% height="20px" style="vertical-align:top">H1 ||<11% height="20px" style="vertical-align:top">H2 ||<11% height="20px" style="vertical-align:top">H3 || ||<11% height="20px" style="vertical-align:top">'''250''' ||<11% height="20px" style="vertical-align:top">107.42 ||<11% height="20px" style="vertical-align:top">32.60 ||<11% height="20px" style="vertical-align:top">55.82 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''250''' ||<11% height="20px" style="vertical-align:top">106.34 ||<11% height="20px" style="vertical-align:top">44.63 ||<11% height="20px" style="vertical-align:top">57.80 || ||<11% height="20px" style="vertical-align:top">'''500''' ||<11% height="20px" style="vertical-align:top">101.45 ||<11% height="20px" style="vertical-align:top">47.69 ||<11% height="20px" style="vertical-align:top">61.46 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''500''' ||<11% height="20px" style="vertical-align:top">100.60 ||<11% height="20px" style="vertical-align:top">48.40 ||<11% height="20px" style="vertical-align:top">62.30 || ||<11% height="20px" style="vertical-align:top">'''1000''' ||<11% height="20px" style="vertical-align:top">102.99 ||<11% height="20px" style="vertical-align:top">56.90 ||<11% height="20px" style="vertical-align:top">53.20 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''1000''' ||<11% height="20px" style="vertical-align:top">101.78 ||<11% height="20px" style="vertical-align:top">57.40 ||<11% height="20px" style="vertical-align:top">53.25 || ||<11% height="20px" style="vertical-align:top">'''2000''' ||<11% height="20px" style="vertical-align:top">94.66 ||<11% height="20px" style="vertical-align:top">61.65 ||<11% height="20px" style="vertical-align:top">25.43 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''2000''' ||<11% height="20px" style="vertical-align:top">94.20 ||<11% height="20px" style="vertical-align:top">61.10 ||<11% height="20px" style="vertical-align:top">26.60 || ||<11% height="20px" style="vertical-align:top">'''3000''' ||<11% height="20px" style="vertical-align:top">90.59 ||<11% height="20px" style="vertical-align:top">50.25 ||<11% height="20px" style="vertical-align:top">20.10 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''3000''' ||<11% height="20px" style="vertical-align:top">90.30 ||<11% height="20px" style="vertical-align:top">51.20 ||<11% height="20px" style="vertical-align:top">22.95 || ||<11% height="20px" style="vertical-align:top">'''4000''' ||<11% height="20px" style="vertical-align:top">85.30 ||<11% height="20px" style="vertical-align:top">30.40 ||<11% height="20px" style="vertical-align:top">2.38 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''4000''' ||<11% height="20px" style="vertical-align:top">85.06 ||<11% height="20px" style="vertical-align:top">33.50 ||<11% height="20px" style="vertical-align:top">2.79 || ||<11% height="20px" style="vertical-align:top">'''6000''' ||<11% height="20px" style="vertical-align:top">62.82 ||<11% height="20px" style="vertical-align:top">20.54 ||<11% height="20px" style="vertical-align:top">0.30 ||<11% height="20px" style="vertical-align:top"> ||<11% height="20px" style="vertical-align:top">'''6000''' ||<11% height="20px" style="vertical-align:top">62.27 ||<11% height="20px" style="vertical-align:top">18.24 ||<11% height="20px" style="vertical-align:top">2.41 || ||<11% height="21px" style="vertical-align:top">'''8000''' ||<11% height="21px" style="vertical-align:top">45.28 ||<11% height="21px" style="vertical-align:top">6.53 ||<11% height="21px" style="vertical-align:top">5.90 ||<11% height="21px" style="vertical-align:top"> ||<11% height="21px" style="vertical-align:top">'''8000''' ||<11% height="21px" style="vertical-align:top">47.40 ||<11% height="21px" style="vertical-align:top">5.45 ||<11% height="21px" style="vertical-align:top">5.04 || |
|
Line 187: | Line 162: |
||<tablewidth="577px"^ 11% height="20px"> ||<^ 11% height="20px"> ||<^ 11% height="20px">'''LEFT''' ||<^ 11% height="20px"> ||<^ 11% height="20px"> ||<^ 11% height="20px"> ||<^ 11% height="20px"> ||<^ 11% height="20px">'''RIGHT''' ||<^ 11% height="20px"> || ||<^ 11% height="19px"> ||||<^ 22% height="19px">Amplitude dB SPL ||<^ 11% height="19px"> ||<^ 11% height="19px"> ||<^ 11% height="19px"> ||||<^ 22% height="19px">Amplitude dB SPL ||<^ 11% height="19px"> || ||<^ 11% height="20px">Freq (Hz) ||<^ 11% height="20px">H1 ||<^ 11% height="20px">H2 ||<^ 11% height="20px">H3 ||<^ 11% height="20px"> ||<^ 11% height="20px">Freq (Hz) ||<^ 11% height="20px">H1 ||<^ 11% height="20px">H2 ||<^ 11% height="20px">H3 || ||<^ 11% height="20px">'''250''' ||<^ 11% height="20px">107.42 ||<^ 11% height="20px">32.60 ||<^ 11% height="20px">55.82 ||<^ 11% height="20px"> ||<^ 11% height="20px">'''250''' ||<^ 11% height="20px">106.34 ||<^ 11% height="20px">44.63 ||<^ 11% height="20px">57.80 || ||<^ 11% height="20px">'''500''' ||<^ 11% height="20px">101.45 ||<^ 11% height="20px">47.69 ||<^ 11% height="20px">61.46 ||<^ 11% height="20px"> ||<^ 11% height="20px">'''500''' ||<^ 11% height="20px">100.60 ||<^ 11% height="20px">48.40 ||<^ 11% height="20px">62.30 || ||<^ 11% height="20px">'''1000''' ||<^ 11% height="20px">102.99 ||<^ 11% height="20px">56.90 ||<^ 11% height="20px">53.20 ||<^ 11% height="20px"> ||<^ 11% height="20px">'''1000''' ||<^ 11% height="20px">101.78 ||<^ 11% height="20px">57.40 ||<^ 11% height="20px">53.25 || ||<^ 11% height="20px">'''2000''' ||<^ 11% height="20px">94.66 ||<^ 11% height="20px">61.65 ||<^ 11% height="20px">25.43 ||<^ 11% height="20px"> ||<^ 11% height="20px">'''2000''' ||<^ 11% height="20px">94.20 ||<^ 11% height="20px">61.10 ||<^ 11% height="20px">26.60 || ||<^ 11% height="20px">'''3000''' ||<^ 11% height="20px">90.59 ||<^ 11% height="20px">50.25 ||<^ 11% height="20px">20.10 ||<^ 11% height="20px"> ||<^ 11% height="20px">'''3000''' ||<^ 11% height="20px">90.30 ||<^ 11% height="20px">51.20 ||<^ 11% height="20px">22.95 || ||<^ 11% height="20px">'''4000''' ||<^ 11% height="20px">85.30 ||<^ 11% height="20px">30.40 ||<^ 11% height="20px">2.38 ||<^ 11% height="20px"> ||<^ 11% height="20px">'''4000''' ||<^ 11% height="20px">85.06 ||<^ 11% height="20px">33.50 ||<^ 11% height="20px">2.79 || ||<^ 11% height="20px">'''6000''' ||<^ 11% height="20px">62.82 ||<^ 11% height="20px">20.54 ||<^ 11% height="20px">0.30 ||<^ 11% height="20px"> ||<^ 11% height="20px">'''6000''' ||<^ 11% height="20px">62.27 ||<^ 11% height="20px">18.24 ||<^ 11% height="20px">2.41 || ||<^ 11% height="21px">'''8000''' ||<^ 11% height="21px">45.28 ||<^ 11% height="21px">6.53 ||<^ 11% height="21px">5.90 ||<^ 11% height="21px"> ||<^ 11% height="21px">'''8000''' ||<^ 11% height="21px">47.40 ||<^ 11% height="21px">5.45 ||<^ 11% height="21px">5.04 || '''Headphone simulator/pre-emphasis tool ''' I have made a tool that allows you to do two things: (1) approximately simulate what your stimuli will sound like in the scanner (2) pre-emphasise your stimuli, boosting the frequencies that will be reduced by the presentation system This tool is described on [[http://www.mrc-cbu.cam.ac.uk/~rhodri/headphonesim.htm|this page]] |
'''Headphone simulator/pre-emphasis tool ''' I have made a tool that allows you to do two things: (1) approximately simulate what your stimuli will sound like in the scanner (2) pre-emphasise your stimuli, boosting the frequencies that will be reduced by the presentation system This tool is described on [[http://www.mrc-cbu.cam.ac.uk/~rhodri/headphonesim.htm|this page]] |
Line 205: | Line 168: |
If the previous two airtube systems will not satisfy your requirements, there is one other option available, a high quality electrostatic system from Nordic Neuro Labs. This has now passed safety evaluation and is available for use. This system provides high-quality stimulus delivery and is intended for studies in which optimal presentation of auditory stimuli is essential. |
If the previous two airtube systems will not satisfy your requirements, there is one other option available, a high quality electrostatic system from Nordic Neuro Labs. This has now passed safety evaluation and is available for use. This system provides high-quality stimulus delivery and is intended for studies in which optimal presentation of auditory stimuli is essential. |
Line 227: | Line 189: |
If there is a piece of equipment you'd like to see added, please contact Rhodri Cusack or Gary Chandler. | If there is a piece of equipment you'd like to see added, please contact Gary Chandler or Marta Correia. |
Line 229: | Line 191: |
If you would like access to the facility to install your programs or test the equipment, please contact mri.admin@mrc-cbu.cam.ac.uk. ''Last updated by Rhodri Cusack and Gary Chandler Feb 2006'' |
If you would like access to the facility to install your programs or test the equipment, please contact mri.admin@mrc-cbu.cam.ac.uk . |
Stimulus delivery in the CBU Tim Trio
Stimulus delivery computers
There are three stimulus delivery computers. All have identical software and receive the scanner trigger pulse and button box responses.
Software
The machines run Windows XP. Installed software is Matlab, Eprime, Visual Basic, Cogent, Psychophysics Toolbox, DMDX.
Synchronising with scanner
From Eprime and VB, you may use the parallel port to synchronise, and to collect button box responses.
From Matlab, National Instruments PCI 6503 card is used to capture all pulses (scanner synch pulse and button pulses alike). You can access its functions via ScannerSynch and MEGSynch.
Parallel port
There's now also the possibility of using the parallel port as an input/output device in your experiment. For the moment only the leftmost stimulus presentation machine has this option. All signals will be send to both the Keithly PIO card and the parallel port.
BEWARE!! All signals coming from the parallel port are inverted as compared to the PIO signals. This means that a button press will show as a button release! This can be solved quite simply by setting the 'Invert' property in the port device properties dialog in E-Prime.
As the scanner pulse is inverted compared to the other buttons, this will now still be the wrong way around, sadly. The simplest way to solve this is to enable two 'Port' devices in E-Prime, one inverted for the buttons and one not inverted for the scanner pulses.
The parallel port can be used with E-Prime, without the need for extra libraries or explicit coding in your scripts. There's also a little test program on the machines, called 'PortTest', which will show all incoming signals from both PIO and parallel port.
For more information contact Maarten.
Setting up the parallel port for E-Prime
NOTE: the following applies to EPrime2 only. It may be possible to do it in EPrime too, but this has not been tested. So if you want to use the ParallelPort as a trigger, please use EPrime2 (professional).
Configuring E-Prime is relatively easy (this was done with a release candidate for E-Prime2). Say you want to configure E-Prime to get input from the parallel port for both response box and scanner pule. First, enable in your project 2 ParallelPort devices (apprently EPrime is touchy about the names you give to devices, so if possible just leave the default names, i.e. ParallelPort and ParallelPort2). For both devices set the port mode to be on Input and the address to be &H379 (not 378 -- this will make the input numbering easier to use in E-Prime). The device you want to use for the ButtonBox should also be inverted (as mentioned above). Now that you have two parallel port devices enabled, all you need to know is that the scanner pulse will be received as a number 8, while the four fingers of the right hand will be (from index to pinky) 7,6,5,4.
At this point you can just set your starting screen to pause until an 8 is received from the appropriate parallelport device, and that will trigger your stimuli as soon as a scanner pulse comes in. However, make sure that screens that need response via button box do not allow the number 8, or each trigger will seem like a response to E-Prime and your data will be of little use!
For more information contact MartinMonti
Mimic machine
In the CBU computer user room there is a "CBU mimic" configured exactly as the stimulus delivery machines, and with a pulse generator to simulator the scanner trigger, and a response box. You must test your programs thoroughly on the mimic before running any experiment.
Pre-testing machine
There is another mimic machine in the imaging centre, which you may use for pre-testing in experiments that require a training session just before the scan. You'll then need to have two experiments attend.
Visual presentation: Christie video projector
Recommended resolution 1024x768
Refresh rate 60 Hz. Please do not change this parameter. Although the projector will accept inputs up to 100 Hz, it will not actually produce output at these higher rates, but instead, sub-sample down to a rate just above 60 Hz.
Latency: There is a fixed temporal delay between computer refresh and actual display of a little less than 20 ms. If you don't account for this, your RTs are probably around 20 ms shorter than you think they are.
Size: Distance between MRI screen and mid-point of mirror = 823mm Approx distance between eyes and mid-point of mirror ~ 90mm Width of full-screen display on MRI screen = 268mm
This means the full screen display has a visual angle of 2 * arctan(268/2/(823+90)) = 0.29 radians = 16.7 degrees.
There are Matlab functions available for transforming visual angle to stimulus size, or the other way around.
Visual presentation: NNL LCD widescreen
Recommended resolution 1920x1080. You can also use 1024x768 but be careful to change the monitor aspect ratio appropriately using the physical buttons next to the display.
Refresh rate 60 Hz.
Latency Unknown at present. Assume similar to old projector.
Size Distance between subject and screen 1565mm
Width display on MRI screen = 698.4mm (25.16 degrees visual angle)
Width if using 4:3 aspect ratio = 522mm (18.94 degrees visual angle)
Height = 392.85mm (14.31 degrees visual angle)
Using Psychtoolbox with the NNL LCD screen
Note that if you are using the new LCD screen with anything other than the native resolution (1920x1080) Psychtoolbox's sync tests will fail, causing some fairly cryptic crashes when you attempt to Screen('OpenWindow'). The workaround is to include Screen('Preference','SkipSyncTests',1) in your script before opening the screen. But before applying this, please be very sure that your experiment really doesn't require any kind of reasonable display timing. Speak to Johan Carlin about this issue if unsure.
Using DMDX
All machines should contain a small DMDX testscript, which should be used to check the proper functioning of the button box, the headphones and the projection system.
There are three video modes available for DMDX:
1024 * 768 |
16 bit |
0 Hz |
1024 * 768 |
16 bit |
60 Hz |
1024 * 768 |
32 bit |
60 Hz |
The first mode is only installed for compatibility. It should not be used. The 0 Hz indicates that the 'default' refresh rate is used, which is usually the refresh rate that is set for Windows. This will always be 60 Hz too, so identical to the second mode. But it is still better to explicitly set the refresh rate. People have had trouble with this before, when someone changed the Windows display settings. People do fiddle.
The second mode is the one that has always been recommended for most users.
The third one will give better colour, so should be used when pictures are being presented. It also has the advantage that it is completely identical to the Windows settings, meaning that there will be no mode switching, which could prevent problems, certainly with flat screens and projectors.
So, to summarise, the best mode to use is the last one, which should be specified in your DMDX script like this:
<VideoMode 1024, 768, 768, 32, 60>
or
<vm 1024, 768, 768, 32, 60>
Additionally, I would like to repeat the need to use QPIO12 with the current setup, instead of PIO12.
<InputDevice "QPIO12" 1>
or
<id "QPIO12" 1>
Auditory presentation
When presenting auditory stimuli at the CBU, you have a choice of three different headphone systems. Unless otherwise specified, the radiographers will provide you with the Siemens tube phone system for communicating with your volunteer. However, for studies in which quality sound reproduction is required, there are two other systems available that will likely be preferred.
Whichever system you use, it is important that you use good quality audio recordings in which the stimuli span use the full dynamic range available. If you don't understand what this means, you should read this page.
Option 1: Siemens tube phones
For many experiments in the scanner that require sound, but not too much audio fidelity, the built-in Siemens tube phones are sufficient.
Frequency response
Sound level set to max on PC and 9 bars on the scanner. Tones at various frequencies were then presented. The levels (in dB SPL) of the primary (H1) and first and second harmonics were:
Freq (Hz) |
H1 |
H2 |
H3 |
250 |
92.97 |
73.86 |
74.39 |
500 |
98.07 |
74.34 |
65.58 |
1000 |
98.10 |
59.20 |
27.16 |
2000 |
68.61 |
32.10 |
9.38 |
3000 |
47.24 |
5.0 |
15.82 |
4000 |
49.99 |
5.05 |
13.53 |
6000 |
27.88 |
11.57 |
7.97 |
8000 |
23.03 |
8.50 |
7.78 |
The full frequency response as measured using periodic noise from a spectrum analyzer:
Headphone simulator/pre-emphasis tool Here is a tool that allows you to do two things: (1) approximately simulate what your stimuli will sound like in the scanner (2) pre-emphasise your stimuli, boosting the frequencies that will be reduced by the presentation system
A new tool for pre-emphasis has been produced by Christopher Long, which does not produce a subtle ringing artefact produced by the previous tool. This is described here
The old tool is described on this page:
Option 2: Etymotic ER3
This alternative pneumatic tube presentation system offers higher quality. It is being installed in Mar 2006.
Frequency response
Gary Chandler kindly made these measurements:
|
|
LEFT |
|
|
|
|
RIGHT |
|
|
Amplitude dB SPL |
|
|
|
Amplitude dB SPL |
|
||
Freq (Hz) |
H1 |
H2 |
H3 |
|
Freq (Hz) |
H1 |
H2 |
H3 |
250 |
107.42 |
32.60 |
55.82 |
|
250 |
106.34 |
44.63 |
57.80 |
500 |
101.45 |
47.69 |
61.46 |
|
500 |
100.60 |
48.40 |
62.30 |
1000 |
102.99 |
56.90 |
53.20 |
|
1000 |
101.78 |
57.40 |
53.25 |
2000 |
94.66 |
61.65 |
25.43 |
|
2000 |
94.20 |
61.10 |
26.60 |
3000 |
90.59 |
50.25 |
20.10 |
|
3000 |
90.30 |
51.20 |
22.95 |
4000 |
85.30 |
30.40 |
2.38 |
|
4000 |
85.06 |
33.50 |
2.79 |
6000 |
62.82 |
20.54 |
0.30 |
|
6000 |
62.27 |
18.24 |
2.41 |
8000 |
45.28 |
6.53 |
5.90 |
|
8000 |
47.40 |
5.45 |
5.04 |
Headphone simulator/pre-emphasis tool I have made a tool that allows you to do two things: (1) approximately simulate what your stimuli will sound like in the scanner (2) pre-emphasise your stimuli, boosting the frequencies that will be reduced by the presentation system This tool is described on this page
Option 3: NNL Electrostatic Headphones
If the previous two airtube systems will not satisfy your requirements, there is one other option available, a high quality electrostatic system from Nordic Neuro Labs. This has now passed safety evaluation and is available for use. This system provides high-quality stimulus delivery and is intended for studies in which optimal presentation of auditory stimuli is essential.
Since optimal audio reproduction is not compatible with the use of ear-plugs, the NNL headphones are typically used without any additional hearing protection. They will therefore not attenuate scanner noise as effectively as using the etymotic system in combination with ear defenders. Although experience has shown that using the NNL headphone without earplugs does not produce uncomfortable sound levels, it would generally be better to use the NNL headphones only for studies which use sparse imaging.
Button box
The default box has four buttons designed to be used from one hand or two.
Microphone
We have a Phonar optical noise cancelling microphone that allows clear recordings of spoken responses without much interference from the scanner noise.
Physiological measurements
Instructions for recording skin conductance can be found here: SCR_fMRI-manual.doc, and here: fMRI_compatible_SCR_recording-CBU.ppt (with thanks to Sonia Bishop)
The same hardware can probably be used for cardiac or respiratory monitoring.
Eye tracking
We have a 50 Hz SMI eye tracking system for MRI on site. See the Eye tracking Wiki for more information.
Points of contact
Gary Chandler, who set up almost all of this equipment, is the best person to ask if you'd like an update on any changes to the system, or if something doesn't work.
If there is a piece of equipment you'd like to see added, please contact Gary Chandler or Marta Correia.
If you would like access to the facility to install your programs or test the equipment, please contact mri.admin@mrc-cbu.cam.ac.uk .