Version 1
(of 1)
|
Version created on:
20/03/09 @ 11:22:45
by:
Jumblejumble
|
Revision comments
Last edited on: 20/03/09 @ 11:29:17 by: Jumblejumble
Title: fetch_fasta
Type: Taverna 1
Preview
(Click on the image to get the full size)
Description
This work flow is designed to take an EMBL file containing the genomic data for an identified bacterium. From this information the workflow can determine whether or not that this strain is an MRSA type of bug. This can be determined based on the MecA profile of the given strain.
Blast is utilised to find a relationship with given proteins and that of know S. aureus strains. This phylogenic output is generated from a ClustalW algorithm that plots a phylogenic tree.
The output is presented in a pdf format detailing this strain. Details include: putative identification, presence of MecA and phylogenic tree and ID of it and its neighbour strains.
This workflow is useful as it can easily be adapted to other projects with only minor modification to its processes.
Download
Run
Option 1:
Note: you need to have both the WHIP Launcher and the Taverna myExperiment/WHIP plugin installed on your machine for this to work. See here for information.
Option 2:
Copy and paste this link into File > 'Open workflow location...'
http://www.myexperiment.org/workflows/732/download?version=1
[ More Info
]
Workflow Components
Workflow Type
Log in to add Tags
Shared with Groups (0)
None
Current:
0.0 / 5
(0 ratings)
Log in to rate and see breakdown of ratings
Statistics
None
Earliest Version:
[1] - fetch_fasta
This Workflow only has one version.
Reviews
(0)
Other workflows that use similar services
(0)
There are no workflows in myExperiment that use similar services to this Workflow.
Linked Data
Non-Information Resource URI: http://www.myexperiment.org/workflows/732
Alternative Formats
Copyright © 2007 - 2011 The University of Manchester and University of Southampton
Log in to make a comment
Hi,
I think you may have some nested workflows in there that have not been uploaded (red boxes). Could you please check it and save it, choosing to embed the nested workflows?
cheers,
Paul