On Wed, Feb 20, 2013 at 2:57 PM, Peter Cock <p.j.a.c...@googlemail.com> wrote: > Bumping one of my old queries again, with some more use-cases at the end, > > On Wed, Aug 10, 2011 at 11:28 AM, Peter Cock <p.j.a.c...@googlemail.com> > wrote: > http://lists.bx.psu.edu/pipermail/galaxy-dev/2011-August/006350.html > <cut> > > Hi all, > > I was prompted to return to this issue after going through a fairly > simple BLAST data analysis flow with a biology colleague - and > being reminded just how non-obvious some of the task steps > were [*]. Galaxy could still be much easier to use. > > Most of my protein analysis tool wrappers output tabular files, > where column 1 is the query name, and the rest of the columns > will be some sort of predictive model outcome or score. I do of > course document the column meanings in the tool's help (and > include a #header line in the output where possible), but this > could be much more user friendly. > > A specific example is BLAST+ tabular output - where I have taken > pains to document the columns in the tools' help text, but it would > be much nicer to be able to annotate the columns within Galaxy's > metadata as well. If this isn't possible in the base 'tabular' datatype, > can it be done as a custom 'blast-tabular' datatype instead? > > ...
Based on this discussion, perhaps I do have to define a sub-format? http://lists.bx.psu.edu/pipermail/galaxy-dev/2013-February/013526.html Peter ___________________________________________________________ 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/
