Bio::S...eatureI(3pm)
π Bio::SeqFeature::TypedSeqFeatureI π
okay bestie, so this is a page from the User Contributed Perl Documentation β you're looking at Bio::S...eatureI(3pm), and it's all about a strongly typed SeqFeature. sit down, hydrate, let's go π«Ά
β¨ NAME β¨
Bio::SeqFeature::TypedSeqFeatureI β a strongly typed SeqFeature, no cap π
π¦ SYNOPSIS π¦
# get Sequence Features in some manner, eg
# from a Sequence object
foreach $sf ( $seq->get_SeqFeatures() ) {
# all sequence features must have primary_tag() return a string
$type_as_string = $sf->primary_tag();
if( $sf->isa("Bio::SeqFeature::TypedSeqFeatureI") ) {
$ot = $sf->ontology_term();
print "Ontology identifier:",$ot->identifier(),
" name:",$ot->name(),
" Description:",$ot->description(),"\n";
} else {
print "Sequence Feature does not have an ontology type\n";
}
}
πΈ DESCRIPTION πΈ
So basically, this interface describes the extension of SeqFeatureI to being a strongly typed SeqFeature. it's giving glow-up, honestly β¨
Bio::SeqFeature::TypedSeqFeatureI extends the Bio::SeqFeatureI interface β meaning a TypedSeqFeatureI feature must also implement all of the Bio::SeqFeatureI interface too. no skipping, bestie, it's a package deal π
It is suggested that the primary_tag() method of SeqFeatureI return the same as the ontology_term()->name() of the OntologyTypedI (ie, the "string" name of the ontology type is used as the primary tag), but this should not be assumed by client code, because there are scenarios where one would like to maintain the difference. iykyk π
π 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 list. Your participation is much appreciated β fr fr, they want to hear from you π₯Ί
bioperl-l@bioperl.org - General discussion
http://bioperl.org/wiki/Mailing_lists - About the mailing lists
π«Ά Support
Please direct usage questions or support issues to the mailing list:
bioperl-l@bioperl.org
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. like, give them the whole lore, not just the vibes π
π Reporting Bugs
Report bugs to the Bioperl bug tracking system to help us keep track of the bugs and their resolution. Bug reports can be submitted via the web:
https://github.com/bioperl/bioperl-live/issues
π AUTHOR - Ewan Birney π
Email - please email the BioPerl mailing list above.
π APPENDIX π
The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _ β so if you see an underscore, mind your business, that's the backend π
β ontology_term β
Title : ontology_term
Usage : my $ot = $seqfeature->ontology_term()
Returns : a Bio::Ontology::TermI compliant object
Args : none
Status : public
This method returns the ontology term for a strongly typed sequence feature. that's it, that's the method, and it ate π₯
π§ quick vibe check: every flag, argument, return value and link up there is exactly as the original says it. no invented lore, bestie, only certified facts.
perl v5.32.1 π 2021-08-15 π Bio::S...eatureI(3pm)
and that's the whole page, mwah π ty for reading, go forth and type your features responsibly πΈππ¦
π¦ where this page comes from
- debian bookworm: libbio-perl-perl 1.7.8-1 Β· Perl
- debian trixie: libbio-perl-perl 1.7.8-1 Β· Perl
- ubuntu jammy: libbio-perl-perl 1.7.8-1 Β· Perl
- ubuntu noble: libbio-perl-perl 1.7.8-1 Β· Perl
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms