NAME
Bio::Tools::HMMER::Results - Object representing HMMER output results
SYNOPSIS
# parse a hmmsearch file (can also parse a hmmpfam file)$res = Bio::Tools::HMMER::Results->new( -file => 'output.hmm' ,-type => 'hmmsearch');# print out the results for each sequenceforeach $seq ( $res->each_Set ) {print "Sequence bit score is",$seq->bits,"\n";foreach $domain ( $seq->each_Domain ) {print " Domain start ",$domain->start," end ",$domain->end," score ",$domain->bits,"\n";}}# new result object on a sequence/domain cutoff of# 25 bits sequence, 15 bits domain$newresult = $res->filter_on_cutoff(25,15);# alternative way of getting out all domains directlyforeach $domain ( $res->each_Domain ) {print "Domain on ",$domain->seq_id," with score ",$domain->bits," evalue ",$domain->evalue,"\n";}
DESCRIPTION
This object represents HMMER output, either from hmmsearch or hmmpfam. For hmmsearch, a series of HMMER::Set objects are made, one for each sequence, which have the the bits score for the object. For hmmpfam searches, only one Set object is made.
These objects come from the original HMMResults modules used internally in Pfam, written by Ewan Birney. Ewan then converted them to BioPerl objects in 1999. That conversion is meant to be backwardly compatible, but may not be (caveat emptor).
FEEDBACK
Mailing Lists
User feedback is an integral part of the evolution of this and other Bioperl modules. Send your comments and suggestions preferably to one of the Bioperl mailing lists. Your participation is much appreciated.
[email protected] - General discussionhttp://bioperl.org/wiki/Mailing_lists - About the mailing lists
Support
Please direct usage questions or support issues to the mailing list:
rather than to the module maintainer directly. Many experienced and reponsive experts will be able look at the problem and quickly address it. Please include a thorough description of the problem with code and data examples if at all possible.
Reporting Bugs
Report bugs to the Bioperl bug tracking system to help us keep track the bugs and their resolution. Bug reports can be submitted via the web:
https://github.com/bioperl/bioperl-live/issues
AUTHOR - Ewan Birney
Email [email protected]
CONTRIBUTORS
Jason Stajich, jason-at-bioperl.org
APPENDIX
The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _
next_feature
Title : next_featureUsage : while( my $feat = $res->next_feature ) { # do something }Function: SeqAnalysisParserI implementing functionExample :Returns : A Bio::SeqFeatureI compliant object, in this case,each DomainUnit object, ie, flattening the Sequenceaspect of this.Args : None
number
Title : numberUsage : print "There are ",$res->number," domains hit\n";Function: provides the number of domains in the HMMER report
seqfile
Title : seqfileUsage : $obj->seqfile($newval)Function:Example :Returns : value of seqfileArgs : newvalue (optional)
hmmfile
Title : hmmfileUsage : $obj->hmmfile($newval)Function:Example :Returns : value of hmmfileArgs : newvalue (optional)
add_Domain
Title : add_DomainUsage : $res->add_Domain($unit)Function: adds a domain to the results array. Mainly used internally.Args : A Bio::Tools::HMMER::Domain
each_Domain
Title : each_DomainUsage : foreach $domain ( $res->each_Domain() )Function: array of Domain units which are held in this reportReturns : arrayArgs : none
domain_bits_cutoff_from_evalue
Title : domain_bits_cutoff_from_evalueUsage : $cutoff = domain_bits_cutoff_from_evalue(0.01);Function: return a bits cutoff from an evalue using thescores here. Somewhat interesting logic:Find the two bit score which straddle the evalueif( 25 is between these two points) return 25else return the midpoint.This logic tries to ensure that with large signal tonoise separation one still has sensible 25 bit cutoffReturns :Args :
write_FT_output
Title : write_FT_outputUsage : $res->write_FT_output(\*STDOUT,'DOMAIN')Function: writes feature table output ala swissprotReturns :Args :
filter_on_cutoff
Title : filter_on_cutoffUsage : $newresults = $results->filter_on_cutoff(25,15);Function: Produces a new HMMER::Results module which hasbeen trimmed at the cutoff.Returns : a Bio::Tools::HMMER::Results moduleArgs : sequence cutoff and domain cutoff. in bits scoreif you want one cutoff, simply use same number both places
write_ascii_out
Title : write_ascii_outUsage : $res->write_ascii_out(\*STDOUT)Function: writes asseq seq_start seq_end model-acc model_start model_end model_nameReturns :Args :FIXME: Now that we have no modelacc, this is probably a bad thing.
write_GDF_bits
Title : write_GDF_bitsUsage : $res->write_GDF_bits(25,15,\*STDOUT)Function: writes GDF format with a sequence,domain thresholdReturns :Args :
add_Set
Title : add_SetUsage : Mainly internal functionFunction:Returns :Args :
each_Set
Title : each_SetUsage :Function:Returns :Args :
get_Set
Title : get_SetUsage : $set = $res->get_Set('sequence-name');Function: returns the Set for a particular sequenceReturns : a HMMER::Set objectArgs : name of the sequence
_parse_hmmpfam
Title : _parse_hmmpfamUsage : $res->_parse_hmmpfam($filehandle)Function:Returns :Args :
_parse_hmmsearch
Title : _parse_hmmsearchUsage : $res->_parse_hmmsearch($filehandle)Function:Returns :Args :
parsetype
Title : parsetypeUsage : $obj->parsetype($newval)Function:Returns : value of parsetypeArgs : newvalue (optional)