Version 1
(of 1)
|
Version created on:
11/11/08 @ 17:26:55
by:
Soton sbs
|
Revision comments
Last edited on: 13/11/08 @ 16:41:33 by: Soton sbs
Title: multi-gridsam-gopher
Type: Taverna 1
Preview
(Click on the image to get the full size)
Description
Generation of Orthologous Proteins from High-Throughput Estimation of Relationships
This workflow uses GOPHER to take in two protein sequence files and generate datasets of orthologous sequence alignments.
The first [seqin] sequence set is the ‘queries’ around which orthologous datasets are to be assembled. This is now optimised for a dataset consisting of one protein per protein-coding gene, although splice variants should be dealt with OK and treated as paralogues.
The second [orthdb] is the list of proteins from which the orthologues will be extracted. The seqin sequences are then BLASTed against the orthdb and processed to retain putative orthologues using an estimation of the phylogenetic relationships based on pairwise sequences similarities.
This version of the workflow utilises a GridSAM backend for parallelisation, currently this employs a PBS cluster in Southampton and thus access is restricted to members of the University.
More info on GOPHER: http://bioinformatics.ucd.ie/shields/software/gopher/index.html
Download
You do not have permission to download this workflow
Run
You do not have permission to run this workflow
Workflow Components
You do not have permission to see the internals of this workflow
All versions of this Workflow are licensed under the Creative Commons Attribution-Share Alike 3.0 License.
Log in to add Tags
Shared with Groups (1)
Current:
3.0 / 5
(1 rating)
Log in to rate and see breakdown of ratings
Statistics
158 viewings
0 downloads
None
Earliest Version:
[1] - multi-gridsam-gopher
This Workflow only has one version.
Reviews
(0)
Copyright (c) 2007 - 2008 The University of Manchester and University of Southampton
Log in to make a comment
This workflow seems interesting.
However, some of the passages are not very clear.
What if the ortholog input database (second input parameter) is not ok for gopher, for example, it has duplicated id? Does the workflow fail or return a warning?
How is the output file like?
Why did you published it in a way that I don't have permission to see the workflow's components?