Bio::T...::Pair(3pm)

πŸ“¦
version 1.7.8 Β· 3 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble

πŸ’– Bio::T...::Pair(3pm) πŸ’–

okay bestie, so this is Bio::Tools::Primer::Pair, straight outta the User Contributed Perl Documentation section, and it's giving very much "let me introduce you to my two best friends, one on the left and one on the right." pull up a chair, we're doing primer pairs today 🧬✨


🌸 NAME 🌸

Bio::Tools::Primer::Pair β€” literally just two primers, one on the left side and one on the right side. that's the whole vibe. πŸ’…


✨ SYNOPSIS ✨

here's how you actually use the thing, copy-paste core:

use Bio::Tools::Primer::Pair;

my $pair = Bio::Tools::Primer::Pair->new( -left => $leftp , -right => $rightp);

# helper functions

print "GC percentage different",$pf->gc_difference(),"\n";
print "product length is ",$pf->product_length,"\n";

okay so like β€” you make your pair with -left and -right, and then there's the helper functions section where you just vibe-check your primers: gc_difference() tells you how different the GC percentages are (slay), and product_length tells you how long the product is. easy. 🫢


πŸ’œ DESCRIPTION πŸ’œ

so a Primer Pair represents one primer in a primer pair β€” no cap, that's the description, that's what it says. this object is mainly for designing primers, and it's probably principly used in the primer design system. (yes, the original says "principly." we're keeping it. it's iconic. πŸ‘‘)

tl;dr: it's a design tool, not a party trick. πŸ’–


πŸ¦‹ FEEDBACK πŸ¦‹

🌸 Mailing Lists 🌸

user feedback is an integral part of the evolution of this and other Bioperl modules β€” fr fr, they mean it. send your comments and suggestions preferably to the Bioperl mailing list. your participation is much appreciated πŸ₯Ή

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. the reasoning? there are many experienced and reponsive experts who will be able look at the problem and quickly address it. (yes, "reponsive." we love a typo that ate. πŸ’€)

and pls pls pls β€” include a thorough description of the problem with code and data examples if at all possible. the more context, the faster the glow-up. ✨

🌈 Reporting Bugs 🌈

report bugs to the Bioperl bug tracking system so they can keep track of the bugs and their resolution. bug reports can be submitted via the web:

https://github.com/bioperl/bioperl-live/issues

do it. it's the responsible main character move. πŸ‘‘


πŸ‘‘ AUTHOR - Ewan Birney πŸ‘‘

Email birney-at-ebi.ac.uk

shoutout Ewan, we love you πŸ’œ


πŸ“ 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, that's an inside-job method, iykyk. πŸ™ˆ


and that's the whole page bestie, we ate and left no crumbs πŸŽ€ this was perl v5.32.1, dated 2021-08-15, and it lives in the User Contributed Perl Documentation. go design some primers, you got this πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from