double asterisk from make stim time

AFNI Message Board
1

Hello,

I’m using make stim time to generate our timing files and some of our conditions only occur in later runs. In the past when I’ve done this I have seen a single asterisk in the empty run, but this time if the first run is empty for that condition, I get a double asterisk. Why is only the first run marked with a double asterisk and is this an issue (see below for example)?

Thank you so much for your help!
Lea

more pilot_001_stimtimes.03.Go.1D

10.0 14.0 18.0 24.0 28.0 32.0 42.0 46.0 54.0 58.0 78.0 86.0 90.0 94.0 100.0 104.0 116.0 120.0 124.0 128.0 132.0 136.0 140.0 144.0 148.0 154.0 160.0 168.0 172.0 178.0 182.0 188.0 192.0 212.0 220.0 226.0 230.0 234.0 238.0 248.0 252.0 256.0 260.0 270.0 274.0 278.0 286.0 290.0 302.0 306.0 314.0 326.0 332.0 336.0 342.0 352.0 356.0 360.0 364.0 368.0 372.0 382.0 386.0 390.0 400.0 412.0 416.0 420.0 428.0 438.0 442.0 448.0 452.0 458.0 466.0 470.0 474.0 478.0 482.0 488.0 492.0 498.0 510.0 514.0 518.0 526.0 536.0 540.0 546.0 554.0 560.0 564.0 568.0 584.0 588.0
*
*

2

Hi Lea,

The double asterisk is not a problem, it is just a precaution.
In case the maximum number of events in a run is one, the
double asterisk will still tell 3dDeconvolve to use local timing
(one row per run). If there are more events than just one in
any run, local timing will be assumed, and the double asterisk
will not make any difference.

If some runs had zero events, the rest had one, and only
single asterisks were used, the timing might be incorrectly
interpreted as being global.

  • rick
3

Hi Rick,

Thank you so much for getting back to me about this!

Lea