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

πŸ“¦
version 1.7.3 Β· 3 versions
, in debian bookworm, ubuntu noble

πŸ’– NAME πŸ’–

Bio::Tools::Run::BlastPlus β€” a wrapper for NCBI's blast+ suite. That's the whole vibe. (Also, for the record, this lil page lives in the User Contributed Perl Documentation section of the manual, so if you were looking for it, hiii, you found it 🫢)


πŸŽ€ SYNOPSIS πŸŽ€

Okay so the synopsis is literally just this, no notes:

Give standard usage here

That's it. That's the synopsis. Iconic of them honestly πŸ’…


✨ DESCRIPTION ✨

Blast+ is NCBI's successor to the blastall family of programs. Like, the glow-up. The next era. The main character taking over from the legacy cast. 🌈


πŸ“£ FEEDBACK πŸ“£

πŸ’Œ Mailing Lists πŸ’Œ

Bestie, user feedback is an integral part of the evolution of this and other Bioperl modules β€” like, the modules literally grow because you talk to them. Send your comments and suggestions preferably to the Bioperl mailing list. Your participation is much appreciated, fr fr.

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, okay? Because the mailing list has so many experienced and responsive experts who will look at your problem and address it quick. And please include a thorough description of the problem with code and data examples if at all possible β€” the more context, the more slay. πŸ¦‹

πŸ› Reporting Bugs πŸ›

Report bugs to the Bioperl bug tracking system so we can keep track of the bugs and their resolution β€” no lost bugs in the group chat, we track everything. Bug reports can be submitted via the web:

http://redmine.open-bio.org/projects/bioperl/

πŸ‘‘ AUTHOR - Mark A. Jensen πŸ‘‘

Email maj -at- fortinbras -dot- us

Describe contact details here


πŸ’œ CONTRIBUTORS πŸ’œ

Additional contributors names and emails here


πŸ“š APPENDIX πŸ“š

The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _ β€” iykyk, if you see that underscore, it's private business. πŸ™ˆ

🌸 new 🌸

  • Title: new
  • Usage: my $obj = new Bio::Tools::Run::BlastPlus();
  • Function: Builds a new Bio::Tools::Run::BlastPlus object
  • Returns: an instance of Bio::Tools::Run::BlastPlus
  • Args: (nothing here, it's a mystery, the Args line is empty πŸŽ€)

🌟 program_version() 🌟

  • Title: program_version
  • Usage: $version = $bedtools_fac->program_version()
  • Function: Returns the program version (if available)
  • Returns: string representing location and version of the program
  • Note: this works around the WrapperBase::version() method conflicting with the -version parameter for SABlast (good argument for not having getter/setters for these)
Lowkey a whole saga. The getter/setter situation said "not today" and honestly? Valid.

πŸ¦‹ package_version() πŸ¦‹

  • Title: package_version
  • Usage: $version = $bedtools_fac->version()
  • Function: Returns the BLAST+ package version (if available)
  • Returns: string representing BLAST+ package version (may differ from version())

And that's the whole page, bestie. Sending you off with the receipts: this was perl v5.36.0, dated 2023-01-22 β€” so if you're reading this from the future, hey, the vibes are still immaculate. Stay blastin'. πŸ’…βœ¨

πŸ“¦ where this page comes from