Bio::Cluster
ClusterFactory
Toolbar
Summary
Bio::Cluster::ClusterFactory - Instantiates a new Bio::ClusterI (or derived class) through a factory
Package variables
No package variables defined.
Included modules
Inherit
Synopsis
use Bio::Cluster::ClusterFactory;
# if you don't provide a default type, the factory will try
# some guesswork based on display_id and namespace
my $factory = new Bio::Cluster::ClusterFactory(-type => 'Bio::Cluster::UniGene');
my $clu = $factory->create_object(-description => 'NAT',
-display_id => 'Hs.2');
Description
Methods
Methods description
Title : _guess_type Usage : Function: Guesses the right type of Bio::ClusterI implementation based on initialization parameters for the prospective object. Example : Returns : the type (a string, the module name) Args : initialization parameters to be passed to the prospective cluster object |
Title : create_object Usage : my $seq = $factory->create_object(<named parameters>); Function: Instantiates new Bio::ClusterI (or one of its child classes)
This object allows us to genericize the instantiation of
cluster objects.
Returns : Bio::ClusterI compliant object The return type is configurable using new(-type =>"..."). Args : initialization parameters specific to the type of cluster object we want. Typically -display_id => $name -description => description of the cluster -members => arrayref, members of the cluster |
Title : new Usage : my $obj = new Bio::Cluster::ClusterFactory(); Function: Builds a new Bio::Cluster::ClusterFactory object Returns : Bio::Cluster::ClusterFactory Args : -type => string, name of a ClusterI derived class. If not provided, the factory will have to guess from ID and namespace, which may or may not be successful. |
Title : type Usage : $obj->type($newval) Function: Get/set the type of Bio::ClusterI object to be created.
This may be changed at any time during the lifetime of this
factory.
Returns : value of type
Args : newvalue (optional) |
Methods code
sub _guess_type
{ my ($self,@args) = @_;
my $type;
my ($dispid, $ns, $members) =
$self->_rearrange([qw(DISPLAY_ID
NAMESPACE
MEMBERS
)], @args);
if($ns && (lc($ns) eq "unigene")) {
$type = 'Bio::Cluster::UniGene';
} elsif($dispid && ($dispid =~ /^Hs\.[0-9]/)) {
$type = 'Bio::Cluster::UniGene';
}
return $type;
}
*create =\& create_object;
1; } |
sub create_object
{ my ($self,@args) = @_;
my $type = $self->type();
if(! $type) {
$type = $self->_guess_type(@args);
if(! $type) {
$self->throw("No cluster type set and unable to guess.");
}
if(! $self->{'_loaded_types'}->{$type}) {
eval {
$self->_load_module($type);
$self->{'_loaded_types'}->{$type} = 1;
};
if($@) {
$self->throw("Bio::ClusterI implementation $type ".
"failed to load: ".$@);
}
}
}
return $type->new(-verbose => $self->verbose, @args); } |
sub new
{ my($class,@args) = @_;
my $self = $class->SUPER::new(@args);
my ($type) = $self->_rearrange([qw(TYPE)], @args);
$self->{'_loaded_types'} = {};
$self->type($type) if $type;
return $self; } |
sub type
{ my $self = shift;
if(@_) {
my $type = shift;
if($type && (! $self->{'_loaded_types'}->{$type})) {
eval {
$self->_load_module($type);
};
if( $@ ) {
$self->throw("Cluster implementation '$type' failed to load: ".
$@);
}
my $a = bless {},$type;
if( ! $a->isa('Bio::ClusterI') ) {
$self->throw("'$type' does not implement Bio::ClusterI. ".
"Too bad.");
}
$self->{'_loaded_types'}->{$type} = 1;
}
return $self->{'type'} = $type;
}
return $self->{'type'}; } |
General documentation
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/MailList.shtml - About the mailing lists
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
email or the web:
bioperl-bugs@bioperl.org
http://bugzilla.bioperl.org/
Email hlapp at gmx.net
This is mostly copy-and-paste with subsequent adaptation from
Bio::Seq::SeqFactory by Jason Stajich. Most credits should in fact go
to him.
The rest of the documentation details each of the object methods.
Internal methods are usually preceded with a _