Bio::SeqIO::kegg(3pm)

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

πŸ¦‹ Bio::SeqIO::kegg πŸ¦‹

okay so bestie, you found Bio::SeqIO::kegg(3pm) β€” it's part of the User Contributed Perl Documentation and it's literally the KEGG sequence input/output stream. let's get into it πŸ’…


✨ NAME ✨

Bio::SeqIO::kegg β€” KEGG sequence input/output stream 🌸


πŸŽ€ SYNOPSIS πŸŽ€

ngl, it's probably best not to use this object directly, but rather go through the SeqIO handler system. so do this:
use Bio::SeqIO;

$stream = Bio::SeqIO->new(-file => $filename, -format => 'KEGG');

while ( my $seq = $stream->next_seq() ) {
      # do something with $seq
}

πŸ’– DESCRIPTION πŸ’–

this class transforms KEGG gene records into Bio::Seq objects. periodt.

🌈 Mapping of record properties to object properties 🌈

this section is supposed to document which sections and properties of a KEGG databank record end up where in the Bioperl object model. it is far from complete and presently focuses only on those mappings which may be non-obvious. $seq in the text refers to the Bio::Seq::RichSeqI implementing object returned by the parser for each record. iykyk 🫢

  • 'ENTRY' β€” maps to $seq->primary_id
  • 'NAME' β€” maps to $seq->display_id
  • 'DEFINITION' β€” maps to $seq->annotation->get_Annotations('description');
  • 'ORTHOLOG' β€” maps to grep {$_->database eq 'KO'} $seq->annotation->get_Annotations('dblink')
  • 'CLASS' β€” maps to:
grep {$_->database eq 'PATH'}
         $seq->annotation->get_Annotations('dblink')
  • 'POSITION' β€” FIXME, NOT IMPLEMENTED 😭
  • 'PATHWAY' β€” maps to:
for my $pathway ( $seq->annotation->get_Annotations('pathway') ) {
   #
}
  • 'DBLINKS' β€” maps to $seq->annotation->get_Annotations('dblink')
  • 'CODON_USAGE' β€” FIXME, NOT IMPLEMENTED 😭
  • 'AASEQ' β€” maps to $seq->translate->seq
  • 'NTSEQ' β€” maps to $seq->seq

πŸ’Œ 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 one of the Bioperl mailing lists. 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. many experienced and reponsive 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. the more deets the better bestie πŸ’œ

πŸ› Reporting Bugs πŸ›

report bugs to the Bioperl bug tracking system to help us keep track the bugs and their resolution. bug reports can be submitted via the web:

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

πŸ‘‘ AUTHOR - Allen Day πŸ‘‘

Email allenday@ucla.edu ✨


πŸ“Ž APPENDIX πŸ“Ž

the rest of the documentation details each of the object methods. internal methods are usually preceded with a _ πŸ’€

⭐ next_seq ⭐

  • Title : next_seq
  • Usage : $seq = $stream->next_seq()
  • Function: returns the next sequence in the stream
  • Returns : Bio::Seq::RichSeq object
  • Args :

🌸 write_seq 🌸

  • Title : write_seq
  • Note : write_seq() is not implemented for KEGG format output. so don't come for me, it's just not a thing πŸ™ˆ

and that's the whole vibe, bestie πŸŽ€ this was perl v5.32.1, dated 2021-08-15, and that's a wrap β€” slay, go parse some KEGG records πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from