Partitioning environmental sequencing data using categorical and phylogenetic information using PhyloH with parsing Qiime
Created: 2013-05-07 09:05:19
Last updated: 2015-06-12 13:39:35
Partitioning environmental sequencing data using categorical and phylogenetic information using PhyloH .
The WF need a tree in newick format, a samplefile that show the where the leaf of the tree are found in the different sample and how many time, and a grouping file where the different sample are grouped using a categorical variable. The WF gives back a tabular and graphical representation of an entropy based partitioning of the information present in the sequence across the groupings, and a graphical and tabular representation of the contribution of each branch of the tree to the differentiation across groups of sample.
Further as side results the WF gives the tree annotated with the per branch contribution to the differentiation across groups of sample in nexml or phyloxml format and all files necessary to produce ex.novo the annotated tree on itol, giving the possibility to the user to add taxonomic information.
Preview
Run
Run this Workflow in the Taverna Workbench...
Workflow Components
Authors (1)
saverio vicario
giacinto Donvito
alfonso monaco
|
Titles (1)
Partitioning environmental sequencing data using categorical and phylogenetic information using PhyloH |
Descriptions (1)
Partitioning environmental sequencing data using categorical and phylogenetic information using PhyloH .
The WF need a tree in newick format, a samplefile that show the where the leaf of the tree are found in the different sample and how many time, and a grouping file where the different sample are grouped using a categorical variable. The WF gives back a tabular and graphical representation of an entropy based partitioning of the information present in the sequence across the groupings, and a graphical and tabular representation of the contribution of each branch of the tree to the differentiation across groups of sample.
Further as side results the WF gives the tree annotated with the per branch contribution to the differentiation across groups of sample in nexml or phyloxml format and all files necessary to produce ex.novo the annotated tree on itol, giving the possibility to the user to add taxonomic information.
|
Dependencies (0)
Inputs (7)
Name |
Description |
TreeFile |
phylogenetic infernece in newick format of the sequences ( or clusters of sequences ) present in the different samples. Internal label are overwritten by the service.
|
SampleFile |
a samplefile that show the where the leaf of the tree are found in the different sample and how many time.
It follows phylocom file input standard. text file with tree columns ( space or tab). First column sample name, second number of times the sequence found, the third the name of the sequence.
|
SampleGroupingFile |
The file define how sample should be grouped.
Text file in two columns ( space or tab). a line for each sample, first column the name of the sample, second the name of the group or state of the categorical variable.
|
randomization |
insert an integer to define number of randomization to perform to estimate significance of the difference found across groups. Good rule of the thumb randomization = nlog(n) where n is the number of sequences.
|
qparamHill |
float larger than zero, define the diversity index to be used following Hill parametrization. 1 is shannon index
|
outputPrefix |
Prefix for all outputfiles
|
xmloutputType |
Type of xml summary output type: two possible standard are used nexml and phyloxml. T
At the moment phyloxml is fully supported while nexml have some possible error
|
Processors (10)
Name |
Type |
Description |
FormInput2PhyloH |
localworker |
Scriptoutput = tree +" "+sample +" "+group +" "+Nrandomization +" "+qparamHill +" "+output_prefix +" "+XMLoutputType; |
ServiceName |
stringconstant |
ValuePhyloH |
File_name_value |
stringconstant |
Valuegroup |
File_name_value_1 |
stringconstant |
Valuesample |
File_name_value_2 |
stringconstant |
Valuetree |
Interaction |
interaction |
|
WebDavJST_uploading_Tree |
component |
|
WebDavJST_Upload_Sample |
component |
|
WebDavJST_Upload_Grouping |
component |
|
AsynJSTInteractionSimple |
component |
|
Outputs (4)
Name |
Description |
JobID |
integer that identify the job on the farm. Use it with the service centre to find out bug or crash of the job
|
OutputPath |
Link to folder with all details of estimation
|
StandardOuput |
URL of the HTML file of summary
|
Log |
|
Datalinks (20)
Source |
Sink |
randomization |
FormInput2PhyloH:Nrandomization |
qparamHill |
FormInput2PhyloH:qparamHill |
xmloutputType |
FormInput2PhyloH:XMLoutputType |
outputPrefix |
FormInput2PhyloH:output_prefix |
WebDavJST_uploading_Tree:REST_Service_redirection |
FormInput2PhyloH:tree |
WebDavJST_Upload_Grouping:REST_Service_redirection |
FormInput2PhyloH:group |
WebDavJST_Upload_Sample:REST_Service_redirection |
FormInput2PhyloH:sample |
AsynJSTInteractionSimple:Standardoutput |
Interaction:destination |
File_name_value_2:value |
WebDavJST_uploading_Tree:File_name |
TreeFile |
WebDavJST_uploading_Tree:InputBody |
File_name_value_1:value |
WebDavJST_Upload_Sample:File_name |
SampleFile |
WebDavJST_Upload_Sample:InputBody |
File_name_value:value |
WebDavJST_Upload_Grouping:File_name |
SampleGroupingFile |
WebDavJST_Upload_Grouping:InputBody |
FormInput2PhyloH:output |
AsynJSTInteractionSimple:Argument |
ServiceName:value |
AsynJSTInteractionSimple:Name |
AsynJSTInteractionSimple:JobID |
JobID |
AsynJSTInteractionSimple:Output_Path |
OutputPath |
AsynJSTInteractionSimple:Standardoutput |
StandardOuput |
AsynJSTInteractionSimple:StandardError |
Log |
Uploader
License
All versions of this Workflow are
licensed under:
Version 2
(of 3)
Credits (2)
(People/Groups)
Attributions (0)
(Workflows/Files)
None
Shared with Groups (1)
Featured In Packs (1)
Log in to add to one of your Packs
Attributed By (0)
(Workflows/Files)
None
Favourited By (0)
No one
Statistics
Other workflows that use similar services
(0)
There are no workflows in myExperiment that use similar services to this Workflow.
Comments (0)
No comments yet
Log in to make a comment