Bio::S..._match(3pm)

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

πŸ’– Bio::SearchIO::cross_match β€” the manual, but make it cute πŸ’–

perl v5.32.1 · User Contributed Perl Documentation · bestie edition 🫢


✨ NAME ✨

Bio::SearchIO::cross_match β€” it's the CrossMatch-specific subclass of Bio::SearchIO, and yes she's giving "specialized baby of a bigger module" and we love her for it πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

okay so here's the vibe β€” you're working with iterations (CrossMatch results), and it goes a lil something like this:

# Working with iterations (CrossMatch results)
my $searchIO = Bio::SearchIO->new( -format => 'cross_match',
                        -file   => "$file.screen.out" )
while(my $r = $searchIO->next_result) {
  while(my $hit = $r->next_hit) {
          while(my $hsp = $hit->next_hsp) {
       #Do the processing here.
    }
  }
}

And fr fr, if you wanna know the whole lore about working with Bio::SearchIO, go peek at Bio::SearchIO β€” it's all there, no cap πŸ“–βœ¨


🌸 DESCRIPTION 🌸

So basically: this object is a subclass of Bio::SearchIO, and she serves up some operations that make working with CrossMatch (and CrossMatch results) actually doable πŸ’–

For the general tea on working with Results, you're gonna wanna check out Bio::Search::Result::GenericResult β€” she's the main character for that πŸŽ€


πŸ’Œ FEEDBACK πŸ’Œ

πŸ“¬ Mailing Lists

User feedback is literally an integral part of the evolution of this module and all the other Bioperl modules β€” so pls, send your comments and suggestions, preferably to the Bioperl mailing list. Your participation is so appreciated, genuinely πŸ₯ΉπŸ«Ά

bioperl-l@bioperl.org                  - General discussion
http://bioperl.org/wiki/Mailing_lists  - About the mailing lists

πŸ›Ÿ Support

Bestie, direct your usage questions and support issues to the mailing list:

bioperl-l@bioperl.org

β€” and not straight to the module maintainer, ok? There are so many experienced and responsive experts on the list who can look at your problem and address it quickly. If you can, pls include a thorough description of the problem with code and data examples. That's the slay way to ask πŸ’…βœ¨

πŸ› Reporting Bugs

Report bugs to the Bioperl bug tracking system so we can keep track of the bugs and their resolution β€” it's a whole system, respect it πŸ™Œ Bug reports can be submitted via the web:

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

πŸ‘‘ AUTHOR - Shin Leong πŸ‘‘

Email: sleong@watson.wustl.edu

(iconic, we stan πŸ’œ)


🌈 CONTRIBUTORS 🌈

Additional contributors names and emails here

(yes, that's literally what it says, the list is a placeholder and I am simply passing the message along, no notes πŸ™ˆ)


πŸ“š APPENDIX πŸ“š

The rest of the documentation details each of the object methods. Heads up: internal methods are usually preceded with a _ β€” that underscore is basically their "do not perceive me" marker 🫣


πŸ” next_result

  • Title: next_result
  • Usage: $result = stream->next_result
  • Function: Reads the next ResultI object from the stream and returns it.

Okay so here's the important part, listen up: certain driver modules may encounter entries in the stream that are either misformatted or that use syntax not yet understood by the driver. If such an incident is recoverable β€” like, say, by dismissing a feature of a feature table or some other non-mandatory part of an entry β€” the driver will issue a warning. But in the case of a non-recoverable situation, an exception will be thrown 😭

Do not assume that you can resume parsing the same stream after catching the exception. That is not a thing. It's not giving "try again bestie", it's giving "this stream is done".

Note that you can always turn recoverable errors into exceptions by calling $stream->verbose(2) (see the Bio::Root::RootI POD page) β€” your choice, your power ✨

  • Returns: A Bio::Search::Result::ResultI object
  • Args: n/a

See Bio::Root::RootI


πŸ”’ _alignment

  • Title: _alignment
  • Usage: private

(that's it, that's the whole entry, she's private and mysterious πŸ«£πŸ’…)


πŸ”’ _parse

  • Title: _parse
  • Usage: private

(also private, also mysterious, also not telling us anything, respect the privacy πŸŽ€)


πŸ”’ result_count

  • Title: result_count
  • Usage: $num = $stream->result_count;
  • Function: Gets the number of CrossMatch results that have been parsed.
  • Returns: integer
  • Args: none
  • Throws: none

literally just a counter, she counts, she returns, no drama, no throwing, immaculate behaviour πŸ‘‘


🫢 cute sign-off 🫢

This lil page came to you from perl v5.32.1, dated 2021-08-15, filed under Bio::S..._match(3pm) β€” yeah the title's a lil abbreviated, she's got main character energy with a short name, and honestly? iconic. Go parse something, bestie πŸ’–βœ¨πŸŒΈπŸ¦‹

πŸ“¦ where this page comes from