222013-03-07 21:23:56localhostconverted to 1.6 markup212007-08-20 14:57:02RhodriCusack202006-06-05 09:20:28RhodriCusack192006-06-02 10:57:25RhodriCusack182006-06-02 10:50:26RhodriCusack172006-06-02 10:45:47RhodriCusack162006-06-02 10:37:12RhodriCusack152006-06-02 10:36:52RhodriCusack142006-06-02 10:33:11RhodriCusack132006-06-02 10:32:45RhodriCusack122006-06-02 10:32:28RhodriCusack112006-06-02 10:32:01RhodriCusack102006-06-02 10:26:31RhodriCusack92006-06-02 10:26:16RhodriCusack82006-06-02 10:25:51RhodriCusack72006-06-01 18:46:08RhodriCusack62006-06-01 18:41:00RhodriCusack52006-06-01 18:13:17RhodriCusack42006-06-01 18:12:52RhodriCusack32006-06-01 18:12:00RhodriCusack22006-06-01 18:10:30RhodriCusack12006-06-01 18:09:07RhodriCusackThis manual is for aa parallel version 2.2 and earlier. You might prefer the new aa wiki for aa version 3.0 and above or information on cloud execution Introduction General overview File format Choosing an appropriate recipe Getting started aa parallel Parameter set reference Release notes for different versions Contents

The system automates the analysis of neuroimaging data using SPM. Two versions are available: one for Siemens data (e.g., CBU 3T Tim Trio), SPM 5 and NIFTI; and one for Bruker data (e.g., WBIC Medspec 3T), SPM 2 and Analyze. It is written in Matlab.

Automatic. Almost completely automatic analysis, currently up to the end of normalisation with minimal coding, and the end of second level statistics with a little customisation to specify your first level model. Flexible control. Users that are new to neuroimaging don't get bombarded with options, but are directed to what is essential, while all other settings take sensible defaults. More experienced users can easily change a range of settings, and advanced users can add or replace modules to the system to change any behaviour Restartable. If the users stops the script, or if it crashes (e.g., because of a machine fault, or because the right data aren't there) then when restarted it will begin at the stage where it left off. Parallel processing. Where multiple machines are available, aa jobs can seamlessly be distributed across them Well behaved. Field maps and structurals are automatically detected. Structurals are copied to /imaging/local/structurals/cbu automatically by default. Easy to maintain. The code components are stored in a central repository (/imaging/local/spm/aa) which means that new components can be made available, or existing ones changed in new releases Record keeping. Unlike SPM used from the GUI, the system records exactly which parameters were used, and allows easy recreation of a dataset from the raw data at a later date. Modular, with simple interface. It is easy for Matlab programmers to write new modules and incorporate them into the processing stream.