Millisecond Forums » Millisecond Forums » Inquisit 7 » Issues converting script from Inquisit 6 to Inquisit 7

Issues converting script from Inquisit 6 to Inquisit 7

vb7 — Thu, 11 Dec 2025 15:13:55 GMT

Hello,
I am adapting an existing script to make a slightly different task, and in the process change to Inquisit 7. The inquisit website claims that Inquisit 7 is backwards compatible, but this does not seem to be the case. In particular, I am getting many "Expression contains an invalid identifier" errors, and I can't find what is causing those errors. Attached is 1) a screenshot of the first set of error messages I am receiving, and 2) the script I am editing.
Thank you.

RE: Issues converting script from Inquisit 6 to Inquisit 7

Dave — Thu, 11 Dec 2025 15:13:55 GMT

+x[quote]

[b]vb7 - 12/11/2025[/b]
+x[quote]

[b]Dave - 12/11/2025[/b]
+x[quote]

[b]vb7 - 12/10/2025[/b]
Hello,
I am adapting an existing script to make a slightly different task, and in the process change to Inquisit 7. The inquisit website claims that Inquisit 7 is backwards compatible, but this does not seem to be the case. In particular, I am getting many "Expression contains an invalid identifier" errors, and I can't find what is causing those errors. Attached is 1) a screenshot of the first set of error messages I am receiving, and 2) the script I am editing.
Thank you.
[/quote]

Inquisit 7 can run legacy IQX files. The problem with the file you attached has nothing to do with Inquisit 7, the same errors are thrown under Inquisit 6. You have parser-breaking mistakes in the script, which cause the parser to effectively not see and be unable to parse elements below a certain point in the script. Because the parser cannot find all the elements that follow, it throws errors regarding them.

There are also various syntax mistakes (e.g. using square brackets where parentheses ought to be used) and elements that are simply missing / not at all defined in the script.

Attached is a fixed up version, that should at least properly parse the things that are actually there.
[/quote]

Thank you! That does indeed work.

Do you have any tips for how to determine where the parser is breaking? I see that I had introduced a formatting error with the trialList list, but even with that fixed the errors are still thrown. I am assuming this is from commenting out some parts of some trials and not others while editing the script - but would it be best to just go through the script rather than relying on the errors then? For example, it's not clear how the commented out code is causing the first error ("'values.selectedstim' Expression contains an invalid identifier." for element "trial.choiceFramePracticeFull" and attribute "ontrialbegin").
[/quote]

There is no super easy way to trace such problems. What works reasonably well is:
Going through the list of errors, find the first element -- in terms of line # in the script -- for which an error is thrown, although the element is present. The parser-breaking problem should be above that line of code in the script, usually very near it

RE: Issues converting script from Inquisit 6 to Inquisit 7

vb7 — Thu, 11 Dec 2025 15:07:31 GMT

+x[quote]

[b]Dave - 12/11/2025[/b]
+x[quote]

[b]vb7 - 12/10/2025[/b]
Hello,
I am adapting an existing script to make a slightly different task, and in the process change to Inquisit 7. The inquisit website claims that Inquisit 7 is backwards compatible, but this does not seem to be the case. In particular, I am getting many "Expression contains an invalid identifier" errors, and I can't find what is causing those errors. Attached is 1) a screenshot of the first set of error messages I am receiving, and 2) the script I am editing.
Thank you.
[/quote]

Inquisit 7 can run legacy IQX files. The problem with the file you attached has nothing to do with Inquisit 7, the same errors are thrown under Inquisit 6. You have parser-breaking mistakes in the script, which cause the parser to effectively not see and be unable to parse elements below a certain point in the script. Because the parser cannot find all the elements that follow, it throws errors regarding them.

There are also various syntax mistakes (e.g. using square brackets where parentheses ought to be used) and elements that are simply missing / not at all defined in the script.

Attached is a fixed up version, that should at least properly parse the things that are actually there.
[/quote]

Thank you! That does indeed work.

Do you have any tips for how to determine where the parser is breaking? I see that I had introduced a formatting error with the trialList list, but even with that fixed the errors are still thrown. I am assuming this is from commenting out some parts of some trials and not others while editing the script - but would it be best to just go through the script rather than relying on the errors then? For example, it's not clear how the commented out code is causing the first error ("'values.selectedstim' Expression contains an invalid identifier." for element "trial.choiceFramePracticeFull" and attribute "ontrialbegin").

RE: Issues converting script from Inquisit 6 to Inquisit 7

Dave — Thu, 11 Dec 2025 03:43:44 GMT

+x[quote]

[b]vb7 - 12/10/2025[/b]
Hello,
I am adapting an existing script to make a slightly different task, and in the process change to Inquisit 7. The inquisit website claims that Inquisit 7 is backwards compatible, but this does not seem to be the case. In particular, I am getting many "Expression contains an invalid identifier" errors, and I can't find what is causing those errors. Attached is 1) a screenshot of the first set of error messages I am receiving, and 2) the script I am editing.
Thank you.
[/quote]

Inquisit 7 can run legacy IQX files. The problem with the file you attached has nothing to do with Inquisit 7, the same errors are thrown under Inquisit 6. You have parser-breaking mistakes in the script, which cause the parser to effectively not see and be unable to parse elements below a certain point in the script. Because the parser cannot find all the elements that follow, it throws errors regarding them.

There are also various syntax mistakes (e.g. using square brackets where parentheses ought to be used) and elements that are simply missing / not at all defined in the script.

Attached is a fixed up version, that should at least properly parse the things that are actually there.