On Wed, May 20, 2009 at 04:03, Ian Dunlop <[email protected]> wrote:
> reference for any errors that are bubbling up. This does mean that no > retry type events can be captured by the provenance unless we start > introducing multiple provenance layers - maybe we'll leave that one > for now! Yeah, as we don't yet expose retry and failover configuration in the UI this would only be used now by Taverna 1 workflows that had it specified, and for the few cases where the .t2flow file was manually edited to include this. So I agree that we can skip the 'deeper' provenance for now - for most users they would care more about where their actual results came from - but for 'correct' provenance we would really need to store the result of *all* the layers - as in a way each layer makes a decision. (The "control" part of the workflow). Luckily the default dispatch stack layers are not black boxes - but there could be third party or extension dispatch stack layers. (Like the loop layer) -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ taverna-hackers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-hackers Developers Guide: http://www.mygrid.org.uk/usermanual1.7/dev_guide.html FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq
