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  

|
Anonymous User
August 28, 2012 10:46PM
Hi Rick

Thanks for getting back to me. Voxel size in the stats dataset looks to be consistent with this (see 1). I've also pasted the out.ss.. file (see 2).

So do you think the lengthy processing speed is to with this size of grid? Any suggestions as to how I can speed things up and get going with this analysis would be great.


1.
Dataset File: stats.CRD_001+tlrc
Identifier Code: XYZ_ndXBzESiPWTx5RLsmB40Hg Creation Date: Sun Aug 26 00:34:34 2012
Template Space: TLRC
Dataset Type: Func-Bucket (-fbuc)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK
Storage Space: 84,360,000 (84 million) bytes
Geometry String: "MATRIX(2,0,0,-79,0,2,0,-79,0,0,2,-64):80,95,75"
Data Axes Tilt: Plumb
Data Axes Orientation:
first (x) = Right-to-Left
second (y) = Anterior-to-Posterior
third (z) = Inferior-to-Superior [-orient RAI]
R-to-L extent: -79.000 [R] -to- 79.000 [L] -step- 2.000 mm [ 80 voxels]
A-to-P extent: -79.000 [A] -to- 109.000 [P] -step- 2.000 mm [ 95 voxels]
I-to-S extent: -64.000 -to- 84.000 -step- 2.000 mm [ 75 voxels]
Number of values stored at each pixel = 37


2.

subject ID : CRD_001
TRs removed (per run) : 0
num stim classes provided : 12
final anatomy dset : anat_final.CRD_001+tlrc.HEAD
final stats dset : stats.CRD_001+tlrc.HEAD
final voxel resolution : 2.000000 2.000000 2.000000

motion limit : 0.3
average motion (per TR) : 0.0506082
num TRs above mot limit : 1
max motion displacement : 4.49427
max censored displacement : 4.49427
outlier limit : 0.3
average outlier frac (TR) : 0.00111181
num TRs above out limit : 0

*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r01.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r01.tcat+orig.BRIK is 35.600002 degrees from plumb.
*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r02.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r02.tcat+orig.BRIK is 35.600002 degrees from plumb.
*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r03.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r03.tcat+orig.BRIK is 35.600002 degrees from plumb.
*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r04.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r04.tcat+orig.BRIK is 35.600002 degrees from plumb.
*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r05.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r05.tcat+orig.BRIK is 35.600002 degrees from plumb.
*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r06.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r06.tcat+orig.BRIK is 35.600002 degrees from plumb.
*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r07.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r07.tcat+orig.BRIK is 35.600002 degrees from plumb.
*+ WARNING: If you are performing spatial transformations on an oblique dset,
such as ./pb00.CRD_001.r08.tcat+orig.BRIK,
or viewing/combining it with volumes of differing obliquity,
you should consider running:
3dWarp -deoblique
on this and other oblique datasets in the same session.
See 3dWarp -help for details.
++ Oblique dataset:./pb00.CRD_001.r08.tcat+orig.BRIK is 35.600002 degrees from plumb.
num runs found : 8
num TRs per run : 180 180 180 180 180 180 180 180
TRs total (uncensored) : 1440

TRs censored : 2
censor fraction : 0.001389
num regs of interest : 12
num TRs per stim : 594 156 35 185 64 64 449 455 441 451 944 1259
num TRs censored per stim : 1 0 0 0 0 0 0 0 2 2 0 2
fraction TRs censored : 0.002 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.005 0.004 0.000 0.002

TSNR average : 151.573
maximum F-stat : 101.254
blur estimates : 5.16298 5.29133 5.45028
Subject Author Posted

afni_proc.py - processing speed issue

David August 26, 2012 01:12AM

Re: afni_proc.py - processing speed issue

Peter Molfese August 26, 2012 09:26AM

Re: afni_proc.py - processing speed issue

Daniel Glen August 26, 2012 10:49AM

Re: afni_proc.py - processing speed issue

rick reynolds August 26, 2012 10:44AM

Re: afni_proc.py - processing speed issue

Anonymous User August 27, 2012 02:58AM

Re: afni_proc.py - processing speed issue

Daniel Glen August 27, 2012 07:17AM

Re: afni_proc.py - processing speed issue

rick reynolds August 27, 2012 08:19AM

Re: afni_proc.py - processing speed issue

Anonymous User August 27, 2012 10:17PM

Re: afni_proc.py - processing speed issue

rick reynolds August 28, 2012 11:43AM

Re: afni_proc.py - processing speed issue

Anonymous User August 28, 2012 10:46PM

Re: afni_proc.py - processing speed issue

rick reynolds August 29, 2012 07:54AM

Re: afni_proc.py - processing speed issue

Anonymous User August 29, 2012 08:34PM

Re: afni_proc.py - processing speed issue

rick reynolds August 29, 2012 09:00PM