Can you review this dev thread http://dev.list.galaxyproject.org/Problem-selecting-datasets-with-a-specifie...
In particular can you go to the "View data types registry" option in the admin menu and see if Galaxy thinks it knows about this datatype? Let me know if Galaxy thinks the datatype exists.
If the datatype doesn't exist - can you tell me how you have defined the custom dataytpe - directly in Galaxy, in a tool shed, etc...? The more details about the definition of the datatype you can provide the better.
-John
On Thu, Oct 30, 2014 at 4:52 PM, David Kelly davidkelly@uchicago.edu wrote:
Hello,
I'm working with two custom tools in my local galaxy instance:
The first tool outputs a single aceb file. aceb is a custom datatype I've added that describes a crop experiment.
The second tool takes three files as inputs, one of which is an aceb file.
I can successfully run these two tools together in Galaxy outside of a workflow. But for some strange reason I cannot connect these two tools in the workflow editor. The connection never turns green and links. Here are the relevant lines in the tool wrappers:
Outputs of first tool:
<outputs> <data format="aceb" name="acebData" label="Experiment data with unified format" /> </outputs>
Inputs of second tool:
<inputs> <param name="acebData" type="data" format="aceb" label="Inut Survey aceb Data" /> <param name="domeData" type="data" format="dome" label="Input Strategy DOME Data" /> <param name="linkData" type="data" format="txt" label="Input Linkage between field overlay and survey" /> </inputs>
Any ideas for what could be causing this? Thanks.
David
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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/