> From: Paul Fisher <[email protected]> > To: taverna-users <[email protected]> > Subject: [Taverna-users] Pushing Taverna execution to server and back
> Hello, Hello, > I've been running an analysis/workflow all day, which takes absolutely > ages. I've now got to leave the office and take my laptop home with me, > which is running the analysis. As you can probably guess, this will > break the workflow and has wasted this analysis run/my day. > What I would like to be able to do is to push the workflow job from my > laptop to a server without interrupting it. If it is still running, when > I return on Monday, I want to get the workflow back and run it > continuously on my laptop to check intermediate inputs/progress/save > results locally/etc, again without interrupting it. > The obvious solution is to "just run it on the server, and stop being > stupid!!!"; but, I didn't know how long it will take when I started it. > So, I would like to push the job to the server only if I run out of time > and need to leave. > Is this possible? Currently no. There are issues in Jira for pausing and resuming workflows, and also for checkpointing them and re-running from a checkpoint (possibly having edited the workflow or tweaked some parameters). Your particular problem may be a special case of wanting to have a distributed engine where computational and storage resources appear and disappear; the server resources becoming available and your laptop resources disappearing for the weekend :-) That general problem could potentially be solved when Taverna moves to being within an OSGi framework. There are distributed and dynamic OSGi systems. There's another major issue hidden in your problem - not knowing how long a workflow is liable to take. Can you think about how you could have known you would have problems? Some services, such as BioMart queries, can estimate how many results they will return. We could look at combining such information with service performance data from BioCatalogue and the predicted workflow behaviour (available in 2.1 beta). That could go some way to estimating the workflow run time. > cheers, > Paul. Alan ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/
