Toolbar

Summary

Bio::EnsEMBL::Funcgen::Parsers::GFF

Package variables

Included modules

Inherit

Bio::EnsEMBL::Funcgen::Parsers::Simple

Synopsis

  my $parser_type = "Bio::EnsEMBL::Funcgen::Parsers::GFF";
  push @INC, $parser_type;
  my $imp = $class->SUPER::new(@_);

Description

This is a definitions class which should not be instatiated directly, it
normally set by the Importer as the parent class. GFF contains meta
data and methods specific to data in bed format, to aid
parsing and importing of experimental data.

Methods

Methods description

  Example    : my $self = $class->SUPER::new(@_);
  Description: Constructor method for GFF class
  Returntype : Bio::EnsEMBL::Funcgen::Parsers::GFF
  Exceptions : None
  Caller     : Bio::EnsEMBL::Funcgen::Importer
  Status     : at risk

  Example    : my $self->set_config;
  Description: Sets attribute dependent config
  Returntype : None
  Exceptions : None
  Caller     : Bio::EnsEMBL::Funcgen::Importer
  Status     : at risk

Methods code

sub new {

  my $caller = shift;
  
  my $class = ref($caller) || $caller;

  #define default fields here and pass
  #We also need to be able to take custom attrs mappings

  #keys are array index of field, key are Feature paramter names
  #reverse this?
  #Unless we have a compound field which we name accordingly
  #And then call e.g. parse_attrs
  #Which will return a hash with the relevant Feature attributes

  #Is splitting this up simply going to make the parse slower due to acessor methods?

  #Pass or just set directly here?
  #<seqname> <source> <feature> <start> <end> <score> <strand> <frame> [attributes] [comments]


  #Some of these may be highly redundant due to the nature of the data.
  #We can hash things to lessen the impact but we're still going to be checking if exists for each one
  #No way around this?  Unless it is marginally faster to set a permanent type and then only check a boolean.
  #Yes there is, this is the exhaustive GFF definition, we can just redefine or delete some entries dynamically to
  #avoid ever considering a particular field index.


  #Don't need any of this? Can we simply define process fields?
  #This will remove the ability to define custom formats
  #But then again we can only have custom format if it has ensembl compliant data
  #i.e. no preprocessing has to be done before populating the feature_params hash

  #my %fields = (
#				0 => 'fetch_slice',
#				1 => 'get_source',
#				2 => 'get_feature_type',
#				3 => '-start',
	#			4 => '-end',
#				5 => '-strand',#Will most likely be , need to convert to -.+ > -1 0 1
				#6 => 'frame',#will most likely be .
#				7 => 'get_attributes',
#			   );

  #We want to be able to define mappings between attributes and fields
  #we're basically just dealing with display_label for annotated_feature
  #e.g -display_label_format => ID+ACC
  #Or maybe format of several fields and attrs + text?
  #We need a separator which will not be used in the GFF attr names
  #we also need to be able to differentiate
  #First check standard GFF field, then check attrs
  ##No no no, just have method, generate display label
  #forget this for now and just use one field

  my $display_label_field = 'ID';#default

  #We still need to define the field name here as a global hash to allow this display_label_field look up.


  my $self  = $class->SUPER::new(@_);#, -fields => \%fields);
  
  ($display_label_field) = rearrange(['DISPLAY_LABEL_FIELD'], @_);

  #We need to define meta header method, starting with '##'
  #Also need to skip comments '#' at begining or end of line
  #Do we also need to skip field header? No methinks not.

  #Define result method
 # $self->{'file_ext'} => 'gff';#Could use vendor here?
  
  #define this if we want to override the generic method in Simple
  #$self->{'config'}{'results_data'} => ["and_import_gff"];  

  $self->display_label_field($display_label_field);


  return $self;

}

sub process_line {

  my ($self, $line) = @_;

  #return if $line ~=

 #my %fields = (
#				0 => 'fetch_slice',
#				1 => 'get_source',
#				2 => 'get_feature_type',
#				3 => '-start',
	#			4 => '-end',
#				5 => '-strand',#Will most likely be , need to convert to -.+ > -1 0 1
				#6 => 'frame',#will most likely be .
#				7 => 'get_attributes',
#			   );



  my ($chr, $start, $end, $pid, $score) = split/\t/o, $line;			
  
  #we need to return feature_params and seq if defined?

}
 


1;

}

sub set_config {

  my $self = shift;

  $self->SUPER::set_config;

  #GFF specific stuff here.

  return;

}

General documentation

This module was created by Nathan Johnson.

Post questions to the EnsEMBL development list ensembl-dev@ebi.ac.uk