NAME
Bio::Variation::VariantI - Sequence Change SeqFeature abstract class
SYNOPSIS
#get Bio::Variant::VariantI somehowprint $var->restriction_changes, "\n";foreach $allele ($var->each_Allele) {#work on Bio::Variation::Allele objects}
DESCRIPTION
This superclass defines common methods to basic sequence changes. The instantiable classes Bio::Variation::DNAMutation, Bio::Variation::RNAChange and Bio::Variation::AAChange use them. See Bio::Variation::DNAMutation, Bio::Variation::RNAChange, and Bio::Variation::AAChange for more information.
These classes store information, heavy computation to determine allele sequences is done elsewhere.
The database cross-references are implemented as Bio::Annotation::DBLink objects. The methods to access them are defined in Bio::DBLinkContainerI. See Bio::Annotation::DBLink and Bio::DBLinkContainerI for details.
Bio::Variation::VariantI redifines and extends Bio::SeqFeature::Generic for sequence variations. This class describes specific sequence change events. These events are always from a specific reference sequence to something different. See Bio::SeqFeature::Generic for more information.
IMPORTANT: The notion of reference sequence permeates all Bio::Variation classes. This is especially important to remember when dealing with Alleles. In a polymorphic site, there can be a large number of alleles. One of then has to be selected to be the reference allele (allele_ori). ALL the rest has to be passed to the Variant using the method add_Allele, including the mutated allele in a canonical mutation. The IO modules and generated attributes depend on it. They ignore the allele linked to using allele_mut and circulate each Allele returned by each_Allele into allele_mut and calculate the changes between that and allele_ori.
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 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 - Heikki Lehvaslaiho
Email: heikki-at-bioperl-dot-org
APPENDIX
The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _
id
Title : idUsage : $obj->idFunction:Read only method. Returns the id of the variation object.The id is the id of the first DBLink object attached to this object.Example :Returns : scalarArgs : none
add_Allele
Title : add_AlleleUsage : $self->add_Allele($allele)Function:Adds one Bio::Variation::Allele into the list of alleles.Note that the method forces the convention that nucleotidesequence is in lower case and amino acds are in uppercase.Example :Returns : 1 when succeeds, 0 for failure.Args : Allele object
each_Allele
Title : allelesUsage : $obj->each_Allele();Function:Returns a list of Bio::Variation::Allele objectsExample :Returns : list of AllelesArgs : none
isMutation
Title : isMutationUsage : print join('/', $obj->each_Allele) if not $obj->isMutation;Function:Returns or sets the boolean value indicating that thevariant described is a canonical mutation with two allelesassinged to be the original (wild type) allele and mutatedallele, respectively. If this value is not set, it isassumed that the Variant describes polymorphisms.Returns : a boolean
allele_ori
Title : allele_oriUsage : $obj->allele_ori();Function:Links to and returns the Bio::Variation::Allele object.If value is not set, returns false. All other Alleles arecompared to this.Amino acid sequences are stored in upper case characters,others in lower case.Example :Returns : stringArgs : string
See Bio::Variation::Allele for more.
allele_mut
Title : allele_mutUsage : $obj->allele_mut();Function:Links to and returns the Bio::Variation::Alleleobject. Sets and returns the mutated allele sequence.If value is not set, returns false.Amino acid sequences are stored in upper case characters,others in lower case.Example :Returns : stringArgs : string
See Bio::Variation::Allele for more.
length
Title : lengthUsage : $obj->length();Function:Sets and returns the length of the affected originalallele sequence. If value is not set, returns false == 0.Value 0 means that the variant position is before thestart=end sequence position. (Value 1 would denote a pointmutation). This follows the convension to report aninsertion (2insT) in equivalent way to a correspondingdeletion (2delT) (Think about indel polymorpism ATC <=> ACwhere the origianal state is not known ).Example :Returns : stringArgs : string
upStreamSeq
Title : upStreamSeqUsage : $obj->upStreamSeq();Function:Sets and returns upstream flanking sequence string. Ifvalue is not set, returns false. The sequence should be>=25 characters long, if possible.Example :Returns : string or falseArgs : string
dnStreamSeq
Title : dnStreamSeqUsage : $obj->dnStreamSeq();Function:Sets and returns dnstream flanking sequence string. Ifvalue is not set, returns false. The sequence should be>=25 characters long, if possible.Example :Returns : string or falseArgs : string
label
Title : labelUsage : $obj->label();Function:Sets and returns mutation event label(s). If value is notset, or no argument is given returns false. Eachinstantiable class needs to implement this method. Validvalues are listed in 'Mutation event controlled vocabulary' inhttp://www.ebi.ac.uk/mutations/recommendations/mutevent.html.Example :Returns : stringArgs : string
status
Title : statusUsage : $obj->status()Function:Returns the status of the sequence change object.Valid values are: 'suspected' and 'proven'Example : $obj->status('proven');Returns : scalarArgs : valid string (optional, for setting)
proof
Title : proofUsage : $obj->proof()Function:Returns the proof of the sequence change object.Valid values are: 'computed' and 'experimental'.Example : $obj->proof('computed');Returns : scalarArgs : valid string (optional, for setting)
region
Title : regionUsage : $obj->region();Function:Sets and returns the name of the sequence region type orprotein domain at this location. If value is not set,returns false.Example :Returns : stringArgs : string
region_value
Title : region_valueUsage : $obj->region_value();Function:Sets and returns the name of the sequence region_value orprotein domain at this location. If value is not set,returns false.Example :Returns : stringArgs : string
region_dist
Title : region_distUsage : $obj->region_dist();Function:Sets and returns the distance tot the closest region(i.e. intro/exon or domain) boundary. If distance is notset, returns false.Example :Returns : integerArgs : integer
numbering
Title : numberingUsage : $obj->numbering()Function:Returns the numbering chema used locating sequnce features.Valid values are: 'entry' and 'coding'Example : $obj->numbering('coding');Returns : scalarArgs : valid string (optional, for setting)
mut_number
Title : mut_numberUsage : $num = $obj->mut_number;: $num = $obj->mut_number($number);Function:Returns or sets the number identifying the order in which themutation has been issued. Numbers shouldstart from 1.If the number has never been set, the method will return ''If you want the output from IO modules look nice and, formultivariant/allele variations, make sense you better setthis attribute.Returns : an integer
SeqDiff
Title : SeqDiffUsage : $mutobj = $obj->SeqDiff;: $mutobj = $obj->SeqDiff($objref);Function:Returns or sets the link-reference to the umbrellaBio::Variation::SeqDiff object. If there is no link,it will return undefNote: Adding a variant into a SeqDiff object willautomatically set this value.Returns : an obj_ref or undef
See Bio::Variation::SeqDiff for more information.
add_DBLink
Title : add_DBLinkUsage : $self->add_DBLink($ref)Function: adds a link objectExample :Returns :Args :
each_DBLink
Title : each_DBLinkUsage : foreach $ref ( $self->each_DBlink() )Function: gets an array of DBlink of objectsExample :Returns :Args :
restriction_changes
Title : restriction_changesUsage : $obj->restriction_changes();Function:Returns a string containing a list of restrictionenzyme changes of form +EcoRI, separated bycommas. Strings need to be valid restriction enzyme namesas stored in REBASE. allele_ori and allele_mut need to be assigned.Example :Returns : stringArgs : string