You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see from my CheckM & QUAST output that there are good quality METABAT2 bins, (results > GenomeBinning > QC > CheckM > checkm_summary.tsv), however my Genome Assembly > MetaBAT2 folder always only contains the unbinned and discard folders. Whereas the MaxBin2 folder contains unbinned, bins, and discarded. Here is an example of what I mean.
This happens with all the samples I ran so far. I’m using the tar.gz file from the 2.5.0 release.
Description of the bug
I can see from my CheckM & QUAST output that there are good quality METABAT2 bins, (
results > GenomeBinning > QC > CheckM > checkm_summary.tsv
), however myGenome Assembly > MetaBAT2
folder always only contains theunbinned
and discard folders. Whereas theMaxBin2
folder containsunbinned
,bins
, anddiscarded
. Here is an example of what I mean.This happens with all the samples I ran so far. I’m using the tar.gz file from the 2.5.0 release.
In other words, it’s not making this file:
bins/[assembler]-[binner]-[sample/group].*.fa.gz
nor thebins
folder underMetaBAT2
(https://nf-co.re/mag/2.5.0/docs/output#binning-and-binning-refinement)There might be an issue with "the glob pattern we use when 'publishing' the files".
Thank you!
Command used and terminal output
nextflow run main.nf -profile singularity -c copy_custom_res.conf --input group_samples_fastq_paths_sub.csv --outdir results_2 --email [my_email] --skip_spadeshybrid true --skip_megahit true --skip_concoct true --skip_prokka true --refine_bins_dastool false --binqc_tool checkm --skip_gtdbtk true --max_cpus 20 --max_memory 250.GB
Relevant files
No response
System information
Nextflow version 23.10.0, build 5889 (15-10-2023 15:07 UTC)
Hardware HTCondor
Local Executor
Container: Singularity
OS: Linux
nf-core/mag: 2.5.0 (https://github.com/nf-core/mag/releases/tag/2.5.0, downloaded the tar.gz file)
The text was updated successfully, but these errors were encountered: