Diff for "ScriptingNotes" - MRC CBU Imaging Wiki
location: Diff for "ScriptingNotes"
Differences between revisions 16 and 21 (spanning 5 versions)
Revision 16 as of 2006-10-02 11:11:40
Size: 981
Comment:
Revision 21 as of 2013-03-07 21:23:05
Size: 1316
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
  ["MYV"]

 '''BitOfScript'''
  [[MYV]]
Line 21: Line 19:
  * Why Batch?  * Why Batch?
Line 25: Line 23:
 * Spm5Tasks   '''BitOfScript'''

 
* Spm5Tasks
Line 31: Line 31:
   * ''Query: how to get jobs saves a .m or .xml files as well as a .mat file? - These options could be useful as these are text files and easier to edit.
Line 33: Line 35:
  * ''To be clarified: there may be some undocumented functionality for linking up tasks in sequence so that output of one task become the input to the next.'''   * ''To be clarified: there is some barely undocumented functionality for linking up tasks in sequence so that output of one task become the input to the next. E.g. if you add a normalisation after creating a realignment you will see the option of choosing r* files for normalizing despite the fact that they do not yet exist!'''
Line 35: Line 37:
 ["Jobs3"] 
[[Jobs3]]
Line 43: Line 46:
PetModelAutomation5    * PetModelAutomation5

Notes on Scripting, Batching and Tasking for SPM5

  • Why Script?

    • A large part of SPM code is complex housekeeping related to files and directories
    • Tailoring requires attention to these housekeeping matters
      • Have I got the right files?

    • Need to create novel suite of analyses out of a number of core modules
    • Intercommunication via the SPM.mat structure

      MYV

      AllGorySpmMat

  • Why Batch?
    • Need to perform same or similar analyses on several datasets

      BitOfScript

    • Spm5Tasks

    • How to access them
    • What they do
      • Query: how to get jobs saves a .m or .xml files as well as a .mat file? - These options could be useful as these are text files and easier to edit.

    • Job/task manager can be extended
    • To be clarified: there is some barely undocumented functionality for linking up tasks in sequence so that output of one task become the input to the next. E.g. if you add a normalisation after creating a realignment you will see the option of choosing r* files for normalizing despite the fact that they do not yet exist!

    Jobs3

  • Other approaches

CbuImaging: ScriptingNotes (last edited 2013-03-07 21:23:05 by localhost)