You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mk_level1_fsf.py contains this bit in the part that generates custom contrasts.
for evt in range(nevs):
if contrasts[c][evt]!=0:
outfile.write('set fmri(con_real%d.%d) %s\n'%(contrastctr,con_real_ctr,contrasts[c][evt]))
outfile.write('set fmri(con_real%d.%d) 0\n'%(contrastctr,con_real_ctr+1))
con_real_ctr+=2
else:
outfile.write('set fmri(con_real%d.%d) 0\n'%(contrastctr,evt+1))
I am not sure whether I fully grok it, but isn't it necessary to increment the con_real_ctr regardless of whether a particular contrast vector element is zero? Otherwise it seems to mess of the con_real specification with duplicate IDs. Moreover, why does it need this special case at all? It should be safe to write out the con_real pair even when the value is zero.
Sorry if this is a false alarm.
The text was updated successfully, but these errors were encountered:
mk_level1_fsf.py contains this bit in the part that generates custom contrasts.
I am not sure whether I fully grok it, but isn't it necessary to increment the con_real_ctr regardless of whether a particular contrast vector element is zero? Otherwise it seems to mess of the con_real specification with duplicate IDs. Moreover, why does it need this special case at all? It should be safe to write out the con_real pair even when the value is zero.
Sorry if this is a false alarm.
The text was updated successfully, but these errors were encountered: