Features: Difference between revisions

From Alida
Jump to navigationJump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 14: Line 14:


'''Automatic Process Documentation'''<br/>
'''Automatic Process Documentation'''<br/>
* inherent '''self-documentation''' of all calls to operators, i.e. of entire analysis procedures
* inherent ''self-documentation'' of all calls to operators, i.e. of entire analysis procedures
* result data objects accompanied by individual '''history graphs''' in XML format
* each result data object accompanied by individual ''history graph'' in XML format
* history graph exploration tool: '''Chipory'''<br/>Chipory is a comfortable graph visualization tool for exploring graph data structures. It is based on [http://www.cs.bilkent.edu.tr/~ivis/chisio.html Chisio], however,<br/>extended to meet the special requirements of Alida's history graphs.<br/><br/>
* history graph exploration tool ''Chipory'', a comfortable graph visualization tool for exploring graph data structures based on [http://www.cs.bilkent.edu.tr/~ivis/chisio.html Chisio], however, extended to meet the special requirements of Alida's history graphs.<br/><br/>


'''User Interfaces'''<br>
'''User Interfaces'''<br>
* automatic generation of user interfaces for command line and graphical applications
* automatic generation of user interfaces for command line and graphical applications
* flexible command line parser supporting regular expressions and various I/O channels (file, console)
* flexible command line parser supporting regular expressions and various I/O channels (file, console)
* handy configuration and control windows for graphical user interfaces
* handy configuration and control windows for configuring and running operators in graphical environments
* support for saving/loading operators configuration parameters in XML format
* support for saving/loading operator configuration parameters in XML format
* batch mode option in GUIs to apply operators to sets of input data objects<br/><br/>
* batch mode option in GUIs to apply operators to sets of input data objects<br/><br/>



Latest revision as of 18:23, 10 March 2016

Alida provides a framework for easy development and usage of data analysis procedures.
Below an overview of its main features is given.

Operator Concept

  • common interface for all implemented operators: unified access to all operator parameters, standardized operator invocation procedures
  • various parameter types: input, output and combined input/output parameters
  • support for operator class inheritance and operators as parameters
  • dynamic addition and removal of parameters at runtime
  • callback functions attached to parameters and invoked in case of parameter value changes
  • support for controllable operators which can be paused/continued and stopped by the user
  • extensible provider framework for data type I/O with built-in support for native data types, enumerations, collections, ...
  • simple definition of new user-defined I/O data types by parameterized classes

Automatic Process Documentation

  • inherent self-documentation of all calls to operators, i.e. of entire analysis procedures
  • each result data object accompanied by individual history graph in XML format
  • history graph exploration tool Chipory, a comfortable graph visualization tool for exploring graph data structures based on Chisio, however, extended to meet the special requirements of Alida's history graphs.

User Interfaces

  • automatic generation of user interfaces for command line and graphical applications
  • flexible command line parser supporting regular expressions and various I/O channels (file, console)
  • handy configuration and control windows for configuring and running operators in graphical environments
  • support for saving/loading operator configuration parameters in XML format
  • batch mode option in GUIs to apply operators to sets of input data objects

Grappa - The Graphical Workflow Editor

  • graphical combination of operator nodes into workflows
  • built-in compatibility checks on dragging edges
  • provider framework for automatic data type conversions
  • user-friendly visual feedback about node states (unconfigured, ready to run, terminated, etc.)
  • different workflow execution modes (complete workflows, sub-workflows, individual nodes)