-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe tabular output column names in Galaxy metadata #84
Comments
@peterjc this is working with recent Galaxy versions. Please have a look at this wrapper: https://github.com/galaxyproject/tools-iuc/blob/master/tools/featurecounts/featurecounts.xml#L356 |
Thanks for that example setting column names @bgruening: <actions>
<action name="column_names" type="metadata" default="Status,${','.join([ a.name for a in $alignments ])}" />
</actions> I see @yhoogstrate worked on this as part of galaxyproject/tools-iuc#588 using the galaxyproject/galaxy#961 addition to Galaxy merged on 11 Feb 2016 by @jmchilton [update: meaning it should work with the two most recent Galaxy releases, v16.04 and v16.07]. Is there any other documentation (e.g. galaxy-dev emails) I should look at? There is an |
Hi Peter, Am 20.09.2016 um 15:35 schrieb Peter Cock:
Not that I now of, sorry.
The wiki is deprecated, please look at this awesome work from John:
|
Doing this for the main BLAST tools might be tricky as they already change the output format dynamically. Therefore I started with the BLAST XML to tabular tool. First hurdle is testing the column names worked, see galaxyproject/galaxy#2941 |
Ideally the tabular files from BLAST tools would result in datasets in Galaxy with the column names in the Galaxy metadata. We know the column names from the command line options used... the trick is how to tell Galaxy this.
There is an open Galaxy issue for using the column data in the interface (e.g. the column selector), https://trello.com/c/kwL8zzSR/436-554-show-column-names-headers-or-first-entry-in-column-select-parameters
See also https://trello.com/c/YlADVbkI which does some clever stuff with metadata which might be helpful.
The text was updated successfully, but these errors were encountered: