Bio::T...y::Base(3pm)

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

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

okay so bestie, this is the manual page Bio::T...y::Base(3pm) from the User Contributed Perl Documentation, and the module it's actually out here documenting is Bio::Tools::Run::Phylo::Hyphy::Base πŸ¦‹ it's giving "wrapper glue for HyPhy" and honestly? we love a base class that knows its job. let's get into it πŸ’…


✨ NAME ✨

Bio::Tools::Run::Phylo::Hyphy::Base β€” Hyphy wrapping base methods 🧬


πŸŽ€ SYNOPSIS πŸŽ€

FIXME
not the FIXME bestie 😭 that's literally the entire synopsis. it's giving "we'll fill this in later" and later never showed up. but it IS what the page says, so here it is, untouched, no cap.

🌸 DESCRIPTION 🌸

HyPhy ([Hy]pothesis Testing Using [Phy]logenies) package of Sergei Kosakowsky Pond, Spencer V. Muse, Simon D.W. Frost and Art Poon. See http://www.hyphy.org for more information. πŸ”₯

like yes, that's the whole description. short, sweet, points you at the website. iconic behavior honestly πŸ‘‘


🫢 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 πŸ’–

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 responsive 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 of the bugs and their resolution. Bug reports can be submitted via the web:

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

πŸ‘‘ AUTHOR - Albert Vilella πŸ‘‘

Email avilella-at-gmail-dot-com πŸ“§


🌈 CONTRIBUTORS 🌈

Additional contributors names and emails here

yes bestie, that's literally the placeholder text. it's giving "the contributors are a mystery" πŸ™ˆ

🧚 APPENDIX 🧚

The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _ ✨

Default Values

Valid and default values are listed below. The default values are always the first one listed. These descriptions are essentially lifted from the python wrapper or provided by the author. πŸŽ€


program_name

  • Title β€” program_name
  • Usage β€” $factory->program_name()
  • Function β€” holds the program name
  • Returns β€” string
  • Args β€” None

valid_values

  • Title β€” valid_values
  • Usage β€” $factory->valid_values()
  • Function β€” returns the possible parameters
  • Returns β€” an array holding all possible parameters (this needs to be specified per child class). Returns an empty array in the base class.
  • Args β€” None
so like, the base class is out here returning an empty array on purpose. it's the "I'm just the blueprint bestie" energy πŸ’…

program_dir

  • Title β€” program_dir
  • Usage β€” ->program_dir()
  • Function β€” returns the program directory, obtained from ENV variable.
  • Returns β€” string
  • Args β€” (empty)

new

  • Title β€” new
  • Usage β€” my $obj = Bio::Tools::Run::Phylo::Hyphy->new();
  • Function β€” Builds a new Bio::Tools::Run::Phylo::Hyphy object
  • Returns β€” Bio::Tools::Run::Phylo::Hyphy
  • Args β€”
    • -alignment β€” the Bio::Align::AlignI object
    • -save_tempfiles β€” boolean to save the generated tempfiles and NOT cleanup after onesself (default FALSE)
    • -tree β€” the Bio::Tree::TreeI object
    • -params β€” a hashref of parameters (all passed to set_parameter)
    • -executable β€” where the hyphy executable resides

See also: Bio::Tree::TreeI, Bio::Align::AlignI

heads up bestie, -save_tempfiles defaults to FALSE, so if you don't flip it, your tempfiles get cleaned up and NOT kept. don't say I didn't warn you πŸ™ˆ

prepare

  • Title β€” prepare
  • Usage β€” my $rundir = $hyphy->prepare($aln);
  • Function β€” prepare the analysis using the default or updated parameters; the alignment parameter must have been set
  • Returns β€” value of rundir
  • Args β€” L<Bio::Align::AlignI> object, L<Bio::Tree::TreeI> object [optional]

create_wrapper

  • Title β€” create_wrapper
  • Usage β€” $self->create_wrapper
  • Function β€” It will create the wrapper file that interfaces with the analysis bf file
  • Example β€” (empty)
  • Returns β€” (empty)
  • Args β€” (empty)

run

  • Title β€” run
  • Usage β€” my ($rc,$results) = $BatchFile->run();
  • Function β€” run the Hyphy analysis using the specified batchfile and its ordered parameters
  • Returns β€” Return code, Hash
  • Args β€” none

error_string

  • Title β€” error_string
  • Usage β€” $obj->error_string($newval)
  • Function β€” Where the output from the last analysis run is stored.
  • Returns β€” value of error_string
  • Args β€” newvalue (optional)

alignment

  • Title β€” alignment
  • Usage β€” $hyphy->alignment($aln);
  • Function β€” Get/Set the L<Bio::Align::AlignI> object
  • Returns β€” L<Bio::Align::AlignI> object
  • Comment β€” We could potentially add support for running directly on a file but we shall keep it simple
  • See also β€” L<Bio::SimpleAlign>

tree

  • Title β€” tree
  • Usage β€” $hyphy->tree($tree);
  • Function β€” Get/Set the L<Bio::Tree::TreeI> object
  • Returns β€” L<Bio::Tree::TreeI>
  • Args β€” [optional] $tree => L<Bio::Tree::TreeI>,
  • Comment β€” We could potentially add support for running directly on a file but we shall keep it simple
  • See also β€” L<Bio::Tree::Tree>

get_parameters

  • Title β€” get_parameters
  • Usage β€” my %params = $self->get_parameters();
  • Function β€” returns the list of parameters as a hash
  • Returns β€” associative array keyed on parameter names
  • Args β€” none

set_parameter

  • Title β€” set_parameter
  • Usage β€” $hyphy->set_parameter($param,$val);
  • Function β€” Sets a hyphy parameter, will be validated against the valid values. The checks can be ignored if one turns off param checks like this:
$hyphy->no_param_checks(1)
  • Returns β€” boolean if set was success, if verbose is set to -1 then no warning will be reported
  • Args β€”
    • $param => name of the parameter
    • $value => value to set the parameter to

See also: L<no_param_checks()>


set_default_parameters

  • Title β€” set_default_parameters
  • Usage β€” $obj->set_default_parameters();
  • Function β€” (Re)set the default parameters from the defaults (the first value in each array in the valid_values() array)
  • Returns β€” none
  • Args β€” none

update_ordered_parameters

  • Title β€” update_ordered_parameters
  • Usage β€” $hyphy->update_ordered_parameters(0);
  • Function β€” (Re)set the default parameters from the defaults (the first value in each array in the %VALIDVALUES class variable)
  • Returns β€” none
  • Args β€” boolean: keep existing parameter values

outfile_name

  • Title β€” outfile_name
  • Usage β€” my $outfile = $hyphy->outfile_name();
  • Function β€” Get/Set the name of the output file for this run (if you wanted to do something special)
  • Returns β€” string
  • Args β€” [optional] string to set value to

version

  • Title β€” version
  • Usage β€” $obj->version()
  • Function β€” Returns the version string from HYPHY
  • Returns β€” string
  • Args β€” none

hyphy_lib_dir

  • Title β€” hyphy_lib_dir
  • Usage β€” $obj->hyphy_lib_dir()
  • Function β€” Returns the HYPHY_LIB_DIRECTORY from HYPHY
  • Returns β€” string
  • Args β€” none

and that's the whole page bestie πŸ’œ it went out with perl v5.36.0 dated 2023-01-22, under the manual name Bio::T...y::Base(3pm) πŸŽ€ go forth and wrap some HyPhy, you absolute main character πŸ‘‘βœ¨

πŸ“¦ where this page comes from