This is usually caused by some syntax issue on the previous line that causes some disruption in the reading of the input file. In this case, it seems you have an extra bit of type after the row terminator (*) on the previous line.
This is usually caused by some syntax issue on the previous line that causes some disruption in the reading of the input file. In this case, it seems you have an extra bit of type after the row terminator (*) on the previous line.
Last edited by jarvis24; 11-24-2005 at 02:23 PM.
[edited from support email]
The Direct RT program keeps telling me that I have a missing value in row 25 yet it is identical to all other rows. I was wondering if you could look at it and tell me what you think the problem is.
Same deal.. looks like there is some some extra text in column V which is after the row terminator (*)--I expect it's impacting the reading of the input. Try clearing that text and then running it and see if that resolves it.
[related response to a edited support email]
In row 2, you've got double quotes around your text stimulus. Try removing the double quotes and replacing them with a single ~ characater at the start of the string, i.e., instead of... When I run it, I get the message to the effect that the row 3 has an error in LOC (location) column. But when I review the file, I don't see anything that is extraordinary in the row 3.
"We're interested..."
try
~We're interested...
Double quotes, commas, and to a lesser extent, single quotes can sometime interact with other input file attributes to cause a problem when DirectRT tries to read the file. Additionally, the lack of a ~ in this case would have DirectRT looking for an image file called "We're interested in how well you can learn these pictures..."!
-Blair