Workflow Entry: Dummy example of looping

Created at: 27/01/10 @ 15:52:50 Last updated: 27/01/10 @ 15:56:10

Version 1 (earliest) (of 2)

Version created on: 27/01/10 @ 14:13:55 by: Stian Soiland-Reyes | Revision comments Expand

Last edited on: 27/01/10 @ 15:53:43 by: Stian Soiland-Reyes

Title: Example of looping using dummy services

Type: Taverna 2

Preview

(Click on the image to get the full size)

Download Scalable Diagram (SVG)

Description

Example of looping over asynchronous services. The dummy beanshell scripts represents the operations of an asynchronous submit-status-results style service, such as EBI's InterProScan and NCBI Blast.

createJob creates a temporary file with the content "0". Filename retuirned as a "job ID".

checkStatus reads the job, and return state "RUNNING" as long as the content is less than 10, increasing the number for each call. (As no actual job is being run)

getResults reads the file content, with the condition 'Run after checkStatus'.

In Details->Advanced for checkStatus you can check the loop condition, which says it will loop as long as the output 'state' is equal to 'RUNNING' - with a 0.5s delay.

Thus when executing this workflow, checkStatus will be called repeatedly, and finally the 'result' should be '10' and 'state' should be 'COMPLETE'.

See http://www.mygrid.org.uk/dev/wiki/display/scrap/Looping+in+Taverna+2.1 for details

Download

Download Workflow File/Package (T2FLOW)

Download Workflow as a Galaxy tool

Run

Run this Workflow in the Taverna Workbench...

Option 1:

Copy and paste this link into File > 'Open workflow location...'
http://www.myexperiment.org/workflows/1028/download?version=1
[ More Info Expand ]

Workflow Components

Authors (1)

Titles (1)

Descriptions (4)

Example of looping over asynchronous services. The dummy beanshell scripts represents the operations of an asynchronous submit-status-results style service, such as EBI's InterProScan and NCBI Blast. createJob creates a temporary file with the content "0". Filename retuirned as a "job ID". checkStatus reads the job, and return state "RUNNING" as long as the content is less than 10, increasing the number for each call. (As no actual job is being run) getResults reads the file content, with the condition 'Run after checkStatus'. In Details->Advanced for checkStatus you can check the loop condition for checkStatus, which says it will loop as long as the output 'state' is equal to 'RUNNING' - with a 0.5s delay. Thus when executing this workflow, checkStatus will be called repeatedly, and finally the 'result' should be '10' and 'state' should be 'COMPLETE'. See http://www.mygrid.org.uk/dev/wiki/display/scrap/Looping+in+Taverna+2.1 for details

createJob creates a temporary file with the content "0". Filename retuirned as a "job ID". checkStatus reads the job, and return state "RUNNING" as long as the content is less than 10, increasing the number for each call. (As no actual job is being run) getResults reads the file content, with the condition 'Run after checkStatus'. In Details->Advanced for checkStatus you can check the loop condition for checkStatus, which says it will loop as long as the output 'state' is equal to 'RUNNING' - with a 0.5s delay. Thus when executing this workflow, checkStatus will be called repeatedly, and finally the 'result' should be '10' and 'state' should be 'COMPLETE'. See http://www.mygrid.org.uk/dev/wiki/display/scrap/Looping+in+Taverna+2.1 for details

Inputs (0)

Processors (3)

Name	Type	Description
createJob	beanshell
checkStatus	beanshell
getResults	beanshell

Beanshells (3)

Name	Inputs	Outputs
createJob		jobId value
checkStatus	jobId	state
getResults	jobId	value

Outputs (4)

Name	Description
jobId
initial_value
state
result

Datalinks (6)

Source	Sink
createJob:jobId	checkStatus:jobId
createJob:jobId	getResults:jobId
createJob:jobId	jobId
createJob:value	initial_value
checkStatus:state	state
getResults:value	result