[MOBY-dev] Moby Collections in Taverna
Edward Kawas
edward.kawas at gmail.com
Wed Apr 19 14:52:47 UTC 2006
One last thing,
When creating new workflows, stay away from the ports labelled 'input' and
'output'. They are there only for legacy reasons.
Eddie
> -----Original Message-----
> From: moby-dev-bounces at lists.open-bio.org
> [mailto:moby-dev-bounces at lists.open-bio.org] On Behalf Of Dirk Haase
> Sent: Wednesday, April 19, 2006 6:46 AM
> To: Core developer announcements
> Subject: Re: [MOBY-dev] Moby Collections in Taverna
>
> Hi Eddie,
>
> On Thursday 13 April 2006 15:56, Edward Kawas wrote:
> > Hi Dirk,
> >
> > The output port behaviour has been cloned for collections
> with a new
> > port, Collection 'As Simples'. So that port now takes the n
> items in a
> > collection and produces n simples that Taverna can iterate over.
>
> Wow, that's what I call a prompt fix!
>
> > However, if that port isn't used and a collection is passed to a
> > service that expects a simple, I transparently break apart the
> > collection with n items into n invocations containing a simple and
> > then invoke the service n times, rather than one time with a n
> > invocation message. This was done, because I noticed that
> there were
> > time out issues with very large collections.
>
> OK, I see this behavior when I use the 'output' port. For the
> old collection-type port 'Object(Collection -
> <outputArticleName>)' things are
> strange: it seems that only the first element in the
> collection is piped to the next service.
>
> However, I think this solution is very convenient. The
> drawback is that we now have three distinct types of output
> ports for moby services, this will confuse people. What I
> want to say is that good documentation is desperately needed ;-)
>
> Thanks,
> dirk
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-dev
More information about the MOBY-dev
mailing list