Dear Wiki user, You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.
The "DebianMed-Taverna-20110130" page has been changed by Hajo Krabbenhöft: http://wiki.debian.org/DebianMed-Taverna-20110130?action=diff&rev1=1&rev2=2 Need to extend Taverna's data handling mechanisms to deal with this. Need to improve some of the invocation mechanisms to better decide where to run the tools. + + == Windows Use cases == + + All current use cases or any new use case without an explicit windows flag is to be considered linux/mac. + + Use case invocation is steered in two locations: + + Every use case activity has a tab in it's configuration for selecting two invocation environments, one for testing and one for production. + The meaning of these invocation environments is specified in Tavern's configuration options and is therefore globally shared for all workflows. + + Invocation environments are always used for linux use cases, which means that on a windows machine it should be impossible to select local invocation in the taverna-wide configuration dialog. + + A windows-only use case has it's tab for selecting invocation environments grayed out, because all invocation environments are for linux only. So a windows-only use case will always use local execution. On a linux machine, this should produce an error when health checking or running the workflow. + + A linux-only use case will have aforementioned tab for selecting, which will be used to choose one of the taverna-wide invocation environments. This makes sense on windows and linux machines, because even when running on windows, the user will not be able to create an invocation environment to use local execution. + _______________________________________________ debian-med-commit mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-med-commit
