-
Notifications
You must be signed in to change notification settings - Fork 21
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
confusion on the results of hapmers.sh #147
Comments
Hi @leon945945 , glad you are trying the hapmer script! Do you have the plot handy? Or the final .hist file? |
Hi @arangrhie , I get the final plot, I'm not clear with each filled region in the plot, and I want to understand why the read-only-kmers account for a large proportion. Looking forward to your reply. |
Curiously, how to understand the peak of the read-only-kmer ? |
That means the child read set has some kmers not found in either parent. The high peak in 1-copy kmer of the child-only kmers (at ~13x) is observed in cases where the parents are not the biological parents. Could be sample mis labeling. Or sequencing platform bias. Are the parents coming from illumina, the child from hifi kmers? If so, can you try again with k=31? |
Hi @arangrhie , I tried K=31, and the peak of the read-only-kmer becomes lower, and seems half of the previous result. If I want to drop error kmers, the kmer count below what number could be removed and use which command? Thanks very much. By the way, how the very high kmer count was generated, like kmer count over hundreds or thousands. Are these kmers errors? |
Following the advice of marbl/meryl#53 (comment), I tried
hapmers.sh
ofmerqury
, and I got the following results:According to the folder size of results, the read-only-kmers account a large proportion of progeny's kmers. Which means the origin of these DNA sequences are unknown.
In my opinion, the DNA of progeny should be inherited from mat or pat, why there exists a large proportion of unknown DNA sequences, and what is the probable reason?
Very hope for your reply. Thanks very much.
The text was updated successfully, but these errors were encountered: