On Tue, Mar 2, 2010 at 15:09, Paul Fisher <[email protected]> wrote:
> I'm building a workflow in Taverna 1.7.2.1 to test it before I port it
> to 2.1, and noticed an error I'm getting on a beanshell.
> The error doesn't say anything about what is causing the problem, but
> the ports on the service do. I only get a red service box in T1.7.2.1,
> but no stack trace error message.

Your attachment was not included, but it is a general problem in
Taverna 1 that you need to Remove and Create the iteration strategy if
you modify the ports of a processor, including connecting or
disconnecting to the input ports. (The default "empty" strategy would
still work, though, as it's implicitly created when you press Run).
This issue is not likely to be fixed in Taverna 1.

For some reason this was not already in Jira, but I added it as
http://www.mygrid.org.uk/dev/issues/browse/TAV-781



In Taverna 2 the iteration strategy is always updated when you modify
the ports. New ports are simply added to the bottom. Note that in some
complex cases when you remove or disconnect a port, you could end up
with empty dot- and/or cross products, so it's always a good idea to
revisit the strategy after such editing.

http://www.mygrid.org.uk/dev/issues/browse/T2-73 says that the user
interface should encourage configuring an iteration strategy when a
processor has more than one input port connected.



-- 
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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/

Reply via email to