The entire paragraph relates minor useful points about JoinNode. Basically:

* If you're lazy (like me) you can often avoid typing the joinfield argument.

* In some cases, you really care about the order of an output list. JoinNode preserves the joinsource order. It is not random. (This order preservation required some care in the implementation).

Fred

From: Michael Waskom <notifications@github.com<mailto:notifications@github.com>>
Reply-To: nipy/nipype <reply@reply.github.com<mailto:reply@reply.github.com>>
Date: Sunday, September 15, 2013 7:49 PM
To: nipy/nipype <nipype@noreply.github.com<mailto:nipype@noreply.github.com>>
Cc: Me <loneyf@ohsu.edu<mailto:loneyf@ohsu.edu>>
Subject: Re: [nipype] Rebased version of JoinNode PR (#658)


In doc/users/joinnode_and_itersource.rst:

> +
> +  d = pe.JoinNode(interface=D(), joinsource="b",
> +                  joinfield=["in_files"], name="d")
> +
> +The *joinfield* defaults to all of the JoinNode input fields, so the
> +declaration is also equivalent to the following:
> +
> +::
> +
> +  d = pe.JoinNode(interface=D(), joinsource="b", name="d")
> +
> +In this example, the node "c" *out_file* outputs are collected into
> +the JoinNode "d" *in_files* input list. The *in_files* order is the
> +same as the upstream "b" node iterables order.
> +
> +The JoinNode input can be filtered for unique values by specifying


I don't know what this means.

—
Reply to this email directly or view it on GitHub<https://github.com/nipy/nipype/pull/658/files#r6369259>.