AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
April 24, 2014 11:30AM
Those are very long blocks, which might make your
results noisy, especially as the polort degree gets
bigger.

Ignoring that, the basic point here is that you
should use duration modulation, probably via the
dmBLOCK(1) basis function.

1. The stimulus timing files would be sequences of
event:duration elements, where one row is a run, e.g.
41.028:138.801 292.071:82.955
... other runs ...

2. The stimulus types would be AM1 (either via the GUI
or via afni_proc.py -regress_stim_types).

3. The basis function might be 'dmBLOCK(1)'. There is
no 'choose' option for that in the GUI, but you can
still type it in the 'init basis funcs' box and hit
<enter>.


So the main work is to generate timing files that are
in the form START:DURATION, rather than START:END as
you are currently using.

- rick
Subject Author Posted

Using proc.py to model block design w/ block times varying by subject

neurobie April 23, 2014 07:47PM

Re: Using proc.py to model block design w/ block times varying by subject

rick reynolds April 24, 2014 11:30AM