Hi John,
I think I have it resolved:
At the end of the day the only thing I had to do was to change in the
definitions of the datatypes from:
to:
and that made the filters work.
I guess data.Text is something Galaxy knows and understands whereas
data:Lefse and tabular:Le
Galaxy can sometimes be... confused :). I think Galaxy's database thinks
the datatype is lefse_res - but Galaxy doesn't think that type exists so it
cannot really treat it as a lefse_res when filtering on tools. I think if
you were able to fix the datatype and get it to appear in what Galaxy
percei
Hi John,
First of all, Thanks!
You are right and the “lefse_res” datatype does not appear when "View data
types registry" .
However:
We had our lefse application which we migrated to the tool_shed.
As part of the migration, we moved the datatypes definition from
//usr/local/galaxy-dist/dataty
When Galaxy cannot find the extension/short name corresponding to a
datatype it treats the input as a 'data' the root datatype meaning
anything can connect to it. So I think the problem here is not so much
your tool format as your datatype - I don't think Galaxy can see the
lefse_res datatype. You
