Mercurial > repos > galaxyp > metaquantome
diff metaquantome_expand.xml @ 4:80ce9ca55697 draft
planemo upload commit d27827cf38d30b9c98923f73bc9cae4ffe41361b
author | galaxyp |
---|---|
date | Fri, 07 Dec 2018 13:43:06 -0500 |
parents | 47bfbd6597d0 |
children |
line wrap: on
line diff
--- a/metaquantome_expand.xml Thu Dec 06 08:50:19 2018 -0500 +++ b/metaquantome_expand.xml Fri Dec 07 13:43:06 2018 -0500 @@ -1,4 +1,4 @@ -<tool id="metaquantome_expand" name="MetaQuantome Expand" version="@VERSION@.0"> +<tool id="metaquantome_expand" name="metaQuantome: expand" version="@VERSION@.0"> <description>annotated functional or taxonomy terms to include all terms</description> <macros> <import>macros.xml</import> @@ -11,9 +11,9 @@ @EXPAND_PARAMS@ @DB_DIR@ #if $input.input_type == 'nopep': - --nopep --nopep_file='$input.nopep_file' + --nopep --nopep_file='$input.nopep_file' #else: - --int_file='$input.int_file' + --int_file='$input.int_file' --pep_colname_int='$input.pep_colname_int' #end if --outfile='$outfile' @@ -29,7 +29,7 @@ <when value="int"> <param argument="--int_file" type="data" format="tabular" label="intensity data" help=""/> - <param argument="--pep_colname_int" type="text" value="" label="Peptide column name" + <param argument="--pep_colname_int" type="text" value="" label="Peptide column name" help="The column name within the intensity file that corresponds to the peptide sequences"> <validator type="empty_field"/> </param> @@ -47,9 +47,6 @@ </outputs> <tests> <test> - <!-- expand('f', sinfo=TTEST_SINFO, int_file=int, pep_colname_int='peptide', pep_colname_func='peptide', - pep_colname_tax='peptide', data_dir=GO_TEST_DIR, outfile=expanded, func_file=func, - func_colname='go', ontology='go') --> <param name="int_file" value="int_ttest.tab" ftype="tabular"/> <param name="pep_colname_int" value="peptide" /> <param name="func_file" value="multiple_func.tab" /> @@ -70,7 +67,59 @@ </test> </tests> <help><![CDATA[ - help +metaQuantome expand +=================== + +The *expand* module is the first step in the metaQuantome analysis workflow, +and can be run to analyze function, taxonomy, or function and taxonomy together. + +See the figure below for an overview of the metaQuantome workflow: + +.. image:: metaquantome_program_structure.png + :width: 100 % + +**metaQuantome workflow**: (A) Outline of metaQuantome program structure, (B) expanding the hierarchy, (C) and the definition of the total term abundance. + + +The following information is required for all 4 analysis modes: + +- experimental design information +- a tab-separated peptide intensity file +- the name of the peptide column in the intensity file + +Function mode +------------- + +In function mode, the following information is required: + +- the ontology being used: Gene Ontology (go), Clusters of Orthologous Groups (COG), or Enzyme Commission (EC) numbers. +- a tab-separated functional annotation file, with a peptide column and a functional annotation column. An entry in the functional annotation column may contain multiple functional annotations separated by a comma. +- the name of the peptide column in the functional annotation file +- the name of the functional annotation column in the functional annotation file + +Taxonomy mode +------------- + +In taxonomy mode, the following information is required: + +- a tab-separated taxonomy annotation file, with a peptide column and a taxonomy annotation column. The taxonomic annotations should be the lowest common ancestor (LCA) for each peptide, preferably given as NCBI taxonomy IDs. +- the name of the peptide column in the taxonomic annotation file +- the name of the taxonomy annotation column in the taxonomy annotation file + +Function-Taxonomy mode +---------------------- + +In the combined mode, all of the above must be provided. In addition, the "target rank" must be provided, which is the desired taxonomic rank at which to summarize the function/taxonomy results. + +Databases +--------- + +Currently, metaQuantome on Galaxy is only set up to use automatically downloaded databases, so your results may change slightly from run to run. In the future, we plan to enable cached databases in Galaxy. + +Questions, Comments, Problems, Kudos +------------------------------------ + +Please file any issues at https://github.com/galaxyproteomics/tools-galaxyp/issues. ]]></help> <expand macro="citations" /> </tool>