GFFUTILS-CLI_PARENTS(1)

πŸ’– GFFUTILS-CLI_PARENTS πŸ’–

okay bestie, welcome to gffutils-cli_parents from the gffutils-cli manual β€” it's the little tool that goes digging in your database to fetch parents according to ID. no cap. let's get into it 🫢


✨ NAME ✨

gffutils-cli_parents β€” Fetch parents from the database according to ID


🌸 DESCRIPTION 🌸

here's the vibe:

usage: gffutils-cli parents [-h] [-l LIMIT] [--exclude EXCLUDE] [--exclude-self] db [ids]

Fetch parents from the database according to ID.

literally that's the whole job. it's giving "family reunion but for genomic features" πŸ’…

πŸŽ€ positional arguments:

  • db β€” the Database to use. but wait β€” if you hand it a GFF or GTF file instead for this argument, a database will be created for you. and bestie, that can take some time (several minutes), so it's best to create one ahead of time. don't say I didn't warn you 😭
  • ids β€” Comma-separated list of IDs. These IDs, along with their parents, will be returned (subject to --limit and --exclude). If none provided, use all exons in the database. default: -

πŸ‘‘ options:

  • -h, --help β€” show this help message and exit. the classic. iconic. never misses ✨
  • -l, --limit LIMIT β€” Feature type (string), or level (integer). No parents below this level will be returned. default: -
  • --exclude EXCLUDE β€” Comma-separated list of featuretypes to filter out (like grep -v). default: -
  • --exclude-self β€” Use this to suppress reporting the IDs you've provided. default: False. so like, if you don't want to see your own faves in the results, flip this on πŸ™ˆ

🫢 quick reminder: --limit and --exclude are literally doing the vibes-check on your results, and if you pass a raw GFF/GTF file as db you're gonna be waiting a while. make the database ahead of time, fr fr.

and that's the whole page, babe. this was gffutils-cli parents 0.14, from August 2026, living inside the GFFUTILS-CLI_PARENTS(1) manual. slay, go fetch those parents πŸ’–πŸŒˆβ­

πŸ“¦ where this page comes from