Bio::L...olicyI(3pm)

💖 Bio::Location::CoordinatePolicyI 💖

the abstract interface for objects that implement a policy of computing integer-valued coordinates of a Location — aka the vibe-setter for how your fuzzy locations get turned into actual numbers, bestie 🦋

this is Bio::Location::CoordinatePolicyI, a 3pm page from the User Contributed Perl Documentation, and yes she's abstract, yes she's iconic, yes she's the blueprint 👑

---

✨ NAME ✨

Bio::Location::CoordinatePolicyI — the abstract interface for objects implementing a certain policy of computing integer-valued coordinates of a Location 💅

---

🌸 SYNOPSIS 🌸

# get a location, e.g., from a SeqFeature
$location = $feature->location();
# examine its coordinate computation policy
print "Location of feature ", $feature->primary_tag(), " employs a ",
      ref($location->coordinate_policy()),
      " instance for coordinate computation\n";
# change the policy, e.g. because the user chose to do so
$location->coordinate_policy(Bio::Location::NarrowestCoordPolicy->new());

---

💜 DESCRIPTION 💜

okay so here's the tea ☕ — objects that implement this interface get used by Bio::LocationI-implementing objects to figure out integer-valued coordinates whenever somebody asks for them. and like, for a simple location that sounds trivial, sure, but for fuzzy or compound (split) locations? there are so many ways to do it 😭

classes that implement this interface each pick a certain policy, like 'always widest range', 'always smallest range', 'mean for BETWEEN locations', etc. and the slay part? you can install a different policy object into a Location object and the behaviour of coordinate computation changes on-the-fly — a single line of code client-side, no cap. main character energy fr fr ✨

---

🫶 FEEDBACK 🫶

user feedback is an integral part of the evolution of this and other Bioperl modules — like, genuinely, your input is the moment. send your comments and suggestions preferably to one of the Bioperl mailing lists. 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. so 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 - Hilmar Lapp, Jason Stajich 👑

Email hlapp@gmx.net, jason@bioperl.org

---

🎀 APPENDIX 🎀

the rest of the documentation details each of the object methods. internal methods are usually preceded with a _ (iykyk 🔍)

⭐ start

• Title: start
• Usage: $start = $policy->start($location);
• Function: Get the integer-valued start coordinate of the given location as computed by this computation policy.
• Returns: A positive integer number.
• Args: A Bio::LocationI implementing object.

⭐ end

• Title: end
• Usage: $end = $policy->end($location);
• Function: Get the integer-valued end coordinate of the given location as computed by this computation policy.
• Returns: A positive integer number.
• Args: A Bio::LocationI implementing object.

---

and that's the whole page bestie, you ate that 🍓

okay love u, bye — this was perl v5.32.1, dated 2021-08-15, from the User Contributed Perl Documentation, page Bio::Location::CoordinatePolicyI(3pm) 💅✨🦋