multi-gridsam-gopher

Created: 2009-03-03 13:49:23

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

 

 

Information Preview

Information Run

You do not have permission to run this workflow


Information Workflow Components

You do not have permission to see the internals of this workflow

Information Workflow Type

Taverna 1

Information Uploader

Information License

All versions of this Workflow are licensed under:

Information Version 1 (earliest) (of 2)

View version:

Information Credits (1)

(People/Groups)

Information Attributions (0)

(Workflows/Files)

None

Information Tags (0)

None

Log in to add Tags

Information Featured In Packs (0)

None

Log in to add to one of your Packs

Information Attributed By (0)

(Workflows/Files)

None

Information Favourited By (0)

No one

 

Citations (0)

None


Version History

In chronological order:



Reviews Reviews (0)

No reviews yet

Be the first to review!



Comments Comments (1)

Log in to make a comment

  • Tuesday 18 November 2008 23:15:02 (UTC)

    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?




Workflow Other workflows that use similar services (0)

There are no workflows in myExperiment that use similar services to this Workflow.