MBAT Plugins API

• Specify well-defined Input/Output data model for plugins

I. DocManager Core

1. File reader plugin
   • Input:
     • Classtype: metafile,2D/3D Image, numeric, etc
     • Extension: .atlas, .img, etc.
   • Output
     • 2D/3D Image
       • Metadata: dimensions, pixelformat
       • Data: Buffer
     • Numerica Data:
       • Metadata: dimensions, format
       • Data: Array[] or {x,y,z,val}

II. Search Core

1. DIY plugin (programmatic/generic database plugin)
   • Input:
     • Query Parameters: Vector< SearchParam > vParameters
     • Keyword string: String sKeyword
   • Output:
     • Search Results: Vector< MBATResults > vQueryResults
2. Template plugin (enduser database must implement Universal WebServices API)
   • Input:
     • Query Parameters: Vector< SearchParam > vParameters
     • Keyword string: String sKeyword
   • Output:
     • XCEDE search results

III. Viewer Core

1. Rendering plugin
   • Input:
     • Layer Data:
       • Image(s) or subimage(s): Vector< BufferedImage > vImages
       • Volume(s): Vector< VolumeBuffer > vVolumes
     • OpenGL Context
       • GLCanvas glCanvas
   • Output:
     • None

IV. Analysis Core

1. Spatial Registration Plugin
   • Input:
     • Image(s): Vector< BufferedImage > vImages
     • Filename(s): Vector< String > vFileNames
     • GUI: JPanel panelMain
   • Output:
     • Registered Image(s): Vector< BufferedImage > vImages
     • Registered File(s): Vector< String > vFileNames
2. Signal Detection Plugin
   • Input:
     • Image(s) or subimage(s): Vector< BufferedImage > vImages
   • Output:
     • Signal value(s): Vector< float > vSignalStrengths