Hi Alex,

we extracted it from the history. Normally we have no problems with it, but 
this tool is something special. It generates multiple output files depending on 
the input.


Von: Bossers, Alex [alex.boss...@wur.nl]
Gesendet: Dienstag, 27. August 2013 16:12
An: Berner, Thomas
Cc: galaxy-dev@lists.bx.psu.edu
Betreff: RE: tool not runing in workflow

Did you generate the work flow from scratch or did you make a simple analysis 
in the history and extracted a work flow from that? The latter we usually do 
without problems whatever...but we don’t use the mothur tools though...

Van: galaxy-dev-boun...@lists.bx.psu.edu 
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] Namens Berner, Thomas
Verzonden: maandag 26 augustus 2013 13:45
Aan: galaxy-dev@lists.bx.psu.edu
Onderwerp: [galaxy-dev] tool not runing in workflow

Hey guys,

we installed and used a tool of the mothur_toolsuite  in our local galaxy 
instance named “get.otulist”, but if we want to integrate it into a workflow 
(extract from history) we get the following error for the next step:

“Error due to input mapping of ‘Join two datasets’ in 
‘__new_primary_file_logfile|0.03.otu__’. A common cause of this is conditional 
outputs that cannot be determined until runtime, please review your workflow.”

In the workflow editor only the *.html file is displayed as output but not the 
tabular file which is generated by the tool normally.
There should be an output (tabular) which we want to join with another one, but 
this doesn’t work in the workflow.

Can somebody give me a hint for this?

Greetings, Thomas

Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at:

Reply via email to