Problem with Batch-Files entering the subject-ID automatically

Back

Home
»
Millisecond Forums
»
Inquisit 4
»
Problem with Batch-Files entering the subject-ID automatically

Problem with Batch-Files entering the subject-ID automatically

Author	Message
MartinGK	MartinGK posted 12 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 4, Visits: 1	Hi everyone, our lab updated to Inquisit 4 last week and now there is a little problem with our batchfiles. We use external batchilfes outside of Inquisit´s batch-element, because we combine experiments with different experimental-software and assignment to conditions is accomplished via those files. This way, we automatically specify our subject-IDs, so that several modules can be started one after another without requiring a research assistant to type the subject-ID at the start of each single module. An example code for a module looks like that: ECHO CLS >> IL2%C%%A%%D%%B%.cmd ECHO ECHO Please wait... >> IL2%C%%A%%D%%B%.cmd ECHO "c:\\program files\\millisecond software\\inquisit 3\\inquisit.exe" "O:\SHARED\Human Lab\Studies\IL2\01_PictureStoryExercise\IL2_pse.exp" %C%%A%%D%%B% >> IL2%C%%A%%D%%B%.cmd ECHO CLS >> IL2%C%%A%%D%%B%.cmd But if I use Inquisit 4 instead of 3, the program wants the user-ID (and now a group number additionally) to be entered by hand again at the start of each module. Could the required group number cause this problem? And if so, how do I turn this feature off so that Inquisit only aks the subject-ID like in 3.0.6 or so? Or could I modify the batch-file in such a way that the group number is automatically entered as a constant and does not interfere with automatic testing anymore? Thanks and best regards, Martin
	Reply Like 19
Dave	Dave posted 12 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 108K	While you do have to supply both group and subject id as parameters to not receive a prompt (cf. the "How to Launch Inquisit Using Command Line Parameters" topic in the Inquisit 4 documentation), it seems to me that this functionality is actually partly broken in the current release. Supplying a script to launch as parameter works fine, however, any supplied group and subject ids aren't properly extracted and passed on (i.e., they are effectively ignored). I'll file a bug report ASAP. Thanks for pointing this out. Unfortunately I cannot think of any easy workaround for the time being: It's either (a) enter ids manually or (b) abandon the limited Windows batch file approach and switch to a more capable automation language (e.g., AutoIt) which supports filling out text boxes, etc. to enter the ids automatically. Best regards, ~Dave
	Reply Like 19
Dave	Dave posted 12 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 108K	I just learned that the command line syntax has changed for Inquisit 4. Unfortunately the documentation does not address those changes, i.e., it is wrong. The relevant parts of the new command line syntax convention is > "inquisitpath" "scriptpath" -s -g Example: To launch a script with e.g. subject id 42 and group id 2 use > "C:\Program Files\Millisecond Software\Inquisit 4\Inquisit.exe" "C:\MyFolder\MyScript.iqx" -s 42 -g 2 Regards, ~Dave
	Reply Like 18