Automatic loops - Revision history

Remi at 22:07, 23 January 2014

2014-01-23T22:07:08Z

← Older revision		Revision as of 22:07, 23 January 2014
Line 1:		Line 1:
	~~This page discusses the possibility or getting rid of the awkward controlflow-style looping~~. ~~We could allow modules to automatically loop if a module's port gets a list of values (or multiple connections)~~.		Ideas/design notes: https://docs.google.com/document/d/1eMOKL7nC7EL5E-WoBHHZWEe1U_-pUu_VjnsmfTLCA2I/edit

	~~typed lists?~~

	* list shouldn't be a type like any other
	** allow connection List<T> -> T
	** allow connection T -> List<T> (make a one-element list, or actual list if the module loops)

	* RR proposes: don't duplicate modules to loop, just make update() call compute() several times

	* probably needs the dont-use-modules-as-data work -- ~~modules that return themselves are going to break~~

	* add logic in vistrails_module:Module:<br/>
	~~if inputport T and input list<T>, call compute several times and build list of outputs~~

	* coupling problem
	*:<pre>def test_module(a:T, b:T) -~~> (c:T, d:T):~~
	:: c = ab
	*:: d = a+b
	*::test_module([1, 2], [3, 4])</~~pre>~~
	** is it c = [3, 8], d = [4, 6]? (pairwise)
	** is it c = [3, 4, 6, 8], d = [4, 5, 5, 6]? (cartesian)
	** can probably be settable in module conf (and default to pairwise)

	=== Implementation ===		=== Implementation ===

Tommy: /* Implementation */

2014-01-21T16:54:54Z

Implementation

← Older revision		Revision as of 16:54, 21 January 2014
Line 25:		Line 25:
	=== Implementation ===		=== Implementation ===
	The controlflow package did not take advantage of the improvements that can be made by modifying the vistrails core. Utilizing this we can make looping over modules more integrated.		The controlflow package did not take advantage of the improvements that can be made by modifying the vistrails core. Utilizing this we can make looping over modules more integrated.

	The branch automatic-loops contains a working version using a ListOf module type.		The branch automatic-loops contains a working version using a ListOf module type.

	Using a ListOf module as an input will cause the inputs to be looped over and the results returned as new ListOf modules. This means the downstream will be iterated automatically until a ListOf input port is used.		Using a ListOf module as an input will cause the inputs to be looped over and the results returned as new ListOf modules. This means the downstream will be iterated automatically until a ListOf input port is used.

Tommy: /* Implementation */

2014-01-21T16:54:33Z

Implementation

← Older revision		Revision as of 16:54, 21 January 2014
Line 24:		Line 24:

	=== Implementation ===		=== Implementation ===
	The branch automatic-loops contains a working version using a ListOf module type.		The controlflow package did not take advantage of the improvements that can be made by modifying the vistrails core. Utilizing this we can make looping over modules more integrated.
			The branch automatic-loops contains a working version using a ListOf module type.
	Using a ListOf module as an input will cause the inputs to be looped over and the results returned as new ListOf modules. This means the downstream will be iterated automatically until a ListOf input port is used.		Using a ListOf module as an input will cause the inputs to be looped over and the results returned as new ListOf modules. This means the downstream will be iterated automatically until a ListOf input port is used.

Tommy: /* Implementation */

2014-01-21T16:51:13Z

Implementation

← Older revision		Revision as of 16:51, 21 January 2014
Line 30:		Line 30:

	Cartesian product should be implemented by making it selectable on the module.		Cartesian product should be implemented by making it selectable on the module.

			Choices for activating the loop:
			# Activate on multiple connections or list input on non-list port. This breaks current uses of multiple input connections like on the List module. Also, list of list is ambiguous.
			# Activate when using ListOf as input. Need an extra module to construct a ListOf input. This is the current choice.
			# Activate by setting a flag on the module. We could then loop over inputs as in 1. Iterating downstream modules would have to be set explicitly.

			==== While module ====
			Could be a module setting specifying delay and which output to check.

	=== References ===		=== References ===
	How Taverna does it:		How Taverna does it:
	http://dev.mygrid.org.uk/wiki/display/taverna/Loops		http://dev.mygrid.org.uk/wiki/display/taverna/Loops

Tommy: /* Implementation */

2014-01-21T13:37:25Z

Implementation

← Older revision		Revision as of 13:37, 21 January 2014
Line 25:		Line 25:
	=== Implementation ===		=== Implementation ===
	The branch automatic-loops contains a working version using a ListOf module type.		The branch automatic-loops contains a working version using a ListOf module type.
			Using a ListOf module as an input will cause the inputs to be looped over and the results returned as new ListOf modules. This means the downstream will be iterated automatically until a ListOf input port is used.

			The ListOf type system is very basic and could be improved.

			Cartesian product should be implemented by making it selectable on the module.

	=== References ===		=== References ===
	How Taverna does it:		How Taverna does it:
	http://dev.mygrid.org.uk/wiki/display/taverna/Loops		http://dev.mygrid.org.uk/wiki/display/taverna/Loops

Tommy at 11:34, 21 January 2014

2014-01-21T11:34:12Z

← Older revision		Revision as of 11:34, 21 January 2014
Line 23:		Line 23:
	** can probably be settable in module conf (and default to pairwise)		** can probably be settable in module conf (and default to pairwise)

	== References ==		=== Implementation ===
			The branch automatic-loops contains a working version using a ListOf module type.

			=== References ===
	How Taverna does it:		How Taverna does it:
	http://dev.mygrid.org.uk/wiki/display/taverna/Loops		http://dev.mygrid.org.uk/wiki/display/taverna/Loops

Tommy at 16:18, 17 January 2014

2014-01-17T16:18:56Z

← Older revision		Revision as of 16:18, 17 January 2014
Line 22:		Line 22:
	** is it c = [3, 4, 6, 8], d = [4, 5, 5, 6]? (cartesian)		** is it c = [3, 4, 6, 8], d = [4, 5, 5, 6]? (cartesian)
	** can probably be settable in module conf (and default to pairwise)		** can probably be settable in module conf (and default to pairwise)

			== References ==
			How Taverna does it:
			http://dev.mygrid.org.uk/wiki/display/taverna/Loops

Remi: Created page with 'This page discusses the possibility or getting rid of the awkward controlflow-style looping. We could allow modules to automatically loop if a module's port gets a list of values…'

2014-01-08T17:06:48Z

Created page with 'This page discusses the possibility or getting rid of the awkward controlflow-style looping. We could allow modules to automatically loop if a module's port gets a list of values…'

New page

This page discusses the possibility or getting rid of the awkward controlflow-style looping. We could allow modules to automatically loop if a module's port gets a list of values (or multiple connections).

typed lists?

* list shouldn't be a type like any other
** allow connection List<T> -> T
** allow connection T -> List<T> (make a one-element list, or actual list if the module loops)

* RR proposes: don't duplicate modules to loop, just make update() call compute() several times

* probably needs the dont-use-modules-as-data work -- modules that return themselves are going to break

* add logic in vistrails_module:Module:<br/>
if inputport T and input list<T>, call compute several times and build list of outputs

* coupling problem
*:<pre>def test_module(a:T, b:T) -> (c:T, d:T):
*:: c = a*b
*:: d = a+b
*::test_module([1, 2], [3, 4])</pre>
** is it c = [3, 8], d = [4, 6]? (pairwise)
** is it c = [3, 4, 6, 8], d = [4, 5, 5, 6]? (cartesian)
** can probably be settable in module conf (and default to pairwise)