BP_UNFLATTEN_SEQ(1p)

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

πŸ’– NAME πŸ’–

okay so bestie, this is bp_unflatten_seq β€” it takes a genbank or genbank-style feature file and unflattens it into a nested SeqFeature hierarchy. glow-up for your features fr fr πŸ¦‹

(and yeah, the manual page itself is BP_UNFLATTEN_SEQ(1p), User Contributed Perl Documentation, iykyk ✨)


🌸 SYNOPSIS 🌸

bp_unflatten_seq.PLS -e 3 -gff ~/cvs/bioperl-live/t/data/AE003644_Adh-genomic.gb

bp_unflatten_seq.PLS --detail ~/cvs/bioperl-live/t/data/AE003644_Adh-genomic.gb

bp_unflatten_seq.PLS -i foo.embl --from embl --to chadoxml -o out.chado.xml

bp_unflatten_seq.PLS --notypemap --detail --to asciitree -ethresh 2 AE003644_Adh-genomic.gb

✨ DESCRIPTION ✨

So this script will unflatten a genbank or genbank-style file of SeqFeatures into a nested hierarchy. periodt.

See Bio::SeqFeature::Tools::Unflattener πŸ’…

Here's the tea: in a GenBank/EMBL representation, features are 'flat' β€” like, there is literally no link between an mRNA and a CDS, other than implicit links (eg via tags or via splice site coordinates) which may be hard to code for. it's giving unlabeled group chat 😭

This is most easily illustrated with the default output format, asciitree.

An unflattened genbank feature set may look like this (AB077698):

Seq: AB077698
  databank_entry                                   1..2701[+]
  gene
    mRNA
      CDS hCHCR-G                                  80..1144[+]
      exon                                         80..1144[+]
    five_prime_UTR                                 1..79[+]
    located_sequence_feature                       137..196[+]
    located_sequence_feature                       239..292[+]
    located_sequence_feature                       617..676[+]
    located_sequence_feature                       725..778[+]
    three_prime_UTR                                1145..2659[+]
    polyA_site                                     1606..1606[+]
    polyA_site                                     2660..2660[+]

Or like this (portion of AE003734):

gene
  mRNA CG3320-RA
    CDS CG3320-PA                                53126..54971[-]
    exon                                         52204..53323[-]
    exon                                         53404..53631[-]
    exon                                         53688..53735[-]
    exon                                         53798..53918[-]
    exon                                         54949..55287[-]
  mRNA CG3320-RB
    CDS CG3320-PB                                53383..54971[-]
    exon                                         52204..53631[-]
    exon                                         53688..53735[-]
    exon                                         53798..53918[-]
    exon                                         54949..55287[-]

The unflattening will also 'normalize' the containment hierarchy (in the sense of standardising it β€” e.g. making sure there is always a transcript record, even if genbank just specifies CDS and gene). lowkey the most responsible friend in the group 🫢

By default, the GenBank types will be mapped to SO types ✨

See Bio::SeqFeature::Tools::TypeMapper


πŸŽ€ COMMAND LINE ARGUMENTS πŸŽ€

  • -i|input FILE β€” input file (can also be specified as last argument)
  • -from FORMAT β€” input format (defaults to genbank)

probably doesn't make so much sense to use this for non-flat formats; ie other than embl/genbank

  • -to FORMAT β€” output format (defaults to asciitree)

should really be a format that is nested SeqFeature aware; I think this is only asciitree, chadoxml and gff3

  • -gff β€” with export to GFF3 format (pre-3 GFFs make no sense with unflattened sequences, as they have no set way of representing feature graphs)
  • -o|output FILE β€” outfile defaults to STDOUT
  • -detail β€” show extra detail on features (asciitree mode only)
  • -e|ethresh INT β€” sets the error threshold on unflattening

by default this script will throw a wobbly if it encounters weird stuff in the genbank file β€” raise the error threshold to signal these to be ignored (and reported on STDERR)

  • -nomagic β€” suppress use_magic in unflattening (see Bio::SeqFeature::Tools::Unflattener)
  • -notypemap β€” suppress type mapping (see Bio::SeqFeature::Tools::TypeMapper)

πŸ‘‘ TODO πŸ‘‘

Bio::SeqFeature::Tools::Unflattener allows fine-grained control over the unflattening process β€” need to add more options to allow this control at the command line. not me noticing a whole to-do list bestie πŸ™ˆ


πŸ’¬ 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. fr fr, they want your thoughts 🫢

bioperl-l@bioperl.org                  - General discussion
http://bioperl.org/wiki/Mailing_lists  - About the mailing lists

πŸ› 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 email or the web:

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

🌟 AUTHOR 🌟

Chris Mungall E<lt>cjm-at-bioperl.orgE<gt> β€” icon, legend, the moment πŸ’…


and that's the whole page bestie!! πŸ’– this was perl v5.32.1, dated 2021-08-15, BP_UNFLATTEN_SEQ(1p) β€” go unflatten something gorgeous, ily, bye πŸ¦‹βœ¨πŸŽ€

πŸ“¦ where this page comes from