Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about output content #492

Open
BOBOL513 opened this issue Mar 15, 2025 · 3 comments
Open

Question about output content #492

BOBOL513 opened this issue Mar 15, 2025 · 3 comments

Comments

@BOBOL513
Copy link

Hi , I'm new to abyss trying to use short-read genome data to build genome assembly. A test was run with one sample from HGSVC3 (about 40x), two illumina short reads fastq.gz files as input. And the question is how to explain that the output contigs.fasta only has about 3G base pairs? I thought it would produce a complete diploid genome assembly.

The command was something like :

abyss-pe name=***** k=96 B=100G in='/absolute_path/sample_1.fastq.gz /absolute_path/sample_2.fastq.gz' -C /absolute_path/abyss_workflow

Thanks for developing this tool and answering my questions

@jwcodee
Copy link
Member

jwcodee commented Mar 17, 2025

Thanks for using ABySS. I am assuming your sample is from a human individual. If so, 3Gbp would be the correct size of the genome that ABySS assembles. ABySS only assembles a pseudo haploid of your genomic data, and not a diploid genome.

@BOBOL513
Copy link
Author

Thanks for using ABySS. I am assuming your sample is from a human individual. If so, 3Gbp would be the correct size of the genome that ABySS assembles. ABySS only assembles a pseudo haploid of your genomic data, and not a diploid genome.

I see, also I want to konw how ABySS represent a heterozygous loci in the reported haploid assembly? Random selection of one allele should not make much difference for SNP and INDEL, but may generate very different assembly for structural variations.

@warrenlr
Copy link
Contributor

Assuming a diploid genome, for large SVs, it depends on paired end read support. Typically, one allele representation will be favoured over the other if it is strongly supported by read pairs (or there is no path for the other allele in the graph). When that is not the case, the assembly may break at those positions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants