| T O P I C R E V I E W |
| syam.gadde |
Posted - Aug 14 2006 : 12:07:50 PM
There was a bug in showplay2xml installed on golgi from July 31 to August 14 (this morning) that matched up timing and stimuli incorrectly in the output XML files. This was introduced in release 1.8.10 and fixed in release 1.8.14 (installed today). If you have used showplay2xml in the last two weeks, please check the timing in your output event XML files and regenerate them (you will have to redo any analysis that depends on this timing). Sorry for the inconvenience. Please reply to this forum topic if you have any questions about this issue. |
| 2 L A T E S T R E P L I E S (Newest First) |
| syam.gadde |
Posted - Aug 14 2006 : 12:28:28 PM
Anything grabbed from the .ppf file (duration, command [usually a stimulus file name], and stimulus code) will be mismatched to the stuff grabbed from the .out file (onset times, responses) by one stimulus event. If you only have stimulus events happening once every TR, then, yes, they will be off by one TR, but this will not be the case in general. More to the point, if your stimulus events are staggered, the timing error is different for every event and there is no way to reliably "fix" the timing by adding or subtracting a constant number of seconds. In any case, the responses will be associated with the wrong stimuli. If you look at the XML events files generated by the buggy version, you will notice that the command, duration, and code of the actual first event is mistakenly put at the end and those values for events other than the first are shifted earlier by one event.
I am happy to provide further assistance if you have any more questions. |
| ckim |
Posted - Aug 14 2006 : 12:12:11 PM
Is it a matter of all the timing being off by one TR or something? Or will the errors be randomly scattered throughout? |
|
|
