Top Ten Reasons Why You Would Want to Use Wings:
  1. Reuse of workflows: rather than having to create a new workflow from scratch, a user would be presented with workflows already created by others and that fit their analysis goals and that contain semantic constraints that determine what datasets are appropriate for a given workflow. To accomplish this, Wings offers a library of pre-defined semantic workflows that you can reuse. See how this is done and try it out!.
  2. Assisting users in using methods correctly: a researcher may have detailed knowledge of the general principles involved in an analysis, but may not be familiar with the detailed requirements of the analytic software to be used. Wings offers assistance in setting up method parameter values that are appropriate for the properties of your datasets. See how this is done and try it out!.
  3. Finding relevant data: a researcher that has data they have collected in their lab and is being processed by a selected workflow would wonder if there are other data collected by others that she could use to strengthen her claims. Wings makes suggestions of datasets that are available and are consistent with the user's current workflow. See how this is done and try it out!.
  4. Managing parallelism for large collections of data: researchers that use large collections of data could benefit from workflow parallelization and concurrency mechanisms that the system would automatically setup by reasoning about the semantics of the workflows and their treatment of data. Wings can represent data collections and generate automatically individual parallel computations. See how this is done and try it out!.
  5. Reproducing published results: rather than having to read the published articles and set up the software, a researcher could retrieve the workflow used in that article and easily re-execute it and/or examine its setup. To support this, Wings allows the reuse of workflow templates created by others while ensuring that the workflows that you set up are valid. See how this is done and try it out!.
  6. Incorporating the latest analytic tools: an expert researcher would like their workflow to always include the latest algorithms that are published and that perform a certain function in their analysis. To accomplish this, Wings can represent classes of components as workflow steps and automatically specialize them to executable components. See how this is done and try it out!.
  7. Automatic triggering of analyses when new relevant data becomes available: a researcher can set up a type of analysis to be automatically run and updated by the system and send her notifications when completed. Wings can represent an abstract workflow containing classes of workflow steps, and customize it automatically to the new datasets. See how this is done and try it out!.
  8. Automatic generation of metadata: the workflow system can automatically generate metadata for new data products resulting from workflow execution. Wings uses the metadata properties of your datasets to figure out what will be the metadata of the results of workflow execution See how this is done and try it out!.
  9. Assisting to create a variant of an existing workflow: a researcher wants to make small changes to an existing workflow, the system can assist them to make sure the resulting workflow is valid. Wings can automatically elaborate templates by propagating semantic constraints and alerting users when the modifications they make are not valid. See how this is done and try it out!.
  10. Assisting to create new workflows: the system could assist users in creating new workflows that are valid according to semantic constraints known about analytic tools and methods. The Wings workflow editor only allows dataflow links that are consistent with the definitions of the workflow components. See how this is done and try it out!.