App Catalog
Sign Up Sign In
HMMER Search & Functional Profile with Custom Models - v3.3
kb_hmmer

v.1.4.0

By: dylan

Launch

Search for matches to all MSAs that are within workspace using Hidden Markov Model (HMMER) Search.

This method performs a set of Hidden Markov Model (HMM) searches on protein sequences using HMMER models built for a Group of MSAs.


Implemented for KBase by Dylan Chivian (DCChivian@lbl.gov)


HMMER Search & Functional Profile with Custom Models performs multiple HMMER searches. It reads the objects in the Narrative to find the Multiple Sequence Alignments (MSAs) and uses those MSAs to create a set of Hidden Markov Models (HMMs) which are used in turn to search a protein sequence database. The MSAs must first be generated using a tool such as MUSCLE that builds an MSA from a FeatureSet object. The KBase implementation permits searching through the genes in a Genome object, the genes in the Genome members of a GenomeSet, or the genes in a FeatureSet. The output object of these searches is a FeatureSet containing those genes that pass the thresholds given by the user. The App also provides a table of the hits (with those hits that are below the thresholds in gray) and links to download the table of hits and a Stockholm format MSA. A separate table for each MSA/HMM is provided, whereas the user may select whether to combine the hits into a single FeatureSet or produce a separate FeatureSet object for each MSA/HMM.


Configuration:

Targets Object: The Targets Object may be a FeatureSet of genes, a Genome, or a GenomeSet. A HMMER search database will be automatically generated from the Targets Object.

Output Object: This is the set of genes that are both hit and pass user-defined thresholds.

Coalesce Output: Select whether to combine all hits into a single FeatureSet (which may be used in subsequent Functional Profiling) or make a separate FeatureSet of hits for each MSA/HMM.

E-value: This bounds the e-value for the weakest hit to consider viable. Values below this do not get reported in the table or the HMMER output text downloads.

Bitscore: This bounds the bitscore for the weakest hit to include in the FeatureSet output object. Hits below this threshold are still reported in the table and HMMER text downloads.

Max Accepts: Hard cap on how many hits to report (Default: 1000)


Output:

Output Object: Gene hits are captured in a FeatureSet output object. If there are additional user-defined thresholds, those are filtered out and do not appear in the object, even if they are shown in the output table. The Output object name is used as a basename to which the MSA/HMM name is prepended if the user has selected to separate FeatureSets.

Output HTML Table: The tab-delimited hit table is HTML formatted and additionally shows the region of the hit sequence (as there is no query sequence) covered by the HMMER alignment. Hits that are above the e-value threshold but below other thresholds and are not included in the FeatureSet output object are shown in gray, with the attributes that were below the threshold in red. A separate table is made for each MSA/HMM.

Downloadable files: HMMER table and Stockholm format MSA are available for download. These are not altered from the direct output from the HMMER run. The text output is generated for each MSA/HMM.

Related Publications


App Specification:

https://github.com/kbaseapps/kb_hmmer/tree/dd4072f5f550ac78d8a8dd4ea15449d618ae4b24/ui/narrative/methods/HMMER_Local_MSA_Group_Search

Module Commit: dd4072f5f550ac78d8a8dd4ea15449d618ae4b24