EukCC
EukCC is a completeness and contamination estimator for metagenomic assembled microbial eukaryotic genomes.
Documentation
Head over to https://eukcc.readthedocs.io/ to check out the documentation.
Run
Download EukCC2 database from FTP
# create a folder were to keep the database
mkdir eukccdb
cd eukccdb
wget http://ftp.ebi.ac.uk/pub/databases/metagenomics/eukcc/eukcc2_db_ver_1.2.tar.gz
tar -xzvf eukcc2_db_ver_1.2.tar.gz
export EUKCC2_DB=$(realpath eukcc2_db_ver_1.2)
Quickstart using container
Get EukCC quickly by fetching the container.
The container is hosted and automatically build from the master branch here: https://quay.io/repository/microbiome-informatics/eukcc
docker pull quay.io/microbiome-informatics/eukcc
singularity pull docker://quay.io/microbiome-informatics/eukcc
Bioconda / pip
Alternatively you can install EukCC using conda or pip.
In addition, you need to install mandatory requirements:
- metaeuk=4.a0f584d
- pplacer
- epa-ng=0.3.8
- hmmer=3.3
- minimap2
- bwa
- samtools
Outputs explanation
eukcc.log- log of execution
eukcc single
eukcc.tsv- table with estimated completeness, contamination and taxonomy lineage
eukcc folder
eukcc.tsv- table with estimated completeness, contamination and taxonomy lineage for good quality binsmerged_bins.csv- table of merged refined binsbad_quality.csv- table with estimated completeness, contamination and taxonomy lineage for bad quality bins (chosen marker gene set is supported by less than half of the alignments)missing_marker_genes.txt- line separated list of bins with not defined set of marker genesmerged_bins- folder with merged bins sequencesrefine_workdir- working directory with intermediate steps results
Don't use EukCC on already pubished data
Or at least not without thinking about it:
You should not use EukCC on already published genomes, if they have used during training of the marker
gene sets. If you want to make sure, you can see all used accessions in the database file db_base/backbone/base_taxinfo.csv.
Cite
If you use EukCC make sure to cite:
Saary, Paul, Alex L. Mitchell, and Robert D. Finn.
"Estimating the quality of eukaryotic genomes recovered from metagenomic analysis with EukCC."
Genome biology 21.1 (2020): 1-21.
EukCC also uses metaEUK, hmmer, pplacer, ete3 and epa-ng.
Changed compared to EukCC 1
Note: With version 2, EukCC should provide a better experience than version 1. Version 2 is not compatible with previous versions, most commandline arguments changed. So version 2 is not a drop in replacement.
- Users can set the prevalence threshold for marker sets. In EukCC 1 this was fixed to 98% single copy prevalence. Now users could change that to be more strict. We find that often 100% single copy prevalence can be found.
Issues and bugs
Please report any bugs and issues here on GitHub. Make sure to
include the debug log (run eukcc using --debug flag).
used exit codes
- 200: File not found
- 201: No Marker gene set could be defined
- 202: No database provided
- 203: Corrupted file
- 204: Predicted zero proteins
- 222: Invalid settings
Metadata
Release files for eukcc 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| eukcc-2.2.0.tar.gz | 57.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eukcc-2.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 109.1 kB
Release files / eukcc-2.2.0.tar.gz
| Download URL | eukcc-2.2.0.tar.gz |
|---|---|
| Size | 57.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2cf505b3e32f7e3957273284bfbfca7a2e7d9590b1173af3d421bc4f585990a3
|
|
BLAKE2b-256 checksum How to use checksums |
4063720c53930fc58f26992d81a132a96c480a777f67594974d3edd3852fbb3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 14, 2026.
Transparency logRelease files / eukcc-2.2.0-py3-none-any.whl
| Download URL | eukcc-2.2.0-py3-none-any.whl |
|---|---|
| Size | 52.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9fbf56f5660b21b1112bbe75653c5acd456bfbf2446c585fdd15cb040d109e0
|
|
BLAKE2b-256 checksum How to use checksums |
22ef581e472decca5135ce471582b2cf67e1a1e07f8f4594410d3c90d215a958
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 14, 2026.
Transparency log