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've had great usage of this pipeline on my isolates. But one isolate sample seems to always return a 11Mbp genome on assembly where a typical P.protegens genome size of ~6.5Mbp is expected. So I tried to run
But it still returns the same size genome.
Checkm indicated there's some (5.43%) contamination and both Kmer and Kaiju queries on the fastq.gz reads shows a near full hit (70%) matching P.protegens, with some Citrobacter spp sprinkled in.
It seem max_genome_size doesn't affect the assembly, or perhaps I'm not using it properly?
Any advice would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I'm still getting a 11Mbp genome from what I expected to be no larger than 6-7Mbps.
I ran bactopia --r1 B_1.fastq.gz --r2 B_2.fastq.gz --sample sample_Pprotegens_v3 --species "Pseudomonas protegens" --genome_size 6000000 --max_genome_size 8000000 --outdir bactopia_out/
I'm pretty certain it's my sample that's causing the problem, since SPADES gives a similar genome.
I've had great usage of this pipeline on my isolates. But one isolate sample seems to always return a 11Mbp genome on assembly where a typical P.protegens genome size of ~6.5Mbp is expected. So I tried to run
bactopia --R1 B_1.fastq.gz --R2 B_2.fastq.gz --sample sample --species "Pseudomonas protegens" --genome_size median --max_genome_size 7000000 --min_coverage 100 --datasets datasets --outdir out/
But it still returns the same size genome.
Checkm indicated there's some (5.43%) contamination and both Kmer and Kaiju queries on the fastq.gz reads shows a near full hit (70%) matching P.protegens, with some Citrobacter spp sprinkled in.
It seem
max_genome_size
doesn't affect the assembly, or perhaps I'm not using it properly?Any advice would be greatly appreciated.
The text was updated successfully, but these errors were encountered: