Running DMDX with Batch File


There are a few benefits to using batch files to run DMDX.  First, the batch file can be used to stop and start various processes that might otherwise interfere with DMDX timing (e.g., virus protection).  Second, this prevents the careless RA from accidently hitting "NO" to the Save data prompt at the end of the script.   Finally, it can reduce errors associated with selecting the correct item file for the appropriate experiment and run order and prevent the RA from forgetting to enter the SubID.  All good things.

There are two files that you will need to create to make this as simple as possible for Research Assistants.

The first is a shortcut that you will put on the desktop.  This shortcut is designed to start a dos shell and change the directory to the local directory where the batch file and DMDX item files reside.  Save this shortcut on the desktop of the DMDX computer.  Next, rename the file, replacing "experimentname" with the acronym for your experiment.  Finally, right click on the shortcut and select properties.  Replace "experimentname" in the Start In box with the acronym for your experiment.  Obviously, make sure this folder exists as well.  You should place all your DMDX files in this folder.

The second file you will need is the actual batchfile.  Downlioad this file into your c:\local\experimentname folder.  Rename it, replacing experiment name with the acronym for your experiment..   This batch expects two parameters, script order and subid.  It expects that there are two script orders, 1 & 2.  It also expects that SubIDs are >= 1000.  You may need to edit the file if you have different needs.   Finally, it stops and then restarts virus scan.  You may need to change the process name to match the name of the virus scan process on your computer.  You can find the name of this (and other processes you may want to stop) by opening Administrative Tools in the Control Panel and selecting Services.

I've provided test DMDX scripts for order 1 and order 2 to allow you to test this setup and record one trial of data to verify subid input, etc.

Further informaton about command line options is available in DMDX help