amyg: A Pipeline for De Novo Genomic Annotation of Non-Model Organisms
amyg is a Python-based annotation pipeline that aims to annotate a de novo sequenced genomes (draft or complete) using RNA-seq evidence. Currently the pipeline:
- Performs GTF processing from StringTie outputs
- Generates gene annotation using GAWN with SwissProt/BLAST integration
- Resolve transcriptome coding potential with TransDecoder, producing longest ORFs, CDS, and peptide sequences for each transcript.
Currently, the pipeline can run through:
- Conda (an environment called
annotate_envwill be created in your system) - Docker (with an auto-built image
myorg/annotate_env:latest)
Synopsis
amyg --help
usage: amyg [-h] [--install {conda,docker}] [--use_conda] [--use_docker] [--threads THREADS] [--force] [--purge_all_envs] [--dups]
[--chunk_size CHUNK_SIZE] [-o OUTPUT] [-a A] [-g G] [--preprocessing] [--egap_gtf EGAP_GTF]
annotation pipeline that aims to annotate a de novo sequenced genome using RNA-seq plus optional synteny BLAST for duplicates.
optional arguments:
-h, --help show this help message and exit
--install {conda,docker}
Install environment and exit.
--use_conda Run commands in conda env
--use_docker Run commands in docker image
--threads THREADS Number of CPUs (NCPUs) for gawn_config.sh
--force Overwrite database and gawn_config.sh if present
--purge_all_envs Remove the conda env and docker image, then exit.
--dups Enable chunk-based synteny BLAST to find duplicates (will run amyg_syntenyblast.py).
--chunk_size CHUNK_SIZE
Chunk size for synteny-based duplication step (only used if --dups is enabled).
-o OUTPUT, --output OUTPUT
Output directory (must exist)
-a A StringTie GTF
-g G Reference genome (in fasta format)
--preprocessing Preprocess GTF using unique_gene_id.py. If --egap_gtf is also provided, then also run merge_stringtie_names.py.
--egap_gff EGAP_GFF EGAP GFF for merging (only used if --preprocessing is true).
amyg is the next version of annotate_my_genomes but streamlines the installation and there is no need for separate config files.
Installation
Via pip:
pip install amyg
Then, users can decide to install all requirements via conda or docker as follows:
# 1) Install conda environment:
amyg --install conda
# 2) Install docker image:
amyg --install docker
# 3) Uninstall and purge old envs (optional):
amyg --purge_all_envs
- While Conda is faster, Docker image takes ~47.8 min to build in Ubuntu 24.04.1 LTS. We aimed to create a reproducible and robust local Docker image. Apologies for the delay.
Run
Currently there are two ways to run the pipeline:
1) Docker Mode
mkdir test_docker
amyg \
-a /path/to/my_genome.gtf \
-g /path/to/my_genome.fasta \
-o ./test_docker \
--threads 25 \
--use_docker \
--force
--threads 25sets number of cpus (NCPUs) for BLAST-based GAWN annotation.- The output is placed in
./test_docker. The main results of the pipeline will be inside i.e:./test_docker/amyg_20250101_150629/final_results/
2) Conda Mode
mkdir test_conda
amyg \
-a /path/to/my_genome.gtf \
-g /path/to/my_genome.fasta \
-o ./test_conda \
--threads 25 \
--use_conda \
--force
- The output is placed in
./test_conda. The main results of the pipeline will be inside i.e:./test_conda/amyg_20250101_150629/final_results/
Notes:
- Ctrl+C kills all running Docker containers, ensuring no stuck processes.
--forceoverwrites existing database/ and gawn_config.sh if they are in the output folder. We reccomend to run the pipeline fresh using this flag.
Detailed Steps
-
Download SwissProt
- Automatically fetches
swissprot.tar.gzfrom the NCBI BLAST FTP server and unpacks it into thedatabase/folder.
- Automatically fetches
-
Create
gawn_config.sh- Docker mode sets
SWISSPROT_DBto/data/database/swissprot. - Conda mode copies SwissProt into
gawn/03_dataand setsSWISSPROT_DBto03_data/swissprot.
- Docker mode sets
-
Run GAWN
- BLAST progress is monitored every 60 seconds, logging how many lines appear in
transcriptome.swissprot.
- BLAST progress is monitored every 60 seconds, logging how many lines appear in
-
TransDecoder
- Discovers longest ORFs and predicts coding regions.
-
Annotate GTF
- Downloads
annotate_gtf.pyand merges final hits intofinal_annotated.gtf. - Outputs organized to
final_results/, with any remaining TransDecoder files moved totransdecoder_results/.
- Downloads
-
Usage with Optional
--dups--dups enables chunk-based synteny BLAST viaamyg_syntenyblast.pyto identify potential duplicated regions. --chunk_size controls the size of each FASTA split for BLAST runs when --dups is used.
Organizes final results in final_results/ subfolder and leftover TransDecoder outputs in transdecoder_results/.
Preprocessing your stringtie.gtf using --preprocessing flag
Sometimes you need to clean or prepare your GTF file before running the main annotation pipeline. The --preprocessing flag lets you do just that. Here's what it does in detail:
- (Recommended) Run
unique_gene_id.py
This script ensures all gene_id fields in your GTF are truly unique. For any conflicting gene_ids (e.g., multiple transcripts with the same gene_name), it automatically appends a suffix to avoid collisions.
The output is a new GTF (e.g., mygtf.gtf => mygtf.unique_gene_id.gtf).
- (Optional, but recommended) Run
merge_stringtie_names.pywith--egap_gff(NCBI Eukaryotic Genome Annotation Pipeline gff)
If you have the NCBI Eukaryotic Genome Annotation Pipeline gff of your genome and provide --egap_gff /path/to/genome.gff, the pipeline automatically downloads and runs the merge_stringtie_names.py script.
That script further refines your GTF by comparing it to the reference (the “EGAP GFF”), ensuring consistent naming of transcripts and unifying gene_id vs. gene_name across transcripts and exons.
The final result is a new file (by default named annotated_and_renamed.gtf), which can then be used in the main amyg pipeline.
1) If you just want to unique‐ify your gene IDs:
amyg --preprocessing -a /path/to/mygtf.gtf
2) If you also want to merge your GTF with an EGAP reference for consistent naming:
amyg --preprocessing \
-a /path/to/mygtf.gtf \
--egap_gtf /path/to/genomic.gff
transcripts_named.gtf will be produced, that can be input for amyg pipeline
Interested in genome-wide duplications? please run with --dups flag
1) Docker Mode
mkdir test_docker
amyg \
-a /path/to/my_genome.gtf \
-g /path/to/my_genome.fasta \
-o ./test_docker \
--threads 25 \
--use_docker \
--force \
--dups \
--chunk_size 20000
2) Conda Mode
mkdir test_conda
amyg \
-a /path/to/my_genome.gtf \
-g /path/to/my_genome.fasta \
-o ./test_conda \
--threads 25 \
--use_conda \
--force \
--dups \
--chunk_size 20000
- Enabling
--dupsflag will also enable--chunk_sizethat will slice the genome (default at 20000 bp) and will test synteny comparing all fragments vs all, and at the end will reconstruct genomic segment with strong duplication evidence across the genome. Also, it will producefinal_annotated_dups.gtfwhich contains the annotation of duplicated genes on thefinal_annotated.gtffile - The results of the pipeline will be inside i.e:
./output_folder/amyg_20250101_150629/final_results/
Plot duplications
- Inside i.e.:
amyg_20250101_150629/final_resultsusers can do the following
wget https://raw.githubusercontent.com/cfarkas/amyg/refs/heads/main/scripts/plot_dups.py
chmod 755 plot_dups.py
python plot_dups.py \
-a transcriptome_annotation_table.tsv \
-g final_annotated_dups.gtf \
-s synteny_blocks.csv \
-o ./
This script will produce two stacked bar plots.
Plot A:
- Sorted contigs with percentage of Ancient (green), Recent (orange), Other (gray) genes
Plot B:
- Classify all duplications (either “ancient” or “recent”) as:
- "intra-only" (blue) if contig is found ONLY in self-synteny blocks
- "inter-only" (red) if contig is found ONLY in cross-synteny blocks
- "both" (black) if contig is found in both self- & cross-synteny
- "other" (gray) if duplication_type ∉ {ancient,recent} OR contig not found in synteny at all So the bar shows how we partition the entire set of duplicated genes among (intra-only, inter-only, both).
Requirements
- Python 3.7+
- Miniconda or Docker installed on your system
- Enough disk space for BLAST DB and GTF/FASTA inputs
Troubleshooting
Ctrl+C in the middle of a run Kills Docker containers so you don’t have to manually do it.
Permission
Make sure you have write access to your output directory and local Docker permissions.
License
This project is licensed under the MIT License.
Metadata
Release files for amyg 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| amyg-0.1.7.tar.gz | 16.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| amyg-0.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.9 kB
Release files / amyg-0.1.7.tar.gz
| Download URL | amyg-0.1.7.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0f295d80a2f9b8eae5c4056a4dbf306f3aaef5a2ba0abb47d84c4d48f142e2dd
|
|
BLAKE2b-256 checksum How to use checksums |
dfef31187526dc66f552d9a43240efd0f66fcc3bc4057f6e59cb3e7c4808d534
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.7
|
Release files / amyg-0.1.7-py3-none-any.whl
| Download URL | amyg-0.1.7-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3fc17aab426b001bb58da8911c81bd7e667d82cc0d86ffd3ac85eda18f9c74c
|
|
BLAKE2b-256 checksum How to use checksums |
b7447ad4f21707aa9c7424603b6a2b0b5cf7f4a7c493d1ccd9dc4656f9f50947
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.7
|
Security for amyg 0.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.